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 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 Administration Tools > Enterprise Collaborator Administration.

M3 Address Structure

The FBM for DE-UVA VAT report requires the address information to be sent with a specific structure. This table shows the structure of the Name and Address fields (1-4) for which the required format is supported.

Field Value
Name Name
Address line 1 Street and building number
Address line 2 Street and building number continued if line 1 is insufficient, otherwise left blank
Address line 3 Postal code and town
Address line 4 Country
Note: The postal code, the town, and the country code must be defined in their dedicated M3 fields regardless of how the address lines are used. If the address information in M3 cannot be defined as described here, the data translation in the ‘addressFieldType’ element must be defined in the function ‘Business Message Data Translation. Display’ (CRS881). See the detailed configuration settings for (CRS881).

Translation in the ‘addressFieldType’ element for address information

If the address structure does not correspond to the settings described in M3 Address Structure, then an additional setting in (CRS881) and (CRS882) is required to identify the contents of the fields in Infor M3 Business Engine.

‘Business Message Data Translation. Display’ (CRS881)

Field Value
Msg standard FBM
Business msg Generic
Message version 1
Parent elements Generic
In/Outbound msg O
Data element addressFieldType

‘M3 Business Message Data Translation. Display’ (CRS882) for data element addressFieldType

Field Value
M3 data (Value – In)

Address rule to indicate the type of address information that requires translation:

  • ALL for the general rule of address information
  • COMP for company address information
  • CUST for customer address information
Message data (Value-Out)

A combination of five characters to indicate whether and how each of the name and address line fields 1 to 4 in M3 Business Engine are used, for example AEFGX.

The value out must contain five characters to correspond to the five positions.

This table describes the available codes for the five-character message data (Value – Out) to define the structure of the address:

Code Description Comment
X Field not used, empty The code indicates that the field is not used.
A Name This information is required. If code A is not defined, then the value of the Name field is retrieved.
B Name, part 2 This information is used in combination with code A. This information is added after the value from code A with a blank as separator.
C Name of location, if different from the name above This information is optional. If code C is not defined, then no information is sent.
D Name of location, part 2, if different from the name above This information is used in combination with code C. This information is added after the value from code C with a blank as separator.
E Street and building number This information is required. If code E is not defined, then the value of the Address line 1 field is retrieved.
F Street and building number, part 2 This information is used in combination with code E. This information is added after the value from code E with a blank as separator.
G Postal code and city This information is required. If code G is not defined and the Postal code and City fields are blank, the value of the Address line 3 field is retrieved.
H Postal code and city, part 2 This information is used in combination with code G. This information is added after the value from code G with a blank as separator.
I Country This information is optional. If code I is not defined, then no information is sent.
J Country, part 2 This information is used in combination with code I. This information is added after the value from code I with a blank as separator.
Note: For the DE-UVA VAT report, only these codes are used:
  • Codes A and B for the identification number 91002, ‘Name of the reporting company’
  • Codes E and F for the identification number 91003, ‘Street of the reporting company’
  • Codes E and F for the identification number 91301, ‘Street of responsible person’