TVFK table — TVFK Billing Type Customizing Table

One row in TVFK represents one billing document type - the configuration object identified by the code entered in FKART, such as F2 for a standard invoice, S1 for a cancellation, or G2 for a credit memo. The row does not represent a document; it represents the rulebook a document of that type follows. It fixes what kind of billing category the type belongs to (invoice, credit memo, cancellation, pro forma and similar), which billing type is used to cancel documents created with it, and low-level controls such as whether posting to accounting is blocked and whether statistics update is relevant. Every actual billing document created in VBRK points back to exactly one row here through its FKART field, and inherits that row's behaviour unless something further downstream in the pricing or account determination chain overrides it.

TVFK is a small, client-dependent customizing table, typically a few dozen rows per client even in a system with heavy Z-type usage. There is no real performance concern reading it directly; the risk is misreading what a field controls. Always restrict on MANDT first out of habit, then select on FKART if checking a specific type. Do not try to infer document behaviour purely from this table without also checking the copy control and account determination tables that sit alongside it - TVFK sets the type's identity, not the full behaviour chain a document goes through.

Symptom: a billing document cannot be cancelled, or the wrong cancellation type is proposed. Pull the FKART from the offending VBRK record, then select TVFK where FKART equals that value and read the cancellation billing type field. If that field is blank, the type was never configured for cancellation and the system is behaving correctly by refusing or by falling back to a manual entry - the fix belongs in customizing, not in the document.

TVFK carries forward into S/4HANA unchanged as a customizing table maintained through the standard SD billing configuration path. It has not been replaced by a CDS compatibility view because it is a configuration table, not a transactional table subject to the VBAK/VBAP-style data model simplification. Existing custom billing types and their TVFK entries migrate through the standard customizing transport path during an ECC to S/4HANA conversion without remapping.

TVFK is SD configuration owned by the SD/billing functional consultant, maintained through the standard billing customizing path and moved by change requests through the transport landscape. A functional question about why a billing type behaves a certain way belongs to that consultant; a question about why a specific transport failed to bring a TVFK entry into a downstream client belongs to Basis.

VBRK is the billing document header table that consumes every TVFK entry through FKART; VBRP is the corresponding item table. T683 holds pricing procedure determination and can be keyed on billing type for billing-specific pricing. Billing types are created and changed in the standard SD customizing transaction for billing document type definition, and billing documents themselves are created through the standard billing transaction, both of which write or read TVFK indirectly rather than exposing it for direct maintenance outside customizing.