Model Transformation Maps for Transaction Document Processing

LANSA Composer

previous page next page

Model Transformation Maps for Transaction Document Processing

The pre-built processing sequences that are central to the transaction document processing framework assume a particular pattern for the transformation maps that it invokes and LANSA Composer supplies the following "model" transformation maps that match this pattern:

  • TXDOC_MODEL_IN (Transaction document inbound model map)
  • TXDOC_MODEL_OUT (Transaction document outbound model map)

 

These maps cannot be used directly but are supplied to serve as a model from which you can create your own maps that reference the database and the transaction document types involved in your organisation's transaction document processing.

The key thing about these maps is that they define the number, order and meaning of the parameters that your maps will be assumed to receive when invoked by the transaction document processing framework, as supplied.  Any maps you create will need to accept the same parameters in order to be compatible with the supplied transaction document processing sequences.

For inbound maps, the expected parameters are:

Name (*)

 Description

TXDOC_MODEL_IN_1(TextfileSourceFilename)

Specifies the path to the inbound transaction document file.

(Adding a file system source component (for example: XML, text, EDI, XBRL or Excel) to your map results in such an input parameter.)

TXDOC_MODEL_IN_2
(DocNumberSourceParameter)

Specifies the transaction document envelope number that identifies the transaction document in the transaction document register.  This value is returned by the TXDOC_REGISTER activity.

(Your map may or may not need to reference this value, but you must define it as an input parameter in your map in any event in order for your map to be compatible with the processing sequences, as supplied, used by the transaction document processing framework.)

TXDOC_MODEL_IN_3
(TXDOC_DATABASETargetConnection)

Specifies a LANSA Composer database configuration name that identifies the database configuration used to connect to the target database for the map.

(Adding a database target component to your map results in such a parameter.)

 

(*) Note that your map does not have to (and will not) use the same parameter names as shown - it is the number, order and meaning of the transformation map parameters that is important for this purpose.

 

For outbound maps, the expected parameters are:

Name (*)

 Description

TXDOC_MODEL_OUT_1
(TXDOC_DATABASESourceConnection)

Specifies a LANSA Composer database configuration name that identifies the database configuration used to connect to the source database for the map.

(Adding a database source component to your map results in such a parameter.)

TXDOC_MODEL_OUT_2
(DocNumberSourceParameter)

Specifies the transaction document envelope number that identifies the transaction document in the transaction document register.  This value is returned by the TXDOC_REGOUTBND or TXDOC_REGOUTX12 activities or equivalent APIs and by the FOR_EACH_TXDOCO iterator activity.

(Your map may or may not need to reference this value, but you must define it as an input parameter in your map in any event in order for your map to be compatible with the processing sequences, as supplied, used by the transaction document processing framework.)

TXDOC_MODEL_OUT_3
(TextfileTargetFilename)

Specifies the path to the outbound transaction document file to be created.

(Adding a file system target component (for example: XML, text, EDI, XBRL or Excel) to your map results in such an input parameter.)

 

(*) Note that your map does not have to (and will not) use the same parameter names as shown - it is the number, order and meaning of the transformation map parameters that is important for this purpose.

 

previous page start next page