4.1.7 Transformation Maps for Transaction Document Processing
Transformation maps are almost always an integral part of a transaction document processing solution:
- For inbound processing, they are typically used to map the data contained in the inbound transaction document into the application database, either directly or via intermediary "staging" database tables.
- For outbound processing, they are typically used to extract data from the application database and map it into the outbound transaction document.
The following topics contain more information about the use of Transformation Maps in the transaction document processing framework:
Model Transformation Maps for Transaction Document Processing
Transformation Map Data Interchange Attributes
For information about pre-built transformation maps supplied for use with the transaction document processing framework, refer to:
4.1.8 Pre-built EDI X12 solution components
For general information concerning Transformation Maps, refer to:
Note If you intend to use Altova MapForce to create mappings involving EDI X12, EDIFACT, HL7 or certain other specialized transaction standards, you may need to install additional configuration files for that transaction standard. These are not installed by the LANSA Composer client installation.
The additional installers for EDI X12 and EDIFACT for the shipped version of Altova MapForce are provided on the LANSA Composer client media.
Configuration files for other versions or standards may be downloaded from the Altova web-site at http://www.altova.com/components_mapforce.html.