Transformation Map Data Interchange Attributes
LANSA Composer defines and stores a set of data interchange attributes for each Transformation Map. These are defined to accommodate attributes that are used by the transaction document processing framework as follows:
|
Map direction |
Specifies the direction (inbound or outbound) of the transaction document processing flow to which this map applies. |
| Map standard |
Specifies, by selection from a drop-down list, the document type and the document standard to which this map applies. |
| Map transaction type |
Specifies the transaction type to which this map applies. For example, '850' for an EDI X12 purchase order transaction or 'ORDERS' for an EDIFACT order transaction. |
| Import processor |
Specifies the name of the import processor that imports inbound transaction data into an application database after it has been received, typically into staging database tables, by this transformation map. |
| Export processor |
Specifies the name of the export processor that extracts transaction information from an application database and writes it, typically into staging database tables, to be read by this transformation map to prepare an outbound transaction document. |
The transformation map data interchange attributes are used in the transaction document processing framework, or can be used in your own custom transaction document processing solution in the following ways:
- Where applicable, the attribute values are accessible within a processing sequence by using built-in variables such as and for the import and export processor names. You must first have assigned a transformation map identifier to the *transform built-in variable before you can access its attribute values in this way.
Refer to Transformation Map (*TRANSFORM) Built-in Variable Qualifiers for more information.
- LANSA Composer refers to some of the attribute values to identify qualifying transformation maps when using the FIND_TPMAP activity.
- Some of these and other attributes relating to the document type and standard can be retrieved in a processing sequence using the DISCOVER_MAP activity.
Import and Export Processors
Note that the use of import and export processors is not mandatory. These attributes and this capability are provided to support the use of intermediary "staging" database tables when processing inbound or outbound transaction documents. If you choose instead that your transformation maps directly read from and write to your application database tables, then you may not need to separately define or execute an import or export step.
For more information about defining import and export processors, refer to:
4.1.9 Application program interfaces (APIs)