At this point, we have understood how to configure the IFlows. Next, we will examine how the real-world client requirements, specifically replicate Sales Pricing Condition records from ECC to S4HANA, are implemented in SAP CPI. In this section 1 of the IFlow walkthrough, we will explore the client requirements and their execution in the SAP system. Additionally, we will review the steps involved in the IDOC transfer from ECC to CPI.
Overview of this blog series:
1. SAP CPI Introduction
2. SAP BTP tools and features overview (BTP, Global Account, Sub-Account, Entitlements, Connectivity, Security)
3. SAP CPI Web IDE overview
4. Registering a trial account and enrolling to SAP CPI service
5. Deep dive into Cloud Integration features with real world scenario example
6. Use cases of palette functions
7. Adapter configurations
8. Using Cloud connector for connecting to backend SAP systems
9. Overview on API Management & Open Connectors
10. Integration using Open Connectors with real world example
In short, below is the content we will elaborate in this tutorial:
1. Functional Requirement from Client
2. IFlow Design
3. Functional Understanding of requirement
4. IDOC Connectivity steps
1. Functional Requirement from Client
The rundown of the prerequisite is to fabricate a connection point among ECC and S4HANA, where the deals estimating condition records made in ECC should be repeated in S4HANA. Just two tables are considered for this replication.
This includes:
- Creation of Condition Record
- Updating the Condition Record
- Delimitation of Existing Condition Record
- Deletion of Condition Record
- Creation of Condition Record and Scales Creation
- Updating Condition Record and Scales Creation
- Updating Condition Record and Scales Update
- Deletion of Scales
2. IFlow Design
Below is the developed IFlow for the requirement.
Sender – IDOC connector
Receiver – OData/HTTP connector
For production of condition record-OData POST activity is utilized.
For update of condition record – HTTP Fix activity is utilized (through clump mode).
3. Functional Understanding of Requirement
Creation/Update/Erase of condition records in ECC/S4 is finished in TCodes – VK11/VK12/VK13. In this connection point, we are utilizing numerous tables to make/update/erase the condition records. Be that as it may, in the clarification, we will cover one table for instance.
Values should have been passed for making of condition record – Material/Sum/Money Unit/UOM/Legitimate Beginning Date/Substantial End Date.
Delimitation of Condition Record
For the above made condition record where the legitimate from and to is 01012020 to 31129999. How about we see the table sections for this condition record.
Presently the client has chosen to change the pace of the above material to 2000 EUR legitimate from 01.01.2021. In this way, client explores to VK11 and makes the new condition record.
You can find in the table, another condition record is made, where the main condition record gets terminated to 31122020 with sum 1000 EUR and second condition record is legitimate from 01012021 to 31129999.
This is the delimitation interaction.
Creation of Scales:
Scales can be made either in Make (VK11) or in Update (VK12) exchange.
4. IDOC Connectivity Steps
With respect to IDOC network arrangement from ECC to CPI, underneath moves toward be followed:
Prior to continuing on to the backend associations, how about we see the arranged IDOC Shipper connector.
Give the idoc shipper address and get the total URL. This should be given to Premise group to making RFC Objective.
1. Create Logical System in S4 System in Tcode BD54
2. Create RFC Destination of Type G (HTTP Connection to External Server) in Tcode SM59
Three fields to be given while the production of RFC objective. Have – Occupant URL, Port – 443, Way prefix – cxf/{endpoint gave in IDOC Source connector Address field}. For this situation it will be cxf/idoc/pricingcondition. Once made, check in the event that RFC ping objective is returning 500 reaction and a sign in CPI observing.
3. Port Creation in Tcode WE21 of port type XML HTTP. SOAP Protocol Option Should be Enabled for getting the http Status Response Back.
4. Partner profile Setup in Tcode WE20.
Accomplice type will be LS. Notice the message sort of the IDOC in the outbound area. For our situation, it will be COND_A.
Once finished, trigger the IDoc from the source system and check whether it’s arriving at CPI. In the next post (Section 2 of the project iFlow walkthrough), we will explore how to replicate Sales Pricing Condition records from ECC to S4HANA and how we transformed the client requirement into an interface.
Trust you got the hang of something helpful. Cheerful learning!!!
YOU MAY LIKE THIS
Your Definitive Guide to Becoming a SAP ABAP Developer
SAP MM Consultant Salary in india (2024)
10 Real-World SAP ABAP Programming Examples (with Code!)
WhatsApp us