Trading Partner Data Interchange Attributes
LANSA Composer defines and stores a set of data interchange attributes for each Trading Partner. These are defined to accommodate some of the attributes commonly used in EDI and other forms of data interchange.
While LANSA Composer pre-defines fields to hold these attributes, the program does not enforce the entry of the fields, nor does it validate values entered. To permit maximum implementation flexibility, LANSA Composer leaves the use and values of many of these attributes to you according to your own circumstances and conventions.
Some of the values are, however, important for the operation of the transaction document framework as supplied. These include:
|
Archive file prefix(inbound and outbound) |
These values determine the naming used when the inbound or outbound process archives a transaction document file that has been successfully processed. |
|
Inbound receiver id |
For an inbound EDI X12 transaction document file these values are matched against corresponding fields in the ISA segment of the EDI document. A successful match enables LANSA Composer to identify the Trading Partner definition to which the EDI transaction applies. |
|
Outbound receiver id |
For an outbound EDI X12 transaction document file these values are matched against corresponding fields in the ISA segment of the EDI document. A sucessful match enables LANSA Composer to identify the Trading Partner definition to which the EDI transaction applies. |
| EDI validation |
The DISCOVER_EDI activity, having matched the EDI transaction document to a Trading Partner, uses the value of this attribute for the Trading Partner to determine whether and how to perform EDI document validation. |
|
EDI split maximum transactions |
These values are passed to the EDI_SPLIT activity for an inbound EDI transaction document file to determine whether and how the transaction document file is split into multiple files containing a subset of the transactions in the original document. |
The trading partner data interchange attributes are used in the transaction document processing framework, or can be used in your own custom transaction document processing solution.
The attribute values are accessible within a processing sequence by using built-in variables such as *tradingpartner.edi.iap (for the inbound archive file prefix). Refer to Trading Partner (*TRADINGPARTNER) Built-in Variable Qualifiers for more information.