Unit 2: Processes and Enterprise Structure in Procurement
Before you post any document you must know which steps the procurement cycle consists of and which organizational units carry the data. This unit introduces the standard procure-to-pay cycle, three special procurement types, and the enterprise structure (client, company code, plant, storage location, purchasing organization, purchasing group).
Lesson 1 · Delineating Procurement Processes
After this lesson you can
- Describe each phase of the external procurement cycle
- Explain stock transfer with a stock transport order, subcontracting and supplier consignment
Key concepts: the procurement cycle
| Phase | What happens | Typical tools |
|---|---|---|
| Determination of requirements | A department reports a need by creating a purchase requisition manually, or MRP generates the requisition automatically when the material is planned. | ME51N, MD01N |
| Source determination / supplier selection | The buyer looks for possible sources: earlier purchase orders, outline agreements (contracts, scheduling agreements) and purchasing info records. RFQs can be sent and quotations compared to find the best price. | ME41, ME49 |
| Purchase order processing | POs are created manually or automatically; data can be copied from requisitions, quotations or contracts to save typing. | ME21N, ME59N |
| Purchase order monitoring | Check whether goods or invoices have arrived for each item and send reminders (urging letters) for overdue deliveries. | ME2N, ME91F |
| Goods receipt | The delivery is posted with reference to the PO; the system proposes data, checks quantities/material and updates the PO history. | MIGO |
| Invoice verification | The invoice is entered with reference to the PO (or delivery). Quantity and price differences against PO and GR become visible. | MIRO |
| Payment processing | Accounting runs the payment program periodically to settle open supplier items. | F110 |
Not all purchasing follows this plain path. Which process runs for a PO item is controlled by the item category: blank (standard), L (subcontracting), K (consignment), U (stock transfer), D (service) and others.
Stock transfer with a stock transport order (STO)
Here goods move between two plants of the same company. The receiving plant "buys" from the supplying plant, so purchasing and inventory management are both involved.
- Purchasing creates the STO (document type
UB, item categoryU) for the receiving plant, entering the supplying plant instead of a supplier. - The supplying plant posts the goods issue against the STO (movement type
351when the goods issue is posted directly against the STO in MIGO, or641when an outbound delivery is used). The quantity now sits in the receiving plant's stock in transit. - The receiving plant posts the GR with reference to the STO (movement type
101), moving the quantity from stock in transit into storage-location stock.
Plant-to-plant transfers can also be done purely with inventory management transfer postings (e.g. 301 one-step or 303/305 two-step) – without any purchasing document.
Subcontracting
You buy a finished or processed material from a supplier (the subcontractor) but provide some or all of the components yourself.
- Create a subcontract PO (item category
L) for the end product; the components to be provided are listed per item (from a BOM or entered manually). - Provide the components with a transfer posting to the special stock stock of material provided to vendor (movement type
541). The components are physically at the supplier but still belong to you and remain valuated in your books. - Post the GR of the end product against the subcontract PO (
101); the system simultaneously posts consumption of the components from the supplier stock (543). - The subcontractor invoices only the processing service.
The S/4HANA transaction ME2ON (SC Stock Monitoring for Vendor) supports the provision of components.
Supplier consignment
The supplier stores material at your site but keeps ownership until you withdraw it. You owe money only for the withdrawn quantities, settled in agreed periods.
- A consignment info record (info category consignment) holding the agreed price must exist first.
- Order the material with a consignment PO item (item category
K); the item has no price. - Post the GR (
101with special stock indicator K); the quantity goes into consignment stock, which is not valuated in your books. No accounting document is created. - Withdraw from consignment stock (e.g.
201 K, or transfer to own stock with411 K). Now the liability to the supplier is created. - Settle the liabilities periodically with MRKO, which can also send a settlement message (self-billing credit memo) to the supplier.
- The item category determines the process:
Lsubcontracting,Kconsignment,Ustock transfer. - Material provided to a subcontractor is still your valuated stock (special stock O); consignment stock (special stock K) belongs to the supplier and is not valuated.
- Consignment: liability arises on withdrawal, not on GR; settlement with MRKO.
- STO: goods issue puts stock into stock in transit of the receiving plant.
- Trap: "a supplier provides material you store but don't pay for immediately" is consignment, not subcontracting.
Lesson 2 · Identifying the Organizational Units in Procurement
After this lesson you can
- Explain client, company code, plant and storage location and how they are assigned
- Distinguish plant-specific, cross-plant and cross-company-code purchasing organizations
- Describe the role of the purchasing group
Key concepts
Organizational units model the legal and organizational structure of the enterprise. Some units are shared by several application areas (company code from Financial Accounting, plant from Logistics), while the purchasing organization exists only for purchasing. Units are defined and linked in the enterprise-structure part of Customizing.
| Unit | Key | Meaning |
|---|---|---|
| Client | 3 digits (numeric) | Highest level, self-contained legally and organizationally, with its own master records and tables (often the corporate group). Settings made at client level apply to all lower units. Users and authorizations are client-specific. |
| Company code | 4 characters, unique in client | Smallest unit for which a complete, self-contained set of books (balance sheet, P&L) can be produced – a legal entity. |
| Plant | 4 characters, unique in client | Logistics unit for production, procurement, maintenance and planning; can be a factory, sales office, headquarters or maintenance site. Material valuation normally happens at plant level. |
| Storage location | 4 characters, unique within a plant | Differentiates stocks within a plant; quantity-based inventory management and physical inventory are done here. |
| Purchasing organization | 4 characters | Procures materials/services, negotiates conditions with suppliers and is legally responsible for purchasing transactions. |
| Purchasing group | 3 characters | Buyer or group of buyers; internally responsible for certain materials, externally the contact person for suppliers. Not assigned to any other org unit. |
Assignment rules
- A client contains many company codes; a company code contains many plants; but each plant belongs to exactly one company code. Because the plant key is unique in the client, entering a plant implicitly identifies its company code.
- A plant can have many storage locations; a storage location belongs to one plant only. The same storage location key (e.g. 0001) can be reused in other plants.
- A purchasing organization may be assigned to at most one company code (the assignment is optional); a company code can have several purchasing organizations.
- Purchasing organization ↔ plant is many-to-many and mandatory: a purchasing organization can only buy for plants assigned to it.
Types of purchasing organization
| Type | Company code assignment | Plant assignment |
|---|---|---|
| Plant-specific | Assigned to one company code | Exactly one plant |
| Cross-plant | Assigned to one company code | Several plants of that company code |
| Cross-company-code (centralized) | Not assigned to any company code | Plants of several company codes |
Even if a purchasing organization is responsible for every plant of its company code, the plant assignment is still required – the company-code assignment alone is not enough. A further option (not covered in detail here) is a reference purchasing organization whose contract conditions other purchasing organizations may use.
Configuration (IMG)
SPRO › Enterprise Structure › Definition › Materials Management › Maintain Purchasing Organization
SPRO › Enterprise Structure › Definition › Logistics – General › Define, copy, delete, check plant
SPRO › Enterprise Structure › Definition › Materials Management › Maintain Storage Location
SPRO › Enterprise Structure › Assignment › Materials Management › Assign purchasing organization to company code
SPRO › Enterprise Structure › Assignment › Materials Management › Assign purchasing organization to plant
SPRO › Enterprise Structure › Assignment › Logistics – General › Assign plant to company code
SPRO › Materials Management › Purchasing › Create Purchasing Groups
The enterprise structure is maintained with SPRO; the individual definitions can also be reached directly via OX10 (plants), OX08 (purchasing organizations) and OX18 (plant to company code).
- Top-down order: client → company code → plant → storage location.
- Storage location key is unique only within its plant; plant key is unique in the client.
- Purchasing organization → max. one company code (optional); purchasing organization ↔ plant is many-to-many and mandatory.
- A purchasing organization is not limited to plants of one company code (cross-company-code purchasing).
- The purchasing group is not assigned to any other organizational unit.
Unit summary & exam focus
The procurement cycle runs from requirement to payment; item categories switch the process to special forms such as subcontracting, consignment or stock transfers. Every document is posted against an enterprise structure in which purchasing organizations are linked to plants (always) and to a company code (optionally).
T-codes in this unit
| T-code | Purpose |
|---|---|
| ME51N | Create purchase requisition |
| MD01N | MRP Live (generates requisitions) |
| ME41 | Create RFQ |
| ME49 | Price comparison of quotations |
| ME21N | Create purchase order |
| ME59N | Automatic creation of POs from requisitions |
| ME2N | Purchasing documents per document number (monitoring) |
| ME91F | Reminders / urging letters for POs |
| MIGO | Goods movement (GR, GI, transfer) |
| MIRO | Enter incoming invoice |
| F110 | Automatic payment program |
| ME2ON | SC stock monitoring for vendor (subcontracting) |
| MRKO | Consignment / pipeline settlement |
| SPRO | Customizing (IMG) |
| OX08 | Maintain purchasing organizations |
| OX10 | Maintain plants |
| OX18 | Assign plant to company code |
Self-check questions
- True or false: in subcontracting a supplier stores material at your site that you pay for only when you use it.
Answer
False – that describes supplier consignment. In subcontracting you provide components to the supplier and pay for the processing. - When does a liability to the supplier arise in consignment?
Answer
When material is withdrawn from consignment stock (goods issue or transfer to own stock); it is settled periodically with MRKO. - Can a purchasing organization be assigned to two company codes?
Answer
No. It can be assigned to at most one company code – or to none for cross-company-code purchasing. - Can a purchasing organization buy for plants of different company codes?
Answer
Yes, if it is not assigned to a company code (cross-company-code purchasing organization) and the plants are assigned to it. - Within which unit is the storage location key unique?
Answer
Within the plant. - Which stock type holds a stock transfer quantity after goods issue in the supplying plant?
Answer
Stock in transit of the receiving plant. - Which organizational unit is not linked to any other unit?
Answer
The purchasing group.