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 window is displayed. Specify the M3 BE user name and password.
  3. In the Output Parameters section, select an M3 BE field to be paired with a Mobility Core column, and click the right arrow.
  4. In the Fields section, select the M3 BE field that you have moved earlier.
  5. Specify this information:
    Select the Mobility Core table where you can find the Mobility Core column. The Mobility Core tables relevant to the selected M3 BE table are listed. Most of the time, only one Mobility Core table is listed.
    Select the Mobility Core column to be paired with M3 BE field.
    Default value
    By default, this field shows the value from M3. To assign a new default value instead of the M3 value, specify a new default value.
    If new record (Use Today or Default Value)
    Select this option if the default field value set will be used. If using the date field, the value is the current date for the new record.
    Use Today or Default Value
    Select this option if the set default field value is used. If using the date field, the value is the current date for the changes made on the record.
    Is Person
    The value for this field must be specified in the Contact table. It only applies to the import and update of account records (OCUSMA in M3).
    Is Address
    The M3 address has four (4) fields. These fields must be added to one field where each line is separated by a carriage return and line feed unicode characters.
    Is Account type selection
    This field is the placeholder for the field that should be compared with the selected Account Types in Specifying selection settings.
    Create for all Languages
    If this option is selected, a record is created for each language that exists in the Language table. This applies to Description tables, such as CodeDescription, ProductDescription and others.
    Skip for Update
    This field is selected if new changes on a record is not reflected. You can only specify this option during Create or Insert operation.
    Must exist
    The value, usually a foreign key, must exist. The foreign key is not part of the key values from M3, but it must exist in a table or you cannot import a record to Mobility Core.
    Combine Date+Time
    Select this option when a date field also contains 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 and the date part is used. When looking at the database, keep in mind that in the date and time is in UTC.
    Is Unique
    The value of the field with this property can only exist once. This field 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 Referring
    The field marked with this property contains a value from the same table, such as the Payer field in Account. The field could contain another AccountID.
    Get Owner/Org Unit from start page
    The field marked with this property must contain the CRMUserID for the User set as the owner on this transaction. If you need to specify the Organisation unit, it should be retrieved from this user.
    Is Account status selection
    This is the placeholder for the field that is compared to the selected Account status from- and to- values in Specifying code group settings.
    Match Code Group selection
    This field (CTSTCO) is from the Event from CSYTAB (this only applies to Codes). This field should only be specified in the database if it matches the Code Groups specified in Specifying code group settings.
    Match with default value
    If the field value is the same value that is specified in Default value, then this record is added to the Mobility Core database.
    Combine to Parent PK
    Select this option 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. The table and field to search in is specified in the drop-down boxes shown when the check box is selected.
  6. Click Save.
    Note: For the changes to take effect after mapping, restart Mobility Core.