# IDocs for SAP PP: LOIPRO, LOIROU and PORDCR Configuration and Monitoring > Source: https://netray.co/erp-help/sap-pp-idocs-loipro-loirou-pordcr-config-monitoring > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer SAP PP exchanges production data with other systems such as an MES or APS through ALE IDocs. Message types commonly met are LOIPRO for production and process orders, LOIROU for routings and PORDCR for creating process orders. The setup is the usual ALE chain: logical system, port, partner profile, distribution model and monitoring in WE02 and BD87. ## Kind advanced ## System sap ## Erp SAP ECC / S/4HANA ## Module PP ALE / IDoc Integration ## Query idoc for sap pp ## Alternate Queries - LOIPRO IDoc - LOIROU IDoc routing - PORDCR IDoc process order create - sap pp production order idoc configuration ## Applies To SAP ECC 6.0 and S/4HANA on-premise; exact basic types and availability depend on release, so confirm in WE81/WE30 before building ## Steps ### How to configure and monitor PP IDocs **Items:** - Confirm the message type and basic type you need: check WE81 (message types) and WE30 (IDoc types) for the PP types in your release. - Create the logical systems and RFC destination for the partner (SALE, SM59) and a port (WE21), for example a tRFC or file port. - Create a partner profile in WE20 with the message type, process code and the processing mode: immediate or collected, with a trigger. - Define a distribution model in BD64 with the sender, receiver and message type, and generate partner profiles if needed. - Test an outbound document using WE19 or by triggering the business event, then see the IDoc in WE02 (list) or WE05. - For inbound, assign the process code (WE42) and function module (WE57) and enable the correct authorization and user. - Reprocess failed IDocs with BD87 after fixing the cause, and set up a monitoring job or alert for status 51 and 02 errors. ## Sections ### Which IDocs belong to PP **Body:** LOIPRO carries production or process order data out of SAP, typically to an MES or a scheduling system, and is generally paired with a trigger on release or change of the order. LOIROU carries routing data. PORDCR creates process orders from an external request, and is used in process industry set-ups. Others exist for BOMs, materials and work centers (for example BOMMAT and MATMAS). Confirmations from the shop floor commonly arrive by BAPIs or interface-specific inbound types rather than a standard IDoc, so check what your integration partner actually sends. Treat the names above as pointers, and confirm basic types and segments in WE60 for your release before you design the interface. ### Configuration chain **Body:** ALE configuration follows the same pattern for any message type: logical system names (SALE), RFC destinations (SM59), ports (WE21), partner profiles (WE20) and the distribution model (BD64). Errors almost always come from one link in that chain, such as a missing partner profile entry for the message type or a wrong process code. For outbound PP data, the trigger is often a change pointer or output determination. Check that the message type is active for change pointers (BD50, BD52) if the interface depends on them, and that the batch job RBDMIDOC runs. ### Monitoring and error handling **Body:** WE02 and WE05 show IDoc status. Outbound problems commonly show as status 02 (error passing data to port) or 29 (ALE service layer error). Inbound problems show as status 51 (application document not posted). Fix the cause, then use BD87 or WE19 to reprocess. Most 51 errors in PP are data problems: missing material in the plant, a closed period or a missing production version. See the status 51 page for general handling. Build a daily check that counts IDocs by status and message type. A growing count of 51 or 02 is the earliest warning sign of a broken interface. **Code:** - WE02 / WE05 IDoc lists and display - WE19 Test tool - WE20 Partner profiles - WE21 Ports - WE42 Inbound process codes - BD64 Distribution model - BD87 Status monitor and reprocessing ## Pitfalls - Assuming IDoc names from forums without checking WE30 and WE81 in your release. - Setting up the partner profile but not the distribution model, so nothing is sent. - Reprocessing in bulk without fixing master data, which only recreates the same errors. - Leaving the collect and send job unscheduled so outbound IDocs wait at status 30. - Using a dialog user that is later locked for the inbound processing user. ## Ai Angle Integration teams spend most of their time finding why a specific IDoc failed and which data it refers to. Netray's ERPray can run this kind of lookup in plain language against your own SAP system, read-only by default, showing the query it ran and respecting SAP authorizations, with the model served on your own hardware when the system is on-prem. It explains and finds the data; it does not replace configuration decisions or post documents without human approval. ## Faq ### What is LOIPRO in SAP? **Answer:** LOIPRO is the message type used to send production or process order data from SAP, typically to an external execution or scheduling system. Confirm its basic type and segments in WE30 for your release. ### How do I resend a failed PP IDoc? **Answer:** Fix the cause, such as the missing master data, then reprocess with BD87 for inbound errors. For outbound, use WE19 or re-trigger the document, after checking port and partner profile settings. ### Which transactions monitor IDocs? **Answer:** WE02 and WE05 list and display IDocs, BD87 shows a status monitor and reprocesses, and WE19 is the test tool. SM58 shows stuck tRFC calls on outbound ports. ### Do I need IDocs, or can I use BAPIs? **Answer:** Both work. IDocs suit asynchronous, queued exchange between systems, while BAPIs and APIs suit synchronous calls. Many modern interfaces use APIs or the SAP Integration Suite instead. ## Search terms idoc for sap pp, LOIPRO idoc, LOIROU idoc, PORDCR idoc, sap pp idoc configuration, WE20 partner profile, BD87 reprocess idoc, sap production order idoc mes --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json