Study guide
4.3 Bill of Materials (BOM) Explosion in Sales Orders
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
4.3 Bill of Materials (BOM) Explosion in Sales Orders
Key Takeaways Explain This Topic AI
Sales Bills of Materials (BOMs) allow composite product bundles, assembled sets, and promotional kits entered under a single header material to explode automatically into constituent components.
The commercial processing model is governed by the Item Category Group in the header material master: ERLA triggers pricing at the header level, whereas LUMF triggers pricing at the component level.
Under the ERLA model, main item category TAQ carries pricing, inventory management, delivery, and billing, while component item categories TAE are text-like explanation items without prices or goods movements.
Under the LUMF model, main item category TAP is an unpriced item without inventory management, while the components get TAN and are individually priced, checked for availability, and delivered.
The Higher-Level Item field (VBAP-UEPOS) links exploded component items back to the parent item number, enabling transaction VOV4 to evaluate the parent's item category during component determination.
Last updated: October 2026
Bill of Materials (BOM) Explosion in Sales Orders
In many commercial environments, enterprises sell complex product bundles, assembled kits, or promotional packages composed of multiple physical items. For example, a personal computer system may consist of a central processing tower, a monitor, a keyboard, and an operating system license; a corporate promotional package may bundle a leather binder, an executive pen, and a printed catalog.
Rather than requiring customer service representatives to enter every sub-component manually, SAP S/4HANA utilizes Sales Bills of Materials (Sales BOMs) . A Sales BOM is created in Production / Sales master data via transaction CS01 with BOM Usage '5' (Sales and Distribution) . When a sales representative enters the top-level parent material in a sales order, the system automatically explodes the BOM structure, generating sub-line items for each component according to the quantities configured in CS01 .
Commercial Processing Models: Header-Level vs. Component-Level (ERLA vs. LUMF)
The most important design decision for a sales BOM is the level at which it is priced and managed in inventory . SAP provides two standard models, controlled by the item category group of the main material ( MVKE-MTPOS , view Sales: sales org. 2 ). The official course adds that the item category of the main item also defines how far the structure is exploded. Sales BOM Architecture
- |
- +----------------------------+----------------------------+
- v v
- Item Cat Group: ERLA Item Cat Group: LUMF
- Main item TAQ: priced, delivered, Main item TAP: not priced,
- goods issue on the main item no inventory management
- Components TAE: information only Components TAN: priced, delivered
- Model 1: Processing at Main Item Level (Item Category Group ERLA )
In the ERLA model, the product is sold, priced, stocked, and shipped as one unit, for example a pre-assembled kit kept in stock under its own material number. The components are listed in the order for information (for example, to print them on the delivery note), but they are not priced and no goods movement is posted for them.
Customizing and Determination Mechanics:
Material Master : The main material has item category group ERLA . The components carry NORM .
Main Item Determination (VOV4) : Order: OR + Item Cat Group: ERLA + Usage: [blank] + Higher Item: [blank] ⟶ T A Q \text{Order: OR} + \text{Item Cat Group: ERLA} + \text{Usage: [blank]} + \text{Higher Item: [blank]} \longrightarrow \mathbf{TAQ} Order: OR + Item Cat Group: ERLA + Usage: [blank] + Higher Item: [blank] ⟶ TAQ
Component Determination (VOV4) : Order: OR + Item Cat Group: NORM + Usage: [blank] + Higher Item: TAQ ⟶ T A E \text{Order: OR} + \text{Item Cat Group: NORM} + \text{Usage: [blank]} + \text{Higher Item: TAQ} \longrightarrow \mathbf{TAE} Order: OR + Item Cat Group: NORM + Usage: [blank] + Higher Item: TAQ ⟶ TAE
Operational Behavior of TAQ and TAE in VOV7 :
Main Item Category TAQ :
Pricing ( PRSFD ) = 'X' : Prices, discounts, and surcharges are determined for the main item only. The customer pays, for example, $1,200 for the complete kit.
Schedule lines allowed : The main item has schedule lines (category CP ), so availability is checked and goods issue (movement type 601 ) is posted for the main material.
Billing Relevance ( FKREL ) = 'A' : The main item is billed with reference to the delivery.
Component Item Category TAE :
Pricing ( PRSFD ) = ' ' (Blank) : Components carry no price, which prevents double billing.
No goods movement : Components are explanation items. They can be copied into the delivery for information, but no goods movement is posted for them.
Billing Relevance ( FKREL ) = ' ' (Blank) : Components do not appear as billed lines on the invoice.
Model 2: Component-Level Pricing (Item Category Group LUMF )
In the LUMF model, the bundle represents a modular or customizable collection of items. The parent material serves primarily as a commercial shell or grouping header, while pricing, inventory valuation, delivery, and billing occur independently for each constituent component.
Customizing and Determination Mechanics:
Material Master : The parent material is assigned Item Category Group LUMF . Component materials carry standard Item Category Group NORM .
Header Item Determination (VOV4) : Order: OR + Item Cat Group: LUMF + Usage: [blank] + Higher Item: [blank] ⟶ T A P \text{Order: OR} + \text{Item Cat Group: LUMF} + \text{Usage: [blank]} + \text{Higher Item: [blank]} \longrightarrow \mathbf{TAP} Order: OR + Item Cat Group: LUMF + Usage: [blank] + Higher Item: [blank] ⟶ TAP
Component Item Determination (VOV4) : Order: OR + Item Cat Group: NORM + Usage: [blank] + Higher Item: TAP ⟶ T A N \text{Order: OR} + \text{Item Cat Group: NORM} + \text{Usage: [blank]} + \text{Higher Item: TAP} \longrightarrow \mathbf{TAN} Order: OR + Item Cat Group: NORM + Usage: [blank] + Higher Item: TAP ⟶ TAN
Operational Behavior of TAP and TAN in VOV7 :
Parent Item Category TAP :
Pricing Relevance ( PRSFD ) = ' ' (Blank) : The parent item carries no commercial price.
No inventory management : TAP uses a schedule line category without inventory management (standard CT ), so the main item can be copied into the delivery for information, but no goods movement is posted for it.
Billing Relevance ( FKREL ) = ' ' (Blank) : The parent does not appear on the invoice as a billed line item.
Component Item Category TAN :
Pricing Relevance ( PRSFD ) = 'X' : Each component is priced independently using standard condition technique records. The customer pays $700 for the tower, $300 for the monitor, and $100 for the keyboard (total $1,100).
Schedule lines allowed: yes : Standard schedule lines ( CP ) are generated.
Item Relevant for Delivery = 'X' : Physical goods issue occurs via movement type 601 .
Billing Relevance ( FKREL ) = 'A' : Each component is billed individually with reference to its delivery quantities.
Side-by-Side Comparison: ERLA vs. LUMF
- Operational Dimension ERLA (Header Pricing Model) LUMF (Component Pricing Model)
- Parent Material Master Group ERLA ( MVKE-MTPOS ) LUMF ( MVKE-MTPOS )
- Component Material Master Group NORM NORM
- Determined Header Item Category TAQ TAP
- Determined Component Item Category TAE TAN
- Pricing Level Main item ( TAQ carries PRSFD = 'X' ) Components ( TAN carries PRSFD = 'X' )
- Component Pricing Blank ( TAE carries no price) Active ( TAN carries condition records)
- Inventory Management / Delivery Main item ( TAQ ) Components ( TAN )
- Main Item Delivery Yes ( TAQ is delivered and goods issued) No goods movement ( TAP is information only)
- Inventory Movement Movement 601 on the main item Movement 601 on each component
- Billing Document ( VF01 ) Single invoice line for TAQ Separate invoice lines for each TAN
- Higher-Level Item Linkage in Table VBAP
When a Sales BOM explodes in transaction VA01 , the system creates multiple records in database table VBAP (Sales Document Item Data). To preserve the hierarchical relationship between the parent bundle and its sub-components, SAP uses the Higher-Level Item field:
Field VBAP-POSNR : The item number of the current line item (e.g., 000010 , 000020 , 000030 ).
Field VBAP-UEPOS : The item number of the superior or parent line item. Sales Order Line Items in Table VBAP:
- Item (POSNR) Material Item Cat (PSTYV) Higher-Level (UEPOS) Description
- ──────────── ───────────── ──────────────── ──────────────────── ───────────────────
- 000010 DESKTOP-KIT TAQ 000000 PC Package (Parent)
- 000020 CPU-TOWER TAE 000010 Tower Unit
- 000030 MONITOR-27 TAE 000010 27-Inch Monitor
- 000040 KEYBOARD-US TAE 000010 Mechanical Keyboard
- How VOV4 Uses Higher-Level Item Category During Explosion
When the user types DESKTOP-KIT on Line 10, the system determines item category TAQ . The system detects that DESKTOP-KIT has a sales BOM (usage 5 ) and executes explosion routines. When creating Line 20 for CPU-TOWER , the system queries determination table T184 with:
- Sales Document Type = OR
- Item Category Group = NORM
- Item Usage = [Blank]
- Higher-Level Item Category = TAQ (copied from Line 10's determined item category)
Because table T184 contains an entry for OR + NORM + [blank] + TAQ , the system determines TAE instead of standard category TAN . This higher-level linkage ensures that sub-items adopt the correct commercial role without manual user intervention.
Multi-Item Logistics: Availability Check, Delivery Groups, and Billing
When the components themselves are delivered (the LUMF model), they can have different availability:
Delivery Groups ( VBAP-GRKOR ) and Correlation
If a customer orders a computer package priced per component, they typically do not want the monitor delivered on Monday, the keyboard on Thursday, and the CPU tower two weeks later. The bundle is useless until all components are present.
To prevent partial or fragmented shipments, SAP allows components to be assigned to a common Delivery Group ( VBAP-GRKOR ):
When a delivery group is active, the system executes delivery date correlation .
The ATP check evaluates the availability of every component in the group.
The system synchronizes the confirmed delivery date of all group components to match the latest confirmed date among the items.
Outbound delivery creation ( VL01N ) creates a single delivery containing all components simultaneously.
Invoicing Implications
In the ERLA model , the main item TAQ is delivered and goods issued as one material, and it is billed at the kit price on a single invoice line. The components TAE appear only as information.
In the LUMF model , each component TAN is delivered and billed with its own price. If components ship on different dates in separate deliveries, the customer receives separate invoice lines (or invoices) for what was actually delivered, unless a delivery group keeps them together.