In Mind Cloud Digital Sales Platform (DSP) provides the importing of internal quotes and importing external quotes which is a sales quote created in DSP from Account or Opportunity imported from C4C. The data point used in the import process can be found in 'DSP and CPQ Quote Data Mapping for Export Processes'. As the DSP needs the company assigned while creating/synchronizing a quote, the company assigned to the employee will be assigned automatically while creating a quote from C4C.
Internal Quote
The internal quote is defined if the quote is created in C4C and then imported to DSP. For the internal quote, the user can edit the quote data not only in the C4C but also in the DSP. The addition or deletion of line items data should be done in the DSP to prevent the inconsistencies of the line-item table between the DSP and C4C as the DSP will mainly be used for the Configuration and Pricing modules. The updating of line-item data such as Quantity and List Price in CFC is allowed, and the DSP will update those data on subsequent imports if changes or inconsistent last change state IDs are found.
External Quote
The external quote means that the quote was created outside from C4C. The external quote can be created from two ways. First path is by importing the account from C4C and create a quote from that Account and export it back to C4C. The second path is by importing the opportunity from C4C and create a quote from that opportunity.
The image below refers to Exporting Quote to C4C as External Quote (Account to Quote Integration).
The image below refers to Exporting Quote to C4C as External Quote (Opportunity to Quote Integration).
Using Product Object External ID to search for Product from C4C in DSP
For every import of quote, it is necessary to have the product with correct objectERPId assigned. Only those products having objectERPId assigned can be searched using the internal ID of product in C4C. Those products with invalid objectERPId assigned will be ignored to import.
Understanding the Sales Document Status Mapping
The life cycle of the quote can be managed by either C4C or DSP. However, there are limitations and Pro and Con due to the technical architectures between the two systems.
Approval Process in C4C
This scenario happened when the submission of the quote is done inside the C4C and the DSP is configured to disable the approval engine in DSP ( See Also Section 4.7 Deactivating the Approval Flow in MX ).
In this scenario, the Sales Document Status of a Quote in DSP is mapped to the three statuses of a Quote in C4C. Therefore, it needs to use the C4C to make the Quote in DSP editable by setting as PENDING if the quote has been submitted in C4C. The following are the three statuses code used in the Sales Document Status Mapping.
- Status Code
- Progress Code
- Approval Code
The following table shows how the DSP changes the Sales Document Status depending on the three statuses code in C4C.
DSP SALES DOCUMENT STATUS |
STATUS CODE |
PROGRESS CODE |
APPROVAL CODE |
---|---|---|---|
OPEN |
Open |
Not Relevant |
Not Started |
OPEN |
Open |
Not Relevant |
In Revision |
COMPLETED |
Open |
Not Relevant |
In Approval |
COMPLETED |
Open |
PENDING |
Not Started |
COMPLETED |
|
|
|
APPROVED |
Open |
Not Relevant |
Approved |
APPROVED |
Open |
Pending |
Approved |
APPROVED |
Completed |
Pending |
Approved |
PENDING |
|
Pending |
|
ACCEPTED |
Completed |
Won |
Approved |
ACCEPTED |
Completed |
Won |
Not Started |
ACCEPTED |
Completed |
Won |
Approval Not Necessary |
ACCEPTED |
Completed |
Won |
Not Found |
ACCEPTED |
Completed |
Won |
In Approval |
ACCEPTED |
Completed |
Won |
In Revision |
ACCEPTED |
Completed |
Won |
Withdrawn |
REJECTED |
Completed |
Lost |
Not Started |
REJECTED |
Completed |
Lost |
Not Started |
It is necessary to note that there are limited functionality in PENDING status.
The following is a list of constraints when Quote in DSP is having the PENDING status.
- When the Quote is in PENDING status, on import of that Quote to DSP will change the Sales Item Status to have the PENDING status as well. Sales Item with PENDING status is not allowed to delete or add sub Sales Item under it. If the Sales Item is having the Configurable Product, it is not allowed to make changes. However, Sales Item with PENDING status is allowed to change the Quantity to get the new Price.
- In PENDING status, it is allowed to add new Product ( which could be Configurable Product or Classified Product or Raw Product ). If the product added was a configurable product, it is allowed to do the configuration. In additional to that, the product added in PENDING status can also be removed from the quote as long as the Sales Item Status is not having PENDING status.
- Repricing is allowed in PENDING status by adding new product, changing quote header information such as Currency, Pricing Date, and changing Quantity of the Sales Item.
The following diagram shows the recommended process that has to be done if the Quote Life Cycle is controlled in C4C. The most important thing is to click the DSP tab especially if the following the pricing relevant changes were made before the submission of the Quote in C4C in order to synchronize the pricing related changes to do reconfiguration or pricing when the Quote in DSP is still OPEN.
Approval Process in DSP
This is for the case where approval engine is configured in DSP. Therefore, the complete life cycle of the Quote is managed by DSP and submission is to be done in DSP and the submission trigger in C4C must be disabled. However, it needs to define the CPQQuoteStatus in C4C to show the latest status of the Quote in DSP. It is also recommended to enable or disable the line item table based on that value of CPQQuoteStatus ( example if the CPQQuoteStatus is not in OPEN state, the line item table should be disabled to align with the behaviour that is allowed in DSP). If the user made some changes while the CPQQuoteStatus is not OPEN that could trigger the pricing in DSP, on import of that changes, DSP will ignore the changes as the Quote in DSP is not OPEN.
Note: Since complete quote life cycle is managed in DSP, it is recommended to do the CRUD operation of line item data in DSP in order to reduce the inconsistencies between two systems.
Importing Partners of Quote from C4C
C4C Partner |
DSP Equivalent |
Quote C4C Import |
Remark/Reason |
---|---|---|---|
BILL_TO_PARTY |
Account |
Supported |
|
SHIP_TO_PARTY |
Account |
Supported |
|
BUYER_PARTY |
Account |
Supported |
|
PAYER_PARTY |
Account |
Supported |
|
SELLER_PARTY |
Account |
Supported |
|
SALES_EMPLOYEE_PARTY |
Employee |
Supported |
It needs to assign the externalId of user in DSP to the internalId of employee in C4C. |
EMPLOYEE_RESPONSIBLE_ PARTY |
Employee |
Supported |
It needs to assign the externalId of user in DSP to the internalId of employee in C4C. |
PRODUCT_RECIPIENT_PARTY |
Not supported |
Not supported |
Not Supported |
SALES_PARTNER_PARTY |
Account |
Not Supported |
Could be a Business Partner in C4C |
COMPETITOR_PARTY |
Account |
Not Supported |
Could be a Business Partner in C4C |
OTHER_PARTY |
Account |
Not Supported |
Could be a Business Partner in C4C |
SALES_UNIT_PARTY |
Company |
Not Supported |
|
SALES_TEAM_PARTY |
Not supported |
Not Supported |
|
By default, the partners will not be synchronized. If you want to synchronize the partners by default, it is necessary to set the following setting.
- Go to Administration -> SettingBoolean
- Search for SettingSyncPartnerQuoteEnabled
- Set Setting Value Boolean to YES
Importing Quote with Custom Field from C4C
WIth Release20/11, DSP supports to import the custom fields to the following SUBJECT TYPE within the Quote dataset.
- Quote
- SalesItem
- PartnerFunctionRecord
Importing Quote Header Custom Field from C4C
For Quote 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 EXPLANATION |
FIXED |
---|---|---|
MX_GRAPH_TYPE_URI |
Yes |
|
MX_SUBJECT_TYPE_URI |
Yes |
|
MX_FIELD_URI |
The DSP field URI is the one that was customized inside the application-schema-ext.owl having the domain as Quote. The following is an example URI. http://www.inmindcloud.com/application/application-schema-ext.owl#zQuoteXxxXxxXxx |
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:zQuoteXxxXxxXxx |
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 |
//CustomerQuote |
Yes |
Importing Quote Line Item Custom Field from C4C
For Quote Line Item 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 EXPLANATION |
FIXED |
---|---|---|
MX_GRAPH_TYPE_URI |
Yes |
|
MX_SUBJECT_TYPE_URI |
Yes |
|
MX_FIELD_URI |
The DSP field URI is the one that was customized inside the application-schema-ext.owl having the domain as SalesItem. The following is an example URI. http://www.inmindcloud.com/application/application-schema-ext.owl#zQuoteSalesItemXxxXxxXxx |
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:zQuoteSalesItemXxxXxxXxx |
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 |
//CustomerQuote/Item[ID='SalesItem.objectExternalId'] |
Yes |
Importing Quote Partner with Custom Field from C4C
For Quote Partner 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 EXPLANATION |
FIXED |
---|---|---|
MX_GRAPH_TYPE_URI |
Yes |
|
MX_SUBJECT_TYPE_URI |
http://www.inmindcloud.com/application/schema.owl# PartnerFunctionRecord |
Yes |
MX_FIELD_URI |
The DSP field URI is the one that was customized inside the application-schema-ext.owl having the domain as PartnerFunctionRecord. The following is an example URI. http://www.inmindcloud.com/application/application-schema-ext.owl#zQuotePartnerXxxXxxXxx |
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:zQuotePartnerXxxXxxXxx |
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 |
The following are list of supported XPath for Quote Partners //CustomerQuote/PayerParty //CustomerQuote/BillToParty //CustomerQuote/BuyerParty //CustomerQuote/ProductRecipientParty |
Yes |
Comments
0 comments
Article is closed for comments.