Analytics Catalog/SAP S/4HANA/Tables/T007A
Explore the catalogBSETTax RegisterTransaction TaxExtraction
SAP S/4HANA · Transaction Tax

T007A

Customizing table · taxTax code configStill live in S/4HANA

The tax-code Customizing table, it registers each tax code per tax procedure and its type, input or output. The percentage rate itself is not here, it lives in condition records, maintained through transaction FTXP.

Primary key: KALSM · MWSKZ (tax procedure · tax code). The same two-character code (A1, V1, …) can exist in several procedures, so the procedure is part of the key.

Key fields (T007A)

FieldKeyUsedDescription
KALSMPKTax calculation procedure, the country procedure the code belongs to (e.g. TAXUS, TAXDE).
MWSKZPKTax code, the two-character code (A1, V1, A0) stamped on documents.
MWARTTax type, V input tax, A output tax (also additional and reverse-charge types).
ZMWSKTarget tax code, for deferred tax, the code a line transfers to when it becomes due.
LSTMLCountry / reporting attributes attached to the code.
, rate, Not in T007A. The percentage sits in condition records (A003 / KONP), maintained via FTXP.

How the rate is set

T007A registers that a code exists and its type. The name and the rate live in two other places, this split is why you can’t read a rate straight off T007A.

ObjectHoldsJoined on
T007AThe tax code exists, per procedure, and its type (input / output)KALSM · MWSKZ
T007SThe tax code name / description (texts)KALSM · MWSKZ
A003 / KONPThe condition records, the actual percentage rate, by codeMWSKZ (via condition key)
The rate is maintained through transaction FTXP, which writes condition records, not T007A. So a tax code can be active in T007A while its rate changes over time in the condition records, with each rate valid for a date range.

Tax type (input vs output)

The tax type (MWART) on the code decides which side of the return a line lands on, and which G/L tax account it posts to.

MWARTTypeMeaning
AOutput taxTax charged on sales, a liability, payable to the authority.
VInput taxTax paid on purchases, deductible, reclaimed from the authority.
When a document posts with a tax code, the type and rate from config drive the amount, and a summarized line is written to BSET. That is the link between this config table and the transactional tax data.

S/4HANA status

T007A is unchanged in S/4HANA, a Customizing table, maintained through transaction FTXP like always. Tax codes and their rates are still defined this way; what changed elsewhere is how the tax data posts (the Universal Journal) and how statutory returns file (Advanced Compliance Reporting).

Because it is Customizing, T007A is small and slow-moving. In an analytics model it is a lookup, the code, its type, and (joined to the condition records) its rate, that you attach to the transactional tax lines in BSET.

Where this surfaces, how to read it

Reports that use it

How the data gets out: T007A is a Customizing table, extract it as a lookup via SLT or Table / Table-CDC, joined to the transactional tax lines, never ODP-RFC (SAP Note 3255746). See the extraction pattern →
Need the tax-code config in your model?
We build T007A (plus texts and condition records) as the conformed tax-code dimension behind your VAT layer, code, type, and rate, and you own the code.
Talk to us
Terms on this page
Tax code (MWSKZ)
The two-character code stamped on a line, sets the rate, type, and accounts.
Tax procedure (KALSM)
The country-specific tax calculation procedure a code belongs to (TAXUS, TAXDE).
Tax type (MWART)
Whether a code is input tax (V) or output tax (A).
Output tax
Tax charged on sales, a liability payable to the authority.
Input tax
Tax paid on purchases, deductible, reclaimed from the authority.
FTXP
The transaction that maintains tax codes and their rates.
Condition record
Where the actual percentage rate lives (A003 / KONP), by code and date.
Target tax code (ZMWSK)
For deferred tax, the code a line transfers to when it becomes due.
BSET
The tax data document segment, the transactional tax lines these codes drive.
CDS view
Core Data Services, an SAP-supplied, upgrade-safe view onto the data.
ODP-RFC
An older extraction route SAP now bans for non-SAP tools (Note 3255746).