- 07 Nov 2024
- 3 Minutes to read
- Print
- DarkLight
Global data setup
- Updated on 07 Nov 2024
- 3 Minutes to read
- Print
- DarkLight
Types of data that can be synchronized with C4C
Some limited master data can be synchronized with C4C in the CPQ Administration area. Currently, the following 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
Synchronizing the data
If you want to synchronize the data with limited languages, for example, English, German and Chinese, it is better to manually define the language rather than synchronizing them from the external system. If you synchronize the languages first, and then synchronize the data, the application will create the data with languages already synchronized.
When you synchronize the data, the system will first check the existing code with the same external ID. If there is no external ID assigned to the existing code, it might result in a duplicate code name after synchronization. Therefore, we recommend you check the external ID of the existing code to assign before synchronizing the data.
To synchronize the data needed for C4C integration, follow these steps:
- Log in to CPQ.
- In CPQ, go to Administration in the left navigation bar and select Data Management.
- Select Master Data under CRM Data Synchronization.
- Click Synchronize.
Understanding the Namespaces of the Imported Data
Data points imported from Cloud for Customer (C4C) will be given a namespace according to the C4C URL defined in [application.properties]. You can find more information about this file in the article: General property and ontology files.
The following business types will be given the C4C namespace with a business type-specific fragment:
Account
Contact
- Address
Address
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 image shows examples of individuals with the C4C namespace and the object external ID of account as a fragment.
Contact Namespace
The following image shows examples of contact individuals with the C4C namespace and account external ID + contact external ID as a fragment. For example the image shows in row that 1, 1000083 represents a contact external ID.
Address Namespace
Since address could be the address of contact or account, review the following guidelines:
- If an address is for a 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 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.
- addressUnitNo
- addressStreet
- addressCity
- addressZip
- addressState
- hasCountry
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, and zip information. For example, the hash code of combined address data + city + country + zip.
The following image shows examples of the address namespace:
Opportunity Namespace
The following image shows examples of individuals with the C4C namespace and object external ID of account as a fragment.
Quote Namespace
The following example shows a list of individuals with the C4C namespace and the object external ID of a quote as a fragment.
Partner Function Record Namespace
The following example shows individuals having the C4C namespace and object External ID of quote as a fragment as well as the partner function type such as the following:
- PAYER_PARTY
- BILL_TO_PARTY
- EMPLOYEE_RESPONSIBLE_PARTY
- BUYER_PARTY
- SHIP_TO_PARTY
The previous examples would be followed by the external ID of partner function record, where the external ID of the partner function record is maintained as quote id + partner function type + link partner id which is the account’s external ID or the user’s rxternal ID.
Master Data Namespace
For the master data fragment, it will start with the business type of master data, followed by the serial ID and the object external ID.