TVKO table — Sales Organization Master Table
TVKO is the SD configuration table that defines sales organizations, one row per sales organization code. It carries the company code, statistics currency, and credit control area assigned to that sales org, and every SD document that stores VKORG ultimately resolves its organizational and accounting defaults back to this table.
TVKO holds the master definition of each sales organization used in the SD enterprise structure. This page covers which fields actually live on the table, how it joins into order and billing data, and the recurring mistake of treating it as the source of company code or currency at document level rather than as a default.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 863 words
What it stores
One row in TVKO represents one sales organization: the top node of the SD enterprise structure, below which distribution channels and divisions are combined into sales areas. The row carries the organizational attributes that everything downstream inherits by default - which company code the sales org posts to, which currency it reports statistics in, and which credit control area governs credit checks for orders created under it. TVKO is maintained during enterprise structure configuration, not by end users, and it changes rarely once a sales organization is live, because every open sales document, condition record, and authorization object built around that VKORG depends on the assignment staying stable.
Key fields
- MANDT - client
- VKORG - sales organization key, the four-character code referenced by every SD document
- BUKRS - company code assigned to the sales organization for financial posting
- VTEXT - descriptive name of the sales organization shown in dropdowns and reports
- WAERS - statistics currency used as the default reporting currency for the sales org
- KKBER - credit control area assigned to the sales org for credit management checks
How it joins the data model
- TVKO-VKORG = VBAK-VKORG
- TVKO-VKORG = VBRK-VKORG
- TVKO-VKORG = KNVV-VKORG
- TVKO-VKORG = VBKD-VKORG
- TVKO-VKORG = KONH-VKORG
How to read it safely
TVKO is a client-dependent config table with typically a few dozen rows per client, so selectivity is not a performance concern. The only thing worth restricting on is VKORG when checking a specific sales organization's setup, and MANDT if querying across clients in a system copy comparison. Do not join TVKO into large transactional tables like VBAP or LIPS for reporting - pull VKORG from the header table once and look up TVKO separately, otherwise the join adds nothing but confusion since TVKO contributes only a handful of static attributes per sales org.
How to prove it in the data
Symptom: a sales order billing document fails to post to Financial Accounting with no company code found for the sales organization. Select TVKO where VKORG equals the sales org on the order and check whether BUKRS is populated. If BUKRS is blank, the sales organization was created without completing the company code assignment step in enterprise structure configuration, and no order under that VKORG can be billed until it is filled in.
ECC vs S/4HANA
TVKO carries forward into S/4HANA unchanged in structure and content, since it is a small configuration table and organizational structures were not redesigned in the move from ECC. It is exposed through the standard compatibility layer for reporting and is still maintained through the same enterprise structure configuration activities. No functional replacement or restructuring is expected for this table.
Common pitfalls
- Treating TVKO-WAERS as the document currency: it is the statistics currency for reporting, not the currency the order or invoice is actually created in - that comes from the customer master or is entered manually on the document.
- Assuming TVKO-KKBER is always the credit control area actually used: credit control area determination can be overridden at customer master level or by a user exit, so TVKO only supplies the default when nothing else overrides it.
- Assuming a change to TVKO-BUKRS retroactively repoints existing documents: open sales orders and unbilled deliveries keep whatever company code was resolved at creation time on their own document fields, so changing TVKO fixes only future documents.
- Confusing sales organization with sales area validity: TVKO defines the sales org itself, not which distribution channel and division combinations are valid under it - that validity lives in a separate sales area table, and a sales org existing in TVKO does not mean every VTWEG/SPART pairing under it is usable.
- Deleting or renumbering a VKORG that has historical documents: the code is a foreign key scattered across VBAK, VBRK, KNVV, and pricing condition tables, so removing the TVKO row does not remove the dependency and simply orphans reporting.
- Assuming plant or valuation area comes from TVKO: those are determined by distribution chain and delivering plant configuration, not by the sales organization record.
Whose problem this is
This table belongs to the SD solution architect or enterprise structure owner during design, and to SD functional configuration afterward. Business users never touch it directly. Questions about why a sales org has no company code, wrong currency, or no credit control area assignment go to whoever owns SD enterprise structure config, not to master data or basis teams.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tables/tvkoERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.