Study guide
2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure
SAP S/4HANA Sales C_TS462
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: SAP S/4HANA Sales Overview and Enterprise Structure
1.1 SAP Business Suite, SAP S/4HANA Sales, Deployment Options, and User Interfaces 1.2 Sales Organization, Distribution Channel, Division, and Sales Area Architecture 1.3 Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments 1.4 Cross-Company and Multi-Plant Sales Enterprise Setup & SD-FI Integration
2 Chapter 2: The Order-to-Cash Process and Sales Master Data
2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration 2.2 Business Partner (BP) Approach, Customer Roles, and Partner Functions 2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure 2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling
3 Chapter 3: Sales Documents, Copying Control, Presales, and Outline Agreements
3.1 Sales Document Header Architecture and Customizing Sales Document Types 3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection 3.3 Copying Control and Document Flow Between Sales Documents 3.4 Pre-Sales Processing: Inquiries, Quotations, and Document Validity 3.5 Outline Agreements: Scheduling Agreements, Quantity Contracts, and Release Orders 3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing 3.7 Special Business Processes: Consignment, Rush Orders, Cash Sales, and Free-of-Charge Deliveries
4 Chapter 4: Item Categories, Schedule Line Categories, and Sales BOMs
4.1 Item Category Customizing Controls and Item Category Determination Logic 4.2 Schedule Line Categories and Determination Mechanics 4.3 Bill of Materials (BOM) Explosion in Sales Orders
5 Chapter 5: Pricing and the Condition Technique
5.1 Condition Technique Architecture: Field Catalogs, Tables, and Access Sequences 5.2 Condition Types, Calculation Types, Scales, and Condition Classes 5.3 Pricing Procedure Determination and Calculation Schema Configuration 5.4 Working with Condition Records: Maintenance Tools, Price Lists, Pricing Reports, and Manage Prices 5.5 Special Pricing Functions: Condition Exclusion, Group Conditions, Header Conditions, Condition Update, and Supplements 5.6 Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding 5.7 Statistical Condition Types and Tax Determination 5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement
6 Chapter 6: Availability Check (ATP) and Delivery Scheduling
6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check 6.2 Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations 6.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements
7 Chapter 7: Delivery Processing and Embedded EWM
7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM 7.2 Shipping Point Determination and Route Determination Mechanics 7.3 Outbound Delivery Creation, Delivery Document Types, and Delivery Item Categories 7.4 Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI) 7.5 Picking and Goods Issue with Embedded EWM 7.6 Inbound Deliveries with EWM and Special Functions in Deliveries
8 Chapter 8: Billing and Integration with Financial Accounting
8.1 Billing Document Types, Categories, and Billing Due List Processing 8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing 8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows 8.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents 8.5 Billing Plans, Down Payment Agreements, and Installment Payments 8.6 Revenue Account Determination and FI-SD General Ledger Integration 8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options
9 Chapter 9: Basic Functions: Partners, Incompletion, Texts, Material Determination, and Output
9.1 Partner Determination Procedures and Account Group Linkage 9.2 Incompletion Procedures, Status Groups, and Log Configuration 9.3 Text Control I: Text Objects, Text Types, Text Determination Procedures, and Manual Text Entry 9.4 Text Control II: Automatic Text Transfer, Text Determination Analysis, and Special Features 9.5 Material Determination, Material Listing, and Material Exclusion 9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST 9.7 Output Parameter Determination with Decision Tables
10 Chapter 10: SAP Fiori, Sales Analytics, RISE with SAP, and Clean Core
10.1 SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics 10.2 Working with the SAP Fiori Launchpad: My Home, Spaces and Pages, Help, Joule, Responsibilities, Situations, and Workflows 10.3 RISE with SAP Methodology: Standardized Framework, Transformation Preparation Service, Toolchain, Expert Guidance, and Dashboard 10.4 Clean Core: Definition, Benefits, the Five Principles, and Clean Core Levels
11 Chapter 11: Implementing SAP S/4HANA Cloud Private Edition
11.1 SAP S/4HANA Cloud Private Edition: Characteristics, Transition Paths, and the Implementation Team 11.2 System Landscapes, System Provisioning, and Release Upgrades 11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion 11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages 11.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration 11.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side 11.7 Integration: ISA-M, SAP Integration Suite, Prepackaged Content, and Monitoring 11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM
2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure
Key Takeaways Explain This Topic AI
Product master records in SAP S/4HANA are maintained across organizational levels via MM01/MM02 or the Fiori 'Manage Product Master Data' app.
The Sales: Sales Org. 1 view controls tax classifications, base and sales units of measure, and default delivering plants.
The Sales: Sales Org. 2 view holds the item category group (such as NORM or BANC), the material pricing group, and the material statistics group.
The Sales: General/Plant view maintains Availability Check checking groups (01/02), Loading Groups, and Transportation Groups essential for shipping.
Delivering plant determination strictly evaluates the Customer-Material Info Record first, the Ship-to Customer Master second, and the Material Master third.
Last updated: October 2026
- Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure
- Product Master Data Architecture in SAP S/4HANA
In SAP S/4HANA, the material master—often designated as the Product Master —serves as the central repository of all physical goods, consumables, services, and digital assets traded or manufactured by the enterprise. Master data maintenance is executed through classical SAP GUI transaction codes ( MM01 for Create, MM02 for Change, MM03 for Display) or through SAP Fiori apps such as Manage Product Master Data .
A key technical enhancement in SAP S/4HANA is the extension of the material number field length ( MATNR ) from 18 characters (in legacy ECC) up to 40 characters . The extended material number must be activated explicitly in Customizing ( Cross-Application Components -> General Application Functions -> Field Length Extension ); it is a system-wide setting to decide on early in a project.
The material master is organized hierarchically across organizational levels to avoid redundant data storage while granting flexible local execution:
Client Level : Attributes valid uniformly across all companies and plants (e.g., material number, material description in multiple languages, base unit of measure, gross and net weight, volume). Stored in table MARA (General Material Data) and MAKT (Material Descriptions).
Sales Organization and Distribution Channel Level : Attributes specific to a commercial selling channel (e.g., sales unit, delivering plant, tax classification, item category groups). Stored in table MVKE .
Plant Level : Attributes governing manufacturing, procurement, quality, inventory valuation, and logistics execution (e.g., availability checking group, loading group, batch management indicator). Stored in table MARC . The transportation group appears on the same Sales: General/Plant view but is a client-level field ( MARA-TRAGR ).
Storage Location Level : Physical bin locations, picking areas, and stock quantities. Stored in table MARD .
Sales: Sales Org. 1 View Field Controls
The Sales: Sales Org. 1 view establishes baseline commercial parameters for a specific combination of Sales Organization and Distribution Channel:
1. Base Unit of Measure vs. Sales Unit
Base Unit of Measure ( MARA-MEINS ) : The primary unit in which warehouse stock is inventoried, valued on the general ledger, and tracked. Defined at the client level.
Sales Unit ( MVKE-VRKME ) : An alternative unit of measure specifically utilized for sales orders, quotations, and customer contracts (e.g., selling by "Box" or "Pallet" while stock is held in "Pieces").
Conversion Factors : If the Sales Unit differs from the Base Unit of Measure, explicit mathematical conversion ratios must be maintained in the material master under Additional Data -> Units of Measure (e.g., 1 Box = 24 Pieces).
Variable Sales Unit Not Allowed : If this indicator is set, the sales unit proposed from the material master cannot be changed in sales documents. Without it, users can enter another unit, but only one for which a conversion factor exists.
2. Delivering Plant ( MVKE-DWERK )
The default plant from which goods are supplied to customers within the specified sales organization and distribution channel. While maintained in Sales Org 1, it represents the third and lowest priority level in the delivering plant determination sequence.
3. Cash Discount Indicator ( MVKE-SKTOF )
A single-character flag specifying whether the material is eligible for cash discounts during payment processing. If deselected, the pricing engine excludes this material item from cash discount condition calculations (such as condition type SKTO ).
4. Tax Classification Matrix
Sales tax determination in SAP SD requires evaluating the tax liability of both the customer and the material. The Sales Org. 1 view contains the Tax Classification table, structured by:
Country of Departure : Derived from the delivering plant assigned to the sales organization.
Tax Category : The fiscal tax condition type configured for that country (e.g., UTXJ for United States, MWST for Germany/EU).
Tax Classification Indicator : A numeric code indicating fiscal tax liability:
0 : Tax Exempt (e.g., non-taxable services, exempt pharmaceutical goods).
1 : Full Tax (standard statutory rate).
2 : Half / Reduced Tax (concessionary rates for food, agricultural, or cultural goods).
During sales order pricing, the condition technique evaluates the material's tax classification in combination with the customer's tax classification (from the customer master sales area view) to derive the applicable condition record for MWST or sales tax.
Sales: Sales Org. 2 View Field Controls
The Sales: Sales Org. 2 view defines grouping criteria essential for pricing, document line item category determination, and sales reporting:
1. General Item Category Group vs. Item Category Group
A vital conceptual distinction tested in the certification exam:
General Item Category Group ( MARA-MTPOS_MARA ) : Defined at the client level (table MARA ). It defines the fundamental commercial nature of the product across the entire enterprise. Common standard values include:
NORM : Standard delivery-relevant inventory item.
BANC : Individual purchase order (item category TAB : a purchase requisition is created for each order item and the vendor delivers to your own plant).
BANS : Third-party item (item category TAS : the vendor delivers directly to the customer).
NLAG : Non-stock material.
DIEN : Service material (non-inventory, order-related billing).
LUMF : Bill of Materials (BOM) item with pricing and delivery at the component level.
ERLA : Bill of Materials (BOM) item with pricing and delivery at the header level.
Item Category Group ( MVKE-MTPOS ) : Defined at the Sales Organization and Distribution Channel level (table MVKE ). It allows a specific sales organization to override the general item category group. If the sales-organization-specific field is left blank, the system automatically defaults to the general item category group.
2. Item Category Determination Integration
The item category group is one of the four criteria that the system evaluates to determine the Item Category in a sales order: Sales Document Type + Item Category Group + Item Usage + Higher-Level Item Category ⟶ Item Category \text{Sales Document Type} + \text{Item Category Group} + \text{Item Usage} + \text{Higher-Level Item Category} \longrightarrow \text{Item Category} Sales Document Type + Item Category Group + Item Usage + Higher-Level Item Category ⟶ Item Category
For example, for a standard order type OR with item category group NORM and no item usage or parent line, the system determines item category TAN (Standard Item).
3. Material Statistics Group ( MVKE-VERSG )
Controls whether sales transactions involving this material update the statistics of the Logistics Information System (LIS). Embedded analytics on CDS views reads the documents directly and does not depend on this update.
4. Product Hierarchy ( MVKE-PRODH )
A multi-level alphanumeric code (up to 18 characters structured across up to three levels) used for product classification, margin analysis, and condition technique pricing discounts across related product families.
Sales: General/Plant View Field Controls
The Sales: General/Plant view is maintained at the Plant level ( MARC ). Its fields establish direct integration between SD, Materials Management (MM), and Warehouse Management (WM):
1. Availability Check Checking Group ( MARC-MTVFP )
The checking group specifies how inventory requirements are aggregated and checked against stock during the Available-to-Promise (ATP) calculation:
01 (Summarized daily requirements): Requirements of the same day are planned as one daily total for MRP.
02 (Individual requirements): Each sales order schedule line is passed to MRP as its own requirement, so planners can trace exactly which order created the demand.
CH (Batches): Availability checks are executed against individual batch allocations.
In classic ERP, summarized requirements were stored in the totals table VBBS . In SAP S/4HANA, requirements are kept as individual records in VBBE and totals are calculated when needed, so VBBS is no longer used.
The Checking Group ( MTVFP ) is combined with the Checking Rule (e.g., A for sales orders, B for outbound deliveries) in SPRO to determine the Scope of Check (stocks, receipts, and issues included in ATP).
2. Loading Group ( MARC-LADGR )
Defines the manual or mechanical handling equipment required to load the material onto transport vehicles (e.g., 0001 Forklift, 0002 Crane, 0003 Manual).
Core SD Impact : The Loading Group is an indispensable input into Shipping Point Determination : Shipping Condition (from Sold-to) + Loading Group (from Material) + Delivering Plant ⟶ Shipping Point \text{Shipping Condition (from Sold-to)} + \text{Loading Group (from Material)} + \text{Delivering Plant} \longrightarrow \text{Shipping Point} Shipping Condition (from Sold-to) + Loading Group (from Material) + Delivering Plant ⟶ Shipping Point
3. Transportation Group ( MARA-TRAGR )
Identifies materials with shared transport requirements (e.g., 0001 Ambient Pallets, 0002 Refrigerated/Cold Chain, 0003 Liquid Tanker).
Core SD Impact : The Transportation Group is a primary input into Route Determination : Departure Country/Zone + Shipping Condition + Transportation Group + Destination Country/Zone ⟶ Route \text{Departure Country/Zone} + \text{Shipping Condition} + \text{Transportation Group} + \text{Destination Country/Zone} \longrightarrow \text{Route} Departure Country/Zone + Shipping Condition + Transportation Group + Destination Country/Zone ⟶ Route
4. Batch Management Requirement ( MARC-XCHPF )
Specifies whether the material must be tracked and issued by discrete manufacturing or vendor batches. If checked, picking and goods issue require batch assignment.
The Sequential Delivering Plant Determination Hierarchy
When an order entry specialist adds a line item to a sales order, the system must establish the supplying plant to perform availability checks and delivery scheduling. The SAP system searches for a delivering plant using a strict, three-tier hierarchical sequence:
First Priority: Customer-Material Information Record (CMIR - table KNMT ) The system queries table KNMT for a record matching the sold-to party, sales organization, and distribution channel with the ordered material. If a delivering plant is maintained in the CMIR, that plant is immediately populated in the order line item.
Second Priority: Ship-to Party Customer Master (table KNVV ) If no CMIR exists or if the CMIR delivering plant field is unpopulated, the system checks the Sales Area data of the Ship-to Party ( KNVV-VWERK ). The Ship-to party governs this step because physical goods are dispatched to the destination site.
Third Priority: Material Master Sales Org. 1 View (table MVKE ) If neither the CMIR nor the Ship-to customer master specifies a plant, the system falls back to the default delivering plant maintained on the material master Sales Org. 1 view ( MVKE-DWERK ).
If all three master data sources lack a delivering plant, the sales order line item triggers an entry in the Incompletion Log . The order cannot be released for delivery until an authorized user manually enters a valid plant in the sales document item.