CardOutput
If the CardOutput element is specified, output is written to map output cards, and the PUT calls are skipped.
The following table describes which cards are used for each type output.
- Cards 1 - 4 continue to be used for internal processing, and output from these cards is not intended to be used by the map caller. These are used to gather information reported with the map trace Input card 9.
- By default, all the output cards in the following section are set to use the Sink adapter, so no physical output is generated for them. Although there is no physical output file to be downloaded with the Sink adapter, outputs may be viewed using the Design Server UI.
| Card number | Card name | Description |
|---|---|---|
|
5 |
ValidData |
X12 interchange that contains all valid and accepted transactions. This output is only produced if one or more valid transaction sets are present in the input data that is to be validated. |
| 6 | InvalidData |
X12 interchange that contains all invalid and rejected transactions and groups. This output is only produced if there are one or more invalid transaction sets or groups, or if the interchange header, or trailer errors are found in the input data that is validated. |
|
7 |
Error log |
Flat file that contains text descriptions of any errors that are detected, and where the errors are located. This output is only produced if there are one or more invalid transaction sets, or groups, or if the interchange header, or trailer errors are found in the input data that is to be validated. This information can also be parsed by use of a user application to reformat error information, if needed. |
|
8 |
AckIn |
X12 interchange that contains all inbound 997, or 999 transactions from the interchange. This output is only produced if the input data that is to be validated contains 997, or 999 acknowledgements. |
|
9 |
AckOut |
X12 Interchange containing generated 997 acknowledgments. This output is only produced if functional acknowledgment (997) transactions are generated for the input data that is to be validated. |
|
10 |
TA1In |
X12 interchange that contains all inbound TA1 acknowledgements from the interchange. This output is only produced if the input data that is to be validated contains TA1 acknowledgements. |
|
11 |
TA1Out |
X12 Interchange containing generated TA1 acknowledgments. This output is only produced if TA1 acknowledgements are generated for the input data that is to be validated. |
|
12 |
FrameworkTrace |
XML-formatted trace log for problem determination. This is only created if there are certain framework errors, or if the value T, or TU is specified for input card 9 (trace flag). |
|
13 |
JsonLog |
X12 JSON formatted report providing information related to the Interchange, Group, and Transaction errors and acknowledgments. |