TSPA table — TSPA Division Master Table

Each row in TSPA represents one division code that has been defined as valid in the client. Division (Sparte) is one of the three legs of the SD sales area, alongside sales organization and distribution channel. The table itself is deliberately thin: it exists to answer the question 'is this division code a real, configured value' rather than to describe what the division means commercially. Divisions get assigned to sales organizations elsewhere, and the human-readable description lives in a separate text table keyed by language. Consultants encounter TSPA almost exclusively during customizing checks, authorization design, or when tracing why a sales area combination is rejected as invalid on a customer or sales document.

TSPA is client-dependent and tiny, typically a handful to a few dozen rows per client, so selectivity is not a concern. There is nothing to restrict on beyond the client itself. The table answers a yes-or-no question about a code's existence; it is not a lookup for meaning. If a description is needed, the join has to go to the language-dependent text table, filtered on the logon language, not to TSPA itself. Do not attempt to infer business rules, sales org assignments, or authorization scope from TSPA alone.

Symptom: a sales order cannot be saved because the sales area sales-org/distribution-channel/division is rejected as not maintained. Select TSPA for the client and the division code entered on the order. If the row is missing, the division itself was never created in customizing, which is a configuration gap, not a master data gap. If the row exists, the actual problem is almost always the sales-area combination in the sales organization structure or the customer's extension to that sales area, not TSPA.

TSPA carried forward into S/4HANA without a change in shape or purpose. Division as a concept is unchanged in S/4HANA's sales area model, and the table continues to be maintained through the same customizing activities as in ECC. No compatibility view replacement is required for this table because it is pure configuration content rather than transactional data subject to the S/4HANA data model simplifications.

Division setup is an SD functional configuration decision, owned by the SD or O2C process consultant during org structure design, usually agreed jointly with FI and controlling since division often maps onto reporting segments. Once live, adding or changing a division is a change request through the normal transport process, not an ad hoc fix applied by a support consultant reacting to a single stuck order.

The division's language-dependent description sits in a companion text table maintained through the same customizing transaction used to create TSPA entries. Division values are consumed downstream by VBAK at sales document header level, by KNVV as part of the customer sales area key, and by pricing and rebate condition tables such as KONA where agreements are restricted by division. Assignment of divisions to a sales organization is configured in separate organizational-structure customizing, not in TSPA itself.