- 22 Oct 2024
- 3 Minutes to read
- Print
- DarkLight
Accounts
- Updated on 22 Oct 2024
- 3 Minutes to read
- Print
- DarkLight
Import an Account from C4C to CPQ
You can export an account from C4C and import it into CPQ. You can then create an opportunity or quote in CPQ, as shown in the following diagram:
Then, you can export the quote back to C4C from CPQ as shown in the following diagram.
During the account export from C4C, CPQ synchronizes account-related data, including addresses and contacts related to the account. When the web service has been set up in C4C using HTML Mashup or URL Mashup, you can export an account from the C4C system into CPQ.
For more information on setting up HTML mashup for C4C and CPQ, see C4C system.
For the HTML mashup, depending on where you placed the embedded component, the Zilliant CPQ login page will be shown inside the C4C system.
To access the account in CPQ:
- If SSO has not been configured in the system, sign in to CPQ.
- After logging to CPQ successfully, one of the following will occur:
- The account will be exported to CPQ if it is not already there.
- If the account is already inside CPQ, the account will be synchronized.
The application completes the following during synchronization:
- Updates the account header, such as account name, account status—active or inactive—account ECC ID, industry, and main address.
- Imports the sales information.
- Creates new addresses and contacts as follows:
- Imports new addresses from C4C.
- Imports new contacts found inside the C4C.
- Deletes unused addresses and contacts as follows:
- Addresses of accounts with an external ID not found in C4C as well as those that are not used in other business objects.
- Contacts of accounts with an external IDs that are found in C4C as well as those that are not used in other business objects.
The synchronize button will appear in the Account Details page as well as within the Account Overview page for accounts that were imported from external systems such as C4C or SalesForceDotcom (SFDC).
Import account with custom field from C4C
CPQ supports the import of the following custom fields to the following SUBJECT_TYPE within an Account dataset.
- Account
- Address
- PartnerRoleRecord
Import account header custom field from C4C
For account header custom field mapping, you must set the following properties, where MX_GRAPH_TYPE_URI, MX_SUBJECT_TYPE_URI and CFC_XPATH are fixed as shown in the following table:
Field Name | Field Value | Fixed |
---|---|---|
MX_GRAPH_TYPE_URI | http://www.inmindcloud.com/application/schema.owl#Account | Yes |
MX_SUBJECT_TYPE_URI | http://www.inmindcloud.com/application/schema.owl#Account | Yes |
MX_FIELD_URI | The CPQ field URI is the one that was customized inside the application-schema ext.owl having the domain as Account. For example, URI.http://www.inmindcloud.com/application/application-schema-ext.owl#zAccountXxxXxxXxx | No |
CFC_FIELD_NAME | The C4C field name is the one that was created in C4C. The following is an example field name. It must start with prefix: a00:zAccountXxxXxxXxx | No |
CFC_FIELD_NAME_SPACE | The namespace of the custom field. For example, http://sap.com/xi/AP/CustomerExtension/BYD/A0014 | No |
CFC_XPATH | //Customer | Yes |
Import account address custom field from C4C
For account address custom field mapping, you must set the following properties where MX_GRAPH_TYPE_URI, MX_SUBJECT_TYPE_URI and CFC_XPATH are fixed, as shown in the following table.
Field Name | Field Value and Description | Fixed |
---|---|---|
MX_GRAPH_TYPE_URI | http://www.inmindcloud.com/application/schema.owl#Account | Yes |
MX_SUBJECT_TYPE_URI | http://www.inmindcloud.com/application/schema.owl#Address | Yes |
MX_FIELD_URI | The CPQ field URI is the one that was customized inside the application-schema ext.owl having the domain as Address. For example, http://www.inmindcloud.com/application/application-schema-ext.owl#zAddressXxxXxxXxx | No |
CFC_FIELD_NAME | The C4C field name is the one that was created in C4C. For example, It must start with the prefix: a00:zAccountAddressXxxXxx | No |
CFC_FIELD_NAME_SPACE | The namespace of the custom field. For example, http://sap.com/xi/AP/CustomerExtension/BYD/A0014 | No |
CFC_XPATH | //Customer/AddressInformation[UUID='Address.objectExternalId'] | Yes |
Import account relationship custom field from C4C
For account relationship custom field mapping, you must set the following properties where MX_GRAPH_TYPE_URI, MX_SUBJECT_TYPE_URI and CFC_XPATH are fixed as shown in the following table.
Field Name | Field Value and Description | Fixed |
---|---|---|
MX_GRAPH_TYPE_URI | http://www.inmindcloud.com/application/schema.owl#Account | Yes |
MX_SUBJECT_TYPE_URI | http://www.inmindcloud.com/application/schema.owl#PartnerRoleRecord | Yes |
MX_FIELD_URI | The CPQ field URI is the one that was customized inside the application-schema-ext.owl having the domain as PartnerRoleRecord. For example, http://www.inmindcloud.com/application/application-schema ext.owl#zAccountPartnerRoleRecordXxxXxxXxx | No |
CFC_FIELD_NAME | The C4C field name is the one created in C4C. For example, it must start with the prefix.a00:zAccountAccountPartnerRoleRecordXxxXxxXxx | No |
CFC_FIELD_NAME_SPACE | The name space of the custom field. For example, http://sap.com/xi/AP/CustomerExtension/BYD/A0014 | No |
CFC_XPATH | //Customer/Relationship[RelationshipBusinessPartnerUUID='PartnerRoleRecord.objectExternalId //Customer/Relationship[RelationshipBusinessPartnerUUID='PartnerRoleRecord.objectExternalId' | Yes |
Import account contact custom field from C4C
For account contact custom field mapping, you must set the properties shown in the following table, where MX_GRAPH_TYPE_URI, MX_SUBJECT_TYPE_URI and CFC_XPATH are fixed.
FIELD NAME | FIELD VALUE and Description | Fixed |
---|---|---|
MX_GRAPH_TYPE_URI | http://www.inmindcloud.com/application/schema.owl#Account | Yes |
MX_SUBJECT_TYPE_URI | http://www.inmindcloud.com/application/schema.owl#Contact | Yes |
MX_FIELD_URI | The CPQ field URI is the one that was customized inside the application-schema-ext.owl having the domain as Contact. For example, http://www.inmindcloud.com/application/application-schema-ext.owl#zContactXxxXxxXxx | No |
CFC_FIELD_NAME | The C4C field name is the one created in C4C. The following is an example field name. It must start the prefix: a00:zAccountContactXxxXxx | No |
CFC_FIELD_NAME_SPACE | Name space of the custom field. Following is an example namespace used for the custom field: http://sap.com/xi/AP/CustomerExtension/BYD/A0014 | No |
CFC_XPATH | //Contact | Yes |