SAPFree referencePDF, Excel, Word exportSAP S/4HANA

SAP PP Transaction Codes List: Production Orders, MRP, BOM, Routing

SAP PP has a lot of transactions, and most consultants only remember the ones they used on their last project. This list groups the production planning codes by job: orders, confirmation, MRP, demand, BOM, routing, work centers and capacity. Search by code or by words such as 'release' or 'where-used'.

Download:

T-code	Area	What it does
CO01	Production orders	Create a production order for a material and plant
CO02	Production orders	Change a production order (dates, quantity, components, status)
CO03	Production orders	Display a production order
CO05N	Production orders	Collective release of production orders
CO11N	Confirmation	Enter a time ticket confirmation for an operation
CO15	Confirmation	Enter a production order confirmation with yield and goods movements
CO13	Confirmation	Cancel a production order confirmation
COOIS	Reporting	Order information system: list orders, operations, components
COHV	Mass processing	Mass processing of orders (release, schedule, TECO, etc.)
COGI	Goods movements	Postprocess goods movements that failed during confirmation
CO24	Reporting	Missing parts information system for production orders
CO09	Availability	Material availability overview for an order
CO27	Material staging	Pick list for production order components
KO88	Settlement	Actual settlement of a single production order
CO88	Settlement	Collective actual settlement of production orders
MD01	MRP run	MRP run for the whole plant (total planning)
MD01N	MRP run	MRP run for the plant using the newer interface
MD02	MRP run	Single-item, multi-level MRP run
MD03	MRP run	Single-item, single-level MRP run
MD04	MRP evaluation	Stock/requirements list for one material and plant
MD05	MRP evaluation	Display the MRP list for a material
MD06	MRP evaluation	Collective display of MRP lists
MD07	MRP evaluation	Collective display of stock/requirements lists
MD11	Planned orders	Create a planned order manually
MD12	Planned orders	Change a planned order
MD13	Planned orders	Display a planned order
MD14	Planned orders	Convert a planned order to a purchase requisition
MD16	Planned orders	Collective display of planned orders
MD20	MRP master	Create planning file entry for a material
MD21	MRP master	Display planning file entries
MD50	MRP run	Single-item, multi-level planning for a sales order (make-to-order)
MD61	Demand	Create planned independent requirements
MD62	Demand	Change planned independent requirements
MD63	Demand	Display planned independent requirements
MD73	Demand	Display total requirements (all independent requirements)
CS01	BOM	Create a material BOM
CS02	BOM	Change a material BOM
CS03	BOM	Display a material BOM
CS07	BOM	Allocate an existing BOM to another plant
CS11	BOM reports	BOM explosion, level by level
CS12	BOM reports	BOM explosion, multilevel
CS13	BOM reports	BOM explosion, summarized
CS15	BOM reports	Where-used list for a material
CS20	BOM	BOM mass change
CA01	Routing	Create a routing
CA02	Routing	Change a routing
CA03	Routing	Display a routing
CA11	Routing	Create a reference operation set
CA85	Routing	Mass replacement of work centers in task lists
CR01	Work center	Create a work center
CR02	Work center	Change a work center
CR03	Work center	Display a work center
CR05	Work center	Work center list
CM01	Capacity	Capacity load evaluation by work center
CM25	Capacity	Capacity planning table for leveling
C223	Master data	Maintain production versions for a material
MM02	Master data	Change material master (MRP, work scheduling views)
MMBE	Stock	Stock overview by plant, storage location, batch

Codes are shown for SAP ERP and SAP S/4HANA on-premise. Some transactions are replaced by Fiori apps in S/4HANA, and a few older codes are flagged obsolete in later releases; check the simplification list for your release before relying on a code.

Ask your SAP PP data in plain English

Optional: see how a read-only natural language layer over SAP production orders and MRP data would work in your landscape.

Optional. The tool and every export work without this. No spam.

How to use the list

Type part of a code or a keyword in the search box to filter the table. Use the Area column to read one workflow end to end, for example the MD group for an MRP run and review. Export to Excel if you want to hand a team new to PP a one-page cheat sheet, or paste the codes into a training document. The list is read-only and does not connect to any SAP system.

How the codes group in practice

Master data is the first layer: material master (MM02), BOM (CS01 to CS03), routing (CA01 to CA03), work center (CR01 to CR03) and production version (C223). Demand and planning come next: planned independent requirements (MD61), the MRP run (MD01, MD02, MD03) and evaluation (MD04, MD05, MD07). Execution follows with CO01, release, confirmation and goods movement fixes in COGI. Finally settlement (KO88, CO88) closes the order.

Single-item runs (MD02, MD03) are the safest way to test a change on one material.
MD04 is the most used screen for planners; MD07 is its collective version.
COOIS and COHV are the two tools for working through many orders at once.

Common mistakes

Planners often change a BOM or routing and then wonder why MRP shows nothing new. The planning file entry (MD20, MD21) decides whether a material is picked up in net change runs, and master data changes normally set it automatically only when the material is MRP relevant. Another frequent issue is confirming with CO15 when goods movements fail, leaving stock unposted until COGI is worked. Check COGI daily.

Frequently Asked Questions

Which transaction shows MRP results for one material?

MD04 is the stock/requirements list, showing current stock, planned orders, production orders, purchase requisitions and requirements in date order. MD05 shows the saved MRP list from the last planning run, which can differ from the live view in MD04 if things have changed since.

What is the difference between CO01 and converting a planned order?

CO01 creates a production order directly for a material. Orders created from a planned order are normally converted through the planned order screens or collective conversion transactions, which carry over quantity, dates and the production version from the planned order.

Are these codes valid in S/4HANA?

Most of them still work in S/4HANA on-premise, but several have a Fiori app equivalent and MD01N or MD01 behaviour depends on release. Always check the S/4HANA simplification list for your target release before standardising on a code.

Can I add my own custom Z transactions?

Export the table to Excel and add a column for your Z-codes and the report each calls. Many plants have custom order lists and shortage reports that planners actually use more than the standard ones, so documenting them next to the standard codes is useful.

If your planners spend time hunting through SAP screens for answers, Netray can set up a read-only natural language layer over your PP data so they can ask for open orders or shortages directly.

Talk to an Expert Explore More Free Tools