EDI_SPLIT

This activity can split a composite EDI transaction document file into one or more EDI transaction documents each containing no more than the specified number of transactions.  This splitting can be important or necessary for two main reasons concerning further processing of the EDI transaction document:

• later standard LANSA Composer EDI document processing, such as the DISCOVER_EDI activity is founded on assumptions that the transactions contained in EDI document are for the same trading partner and/or are of the same EDI transaction type
• when very large EDI transaction documents are expected, splitting them into smaller documents optimizes their further processing, especially in any mapping steps.

INPUT Parameters:

EDIFILE: Required

This parameter specifies the path and name of the EDI transaction document file to be split.

EDILIMIT: Optional

This parameter specifies the maximum number of transactions to be contained in each of the resulting split EDI transaction documents.  If not specified, a default of 1 (one) is assumed.  The value for this parameter can be taken from the value specified for the exchange trading partner associated with the EDI transaction document file using the *tradingpartner.edi.splitmax built-in variable.

EDIIGNORECRLF: Optional

When Y (yes) is specified, carriage return / line feeds in the source EDI transaction document file are ignored when parsing the document.  If not specified, a default of N (no) is used.  The value for this parameter can be taken from the value specified for the exchange trading partner associated with the EDI transaction document file using the *tradingpartner.edi.splitignorecr built-in variable.

OUTPUT Parameters:

EDISPLITLIST:

Upon successful completion, this parameter will contain a list of the resulting EDI transactions documents.  The individual split documents in the list are typically further processed using the LOOP directive.