This document describes, how to use Hybrid mapping mode in Skyvva.
Our solution can be used to map the incoming data stream in SFDC. Currently for example in case of SAP-PO user can map in SAP PO and thus no need to map again in SFDC. Therefore we set the flag “External Mapping”. When we check the Flag ‘Mapping in SFDC‘ this means that the incoming data will be map again. But in this case, we need to do the whole mapping again. In this new version, we have enabled the Hybrid mapping or merge the mapping from an external system and SFDC.
For Hybrid Mapping, we need to check both “Mapping in SFDC” and “External Mapping” as shown below.
Whenever we are not able to handle the mapping logic in SAP PI/PO in those cases we try to use the mapping logics in SFDC.
For example in Account inbound interface, If we want to send the data based upon the RecordType Id. In such cases, we have to use VLOOKUP formulae in Skyvva.
Here the VLOOKUP will compare Account.RecordTypeId with DeveloperName, then in Account.RecordTypeId there will be developer name which will be mapped as constant to RecordTypeId in SAP PO as shown below.
Then this vlookup first compares that name with the existing developer name in salesforce. if the developer name matched it returns Id of that record type. If the developer name doesn’t match then it will do nothing.
In Salesforce, “Record Types” are a way to arrange and classify data in an object. An example of how Record Types can be particularly helpful is when you want to assign different sets of data to different groups of sales teams.
So, the above one is an example of Hybrid mapping where we can handle both in SAP PI/PO and in Skyvva.