Trading Partner TRADINGPARTNER Built in Variable Qualifiers

Trading Partner (*TRADINGPARTNER) Built-in Variable Qualifiers

The *TRADINGPARTNER built-in variable may be extended with a range of qualifiers to access the attributes and properties of the trading partner and the directories, Transformation Maps and/or Configurations linked to the trading partner.  The available qualified forms of the *TRADINGPARTNER built-in variable may be displayed and accessed by expanding the corresponding item listed on the Built-ins tab in the Processing sequence editor.

Note: While the *TRADINGPARTNER built-in variable is writeable, the qualified forms that provide access to the attributes of the current trading partner are not writeable.

Trading Partner Attributes

The base attributes for the current trading partner may be accessed using the following qualifiers with the *TRADINGPARTNER variable:

In the following example, the *tradingpartner.id form is used in an If condition to condition a part of the Processing Sequence:

Trading Partner Properties

Values of installation-defined properties for a Trading Partner may be accessed by using the following qualified forms of the *TRADINGPARTNER built-in variable:

     where <property name> is the name of the installation-defined Trading Partner property.  Refer to Code maintenance for information on defining Trading Partner properties.

In the following example, the *tradingpartner.property.myproperty form is used in the details for an activity to access the value of the installation-defined property named myproperty for the current Trading Partner:

Note:  The use and values of these properties is subject to your own circumstances and conventions.  LANSA Composer does not enforce the entry of the fields corresponding to these properties, nor does it validate any values entered.

Trading Partner Data Interchange Attributes

The data interchange attributes for the current trading partner may be accessed using the following qualifiers with the *TRADINGPARTNER variable:

Note:  The use and values of these attributes is subject to your own circumstances and conventions.  LANSA Composer does not enforce the entry of the fields corresponding to these attributes, nor does it validate any values entered.

Trading Partner Linked Directories

Directories linked to a trading partner may be accessed using the following qualified form of the *TRADINGPARTNER built-in variable:

     where <directory type> is a directory type code defined for the system. Refer to Code maintenance for information on defining directory types.

In the following example, the *tradingpartner.dir.iftp form is used in the details for an FTP_INBOUND Activity to access the inbound FTP directory for the current trading partner:

Trading Partner Linked Transformation Maps

Transformation maps linked to a trading partner may be accessed using the following qualified form of the *TRADINGPARTNER built-in variable:

     where <map type> is a map type code defined for the system. Refer to Code Maintenance for information on defining map types.

In the following example, the *tradingpartner.map.orderin form is used in the details for a TRANSFORM Activity to access the Transformation Map of type orderin linked to the current trading partner:

Trading Partner Linked Configurations

Configurations linked to a trading partner may be accessed using the following qualified forms of the *TRADINGPARTNER built-in variable:

In the following example, the *tradingpartner.ftpin form is used in the details for an FTP_INBOUND Activity to access the inbound FTP directory for the current trading partner: