M3 Address Structure

For the FBMs that include VAT reports, the address information must 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 in-sufficient, 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
Message/ Business msg Generic
Message version 1
In/Outbound msg O
Parent elements Generic
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
  • SUPP for tax representative 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 shows the available codes for the message data (Value – Out), which is five characters long, 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 a 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 a separator.
E Street and building number This information is optional. If code E is not defined, then no information is sent.
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 optional. If code G is not defined, then the value of City 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 a separator.
I Country This information is optional. If code I is not defined, then the value of Country field is retrieved.
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 a separator.

Example:

M3 data – Value in Message data – Value out
ALL ABEGX
M3 field Value stored in field
NAME (CONM) ABC Company
Address field 1 (COA1) Services Limited
Address field 2 (COA2) ul. Smolki
Address field 3 (COA3) Warszawa 00-362
Address field 4 (COA4) Poland
Output Field Formatted output
Nazwa ABC Company Services Limited
AdresL1 ul. Smolki Warszawa 00-362