Input card details

The primary compliance check maps, cc12, ccrail, and ccedf take the input cards that are described in the following sections.

Card 1: EDI data
This is the input X12, RAIL, or EDIFACT interchange that is to be validated. It must be a single X12, RAIL, or EDIFACT interchange. Multiple interchanges in a single input card are not permitted. If the input contains multiple interchanges, you get the message “Input valid but unknown data found”, and only the first interchange is processed.
Card 2: unique ID
This string value specifies a unique ID that identifies the input interchange. For file output, this ID is included as part of the output file names to help link the acknowledgments, output transactions, and error logs to the original interchange.
Card 3: configuration information
This input card contains XML formatted data that describes processing options.
Card 4: duplicate interchange flag
The duplicate interchange flag is a flag that can be passed to indicate that the interchange is a duplicate.
Card 5: table data
This input card contains table data that is used to help validate restriction lists for X12, RAIL, and EDIFACT envelope segments.
Card 6: message code list
This input card contains the text for error messages that are written to the log file.
Card 7: structure detail file
This input file contains structure information about the expected order of the segments.
Card 8: system information file
The system information file, edicc.ini, defines system information.
Card 9: trace flag
If this is set to T or TU, the map writes an XML formatted trace file to the map directory.

Parent topic: Configuration