Item Categories
SD / O2Cadvanced

SD Item Categories Part 4: Complex Scenarios — Sales BOMs, Sub-Items and Free Goods

Key takeaway

Handle items with structure: sales BOMs priced at header (ERLA → TAQ/TAE) or at component level (LUMF → TAP/TAN), how higher-level item categories drive sub-items, delivery group behavior, and free goods with item usage FREE creating TANN sub-items — plus the pitfalls in pricing, availability and billing.

Explanation

📌 KEY POINTS
✅ Sales BOM with item category group ERLA: header TAQ is priced and billed, components TAE are delivered but not priced.

✅ Sales BOM with LUMF: header TAP is only a grouping (not priced, not delivered), components TAN are priced, delivered and billed.

✅ Sub-item categories are determined in VOV4 using the higher-level item category (TAQ → TAE, TAP → TAN).

✅ Free goods create a sub-item with item usage FREE → TANN (priced 100% discount, not billed) under the paid item.

⚠️ Header pricing with component delivery means cost and revenue sit on different items — check profitability reporting and partial delivery rules.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE

Part 3 covered the special processes. Now items that have structure below them.

━━━━━━━━━━━━━━━━━━━━
▶ 1. SALES BOM BASICS

  • BOM usage 5 (sales and distribution) created with CS01.
  • Item category's structure scope explodes the BOM in the order.
  • Item category group on the header material decides the model (ERLA or LUMF).

━━━━━━━━━━━━━━━━━━━━
▶ 2. PRICING AT HEADER (ERLA)

  • Header TAQ: pricing, billing, credit.
  • Components TAE: delivery-relevant, no pricing — availability checked per component.
  • Use when the kit has one price and components are logistics detail.

━━━━━━━━━━━━━━━━━━━━
▶ 3. PRICING AT COMPONENT (LUMF)

  • Header TAP: text-like grouping; no pricing, no delivery.
  • Components TAN: normal items with pricing, delivery, billing.
  • Use when each component has its own price and revenue account.

━━━━━━━━━━━━━━━━━━━━
▶ 4. DELIVERY GROUPS AND COMPLETENESS

  • Components can form a delivery group (deliver together).
  • Partial delivery settings per item and customer.
  • ATP on components; header shows the combined confirmation.

━━━━━━━━━━━━━━━━━━━━
▶ 5. FREE GOODS

  • Free goods condition records (VBN1) with determination procedure.
  • Inclusive (part of ordered quantity free) or exclusive (extra quantity free) free goods.
  • Sub-item with item usage FREE → VOV4 entry OR + NORM + FREE + TAN → TANN.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

  1. Create a sales BOM (CS01, usage 5) for a kit material.
  2. Set item category group ERLA or LUMF on the header material.
  3. Check VOV4 entries for header and higher-level item categories.
  4. Create an order, check pricing, schedule lines and delivery.
  5. Add a free goods record and check the TANN sub-item.

✅ CHECKPOINT: you can explain where revenue and cost are posted for an ERLA kit versus a LUMF kit.

Code example

ABAP Code
===== STEP 1: sales BOM =====CS01  material KIT-100, plant 1000, BOM usage 5 (sales)  components COMP-1 x1, COMP-2 x2 ===== STEP 2: item category determination for structures (VOV4) =====SaTy | ItCGr | Usg  | HLevItCa | DfItC   MeaningOR   | ERLA  |      |          | TAQ     header priced, billedOR   | NORM  |      | TAQ      | TAE     component delivered, not pricedOR   | LUMF  |      |          | TAP     header grouping onlyOR   | NORM  |      | TAP      | TAN     component priced, delivered, billedOR   | NORM  | FREE | TAN      | TANN    free goods sub-item ===== STEP 3: free goods =====SPRO > Sales and Distribution > Basic Functions > Free Goods > Condition Technique for Free GoodsCondition records  VBN1   e.g. buy 10, get 1 free (exclusive)Free goods determination procedure assigned per sales area / document pricing procedure / customer ===== STEP 4: check in the order =====VA03 > item overview: higher-level item (UEPOS) links sub-items to header

Real project scenario

A healthcare supplier sold surgical kits priced as one unit (ERLA). Management accounting reported the kits as loss-making because costs of goods sold posted on component items (TAE, delivery-relevant with cost) while revenue posted on the header item. The team kept header pricing for the customer but enabled cost determination at header level with a statistical cost roll-up, and adjusted the profitability report to aggregate by higher-level item. A second fix: partial deliveries of kits were prevented with a delivery group, as hospitals rejected incomplete kits.

Common mistakes

  • Choosing ERLA vs LUMF without deciding where revenue and cost should sit.
  • Missing VOV4 entries for higher-level item categories, so components get wrong categories.
  • Allowing partial delivery of kits that must ship complete.
  • Confusing inclusive and exclusive free goods.
  • Forgetting that TANN items still need availability and delivery.

Best practices

  • Decide pricing level (header or component) with finance and controlling.
  • Maintain complete VOV4 entries including higher-level categories.
  • Use delivery groups for kits that ship complete.
  • Test free goods with pricing, delivery and billing.
  • Keep BOM usage 5 BOMs under master data governance.

Interview angle

Questions: "Difference between ERLA and LUMF?", "How are sub-item categories determined?", "How are free goods processed?"
Strong answer: ERLA → TAQ header priced/billed with TAE components delivered; LUMF → TAP header grouping with TAN components priced/delivered/billed; sub-items via VOV4 with higher-level item category; free goods via condition technique (VBN1) creating TANN sub-items with item usage FREE, inclusive vs exclusive. Mentions revenue/cost placement and delivery groups.

Practice this lesson

Quick check

1. Customers reject partial deliveries of kits. Which setting ensures kit components are delivered together?

2. A kit must be priced as one unit, while its components are delivered individually. Which sales BOM setup fits?

3. How does SAP determine the item category of a free goods sub-item?

Interview questions

1. You are designing item category determination for a multi-level sales BOM sold across several document types (standard order, rush order, and consignment fill-up). What architectural principles should guide the higher-level and sub-item category assignments?

Answer it in your own words first, then compare.

2. A customer places an order for a promotional free sample alongside a paid product. How should item category determination be configured to correctly process the free-of-charge item without triggering pricing or credit issues?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics