Data Translation Configuration in Mapper

Data for transformation is defined and published in Mapper for the user to identify which elements need to be translated. Data translations are built into the mappings using Java code.

In the data translation, you specify the application context for the message, the message identification, and the message direction (inbound or outbound). For every translation, you must specify the rest of the data translation identification and the data to translate. This is the metadata used for translations.

The data translation metadata is automatically created in the Mapper database when a mapping is published and when a published mapping is republished. Mappings are published to make them available for use from the EC Partner Administration tool.

Follow these guidelines:

• When a mapping is published, the mapping and its Data Translations are available in the EC Partner Administration tool.

• When a mapping is unpublished, the data translation records are automatically removed. Or, the data translation record acquires a "deleted" state if you have specified any translation data for it. This design helps prevent accidental deletion of business data.

• When the data translation definitions in the mapping are updated, the data translation records are updated when you re-publish.