Understanding BOD Field Mappings

BOD Field mappings define the mapping of BOD element content to Infor CRM CE database properties.

The Infor CRM CE BOD Field Mapping contains:
Field Mapping
A descriptive name for the BOD field mapping.
Mapping Type
The type of content contained in the BOD element, possible types are:
  • Property: Generic text, date or numeric content to be stored in specified database property.
  • OneToMany: Parent-child relationship between the current record and a child collection based on the current records ID value.
  • OneToOne: Parent-child relationship between the current record and the first child record based on the current records ID value.
  • ManyToOne: A child record related to a parent record based on the unique ID value contained in the specified BOD element.
  • ManyToMany: A child junction record referencing the active record and an already existing record based on the unique ID value contained in the specified BOD element.
  • SetRelatedID: Used to capture additional relationship content when dynamically generating missing related content.
  • FullName: A generic contact full name BOD element that requires the system to auto parse and store the name prefix, first name, middle name, last name and suffix components in the corresponding CRM contact properties.
IDO
A period delimited IDO path from the primary IDO for the BOD to the related IDO for the specific BOD element. (Example: CRMContact.CRMPhoneNumberFax)
IDO XPath
The BOD element XPath corresponding to the specified IDO.
  • Multiple BOD elements contain a common IDO XPath value if the BOD elements are mapped to a common IDO record.
  • IDO XPaths can contain optional case sensitive criteria based on the .Net XPath filter patterns such as /ContactMaster/CommunicationDetail[./ChannelCode='EMail' and ./UseCode='Home']
Property
The target property on the specified IDO which receives the content of the specified BOD element or related record ID.
Property XPath
An XPath, based on the IDO XPath, for the actual BOD element to be captured or used to lookup the required related record.
Note:  Property XPaths can contain optional case sensitive criteria based on the .Net XPath filter patterns such as Note[@languageID='{LangToken}' or not(@languageID)]
Active
Select this check box to enable the BOD field mapping.
Custom
This check box is automatically selected for customizable BOD field mappings.
Required

Select the check box to require the BOD field mapping content..

Sync Direction
The usage of the BOD field mapping, possible values include:
  • Both: Used for both inbound and outbound BOD processing.
  • In: Used for inbound only BOD processing.
  • Out: Used for outbound only BOD generation.
BOD Element
The sequencing of outbound BOD field mappings when generating the outbound template.
Default Value
This is used for both inbound and outbound BOD processing to supply a constant value to be used in the absence of the specified BOD element.
Related ID Property
The source content for BOD field mappings with a Mapping Type of SetRelatedID.
Key
A specific related record of a related child collection and defines a property in the target IDO whose value must match the specified BOD element content or Bod field mapping default value.

Infor CRM CE, as a subscriber application, consumes inbound Sync BODs published by the host system. Infor CRM CE maps Inbound BOD content to the specified database properties by BOD field mappings defined with a direction value of ‘In’ or ‘Both.’

Infor CRM CE, as a subscriber application, publishes outbound Process BOD requests to generate new data or update already existing data in the host ERP system. Outbound Process BOD templates are auto-generated based on BOD field mappings defined with a direction of ‘Out’ or ‘Both.’

Related topics