Types of Master Data that can be synchronised with C4C
Some of the limited master data can be synchronized with C4C system using the administration screen. Currently the following master data can be synchronized with languages based on the languages defined.
- Gender
- Country
- Industry
- Org Unit
- Currency
- Language
- Employee
- Time Zone
- INCO Terms
- Person Title
- Partner Role
- Reject Reason
- Payment Terms
- Sales Organization
- Distribution Channel
- Unit of Measurement
- Sales Document Type
If you just wanted to synchronize the master data with limited language (example English, German, Chinese), it is better to manually define the language without synchronizing from the external system. If you synchronized the languages first and then synchronized other master data, it will create the master data with languages synchronized before.
When you do the synchronization, it will first check the existing code with the same external id. If there is no external id assigned to the existing code, there can be duplicate code name after synchronization. Therefore, it is recommended to check the external id of the existing code to assign if necessary, before synchronization of particular master data.
To synchronize the master data needed for C4C integration,
- Go to Administration -> Data Management
- Select the Master Data under the Section CRM Data Synchronization
Click Synchronize
Understanding the namespace of the imported data
Since 1604 release, those data points imported from Cloud for Customer (C4C) will be given the namespace according to the C4C URL defined in [application.properties]. The following business types will be given the C4C Namespace with business type-specific fragment:
- Account
- Contact
- Address
- Address
- Contact
- Opportunity
- Quote
- Partner Function Record
- Master Data
- Country
- Industry
- Distribution Channel
- Unit of Measurement
- Currency
- Gender
- Title
- Payment Terms
- INCO Terms
- Sales Document Type
- Language
Account Namespace
The following is an example of individuals having the C4C namespace and object external id of account as a fragment.
Contact Namespace
The following is an example contact individuals having the C4C namespace and account external id + contact external id as a fragment. For example, in row 1,1000083 represents a contact external id.
Address Namespace
Since address could be an address of contact or account, the following shows an example of address namespace and fragment. If an address is for contact, the fragment will start with Contact followed by its external id and the combined key of address data. If an address is for an account, the fragment will start with the Account followed by its external id and the combined key of address data.
Currently, the combined key of address data is obtained by combining the following address business data attributes. If the length of the combined key is more than 100, it will use the hash code value of the combined address string with city, country, zip information (example hash code of combined address data + city + country + zip).
- addressUnitNo
- addressStreet
- addressCity
- addressZip
- addressState
- hasCountry
Opportunity Namespace
The following is an example of individuals having the C4C namespace and object external id of account as a fragment.
Quote Namespace
The following is an example of individuals having the C4C namespace and object external id of a quote as a fragment.
Partner Function Record Namespace
The following is an example of individuals having the C4C namespace and object external id of quote as fragment as well as the partner function type such as PAYER_PARTY, BILL_TO_PARTY, EMPLOYEE_RESPONSIBLE_PARTY, BUYER_PARTY, SHIP_TO_PARTY followed by the external id of partner function record where the external id of partner function record will be maintained as quote id + partner function type + link partner id (account’s external id or user’s external id).
Master Data Namespace
For master data fragment, it will start with the business type of master data followed by the serial id and the object external id.
Comments
0 comments
Article is closed for comments.