External field mapping – Non-code lists
This can be used to configure how certain field values are mapped to and from an external system.
For the external field mapping – non-code lists, the following mapping types are available:
• External code – BO definition (refers to a BO, so typically used to create a certain UdBO)
• External code – Boolean (refers to an External Business object field definition that is (based on the value of the External code) either Yes or No)
• External code – No mapping (External Business object field definition that can be completely consumed or provided to the external system)
• External code – Code mapping (External Business object field definition that can only be consumed if there is a mapping available in the External BO Code mapping)
Field | Description | ||
|---|---|---|---|
Mapping type | Drop-down list that contains the mapping options available meaning: • BO Definition • Boolean • No mapping • Code mapping | ||
External object type | This is the name of the external system entity. | ||
External field name | The field name to refer to, from the external object type. | ||
External code | The unique ID that identifies business objects in both the current system and the external system.
| ||
External business object field definition | A reference to the field from the Externally managed BO that will be used for mapping. | ||
Yes/No value | Determines how the field value is mapped to a Boolean value. | ||
Planon external business object definition | The name of the externally managed business object field to which the data is mapped in Planon. |
