Enterprise structure & master data

The MM view of the enterprise is built from company code, plant, storage location and purchasing organisation, plus purchasing groups for buyer responsibility. The plant is the central logistics unit: it carries MRP, stock and (normally) the valuation area.

• Plant → company code is a 1:1 assignment; a company code can own many plants.
• Purchasing organisation can be plant-specific, cross-plant or cross-company (central/reference purchasing org).
• Valuation level is set once (plant or company code) — plant level is the practical standard and is required for PP and split costing.

T-codes & apps

OX10OX09OX08OX18OME4OX17

Configuration

IMG › Enterprise Structure › Definition / Assignment › Logistics – General & Materials Management

The material master is organised in views (Basic data, Purchasing, MRP, Accounting, Storage, Warehouse…) maintained at client, plant and storage-location level. The material type (ROH, HALB, FERT, HAWA, NLAG, DIEN…) controls which views are allowed, number ranges and whether quantity and value are updated.

• Field selection groups decide which fields are required, optional or hidden per transaction and material type.
• Alternative units of measure (order unit, issue unit) are converted against the base unit — conversion errors surface later as stock and invoice differences.
• Cross-plant (MSTAE) and plant-specific (MMSTA) material status can block purchasing, MRP or goods movements.

T-codes & apps

MM01MM02MM03MM17 (mass change)MM60OMS2

In SAP S/4HANA the Business Partner (BP) is the single entry point for suppliers and customers. Customer–Vendor Integration (CVI) keeps the classic vendor tables (LFA1, LFB1, LFM1) synchronised in the background.

• BP roles: FLVN00 (FI supplier) and FLVN01 (purchasing supplier).
• Purchasing data (order currency, payment terms, GR-based IV, ERS flag, partner functions) sits at purchasing organisation level.
• Account group / BP grouping drives number ranges and field control.

T-codes & apps

BPXK03 (display only, redirects)MK03CVI_COCKPITMKVZ

Configuration

IMG › Cross-Application Components › Master Data Synchronization › Customer/Vendor Integration

An info record stores the commercial relationship between one supplier and one material (or material group): price and conditions, planned delivery time, tolerances, order unit and the last PO reference.

• Categories: standard, subcontracting, pipeline and consignment.
• Conditions in the info record are proposed into new PO items; 'No cond.' on the info record forces manual pricing.
• Info update indicator on the PO item can create or update the info record automatically.
• Vendor sub-range (VSR) can group a supplier's product range for info records and pricing.

T-codes & apps

ME11ME12ME13ME1LME1MMEK1

The source list defines which suppliers (or outline agreements) are allowed for a material in a plant over a period. It can mark a source as fixed (preferred) or blocked, and can be made mandatory per plant.

• Source list requirement can be set at plant level or per material (Purchasing view).
• MRP-relevant flag lets MRP assign the source automatically to requisitions or scheduling-agreement lines.
• Generate from info records/contracts with ME05.

T-codes & apps

ME01ME03ME04ME05ME06

The item category defines how a PO item is procured (standard, consignment K, subcontracting L, third-party S, stock transfer U, service D, text T). The account assignment category (K cost centre, F order, P project, A asset, C sales order…) decides whether the item goes to stock or is consumed directly.

• Consumable items with account assignment post to expense at GR (or at IR if non-valuated GR).
• Account assignment category controls GR indicator, IR indicator and GR non-valuated defaults.
• Multiple account assignment can split one item by quantity or percentage.

T-codes & apps

OME9ME21N

Configuration

IMG › Materials Management › Purchasing › Account Assignment › Maintain Account Assignment Categories