For any SAP S/4HANA Materials Management (MM) implementation team, there is a foundational architectural decision that subtly defines the granularity of inventory valuation across the whole enterprise: the decision of valuation level.The decision on whether to value materials at company code level or at plant level defines the basic structure for storing, calculating and reporting material prices in the material master record. In this piece we will take a closer look at these two pricing concepts and in particular at the valuation area price and company code price in S/4HANA. We will cover the structural requirements, configuration details, the major influence on the Accounting and Costing views of the material master and unique issues in linking Materials Management with Controlling (CO) by means of transfer pricing and actual costing.
The Enterprise Structure Foundation: Defining the Valuation Area
Before a single material master record is created, the enterprise structure must be configured with a defining parameter: the valuation level. This setting answers a critical question: At what organizational level will inventory be valued? The valuation area is the organizational unit where materials are valuated, and it is strictly defined by the valuation level configured in Customizing.
Company Code as Valuation Area: If the valuation level is set to company code, the “company code price” becomes the standard for all materials. In this scenario, a material number used across multiple plants within the same company code shares a single, unified valuation price. Inventory values are aggregated, meaning a goods receipt in Plant A and Plant B has the same immediate impact on the total stock value of that material from an accounting perspective.
Plant as Valuation Area When the valuation level is set to plant then each plant is its own valuation area. Each facility can have a different price for the same material number. This is the prerequisite for material costing within the Controlling (CO) module, as a plant must correspond to a valuation area and be assigned to a controlling area for cost estimates to function. The “controlling area price” concept, in this context, typically refers to the valuation price within a plant that is assigned to a controlling area.
This is not a decision to be made lightly. A critical SAP error message (CK007) explicitly states: “For material costing, you must carry out valuation at plant level so that a plant corresponds to a valuation area”. Therefore, if a business intends to use Product Cost Planning (CO-PC-PCP) to calculate standard costs for materials in different plants, plant-level valuation is a non-negotiable technical requirement. Attempting to execute a costing run for a material in a plant not assigned to a controlling area will halt the process. The underlying principle is that valuation area prices (plant-level prices) are essential for localized performance analysis, while company code prices facilitate consolidated financial reporting.
Architectural Underpinnings: The Material Master Accounting Views
Once the valuation level is set, its effects ripple directly into the material master’s Accounting 1 and Accounting 2 views. The Accounting 1 view is where the valuation data for each valuation area—be it a company code or a plant—is meticulously maintained.
Within the “Prices and Values” section of the Accounting 1 view, the fields for “Standard Price” and “Moving Average Price” (or Periodic Unit Price) are displayed. If the valuation is at the company code level, the price entered here is the company code price, universally applied. If at plant level, this screen is maintained for each plant, allowing Plant A to hold a standard price of 10.00 while Plant B holds10.50 for the exact same material.
This behavior is further defined by the “Price Control” indicator (S for Standard Price, V for Moving Average Price)., all goods movements are valuated at this fixed price, and variances are posted to price difference accounts. With Moving Average Price (V) the system recalculates the price constantly after each movement of items or after receiving an invoice, dividing the entire value by the total stock. It is crucial to note the constraint with Split Valuation: materials subjected to split valuation can only use the moving average price method. This means that normal price control is not possible if a company has to value multiple lots or origins of a material individually within the same valuation region.
Practical Configuration: Activating and Managing Valuation Areas
Step1
The Valuation Level is a one-time irreversible choice taken in the IMG/SPRO under Enterprise Structure > Definition > Logistics - General > Define Valuation Level. The two options are clear: "Valuation area is a plant" or "Valuation level is a company code". Once saved and transactional data is created this setting cannot be changed without significant system remediation.
Step2
Activate Split Valuation (If Required). If the business needs to value materials differently based on origin or quality within the same valuation area, split valuation must be activated globally via transaction OMW0. This is a prerequisite before any material master is configured with a valuation category.
Step3
Configure Split Valuation. In transaction OMWC, the valuation categories (e.g., "B" for batch) and valuation types (e.g., "IN" for in-house, "EX" for external) are defined and mapped to valuation areas. This allows the creation of material master records where the Accounting 1 view is maintained for multiple valuation types, each with its own price.
Step4
Material Master Maintenance. Using transaction MM01, the material is created with the Accounting 1 view for the required valuation area. The user enters the valuation class (linking to G/L accounts), chooses the price control indicator (S or V), and enters the initial standard or moving average price.
Integrating MM and CO: Transfer Pricing and Cross-Company Flows
The distinction between company code price and valuation area price becomes significantly more complex in intercompany scenarios or when transfer pricing is active. In SAP S/4HANA, transfer pricing enables the valuation of goods movements between profit centers or company codes at internal transfer prices, rather than mere book values.
Intercompany Transfer Pricing: When a stock transport order (STO) is created between two plants belonging to different company codes, the delivering plant may value the material at its local valuation price, while the receiving plant receives it at a transfer price that includes an internal markup. The material master in the receiving plant (and its valuation area) could therefore have a different valuation than the original. The actual costing mechanism in the Material Ledger picks up these intercompany profits during the period end closing process and posts them to specific accounts.
Profit Center Transfer Pricing can add an internal profit margin when items are transferred between profit centers inside the same company code. The material master price remains unchanged, but parallel valuation views (ledgers) track the internal revenue and cost of sales for the sending and receiving profit centers.
The Costing view in the material master plays a pivotal role here. It contains the “Special Procurement Type,” which defines how a material is procured for costing purposes. For instance if a material is produced in another plant within the same company code, the special procurement key directs the cost estimate to pull the cost from that source plant’s valuation area price, rather than costing it locally. This ensures that the cost component structure accurately show the supply chain cost for better analysis.
Periodic Pricing and the Material Ledger
SAP S/4HANA has fundamentally shifted valuation methodology by making the Material Ledger mandatory, a key difference from legacy SAP ERP systems. The Material Ledger allows for actual costing, which calculates a “Periodic Unit Price” (PUP), an alternative valuation price that reflects all actual expenses incurred during a period.
This PUP is particularly relevant to the moving average price control indicator ‘V’. In the Accounting 1 view, the statistical moving average price update from the previous period is no longer available in S/4HANA as it was in ERP ECC 6 instead, the Material Ledger takes center stage. When actual costing is active, the system collects valuation-relevant transactions from inventory management, invoice verification, and order settlement. At month-end, the single-level or multi-level material price determination process calculates a periodic unit price, which can then be used to revaluate inventory back at the plant level (valuation area price) or company code level, depending on the valuation area configuration.
This capability bridges the gap between standard legal valuations (company code price) and more granular, operational performance measurement (valuation area price). For example, a material might have a standard price of 15.00 for statutory reporting but could be analyzed in CO using the periodic unit price of 14.80 to reflect actual production efficiencies in that specific plant.
Strategic Considerations: Choosing the Right Path
Choosing a company code price vs a valuation area (plant level) pricing is a business decision. Plant level valuation enables granular cost management, allowing for more exact profitability analysis by plant and more effective inventory variance control. For Detailed Product Cost Controlling it is required. However, it adds master data maintenance complexity as the Accounting 1 view has to be maintained for each plant. On the other hand, company code valuation simplifies master data administration and provides a consolidated picture, suitable for organizations where facilities inside a company code have extremely similar production and procurement costs, but it severely limits the depth of management accounting insights.
Conclusion
The financial and logistics connection in SAP S/4HANA is based on the setting of a valuation level and then the setting of company code or plant level prices in the material master. S/4HANA has removed the statistical moving average pricing and made the Material Ledger essential, therefore it has become more important to understand actual costing and how it impacts inventory valuation. Whether you are preparing a simple split valuation for batch-specific prices or a comprehensive intercompany transfer pricing model, the logic is based on the core relationship between the valuation area, the controlling area and the company code. Mastering these characteristics guarantees that the material master drives procurement and planning, but also becomes an accurate instrument for financial truth and cost transparency.
Note
Configuration paths and specific transaction codes (e.g., OMW0, OMWC) mentioned are based on standard SAP conventions available through on-premise or private cloud documentation and may require adaptation based on specific S/4HANA releases and scope
