When generating an ASC X12 file, MapForce may automatically create certain fields or values, according to the rules below (subsequently referred to as "automatic data completion", or "auto-completion" rules). To disable this behavior, clear the Auto-complete missing fields check box in EDI Component Settings.
Automatic data completion for EDI/X12 makes sure:
•That an ISA and IEA pair exist on the interchange level.
•That if either GS or GE exist, the other ID also exists.
•That there is at least one ST/SE pair on the message level.
•That ISA/I01 and ISA/I03 exist. If they do not contain data, 00 is inserted.
•That ISA/I02 and ISA/I04 exist. If they do not contain data, ten blanks are inserted.
•That both ISA/I05 segments exist. If they do not contain data, ZZ is inserted.
•That ISA/I08 exists. If it does not contain data, the current date in EDI format is inserted.
•That ISA/I09 exists. If it does not contain data, the current time in EDI format is inserted.
•That ISA/I65 exists. If it does not contain data, the repetition separator is inserted.
• That ISA/I11 exists. If it does not contain data, the interchange control version number from the user-defined settings is inserted (see the setting Extended | Interchange control version-number of the EDI Component Settings).
•That ISA/I12 exists.
•That ISA/I13 exists. If it does not contain data, the request acknowledgment setting is used (see the setting Extended | Request Acknowledgement of the EDI Component Settings).
•That ISA/I14 exists. If it does not contain data, P is inserted.
•That ISA/I15 exists. If it does not contain data, the composite separator from the user-defined settings is inserted (see the setting Composite Separator of the EDI Component Settings)..
•That IEA/I16 exists. If it does not contain data, the number of function groups in the interchange is calculated and inserted.
•That IEA/I12 exists. If it does not contain data, the value from ISA/I12 is copied.
| Note: | Any fields not mentioned here are not inserted or created. The correct values cannot be ascertained automatically. Given a (target) parent element A (in the target EDI component) with child items x, y, and z - where y is mandatory, parent element A will only be created in the output file if the mandatory child element "y" in the target component has been mapped. |
The potentially existing function group is checked as follows:
•That GS/373 exists. If it does not contain data, the current date in EDI format is inserted.
•That GS/337 exists. If it does not contain data, the current time in EDI format is inserted.
•That GE/97 exists. If it does not contain data, the number of messages in the function group are calculated and inserted.
•That GE/28 exists. If it does not contain data, the value from GS/28 is copied.
Message checking makes sure:
•That ST/143 exists. If it does not contain data, the name of the message is inserted.
•That SE/96 exists. If it does not contain data, the number of segments in the message is calculated and inserted.
•That ST/329 and SE/329 exist. If SE/329 does not contain data, the value from ST/329 is copied.
