TXDOC_EXPORT

LANSA Composer

TXDOC_EXPORT

This activity exports transaction data for out-going transactions by executing the re-useable part specified as the export processor (the export processor is typically associated with the transformation map that will be used to transform the data to its out-going transaction document format).

Refer to the supplied processing sequence TXDOC_IEDI090 as an example of using this activity in the course of generating an outbound EDI X12 997 acknowledgement in response to an in-coming EDI document.

INPUT Parameters:

DOCEXPORTPROCESSOR : Required

This parameter specifies the name of the transaction data export processor component name.  This must be the name of a re-useable part derived from the supplied ancestor class DXXEXPBAS.  This component must be written to be capable of performing the required processing to export the transaction data identified by the transaction data identifiers, typically into staging files that will subsequently be used by the associated transformation map to create an outbound transaction document file containing the data.

DOCPRODTEST : Optional

This parameter specifies whether the transaction document will be for production (P) or test (T) use.  It is up to the specific export processor implementation how it makes use of this value - for EDI X12 transactions, it would typically be used to fill the ISA15 (use) field of the interchange header.

DOCDATAKEY1DOCDATAKEY2 : Optional

These parameters are used to identify to the export processor the set of transaction data to be exported.  For example, they may be used to identify a sales order, an invoice or another transaction document envelope to which this is generating a response or acknowledgement.  The meaning and interpretation of these values is up to the implementation of the particular export processor being used.  The values supplied must be appropriate for the use in that export processor.

OUTPUT Parameters:

DOCNUMBERLIST :

Upon successful completion, this will contain a list of one or more transaction document envelope numbers generated by the activity.