Configuration guidelines for M3 Business Message Data Translation
Overview of M3 Business Message Data Translation
Data translation is normally required between an in-house system and an external system. Data translation allows string data going to (outbound) or received from (inbound) systems to be translated from one value to another.
For example, between two partnering companies, the same things may have different representations, like units of measure codes. For example, one company uses the string data code STK, while the partner company uses the string data code PCS. Both codes refer to the same single unit of measure, designated as styck in Swedish and as pieces in English. It applies only to the string data value and not to the numeric values carried by the string data.
See the instructions for specifying and editing translation data in the Infor M3 Cloud Configuration Guide.
The values for data translation are specified in the M3 functions ‘Business Message Data Translation. Displ’ (CRS881) and ‘M3 Business Message Data. Translate’ (CRS882), where (CRS881) is based on the imported translation definitions. The values in (CRS882) can require an update during the ongoing business processes.
To activate the new translation values defined in (CRS881) and (CRS882) in Enterprise Collaborator in the next set of business messages to be processed, you must reload Data translator on the Enterprise Collaborator management pages. To complete this task, select
.Translation of business message data for the camt.054.001.02 message
In CRS881, it stores the header data for information that should be translated. This is generated through MBMTRN Updated in the grid management pages for the MEC server.
Settings | Data |
---|---|
Msg standard (MSTD) | FBM |
Message version (MVRS) | BankStatement |
Business message (BMSG) | 1 |
Inbound or outbound message (IBOB) | BankStatementHeader |
Parent elements (ELMP) | I |
Data element (ELMD) | BankStatmtCode |
This setting must be used to handle both CAMT.053 and CAMT.054 for the same Bank account identifier and it identifies the division and Bank account identifier for the processing in the M3 Business Engine.
In CRS882 it stores the actual translation data. The input data must be manually entered into M3 BE as specified below.
Settings | Data |
---|---|
M3 data - Value in | CMT054 |
Message data - Value out | camt.054.001.02 |
The translation rules in (CRS882) is defined in Company level with Division blank.
If translation for the Message data with value 'camt.054.001.02' exists, the M3 data is used as part of the Bank account identifier which is positions 1-6 and succeeding positions from Priority 1: Ntfctn/Acct/Id/IBAN or Priority 2: Ntfctn/Acct/Id/Othr/Id of the input file.
If no record is found, a new search is done without the Message data (MBMD) defined in CRS882.
If no translation is available in CRS881-CRS882 for Message data with value 'camt.054.001.02', then the Bank account identifier from the input file with Priority 1 Ntfctn/Acct/Id/IBAN or Priority 2 Ntfctn/Acct/Id/Othr/Id is searched.
Reload of Data Translator
Data translator must be reloaded from the Enterprise Collaborator Administration, every time a new data translation is added in CRS881 and CRS882, or when an exisiting data transaltion is changed. This must be done before uploading payment specification file.
Select
, and click .