2.4.2 Trading Partner Details
The details for a trading partner definition consist of basic identification and status information and basic contact details:
Basic identification and status information for a trading partner definition is:
|
Identifier |
An identifier to uniquely identify this trading partner. |
| Description |
This should describe the trading partner definition. |
| Status |
Active or Inactive. Trading partner definitions cannot be used in a processing sequence while they are in inactive status, and they will not be included in processing sequence loops that specify the *TRADINGPARTNERS built-in variable. |
The trading partner definition can hold basic contact details. These details are largely for reference. LANSA Composer does not automatically make use of any of these fields. However your Processing Sequences can use them in any way you see fit by referencing the corresponding built-in variables. The contact information is:
|
Contact |
The name of a contact at the trading partner's organization. |
| Address 1, 2, 3 |
The street address for the trading partner. |
| Email, 2, 3 |
These fields can specify email addresses used with this trading partner. Each field can specify a single email address or a list of email addresses separated by commas. Click the adjacent prompt button to enter or maintain the list of email addresses. |
| Phone number |
The telephone number for the trading partner. |
| Fax number |
The fax number for the trading partner. |
The trading partner definition can specify specific processing sequences associated with the trading partner in connection with LANSA Composer's transaction document processing and framework:
|
Receive processing sequence |
Specifies the name of a processing sequence that is used to receive inbound transaction documents for this trading partner. This processing sequence, if specified, will be called by the supplied TXDOC_RCV processing sequence to perform inbound processing specific to this trading partner. You can use it in your own processing sequences too, by referencing the associated trading partner built-in variable (refer to TXDOC_RCV for an example of doing this). |
| Send processing sequence |
Specifies the name of a processing sequence that is used to send outbound transaction documents for this trading partner. This processing sequence, if specified, will be called by the supplied TXDOC_SEND processing sequence to perform outbound processing specific to this trading partner. You can use it in your own processing sequences too, by referencing the associated trading partner built-in variable (refer to TXDOC_SEND for an example of doing this). |