4 1 4 Trading Partner support for Transaction Document Processing

LANSA Composer

4.1.4 Trading Partner support for Transaction Document Processing

The transaction document processing framework, as supplied, makes significant use of Trading Partner definitions and features.  Both the inbound and outbound processes process transaction documents by Trading Partner, in the first place.

Amongst the base attributes for a trading partner are values that let you identify specific processing sequences to perform receive and send processing for that trading partner.  This optional feature provides additional flexibility for you to tailor your transport mechanisms to your particular trading relationships.  If specified, these processes are invoked from the standard "model" inbound and outbound processes.

Furthermore, Trading Partner definitions provide several crucial links:

  • To the directories used to hold the inbound or outbound transaction documents through the various stages of their processing (using the Linked Directories feature of a Trading Partner definition)
  • To the configurations used for transport and other activities that form part of the transaction document process (using the Linked Configurations feature of a Trading Partner definition)
  • To the Transformation Maps used to receive inbound transaction document data or prepare outbound transaction document data for a given document type, standard, transaction type and direction (using the Linked Maps feature of a Trading Partner definition)

 

In addition, the Trading Partner Data Interchange Attributes provide certain values that facilitate the recognition of the source and / or the target of certain transaction document types and specify aspects of how they are to be processed.