CPI IDoc Part 2: Sending IDocs from Cloud Integration into S/4HANA
Full lesson currently free to read · AI practice limits apply separately
Post IDocs into S/4HANA from Cloud Integration: the IDoc receiver adapter calling S/4HANA's SOAP IDoc endpoint through Cloud Connector, service activation, partner profiles for inbound processing and handling of status 51 errors.
Visual overview
Explanation
📌 KEY POINTS
✅ The IDoc receiver adapter sends IDoc XML to S/4HANA's SOAP-based IDoc endpoint (SRTIDOC).
✅ On-premise S/4HANA is reached via Cloud Connector with the endpoint path allowed.
✅ Inbound partner profiles (WE20) define the process code for each message type.
✅ Status 53 means posted; status 51 means an application error that must be fixed and reprocessed.
⚠️ Treating 'IDoc delivered' as 'business document posted' hides application errors.
━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 covered outbound. Part 2 covers inbound IDocs into S/4HANA.
━━━━━━━━━━━━━━━━━━━━
▶ 1. THE ENDPOINT
S/4HANA can receive IDocs via a SOAP endpoint provided by the SRTIDOC service, which must be activated (SICF) and configured. The IDoc receiver adapter in Cloud Integration sends to this endpoint with the correct IDoc XML structure.
━━━━━━━━━━━━━━━━━━━━
▶ 2. CONNECTIVITY
For on-premise S/4HANA, the receiver adapter uses a Cloud Connector virtual host and location ID. The Cloud Connector must allow the IDoc endpoint path. Authentication uses a technical user with authorization to post IDocs, or principal propagation if required.
━━━━━━━━━━━━━━━━━━━━
▶ 3. PARTNER PROFILES
S/4HANA needs inbound partner profiles for the sender partner with message types and process codes that call the posting function. The control record values in the IDoc (sender partner, port, message type) must match, or the IDoc ends in error status.
━━━━━━━━━━━━━━━━━━━━
▶ 4. STATUS AND ERRORS
Inbound IDocs are created with status 64 (ready) and processed; 53 means the application document was posted, 51 means an application error such as missing master data. BD87 reprocesses after fixing causes. The iFlow's success only means the IDoc reached S/4HANA.
━━━━━━━━━━━━━━━━━━━━
▶ 5. MONITORING END TO END
Combine Cloud Integration message monitoring with IDoc status monitoring in S/4HANA, ideally through SAP Cloud ALM or alerts on status 51. Business owners should be informed of application errors they must fix.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Activate the SRTIDOC service in S/4HANA test.
- Expose the endpoint through Cloud Connector.
- Configure an IDoc receiver adapter and send a test IDoc.
- Cause a status 51, fix the master data and reprocess with BD87.
✅ CHECKPOINT: inbound IDocs post in S/4HANA and application errors are visible and reprocessed.
How the SAP process fits together
SAP PROCESS EXPLORER · Integration: sender to receiver
ERPClimb.comIDoc Integration with S/4HANA — process breakdown
Topic-specific conceptual flow: how key objects and decisions fit together. SAP configurations and exceptional cases can follow different paths.
Selected process stage
Configure
Ports, RFC destinations and partner profiles in S/4HANA
What this specific lesson teaches
Post IDocs into S/4HANA from Cloud Integration: the IDoc receiver adapter calling S/4HANA's SOAP IDoc endpoint through Cloud Connector, service activation, partner profiles for inbound processing and handling of status 51 errors.
Key lesson principle: The IDoc receiver adapter sends IDoc XML to S/4HANA's SOAP-based IDoc endpoint (SRTIDOC).
Representative SAP learning flow, not a guarantee of system runtime sequence in every scenario. The chapter-specific facts come from the published lesson text.
Real project scenario
A supplier integration reported 100% success in Cloud Integration, but finance found missing invoices. In S/4HANA, many IDocs were in status 51 because vendor master data was missing. An alert on status 51 routed to the procurement team and a daily reprocessing routine closed the gap.
Common mistakes
- Monitoring only Cloud Integration.
- Mismatched control record values.
- SRTIDOC not activated or not allowed in Cloud Connector.
- No owner for application errors.
Best practices
- End-to-end monitoring including IDoc status.
- Alerts on status 51 to business owners.
- Documented partner profiles.
- Reprocessing procedure with BD87.
Interview angle
Interviewers ask how Cloud Integration posts IDocs into S/4HANA through Cloud Connector, and how you monitor and reprocess status 51 application errors.
Frequently asked questions
How does Cloud Integration post IDocs into S/4HANA?
The IDoc receiver adapter sends IDoc XML to S/4HANA's SOAP IDoc endpoint provided by the SRTIDOC service, reached through Cloud Connector for on-premise systems, with a technical user authorized to post IDocs.
What do IDoc status 53 and 51 mean?
53 means the application document was posted; 51 means an application error such as missing master data. After fixing the cause, the IDoc is reprocessed with BD87.
Why isn't a successful iFlow enough to confirm posting?
A successful iFlow only means the IDoc reached S/4HANA. Posting can still fail there, so IDoc statuses must be monitored and status 51 alerted to business owners.
Practice this lesson
Original educational case studies for SAP consultants, not official SAP certification exam questions. Verify product edition and implementation details against the current SAP documentation.
Quick check
0 of 3 questions attempted
1. Which S/4HANA service receives IDocs via SOAP from Cloud Integration?
2. An inbound IDoc is in status 51. What does it mean?
3. Why monitor IDoc status in S/4HANA in addition to Cloud Integration?
Interview questions
1. How do you send IDocs from Cloud Integration into on-premise S/4HANA and make sure they post?
Answer it in your own words first, then compare.
Check before use: lesson examples are educational, not a guarantee of correctness for your SAP edition or release. Sample code has not been executed on your SAP system. Confirm API availability, syntax, authorizations and business impact in an approved development or test environment.