Mapping #
Mapping is the term to map source data fields to their related target data fields. It depends on the key concepts. To check the fields in the UI/Front end forms and mapped consistently with the corresponding DB table.
Purpose #
In order to figure out how the data needs to be formatted or mapped. It must also explain the primary key in the source system.
SKYVVA provided the following possibilities for mapping in both inbound processing. If you either set the flag “External Mapping” or “Internal Mapping”. If both flags are checked then you have created another new method called “Hybrid-Mapping”.
External Mapping | Internal Mapping | Description | Comment |
x | Mapping in Sender e.g. SAP-P) | Fields are Salesforce field names. A mapping editor is not shown. | |
x | Internal Mapping | Fields are not Salesforce field names. A mapping editor is shown. | |
x | x | Hybrid Mapping | Fields in Salesforce Field names. A mapping editor is shown. |
External Mapping #
Indicate the interface is over PI (SAP-PI-SF). In this case, no mapping is required. In other words, the mapping and business logic are managed by an external system.
To use external Mapping you have to create an interface and check the flag in order to activate.
As mentioned above in the table, the mapping editor is just shown the root Node when using External Mapping.
Internal Mapping #
Create an inbound Istructure on the interface.
To use Mapping in SFDC you have to create an interface and check the flag in order to activate.
As mentioned above in the table, the mapping editor is shown when using Internal Mapping.
Hybrid Mapping #
Hybrid Mapping is a combination of both External Mapping and Internal Mapping. Fields Mapping in SFDC will overwrite the Fields in External Mapping.
To use Hybrid Mapping you have to create an interface and check the flag in order to activate.