Transformation Map TRANSFORM Built in Variable Qualifiers

Transformation Map (*TRANSFORM) Built-in Variable Qualifiers

The *TRANSFORM built-in variable may be extended with a range of qualifiers to access the attributes of the Transformation Map.  The available qualified forms of the *TRANSFORM built-in variable may be displayed and accessed by expanding the corresponding items listed on the Built-ins tab in the Processing sequence editor.

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

 

Transformation Map Attributes

The base attributes for the current transformation map may be accessed using the following qualifiers with the *TRANSFORM variable:

Qualifier Description .II The unique internal identifier of the Transformation Map. (The internal identifier is a 32 character value uniquely assigned by LANSA Composer. You can see the unique identifier for a Transformation Map on the Audit tab.) .ID The identifier or name of the Transformation Map definition This is the value returned for the *TRANSFORM built-in variable if no qualifier is specified.  In other words *TRANSFORM yields the same value as *TRANSFORM.ID. .STATUS The status code (A=active, I=inactive) of the current Transformation Map. .TYPE The map type code for the Transformation Map definition.

 

Transformation Map Data Interchange Attributes

The data interchange attributes for the current Transformation Map may be accessed using the following qualifiers with the *TRANSFORM variable:

Qualifier Description .EDI.DIR The direction (I = inbound, O = outbound) of the current transformation map .EDI.EXP The transaction data export processor for the current transformation map .EDI.IMP The transaction data import processor for the current transformation map .EDI.TID The transaction ID associated with the current transformation map

 

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.