How to import custom sales child object using party id instead of orig system reference
(Doc ID 1608563.1)
Last updated on DECEMBER 22, 2020
Applies to:Oracle Fusion Trading Community Model - Version 22.214.171.124.0 and later
Oracle Fusion CRM Application Composer - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Document shows the mapping that should be done when using party id's instead of orig system references.
The child object is PurchaseHistory_cWBIT in this example. The SalesAccountVO_Id_c attribute value needs to be the sales account id. This is required.
In this example, all the other fields on the custom object are custom fields. ProductService_Id_c is a custom pick list that we pass the id of the object it is referencing. For example, if it was referencing customer name, we woud pass the party id.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document