The user can export an account from C4C to MX where he/she can create an opportunity or quote in MX and then export the quote back to C4C from MX.
During the exporting of the account from the C4C to MX, the MX will also synchronize the account related data including addresses and contacts of the account. Once the web service has been setup in C4C using HTML Mashup or URL Mashup, the user can export an Account from the C4C system into MX. For the HTML Mashup, depending on where you place the embedded component, the MX login page will be shown there inside the C4C system.
- Log in to our system MX if SSO was not configured in the system.
- After logging in successfully, the account will be exported to MX if the account was not found in MX or it will be synchronized if the account was already inside the MX. The image above shows an example of the Account View of MX inside the C4C system.
While importing the account from C4C, MX will also synchronize the account if the account from C4C already exists in MX. The following processes will be done during synchronization:
- Updating the account header such as account name, account status (such as active/inactive), account ECC ID, industry, main address, etc.)
- Importing the Sales Info
- Creating New Addresses and Contacts
- Importing new addresses from C4C.
- Importing new contacts found inside the C4C.
- Deleting Non-Used Addresses and Contacts
- Deleting addresses of accounts with an external ID which are not found in C4C as well as those which are not used in other business objects.
- Deleting contacts of accounts with an external ID which are found in C4C as well as those which are not used in other business objects.
The synchronise button will also be appear in the Account Details page as well as inside the account overview page for those accounts which were imported from external systems such as (C4C/SFDC).
Importing Account with Custom Field from C4C
In 2011, MX supports to import the custom fields to the following SUBJECT TYPE within an Account dataset.
- Account
- Address
- PartnerRoleRecord
Importing Account Header Custom Field from C4C
For account header custom field mapping, it needs to set the following properties where MX_GRAPH_TYPE_URI, MX_SUBJECT_TYPE_URI and CFC_XPATH are fixed.
FIELD NAME |
FIELD VALUE or EXPLAINATION |
FIXED |
---|---|---|
MX_GRAPH_TYPE_URI |
http://www.inmindcloud.com/application/schema.owl#Account |
Yes |
MX_SUBJECT_TYPE_URI |
Yes |
|
MX_FIELD_URI |
The MX field URI is the one that was customized inside the application-schema-ext.owl having the domain as Account. The following is an 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 the prefix. a00:zAccountXxxXxxXxx |
No |
CFC_FIELD_NAME_SPACE |
The name space of the custom field. The following is an example namespace used for custom field. http://sap.com/xi/AP/CustomerExtension/BYD/A0014 |
No |
CFC_XPATH |
//Customer |
Yes |
Importing Account Address Custom Field from C4C
For account address custom field mapping, it needs to set the following properties where MX_GRAPH_TYPE_URI, MX_SUBJECT_TYPE_URI and CFC_XPATH are fixed.
FIELD NAME |
FIELD VALUE or EXPLAINATION |
FIXED |
---|---|---|
MX_GRAPH_TYPE_URI |
http://www.inmindcloud.com/application/schema.owl#Account |
Yes |
MX_SUBJECT_TYPE_URI |
Yes |
|
MX_FIELD_URI |
The MX field URI is the one that was customized inside the application-schema-ext.owl having the domain as Address. The following is an example URI. 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. The following is an example field name. It must start with the prefix. a00:zAccountAddressXxxXxx |
No |
CFC_FIELD_NAME_SPACE |
The name space of the custom field. The following is an example namespace used for custom field. http://sap.com/xi/AP/CustomerExtension/BYD/A0014 |
No |
CFC_XPATH |
//Customer/AddressInformation[UUID='Address.objectExternalId'] |
Yes |
Importing Account Relationship Custom Field from C4C
For account relationship custom field mapping, it needs to set the following properties where MX_GRAPH_TYPE_URI, MX_SUBJECT_TYPE_URI and CFC_XPATH are fixed.
FIELD NAME |
FIELD VALUE or EXPLAINATION |
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 MX field URI is the one that was customized inside the application-schema-ext.owl having the domain as PartnerRoleRecord. The following is an example URI. http://www.inmindcloud.com/application/application-schema-ext.owl#zAccountPartnerRoleRecordXxxXxxXxx |
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 starts the prefix. a00:zAccountAccountPartnerRoleRecordXxxXxxXxx |
No |
CFC_FIELD_NAME_SPACE |
The name space of the custom field. The following is an example namespace used for custom field. http://sap.com/xi/AP/CustomerExtension/BYD/A0014 |
No |
CFC_XPATH |
//Customer/Relationship[RelationshipBusinessPartnerUUID ='PartnerRoleRecord.objectExternalId'] |
Yes |
Importing Account Contact Custom Field from C4C
For account contact custom field mapping, it needs to set the following properties where MX_GRAPH_TYPE_URI, MX_SUBJECT_TYPE_URI and CFC_XPATH are fixed.
FIELD NAME |
FIELD VALUE or EXPLAINATION |
FIXED |
---|---|---|
MX_GRAPH_TYPE_URI |
http://www.inmindcloud.com/application/schema.owl#Account |
Yes |
MX_SUBJECT_TYPE_URI |
Yes |
|
MX_FIELD_URI |
The MX field URI is the one that was customized inside the application-schema-ext.owl having the domain as Contact. The following is an example URI. http://www.inmindcloud.com/application/application-schema-ext.owl#zContactXxxXxxXxx |
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 the prefix. a00:zAccountContactXxxXxx |
No |
CFC_FIELD_NAME_SPACE |
The name space of the custom field. The following is an example namespace used for custom field. http://sap.com/xi/AP/CustomerExtension/BYD/A0014 |
No |
CFC_XPATH |
//Contact |
Yes |
Comments
0 comments
Article is closed for comments.