The Inbound Process
Note 1: the following descriptions relate to the inbound processes as supplied with LANSA Composer. Naturally it does not take account of modifications that may have been made to suit a particular installation.
Note 2: you are strongly advised to make your own copies of the supplied Processing Sequences and use or modify the copies. For further information, please refer to Copy the Supplied Processing Sequences Before Use.
The supplied inbound process is designed to be modular - that is, it is broken down into more than one Processing Sequence with the main Processing Sequence calling the subsidiary Processing Sequences as required.
The main inbound Processing Sequence is:
|
TXDOC_INBOUND |
Processes inbound transaction documents |
This Processing Sequence can be run for one named Trading Partner, or for all eligible Trading Partners according to the value of the corresponding parameter. It performs the following main steps:
- Receives transaction document files from each Trading Partner
Receiving transaction document files is accomplished by calling a separate processing sequence, TXDOC_RCV. This processing sequence, as supplied, includes provision for executing processing sequences that are specific to one or more trading partners, providing the possibility of tailoring the inbound transport for each trading partner.
- For each transaction document file, TXDOC_INBOUND uses the DISCOVER_DOC Activity to determine the document type and then to call the inbound Processing Sequence associated with that document type.
LANSA Composer is supplied with inbound documents of types EDI and XML configured to be processed using the following Processing Sequences:
|
TXDOC_IEDI010 |
Processes inbound EDI transaction document files |
| TXDOC_IXML010 |
Processes inbound XML transaction document files |