TVTW table — Distribution Channel Master Table
TVTW holds the client-wide list of valid distribution channels (VTWEG), the two-character code used everywhere in SD to segment how a product reaches the customer, such as wholesale, retail, or direct sales. It is a small, low-volume control table maintained in customizing, not a transactional or master data table, and it rarely changes once a rollout is live.
TVTW is the customizing table that defines which distribution channel codes exist in the system. It is the anchor for every sales area combination and every place a document or customer master carries a VTWEG value, but it says nothing about which combinations are actually valid or which customer is extended to which channel.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 893 words
What it stores
One row in TVTW represents a single distribution channel code that has been defined in the system, such as '10' for direct sales or '20' for wholesale. The table itself is a flat, client-dependent list of codes with no organizational assignment built in; it does not say which sales organization uses that channel, which division it can combine with, or which company code it belongs to. Those relationships live in separate assignment tables. TVTW is consulted constantly as a lookup and foreign key target from documents and master data, but as a standalone table it is almost never the source of a functional problem, because there is little to configure wrong inside it beyond the code and its description.
Key fields
- MANDT - client, standard first key field on every client-dependent customizing table
- VTWEG - the two-character distribution channel code, the actual key value referenced by every other table that carries a distribution channel
How it joins the data model
- TVTW-VTWEG = VBAK-VTWEG, sales document header carries the distribution channel of the sales area it was created in
- TVTW-VTWEG = KNVV-VTWEG, customer sales area segment, this is where a customer is extended to a specific distribution channel
- TVTW-VTWEG = VBRK-VTWEG, billing document header inherits the distribution channel from the underlying sales document
- TVTW-VTWEG together with TVKO-VKORG and TSPA-SPART form the three-part sales area key used across SD configuration and master data
How to read it safely
TVTW is tiny, typically a few dozen rows per client, so selectivity is not a concern; a full table scan costs nothing. Always restrict by MANDT as with any customizing table, though in practice most tools do this automatically. The only real reading trap is treating TVTW as if it told you something valid about a sales area. It does not. It only confirms the code exists. Whether that code is actually usable with a given sales organization and division is governed by the sales area assignment table, not by TVTW.
How to prove it in the data
Symptom: a user reports that distribution channel '30' does not appear as a selectable option when creating a sales order. First confirm the code exists at all: select from TVTW where VTWEG equals '30'. If no row comes back, the channel was never defined and customizing is missing. If a row does exist, the problem is not TVTW at all, it is that '30' has not been assigned to the relevant sales organization and division combination, which is checked in the sales area assignment table, not here.
ECC vs S/4HANA
TVTW carries forward into S/4HANA unchanged as a customizing table; the distribution channel concept and its key structure were not touched by the simplification items around sales document processing. It is exposed through the standard customizing transactions and through CDS views used in analytics and Fiori apps that need to display or filter by distribution channel, but the underlying table and its meaning are the same as in ECC.
Common pitfalls
- Assuming a distribution channel is usable simply because it exists in TVTW. Existence in TVTW only means the code has been defined somewhere in the client, not that it is valid for the sales organization in question. The valid combination is maintained in the sales area assignment configuration, and TVTW has no visibility into it.
- Deleting or renaming a distribution channel code in TVTW after it has been used in live documents. VBAK, KNVV, VBRK, and other tables still hold the old VTWEG value, so the master record becomes orphaned relative to customizing and reports built on joins start dropping rows silently.
- Confusing TVTW with the customer-specific extension. A customer existing in KNA1 does not mean the customer can be used with every distribution channel; that requires a KNVV row for the specific sales area, and the absence of that row is a common cause of 'customer not found in this sales area' errors that people wrongly go looking for in TVTW.
- Expecting a description field directly on TVTW. The channel description sits in the language-dependent text table, so a lookup by VTWEG alone in TVTW without joining the text table returns no readable name, and some consultants mistakenly conclude the channel has no description configured at all.
Whose problem this is
Questions about which distribution channel codes exist belong to the SD functional consultant maintaining sales area customizing. Questions about why a specific customer or material is not usable in a given channel belong to whoever owns customer and material master data extension, since that is a master data assignment problem, not a TVTW problem.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tables/tvtwERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.