TVAP table — Item Category Configuration Table (TVAP)
TVAP is the customizing table behind sales document item categories, maintained through the item category configuration transaction. One row per item category (field PSTYV) holds the control flags that govern whether items of that category are delivery relevant, billing relevant, pricing relevant, and schedule-line capable. It is config master data, not transactional data, and changes to it do not retroactively alter existing sales order items.
This page covers what TVAP stores, its key control fields, and how it links into item category determination and the sales document. The focus is on why flags in TVAP often get blamed for behavior actually driven by determination logic or by values already frozen on existing order items.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 985 words
What it stores
One row in TVAP represents one item category and the set of control indicators that define how a sales document item of that category behaves once assigned. This includes whether the item is relevant for delivery processing, whether it is relevant for billing, whether pricing is carried out, whether schedule lines can be created, and other business-item level switches. TVAP does not hold any sales order, delivery, or billing document itself; it is pure customizing, maintained through the item category definition screen and transported like any other IMG entry. The values in TVAP are read at the moment an item category is assigned to a document item, and the resulting behavior is then stored on the document item record itself, not re-derived from TVAP every time the document is displayed or processed.
Key fields
- MANDT - client
- PSTYV - item category key, e.g. TAN, TANN, TAS, REN; the primary lookup value for the whole table
- LFREL - indicator marking the item category as relevant for delivery, controls whether a delivery item can ever be created for items of this category
- FKREL - indicator marking the item category as relevant for billing, controls whether the item is picked up for invoice creation
How it joins the data model
- VBAP-PSTYV = TVAP-PSTYV, the item category actually assigned on a sales order item and the configuration row that defines its behavior
- T683-PSTYV = TVAP-PSTYV, the determination table that decides which item category gets proposed, cross-checked against the TVAP entry that must exist for the value to be valid
- T683S-PSTYV = TVAP-PSTYV, the sub-item determination table used for scenarios like free goods or third-party items
- TVAK used together with T683 during determination, not joined directly to TVAP, since document type feeds the determination logic rather than the item category's own behavior row
How to read it safely
TVAP is small, a few hundred rows across all clients, so there is no performance concern in reading it. Always restrict by MANDT and PSTYV; there is no reason to ever full-scan it in a diagnostic session. The practical trap is not selectivity but scope: client 000 holds the SAP-delivered originals, and a production client may hold copies with the same or a renamed PSTYV whose flags were changed locally. When comparing behavior against expectation, confirm which client's row is actually in effect for the document being investigated, not the client 000 reference.
How to prove it in the data
Symptom: an order item never generates a delivery item despite the order being released. Read VBAP for the order and item number to get PSTYV. Look up that PSTYV in TVAP in the relevant client and check the delivery relevance flag. If it is off, no delivery will ever be created for that item regardless of stock, credit status, or shipping point, and the fix is either a different item category or a customizing change, not a document-level workaround.
ECC vs S/4HANA
TVAP is unchanged in shape between ECC and S/4HANA. It is foundational SD customizing, not a document or reporting table, so it was never a target for the S/4HANA data model simplification and has no CDS compatibility view sitting in front of it. The maintenance transaction for item categories continues to work the same way, and the field set consultants actually use for diagnosis has not moved.
Common pitfalls
- Changing a flag in TVAP and expecting existing order items to change behavior. The flags are read at item creation and copied into control fields on the document; existing items keep their original behavior until reprocessed or recreated.
- Treating TVAP as the place where item category assignment logic lives. It is not. TVAP only describes the behavior of a category once assigned; the assignment itself is driven by determination tables keyed on document type, item category group, usage, and higher-level item category.
- Assuming naming conventions carry meaning. A category named TANN looks like a delivery-blocking variant of TAN by convention, but the actual behavior is only what the flags in the row say, and a poorly maintained copy can contradict its own name.
- Editing SAP standard item categories directly instead of copying to a Z-namespace entry. This survives until the next upgrade or support pack, then gets overwritten or flagged as a modification.
- Concluding that a missing schedule line is a TVAP problem. Schedule line eligibility and the schedule line category used are governed by separate schedule line category configuration, not by TVAP itself; TVAP only says whether schedule lines are allowed at all for the item category, not which one gets used.
Whose problem this is
Item category configuration belongs to the SD functional consultant or order-to-cash process lead, not to basis or a generic data governance function. Any change to a TVAP entry is a customizing change and goes through the same transport and regression testing as other SD configuration, tested through the full order-delivery-billing chain before it reaches production.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tables/tvapERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.