We are just now attempting to process inbound 997 transaction files through Mercator. Our files come from several different sources. Some are getting Red indicators (data type unknown) and others are getting geen indicators. We have been trying to find some common factors amongst the files that are failing, but have been unable to come up with any common characteristics. Does anyone know what Mercator actually requires of the input data on a 997 transactions?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Inbound 997 problems
- Thread starter evesyst
- Start date
- Thread starter
- #3
We are running 6.7, They are being run thru Message mgr.
Someone gave us some information today that may be a good lead. Many of the 997 files that are being dropped on our mainframe server are being dropped as fixed block and only having an lrecl of 80. The segment terminator defined in the ISA segment is in something like position 106... which is putting it in record #2. This particular source says that this is the main processing problem that we are having. He says that the files need to be dropped on our mainframe as either unblocked or variable blocked. We are experimenting with this currently.
If you have any other ideas, we would be glad to hear them too.
Someone gave us some information today that may be a good lead. Many of the 997 files that are being dropped on our mainframe server are being dropped as fixed block and only having an lrecl of 80. The segment terminator defined in the ISA segment is in something like position 106... which is putting it in record #2. This particular source says that this is the main processing problem that we are having. He says that the files need to be dropped on our mainframe as either unblocked or variable blocked. We are experimenting with this currently.
If you have any other ideas, we would be glad to hear them too.
BocaBurger
Vendor
How are you running Msg Mgr on Mainframe?
To debug, take input file and take x12mail tree and create validation map, turn on input trace and see why it is failing.
BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!
To debug, take input file and take x12mail tree and create validation map, turn on input trace and see why it is failing.
BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!
- Thread starter
- #5
Sounds like it's the fixed length issue. Good luck!
A validation map will catch that as part of a debug.
We have a similar issue with a TPA that refuses to send a valid X12 file. They put <NL> in records over 80 bytes. Goofy but they don't want to be considers a TPA for HIPAA so refuse to fix the problem. We've built a work-around.
eyetry
A validation map will catch that as part of a debug.
We have a similar issue with a TPA that refuses to send a valid X12 file. They put <NL> in records over 80 bytes. Goofy but they don't want to be considers a TPA for HIPAA so refuse to fix the problem. We've built a work-around.
eyetry
- Status
Similar threads
- Locked
- Question
- Locked
- Question