Custom IDoc Development for Business Processes

A Step-by-Step Guide to Building Your Own IDoc Interface (Even if You’ve Never Done It Before) Most SAP consultants use IDocs… But very few know how to actually build an IDoc interface from scratch. Here is a simple, complete, real-world guide you can follow step-by-step 👇 (This is the same approach used in PP/MM/MES/EWM integrations.) 1️⃣ Define the business scenario Before touching SAP, answer 3 questions: • What data needs to be exchanged? (Production order, material, GR…) • Who sends and who receives? (SAP → MES, MES → SAP, etc.) • When is the message triggered? (Creation, change, confirmation…) 📌 Clarity here = no rework later. 2️⃣ Identify the right Message Type & Basic Type Example: • LOIPRO → Production orders • MATMAS → Material master • DELVRY → Deliveries • ORDERS → Purchase orders Check with: WE60 → IDoc documentation WE81 / WE82 → Message types & Basic types 📌 This tells you the structure of the IDoc. 3️⃣ Configure the ALE Layer This is where most interfaces fail. Steps: ✔ Create a Logical System (SALE) SAP_SENDER MES_RECEIVER ✔ Assign logical systems to clients (SCC4) ✔ Create a RFC destination (SM59) Type: TCP/IP or ABAP → depends on middleware/MES. ✔ Create Port (WE21) Usually: tRFC + RFC destination ✔ Create Partner Profile (WE20) Outbound parameters: • Message type • Basic type • Port • Output mode (immediate, collect…) 📌 If WE20 is wrong → IDoc never leaves SAP. 4️⃣ Create the Distribution Model (BD64) Add: • Sender system • Receiver system • Message type (ex: LOIPRO) Generate Partner Profiles (menu option). 📌 BD64 tells SAP: “Send this IDoc to this partner.” 5️⃣ Trigger the IDoc Example for LOIPRO (production order): • Create/Change order → SAVE • SAP automatically generates IDoc in status 03 • Check with WE02 / WE05 For inbound IDocs (MES → SAP): • IDoc arrives → processed via function module linked to the message type. 📌 Trigger = event that fires the interface. 6️⃣ Map & Validate Data (Middleware or SAP) Segments → business fields Example LOIPRO: • E1AFKO → order header • E1AFVC → operations • E1RESB → components 📌 This is where MOST integration complexity lives. 7️⃣ Debug Errors (Status 51) Tools: • WE02 / WE05 → Analyze • BD87 → Reprocess • WE19 → Test IDoc manually (super useful!) • SLG1 → Application logs • ST22 → Dumps 📌 90% of failures = missing master data or wrong partner setup. 8️⃣ Move to Production (Transport + Connectivity) Checklist: ✔ Logical systems consistent ✔ RFC destinations pointing to correct servers ✔ Ports & partner profiles transported ✔ Middleware/MES connection tested ✔ IDoc test end-to-end validated 📌 Do a full roundtrip test — both outbound AND inbound. #SAP #IDoc #S4HANA #Integration #SAPPP #SAPMM #MES #EWM #SAPTips #ERP #Manufacturing #SAPConsultant #ProductionPlanning

How I convinced a project to choose IDOCs — Second line: Turned out to be the best decision we made. — What was the scenario? A plant was sending quality results from an external lab back into SAP. Daily. 3000+ records. Initial design? Custom CSV files on FTP. Every week: • Missing files • Wrong decimal format • Job failures Production was waiting. Nobody knew where data got stuck. — Why IDOCs? Because the two systems did not need to talk in real-time. Lab sent results whenever they finished: 7 PM Midnight Next morning So we needed: ✔ Asynchronous ✔ Guaranteed delivery ✔ Re-processing ✔ Monitoring That is exactly what IDOCs do. — When to choose IDOCs? (Simple rule) Use IDOCs when timing is unpredictable, but data must arrive and be traceable. I shared a small analogy with the team: Coffee machine at 9:00 People drink at 11:00 No problem. That’s IDOC-style integration. Decoupled time. No pressure. But an API? Someone must drink at the same minute. If they don’t, alarms go off. That helped everyone understand. — How we implemented Step 1 — Standard IDOC We found QALITY01 covered inspection data. Step 2 — Partner Profile WE20 Outbound from SAP Step 3 — Port RFC to middleware Step 4 — Mapping Segment → Characteristic → Value Worked closely with ABAP Step 5 — Monitoring Trained plant users: WE02 / WE05 Reprocess if red Raise ticket if stuck — Real results after go-live Before: ❌ Missing files ❌ Manual uploads at midnight ❌ 3 days delay in quality approval After IDOCs: ✔ 0 missing records ✔ Full traceability ✔ Faster release ✔ Audit-friendly Nobody talked about CSV again. — Key takeaway: Technology is not fashion. It’s context. IDOCs win when • High volume • Unpredictable timing • Guaranteed delivery • Monitoring matters — Your turn: Where have IDOCs saved your project?