Bidirectional Translation Data
Datatranslator is used to convert data between your external messages and M3. Usually, you set up separate translation rules for each direction: one for inbound and one for outbound.
When the Bidirectional Translation Data setting is enabled, you only define the rule once. The reverse mapping is automatically created.
Example
You define one inbound rule in CRS881 or CRS882:
| Direction | Data element | Message data | M3 data |
|---|---|---|---|
| Inbound | e01_3039 | EXT_CUST_001 | 100001 |
This reverse mapping is automatically created:
| Direction | Data element | Message data | M3 data |
|---|---|---|---|
| Outbound | e01_3039 | 100001 | EXT_CUST_001 |
No extra setup is required because there are both directions in one rule.
Disable the Bidirectional Translation Data setting
By default, this setting is enabled. To disable this setting, select and then clear the Bidirectional Translation Data check box.
You can disable this setting for these scenarios:
- Inbound and outbound mappings are intentionally different for the same element
- You need different translated values depending on direction
Translation methods
This table shows the translation methods for bidirectional translation data:
| Method | Direction | Function |
|---|---|---|
| toMovex() | Inbound | Converts message data to M3 data |
| toMessage() | Outbound | Converts M3 data to message data |