Technical Articles
SAP CLOUD FOR CUSTOMER INTEGRATION WITH S/4 HANA ON-PREMISE – PART II
This blog post is continuation to Part 1, which gives complete overview of Cloud for Customer Integration with S/4HANA On-Premise and Vice Versa.
For Part 1, refer below blog
https://blogs.sap.com/?p=1060139
Scenario II: Submit for External Document from cloud for customer which in turns creates either Sales quotation or Sales order based on the document type received in Target system
Step 1: Make sure, Cloud Connector is reachable
Step 2: In Cloud Platform Integration, Identify the right iFlows to deploy
- Login to CPI
- Navigate to Package => SAP Cloud for Customer Integration with SAP S/4HANA
- Navigate to Artifact => Create Sales quote Follow Up Document in SAP Business Suite
Step 3: In Cloud for Customer, Maintain Code List mapping
Step 4: In Cloud for Customer, Create Communication Arrangement for the respective artifacts
- Sales Quote Replication to SAP Business Suite
- Sales Quote Replication from SAP Business Suite
- Pricing in Sales Quote Replication Scenario in SAP Business Suite
- Sales Order Replication from SAP Business Suite
- Pricing in Sales Quote Follow Up Scenario in SAP Business Suite
- Request Sales Document Data from SAP Business Suite
- Creation of Sales Quote Follow Up Document in SAP Business Suite
Sample Communication Arrangement for Creation of Sales Quote Follow Up Document in SAP Business Suite: Outbound communication to be maintained here as shown below
Similarly maintain communication arrangement for all above mentioned ( Based on your scenario )
Step 5: In Cloud Platform Integration, deploy the relevant iFlow by maintaining right sender and receiver details
As mentioned in Step 5, For the artifact “Create Sales Quote Follow Up Document in SAP Business Suite” we need to maintain Sender and Receiver details as shown below
Similarly maintain Sender and Receiver details for all other iFlows in CPI.
Step 6: In S/4 HANA If the Sender adapter type is of “IDOC”, need to maintain below configuration
Transactions: WE20 & WE21
WE21 : Maintain Port
WE20 : Maintain Partner Profiles
Inbound : SALESORDER_CREATEFROMDAT2
Outbound : COD_REPLICATE_SALES_ORDER
Step 7: In S/4HANA, Check the “NACE” Configuration for Sales “V1”
Output Type to be configured
Step 8: We are executing below scenario from Cloud for Customer to S/4 HANA
Opportunity => Create Sales Quote (C4C)
=> Request External Pricing (From S/4 HANA)
=> Price will be replicated successfully in Cloud for Customer
=> Submit for External Document
=> Sales Order is created in S/4 HANA
=> Above created Sales Order is replicated in Cloud for Customer
Opportunity => Create Sales Quote (C4C)
In Cloud for Customer, Enter Document Type
In Cloud for Customer, Request External Pricing
In CPI, respective iFlow is deployed successfully
Price is calculated successfully from S/4HANA
Replicated Price Screenshot
In Cloud for Customer, Submit for External Document
In CPI, respective iFlow is deployed successfully
Sales Order “195” is successfully created in S/4HANA
Sales Order “195” is successfully replicated, screenshot from Cloud for Customer
Step 9 : Once the IDOC is successfully processed for both Inbound and Outbound
Transaction: WE05
That’s all, Hope you liked the multiple series of blog posts for Standard iFlows Integration
Conclusion
Hope these above screenshots/steps helps to cover standard integration scenarios for C4C & S/4HANA On-Premise.
Thanks,
Vijay Vegesana
Great blog Vijay! Thanks again for posting it.
Hi,
How sales area, sales office, sales group, and plants replicate from S/4 to C4C ?
Regards
Hi Damodar Damodar , for sales group and sales office you can use report: "COD_ERP_ORG_UNIT_EXTRACT" which uses message: "COD_ERP_SD_ORGS_SAVE"
Regards
Hi
We are trying to configure External Pricing in our C4C system and our Document Type in S4 for Sales Quote is QT and I have created a new document type (with external pricing) in C4C named ZQT. How do I map these two Document types? Please help
Vijay,
We are in the midst of adding C4C to a live S4HANA 1909 implementation (S4 has been live for 2+ years). Your blog references NACE based output to trigger the S4HANA outbound message COD_REPLICATE_SALES_ORDER.
During the implementation we deployed the new S4HANA Output Management based on BRF+. You cannot use NACE based output for some output types and BRF+ for other, so reverting back to NACE would require significant effort to redevelop all output based forms. Have you encountered this before, and if so, how did you address?
Sean