Mapping M3 BE fields to Mobility Core columns

Note: The default values are pre-configured.
  1. Select Data import > Integration MetaData.
  2. Right click on an M3 BE table and select Output Parameters.
    If you have not logged in yet, the Provide BE Credentials displays. Specify the M3 BE user name and password.
  3. In the Output Parameters section, select an M3 BE field that will be paired with a Mobility Core column, then click the right arrow.
  4. In the CLM fields section, select the M3 BE field that you have moved earlier.
  5. Specify this information:
    CLM table
    Select the Mobility Core table where the Mobility Core column is found. The Mobility Core tables relevant to the M3 BE table that you have selected earlier are listed. Most of the time, only one Mobility Core table is listed.
    CLM column
    Select the Mobility Core column that will be paired with M3 BE field.
    Default value
    If this column should be filled with a default value instead of the value from M3, specify a value here.
    If new record (Use Today or Default Value)
    Select if the default field value set will be used; else if it is a date field, the value will be the Current date for the new record.
    Use Today or Default Value
    Select if the default field value set will be used; else if it is a date field, the value will be the Current date for the changes made on the record.
    Is Person
    This field should be entered into the Contact table. It only applies to the import and update of Account records (OCUSMA in M3).
    Is Address
    M3's address has four fields. These should be added to one field where each line is separated by a "carriage return" and "line feed" unicode characters.
    Is Account type selection
    Placeholder for the field that should be compared to the selected Account Types in Specifying selection settings.
    Create for all Languages
    If this is checked, a record is created for each language that exists in the Language table. Applies to the "Description" tables, such as CodeDescription, ProductDescription and so on.
    Skip for Update
    The field that is marked with this property is not updated if the record already exists. The value is only entered if it is a Create /Insert operation.
    Must exist
    The value (usually a foreign key) must exist – that a foreign key is not part of the key values from M3, but it must exist in a table or the record to be imported cannot be imported to Mobility Core.
    Combine Date+Time
    Select this when you have a date field that should also contain the time portion. For example, the field Activity.StartDate should contain both date and time because you can plan the activity to be performed today at three in the afternoon. Usually the dates display the time in the database, but it is only the date part that is used (when you look at the database, keep in mind that it is in UTC).
    Is Unique
    The value of the field with this property can only exist once. This is usually a key-field in M3.
    Is Combined Unique
    The values of the fields marked with this property can exist together only once. Together, they are the unique key in M3.
    Is Self Refering
    The field marked with this property contains a value from the same table, such as the Payer field in Account. That field could contain another AccountID.
    Get Owner/Org Unit from start page
    The field marked with this property should contain the CRMUserID for the User set as "Owner" on this transaction. If it is the Organisation unit that should be entered, it should be retrieved from this user.
    Is Account status selection
    Placeholder for the field that should be compared to the selected Account status from- and to- values in Specifying selection settings.
    Match Code Group selection
    This field (CTSTCO) from the Event from CSYTAB (this only applies to Codes), should only be entered in CLM if it matches the CodeGroups entered in Specifying code group settings.
    Match with default value
    If the field value is the same value that is entered in "Default value", then this record is added to the Mobility Core database.
    Combine to Parent PK
    Select this when mapping Header and Lines. You need to know which fields that are unique keys in M3 for the header record so that you can use these to check in the header table for that record. For Sales quotes that are the QuoteNumber in the Header record, and the QuoteNumber, Line number and Line suffix for the Line record.
    Is Foreign Key
    The value of this field must exist in another table. That table and the field to search in is entered in the drop-down boxes that are displayed when the checkbox is checked.
  6. Click Save (the button at the right of the CLM table field).
  7. Click Save (the button at the right of the CLM fields section).
    Note: For the change to be applied after the mapping, you need to restart the Mobility Core node in the Grid Management Pages using LifeCycle Manager.