This section provides information about when the EDI Specification identifies multiple files.
If the EDI Specification identifies multiple files, then a separate specification is defined for each file and the processing for each file is completely separate from the others, but the source EDI file is processed in a single pass.
For example, if an EDI File is to generate a Product file and a SKU file, two EDI Target Files will be defined, and each will have a complete set of EDI Sections and EDI Fields. For the Product file, the EDI Section set to be the Is Output Row would be for the LIN data element (Example 5 above). Since the SKU data would not be stored, there would be no need to define any fields nor sections containing SKU data. For the SKU file, the first EDI section would be the LIN Data Element and its child section would be the SLN Data Element, which would be set to Is Output Row (Example 2 above). If consecutive LIN Data Elements are encountered (with no SLN Data Elements), then the Product data will not be saved to the SKU file. Anytime an SLN Data Element is encountered, then its data would be written the next time the next SLN, or LIN Data Element is encountered, or once the end of the file is reached.