SAP PP Standard Reports: COOIS, CO46, MD04, CM01, CS12 and PPIO_ENTRY
sap pp standard reports
Also searched as
- standard report in sap pp
- report in sap pp
- sap report ppio_entry
- COOIS production order report
Short answer
The core standard reports in SAP PP are COOIS (order information system), CO46 (order progress), MD04 (stock and requirements list), CM01 (capacity load by work center), CS12 (multilevel BOM) and COGI (goods movement errors). PPIO_ENTRY is an entry point to the order information system with list-based selection for orders, operations and components.
Applies to: SAP ECC 6.0 and S/4HANA on-premise discrete and repetitive manufacturing; some reports differ in PP-PI
Which PP report to use
- 1To list production orders and their status, operations or components, use COOIS (or PPIO_ENTRY) with a layout for the columns you want.
- 2To see order progress and delays by operation, use CO46 (Order Progress Report) with your plant and MRP controller.
- 3To see supply and demand for one material, use MD04, with the exception messages and receipts and requirements by date.
- 4To check work center loading, use CM01 (capacity load, by work center) and CM02 for the work center overview for planning.
- 5To explode a BOM, use CS12 (multilevel) or CS11 (level by level), and CS13 for a summarized BOM.
- 6To find missing parts for released orders, use CO24; to clear goods movement errors from confirmations, use COGI.
- 7Save your selections as variants and layouts, so planners run the same report every day.
Order reports: COOIS, CO46 and PPIO_ENTRY
COOIS is the most flexible list. You choose the list type (headers, operations, components, sequences) and filter by plant, order type, status and dates. Use layouts to show fields such as target and confirmed quantity, scheduled start and finish, and system status.
PPIO_ENTRY is the generic entry screen of the order information system and, depending on release, is the route to the same list types with an initial screen for choosing orders, planned orders or other objects.
CO46 focuses on progress: it shows the orders and operations that are late or waiting, so supervisors can see where work is stuck.
Planning reports: MD04, MD05, CM01
MD04 is the stock and requirements list, the first stop when someone asks why a material is short. It lists receipts such as planned orders, production orders and purchase orders against requirements such as sales orders and dependent requirements.
MD05 is the MRP list from the last run, while MD04 is current. Use MD04 when you need today's state.
CM01 and the related capacity transactions show load against available capacity per work center. Run them with a time horizon that matches your planning window.
Master data reports: BOM and routing
CS12 shows a BOM across all levels, with quantities for a lot size. CS11 shows only the first level, and where-used lists are in CS15. For routings, CA03 displays a routing and CR05 lists work centers.
These are master data views, so they show the current valid state for a date. For past orders, check the order itself, because it keeps its own copy of the BOM and routing.
COOIS Order information system
CO46 Order progress report
MD04 Stock/requirements list
CM01 Capacity load by work center
CS12 Multilevel BOM
CO24 Missing parts info system
COGI Goods movements with errors
Try it here, free
SAP PP BOM Component Scrap and Requirements Worksheet
List components with quantity per, base quantity, assembly and component scrap, and see required quantity and cost for the order.
Common pitfalls
- !Using MD05 when you need current data; use MD04.
- !Not saving layouts, so each planner rebuilds columns every time.
- !Reading BOMs in CS12 for a past order, instead of the order's own components.
- !Ignoring COGI, which leaves stock and confirmations out of sync.
- !Running COOIS without status filters on a large system.
How an ERP-grounded AI assistant handles this
Planners often combine several of these screens to answer one question about a late order. 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.
Frequently asked questions
What is the difference between COOIS and CO46?
COOIS is a general list of orders, operations or components with flexible filters. CO46 is a progress report that highlights late or waiting orders, so it suits supervisors tracking shop floor delays.
What is PPIO_ENTRY?
It is the entry point to the production planning information system list reports for orders and related objects. Depending on release it leads to the same list types as COOIS.
How do I see all components of a production order?
Use COOIS with the component list type, filtered by order, or open the order with CO03 and look at the Components tab.
Which report shows MRP exceptions?
MD04 shows exception messages for one material, and MD06 gives a collective MRP list. MD07 shows the stock and requirements for the planning run result by material group.
Related
How to Read MD04 Exception Messages in SAP
The exception indicator in MD04 flags procurement elements whose date or quantity no longer matches the current demand situation - it is SAP's built-in change signal, read element by element in the detail screen, not just the header icon. Triage by exception group first, then decide to reschedule, cancel, or accept each one.
How-toSAP MD01N (MRP Live) vs MD01: How to Run MRP Correctly
MD01N is MRP Live: the same planning logic as classic MD01, but executed inside the SAP HANA database instead of looping through materials in ABAP. Run it from MD01N by entering the plant, choosing a processing key (net change or regeneration), setting the purchase requisition and scheduling parameters, and executing in the background for large scopes.
Error fixSAP CO11N Confirmation Errors and How to Fix Them
CO11N (time ticket confirmation for production/process orders) throws several distinct errors: deviation from the standard value is too large, goods movement not possible for a component, or the order/operation status does not allow confirmation. Each has a specific cause in order status, routing tolerance settings, or component availability, not a single generic fix.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
Error fixSAP Short Dump TIME_OUT: Maximum Runtime Exceeded
A TIME_OUT runtime error means a dialog (or RFC) work process ran longer than the maximum allowed runtime, controlled by profile parameter rdisp/max_wprun_time (600 seconds by default). The fix is almost always to move the long-running work to background processing or tune the underlying program, not to raise the timeout.
AI for ERPAI Agents for SAP Production Planning, MRP, and Exception Triage
AI agents that triage SAP MD04 exceptions, explain predictive MRP shortages, and draft planned-order actions, grounded on your own SAP data, deployed on-prem.
Stuck on SAP ECC / S/4HANA?
Talk to engineers who work inside SAP ECC / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP PP BOM Component Scrap and Requirements WorksheetList components with quantity per, base quantity, assembly and component scrap, and see required quantity and cost for the order.
- SAP PP Cutover Data Load TrackerAn editable tracker for PP master data loads during migration cycles, with load success rates and remaining records.
- SAP MD04 Exception Messages and MRP Elements ReferenceA searchable lookup of MD04 element abbreviations, key exception messages and the MRP transactions you use to act on them.
ERP fixes and how-tos
- Capacity Leveling in SAP PP, with an ExampleCapacity leveling in SAP PP step by step: find an overloaded work center in CM01, level with CM21 or CM25, dispatch options and the resulting schedule.
- How to Read MD04 Exception Messages in SAPMD04 exception icons tell a planner why a procurement element no longer matches demand. Read the element detail and act on it, not just rerun MRP.
- Planning Strategy 40 in SAP PP, with a Worked ExamplePlanning strategy 40 (planning with final assembly) with a worked MTS example: PIR consumption, MRP results in MD04, setup and common mistakes in SAP PP.
Integrations
- How to use ChatGPT with SAP ECC 6.0Using ChatGPT with SAP ECC 6.0: custom GPT actions, exports versus live access, an OData or MCP bridge, enterprise data controls, and when a private model is safer.
- How to automate email into SAP ECC 6.0Turn inbound emails into SAP ECC 6.0 transactions: customer POs into sales orders, supplier confirmations, RFQs and invoices, with review and BAPI posting.