How to Create a Plant in SAP MM and Configure the Organizational Structure
how to create plant in sap mm
Also searched as
- sap mm organizational structure configuration
- what is sap mm organization structure
- OX10 define plant
- assign plant to company code OX18
Short answer
Create a plant in the IMG under Enterprise Structure > Definition > Logistics - General > Define, copy, delete, check plant (OX10), then add storage locations (OX09), a purchasing organization, and assign the plant to a company code (OX18) and to a purchasing organization (OX17). The MM organizational structure is client > company code > plant > storage location, with purchasing organization and group on the procurement side.
Applies to: SAP ECC 6.0 and S/4HANA on-premise; transaction codes can differ in S/4HANA Cloud
How to create and wire up a plant
- 1Run OX10 (or IMG Enterprise Structure > Definition > Logistics - General > Define, copy, delete, check plant). Prefer 'Copy' from an existing plant, since it carries over settings.
- 2Enter the 4-character plant key, name, address, country, region, language and factory calendar in the plant details.
- 3Define storage locations with OX09 (Maintain Storage Location), each belonging to one plant.
- 4Define the purchasing organization (IMG Enterprise Structure > Definition > Materials Management > Maintain purchasing organization; OX08/OX01 depending on release) if you do not already have one.
- 5Assign the plant to a company code with OX18, and assign the purchasing organization to the plant with OX17. Assign the purchasing org to a company code (OX15) when it is company-code specific.
- 6Check valuation: confirm the plant's valuation level (usually plant) and that account determination exists for its valuation areas in OBYC.
- 7Extend master data: users can then extend material views to the new plant with MM01, and vendors with purchasing org data.
The MM organizational structure
The structure that matters in MM has two sides. The legal and accounting side is client > company code > plant > storage location; the plant is the main level for planning, valuation and stock, and the storage location is a physical stock separation inside it.
The procurement side is purchasing organization and purchasing group. A purchasing organization buys for one or more plants or for a company code, depending on whether it is plant-specific, company-code specific or cross-company-code. The purchasing group is a buyer or buyer team and is not tied to a plant.
Plant is also the key for MRP, production scheduling, and shipping or delivery points, so a complete plant needs settings from several modules, not just MM.
What a new plant also needs
A new plant is not usable until it has the basics: assignment to a company code, a purchasing organization, a valuation area setup with account determination, and a number range for material documents if your setup separates them by plant.
For production, add MRP and production settings such as MRP controller and production scheduler (set through the IMG paths for your release), and for sales a shipping point, loading group and the plant assignment in the sales area.
For intercompany or inter-plant flows, maintain the vendor number and customer number of the plant in the plant's details so stock transport orders can find them.
Copy versus create
OX10 offers Copy, with the option to copy dependent entries such as the storage locations and settings from a reference plant. Use it when the new site behaves like an existing one. Starting from scratch is more flexible but you will probably miss settings in other modules, because plant data is spread across many tables.
Deleting a plant is possible only before it has transaction data. Check that nothing references it before you try, which can be a long job in a live system.
Try it here, free
SAP New Plant Setup Checklist
Step-by-step checklist for creating a new SAP plant: enterprise structure, assignments, master data, production, quality and go-live checks.
Common pitfalls
- !Creating the plant but forgetting OX18, so the plant has no company code and valuation cannot be derived.
- !Missing account determination for the new valuation area, which breaks the first goods movement.
- !Not assigning a purchasing organization, so buyers cannot create POs for the plant.
- !Skipping the factory calendar, which affects MRP dates.
- !Customizing in production directly instead of through a transport.
How an ERP-grounded AI assistant handles this
Consultants frequently need to compare how an existing plant is set up before copying it. 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
Which transaction creates a plant in SAP MM?
OX10 is the usual transaction for defining, copying, deleting and checking a plant. The same function is available through the IMG under Enterprise Structure > Definition > Logistics - General.
What is a storage location in SAP MM?
A storage location is a physical or logical place within a plant where stock is kept. Stock is managed per storage location, but valuation is typically at plant level, and a storage location cannot exist without a plant.
Can one purchasing organization serve several plants?
Yes. A purchasing organization can be assigned to several plants through OX17. It can also be assigned to a company code, or in a cross-company-code set up, to several company codes.
Do I need a transport to create a plant?
Yes, in a normal landscape. These are customizing changes, so create them in the development client under a customizing request and transport them to test and production.
Related
SAP open purchase orders report: ME2N, ME2M, ME2L and the underlying tables
Use ME2N for a flexible open PO list, ME2M by material and ME2L by vendor, with the selection parameter Still to be delivered. The open quantity is the scheduled quantity in EKET minus goods received in EKBE, excluding deleted and delivery-completed items. For custom reports, read EKKO, EKPO, EKET and EKBE.
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 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.
How-toHow 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.
AI for ERPAI for SAP S/4HANA, Running On-Prem or in Your Private Cloud
Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.
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 New Plant Setup ChecklistStep-by-step checklist for creating a new SAP plant: enterprise structure, assignments, master data, production, quality and go-live checks.
- SAP MM Configuration Checklist (SPRO)A tickable SPRO checklist for configuring SAP MM, grouped by enterprise structure, material master, purchasing, inventory, invoice verification and accounting.
- SAP Functional Location Structure TemplateDocument your SAP PM functional location hierarchy, structure indicator and labeling rules in one clean design document.
ERP fixes and how-tos
- SAP PP End to End Configuration: Steps, IMG Paths and Process FlowSAP PP end to end configuration in order: organizational structure, master data, MRP, order types, confirmation, costing and settlement, with IMG paths and tcodes.
- How to Create a Purchase Order in SAP MM (ME21N)Step-by-step purchase order creation in SAP MM with ME21N: manual PO, PO from requisition, account assignment, release and the order-to-invoice flow.
- SAP MM Errors and Solutions: The Common Ones, by Process StepCommon SAP MM errors by process step, with cause and fix: stock deficit, closed periods, release strategy, blocked invoices and account determination.