SAP SD Item Category Determination — VOV4 & VOV7
The 4-key logic · VOV4 & VOV7 · TAN, TANN, TAS · troubleshooting — for S/4HANA & ECC, updated 2026
Every line you enter in a sales order gets an item category, and that single field decides whether the line is priced, delivered, billed, or planned. Get the determination wrong and the order behaves in ways nobody can explain.
This guide covers the four-key determination logic, how VOV4 and VOV7 differ, the item categories that matter, what the item category actually controls, and the errors that come up on every project.
Quick Jump
What is an item category in SAP SD?
An item category is the control key for a single line in a sales document. The document type (OR, RE, CR) controls how the whole document behaves; the item category controls how this line behaves.
It answers questions like: should this line be priced? Can it be delivered? Will it be billed, and on what basis? Does it create schedule lines and pass demand to planning? Two lines in the same order can behave completely differently purely because they carry different item categories.
Why it matters
Most “the order is behaving strangely” tickets in SD end at the item category. A free item that gets invoiced, a service that appears on a delivery due list, a third-party line that never raises a purchase requisition — all of these are item category configuration, not user error.
The one-line version: the document type decides how the order behaves; the item category decides how each line behaves. Almost every odd line-level symptom traces back here.
Determination logic
SAP determines the item category from four inputs. Combine them, look the combination up in VOV4, and you get the item category:
SAP SD item category determination: sales document type + item category group + usage + higher-level item category → item category (VOV4).
The four keys explained
Sales document type
MandatoryWhere the line sits — OR for a standard order, RE for returns, CR for a credit memo request. The same material behaves differently in a return than in a sale.
Item category group
MandatoryFrom the material master (Sales Org 2 view). NORM for standard stock, DIEN/LEIS for services, LEIH for returnable packaging, ERLA/LUMF for BOMs.
Usage
OptionalA special use of the line within the same document and material. The clearest case is FREE for free goods; blank for ordinary items.
Higher-level item category
OptionalThe category of the parent item, used when the line is a sub-item — BOM components and free goods sub-items are determined relative to the item above them.
VOV4 — item category determination
VOV4 is the determination table. Each row maps a key combination to a default item category, plus the manual alternatives a user is allowed to choose instead.
| Doc type | Item cat. group | Usage | Higher-level | → Item category |
|---|---|---|---|---|
| OR | NORM | — | — | TAN |
| OR | DIEN | — | — | TAD |
| OR | BANS | — | — | TAS |
| OR | NORM | FREE | TAN | TANN |
| RE | NORM | — | — | REN |
Illustrative rows — your exact entries depend on your document types and item category groups.
VOV7 — define item categories
VOV7 is where the item categories themselves are defined — the behaviour behind the code. The distinction that gets tested in interviews:
VOV7
Definition
Defines what an item category does — pricing, billing relevance, delivery relevance, schedule line allowance, credit relevance, incompletion procedure.
VOV4
Assignment
Decides which item category is picked for a given line, from the four-key combination.
Important item categories
| Category | Description |
|---|---|
| TAN | Standard itemThe default sales item. Priced, delivery relevant, billing relevant. Result of OR + NORM. |
| TANN | Free of charge itemFree goods sub-item. Not priced and not billed independently — created by free goods determination. |
| TAS | Third-party itemVendor ships directly to the customer. Triggers a purchase requisition via schedule line CS. |
| TAB | Individual purchase order itemProcured specifically for this sales order, received into stock, then delivered. |
| TAD | Service itemResult of item category group DIEN/LEIS. Not delivery relevant — services do not ship. |
| TAX | Non-stock / text itemUsed for non-stock materials and text-only lines. |
| TAC | Configurable material itemUsed for variant configuration, where characteristics are assigned at item level. |
| TAP / TAE | BOM header / sub-itemSales BOM explosion — the main item and the components created beneath it. |
| REN | Returns itemDetermined in returns order type RE. Drives the returns delivery and credit memo flow. |
| TALA | Returnable packagingResult of item category group LEIH — packaging that is expected back. |
Worked example: OR + NORM → TAN
A user creates a standard sales order
Document type OR.
They enter a stock material
Its Sales Org 2 view carries item category group NORM.
It is a normal line, not a sub-item
Usage is blank and there is no higher-level item.
SAP looks up OR + NORM + blank + blank in VOV4
The row returns TAN.
TAN applies its behaviour from VOV7
Priced, schedule lines allowed, delivery relevant, billing relevant.
Change one input and the outcome changes: the same material with item category group DIEN determines TAD — a service line that is not delivery relevant.
What does the item category control?
Pricing
Whether the item is priced at all. TANN (free goods) is not priced; TAN is. On BOM items, this decides whether the header or the components carry the value.
Billing relevance
Whether and how the item is billed — order-related, delivery-related, or not at all. Third-party TAS uses order-related billing (relevance "B"); TANN is blank so free goods are never invoiced.
Schedule lines
Whether schedule lines are allowed, and which schedule line category is determined (together with the MRP type). This is what links the item to availability check and transfer of requirements.
Delivery relevance
Whether the item can appear on a delivery. Service items (TAD) are not delivery relevant — forget this and services show up incorrectly on delivery due lists.
Returns
Whether the item is a returns item, which drives the reverse flow — returns delivery, goods receipt movement, and credit memo.
Business data
Whether business data (payment terms, Incoterms) can differ at item level from the header, plus credit relevance, incompletion procedure, and partner determination at item level.
Next: the item category decides whether schedule lines are allowed — the schedule line category then decides the movement type, availability check, transfer of requirements, and purchase requisition. Understand how SAP determines the Schedule Line Category →
Item category group in the material master
The item category group is the material’s contribution to the determination key. It lives on the Sales Org 2 view — technically field MTPOS_MARA in table MARA. Because it is maintained per sales area, the same material can behave differently in different sales organisations.
| Group | Meaning | Typical result |
|---|---|---|
| NORM | Standard stock item | TAN |
| DIEN / LEIS | Service — no physical delivery | TAD |
| BANS | Third-party item | TAS |
| LEIH | Returnable packaging | TALA |
| ERLA / LUMF | Sales BOM — controls whether the header or the components are priced | TAP / TAE |
Changing this field on materials that already have open orders is disruptive — retest every affected document type before you do it.
Third-party item category (TAS)
In third-party processing the vendor ships directly to your customer — you never hold the stock. The item category TAS is what makes that happen:
- →Determination. Item category group BANS on the material yields TAS in a standard order.
- →Purchase requisition. The schedule line behind TAS creates a purchase requisition automatically when the order is saved — no plant goods movement.
- →Goods receipt. The GR is statistical; stock never really enters your plant.
- →Billing. TAS uses order-related billing (billing relevance "B"), triggered after goods receipt or vendor invoice depending on configuration.
Compare with TAB (individual purchase order): there you also procure to order, but the goods come into your stock first and you deliver them yourself.
Free goods item category (TANN)
Free goods are the clearest demonstration of why usage and higher-level item category exist in the key. When free goods determination adds a free sub-item, the determination runs as:
The usage FREE and the parent’s category TAN are what separate the free sub-item from an ordinary line of the same material.
⚠ The classic mistake
If TANN is left billing relevant, the system happily invoices the free goods. Billing relevance must be blank, and the item must not be priced — otherwise “buy 10 get 2 free” quietly bills 12.
BOM & higher-level item determination
When a sales BOM explodes, the components are created as sub-items beneath the main item. Their determination therefore depends on the parent’s item category — which is exactly why the higher-level item category is part of the key.
The design decision is where the value sits. The item category group on the material (ERLA or LUMF) determines whether the header item carries the price and the components are informational, or the header is informational and the components carry the price. The resulting main-item and sub-item categories (commonly TAP and TAE) follow from that choice in VOV4.
Practical consequence: if pricing appears on the wrong level of a BOM, the fault is almost always the item category group on the material, not the pricing procedure.
What changed in S/4HANA
Honestly: very little — and that is worth knowing. Item category determination is one of the stable parts of SD. VOV4 and VOV7 work as they always have, the four-key logic is unchanged, and TAN, TANN, TAS and the rest behave the same. Knowledge from ECC transfers directly.
What changed is the landscape around it — and that is where consultants get caught:
- →Customer master: Business Partner replaces XD01 — read the guide
- →Availability check: Advanced ATP replaces the classic check — read the guide
- →Output: BRF+ replaces NACE determination — read the guide
Where more flexibility is needed today, it usually comes from extensibility — custom fields and BAdI-based logic — rather than a change to the determination table itself.
Common errors & troubleshooting
"No item category available" when entering a line
Cause: No VOV4 entry exists for that combination of sales document type + item category group + usage + higher-level item category.
Fix: Check the material master Sales Org 2 view for the item category group, then create the missing VOV4 entry. The message names the combination it could not find — read it literally.
Wrong item category determined
Cause: The material has an unexpected item category group, or a manually-allowed alternative category is being defaulted.
Fix: Verify MTPOS_MARA on the material, then check the default and the manual alternatives on the VOV4 entry.
Free goods sub-item is being priced or billed
Cause: TANN is configured with pricing or billing relevance switched on.
Fix: In VOV7, TANN must have pricing set so the item is not priced, and billing relevance blank.
Service item appearing on the delivery due list
Cause: The service item category is flagged as delivery relevant.
Fix: Check the item category group on the material (DIEN/LEIS) and confirm the resulting category is not delivery relevant.
Third-party item not creating a purchase requisition
Cause: The schedule line category behind TAS is not the one that triggers a PR, or the item category was not determined as TAS at all.
Fix: Confirm the item category is TAS, then check the schedule line category determination and its purchase requisition settings.
Item category cannot be changed manually in the order
Cause: No manual alternative item categories are maintained on the VOV4 entry.
Fix: Maintain the permitted alternatives in VOV4 — only those appear in the dropdown for the user.
Interview questions
Item category determination is a favourite of SD interviewers because it separates people who configured it from people who read about it.
What are the four keys of item category determination?
Sales document type, item category group (from the material master), usage, and higher-level item category. The combination is maintained in VOV4.
A material has item category group NORM and the order type is OR. What item category results?
TAN. If the same material had item category group DIEN (service), the result would be TAD.
Where does the item category group come from?
The material master, Sales Org 2 view — field MTPOS_MARA in table MARA. It can differ per sales organisation and distribution channel.
What is the difference between TAS and TAB?
Both are procure-to-order. TAS is third-party — the vendor ships directly to the customer and you never hold the stock. TAB is an individual purchase order — you procure it, receive it into your own stock, then deliver it yourself.
Why is the higher-level item category part of the key?
Because sub-items must be determined differently from the item above them — BOM components and free goods sub-items depend on what the parent item is. Free goods, for example, are determined with usage FREE and the parent category as the higher-level key.
What does the item category control?
Pricing, billing relevance, schedule line allowance, delivery relevance, returns behaviour, credit relevance, incompletion procedure, and whether business data may differ at item level.
Frequently Asked Questions
What is item category determination in SAP SD?
Item category determination is how SAP automatically decides the item category for every line in a sales document. It uses a four-part key: sales document type, item category group (from the material master), usage, and higher-level item category. That combination is maintained in transaction VOV4, and the resulting item category then controls how the line behaves — pricing, billing, delivery, schedule lines, and returns.
What is the difference between VOV4 and VOV7?
VOV7 defines the item categories themselves — what TAN, TANN, or TAS actually do (pricing, billing relevance, delivery relevance, schedule line allowance, and so on). VOV4 is the determination table that decides which of those item categories is picked for a given line. In short: VOV7 is the definition, VOV4 is the assignment.
Where is the item category group maintained?
On the material master, Sales Organisation 2 view — technically field MTPOS_MARA in table MARA. Common values are NORM (standard), DIEN or LEIS (service), LEIH (returnable packaging), and ERLA/LUMF for BOM handling. Because it is maintained per sales area, the same material can behave differently in different sales organisations.
What item category results from OR and NORM?
TAN, the standard sales item. It is priced, delivery relevant, and billing relevant. If the item category group were DIEN instead of NORM, the same order type would determine TAD, a service item that is not delivery relevant.
What is usage in item category determination?
Usage is an optional key that distinguishes special uses of an item within the same document and material combination. The clearest example is free goods: a free sub-item is determined with usage FREE, which — together with the parent item category — yields TANN instead of TAN. Usage is blank for ordinary items.
Can the item category be changed manually in the sales order?
Only to the alternatives allowed in the VOV4 entry. Each determination row can carry a default item category plus permitted manual alternatives, and only those appear to the user. If nothing can be changed, no alternatives were maintained.
Did item category determination change in SAP S/4HANA?
No — this is one of the areas that stayed stable. VOV4 and VOV7 work the same way, the four-key logic is unchanged, and TAN, TANN, TAS, and the rest behave as before. What changed around it is the surrounding landscape: Business Partner replaces the customer master, advanced ATP handles availability, and BRF+ handles output. So item category knowledge from ECC transfers directly to S/4HANA.
Why do I get "no item category available"?
Because no VOV4 entry exists for the combination the system built from your document — sales document type, the material's item category group, usage, and the higher-level item category. Read the error message: it names the exact combination. Check the material's item category group first, since an unexpected or blank group is the most common cause, then create the missing determination entry.
Practise this properly before the interview.
The SD Vault has depth-graded practice questions on item categories, schedule lines, third-party and free goods — plus 38 real configuration scenarios, built by an SAP SD Solution Architect with 17+ years on live projects.
Get Lifetime Access →Or try the free sample pack — 10 real interview questions with full answers, a complete configuration scenario, and a Ready Reckoner topic. No login.