SAP Knowledge Base Article - Public

3846848 - Custom 9* tax category not replicated to STCD fields

Symptom

Tax number fields STCD1, STCD2, or STCEG are blank in tax declaration reports, billing documents, or FI accounting documents, even though the tax number is correctly stored and visible on the Business Partner record. The affected Business Partners belong to a country for which SAP does not deliver a standard tax number category for the required field, or a custom tax number category under the user namespace (prefix 9, e.g. 9MA1, 9DK1, 9HK1) was created and assigned to the Business Partner.

Environment

SAP S/4HANA Cloud Public Edition

Cause

This behavior has two related causes depending on the entry point.

Missing standard SAP tax category for the country

SAP delivers standard tax number categories only for localized countries. The suffix of the category name determines the classic field it maps to: suffix 0 → STCEG, suffix 1 → STCD1, suffix 2 → STCD2 (see SAP Note 2865204). For countries not covered by SAP's standard localization, no such categories are delivered (SAP Note 775919). When a tax number must be stored for such a country, the available configuration option is a custom category in the user namespace: prefix 9, two-character ISO country code, sequential digit 1–6 (e.g. 9MA1). This allows the number to be stored on the Business Partner, but it does not enable replication to the classic tables.

Custom 9 categories excluded from CVI synchronization*

The Customer-Vendor Integration (CVI) framework synchronizes Business Partner tax data to the classic customer and vendor tables (KNA1, LFA1), from which tax declaration reports and other downstream processes read. By design in S/4HANA Cloud Public Edition, CVI excludes all 9* categories from this synchronization. This is documented in the SAP Help Portal for the Define Tax Number Categories configuration activity:

"Custom TAX Category (9*) will not be replicated to the Customer or Vendor tables. Tax numbers must be directly read from Business Partner tables/APIs."

SAP Note 3163497 (July 2022) established this as the intended behavior. The classic CVI field-mapping customizing — available in on-premise systems to configure which tax category writes to which STCD field — is not available as an SSCUI in S/4HANA Cloud Public Edition and cannot be accessed or modified in this environment.

Resolution

Three paths are available depending on the situation.

1. Verify whether a standard SAP category already exists

Before treating the absence of a standard category as confirmed, check SSCUI 104758 or SAP Note 775919. If a standard category ending in the required digit exists for the country but was not used — for example because a custom one was created alongside it — migrate the tax number assignment to the standard category. CVI will then replicate the number correctly on the next Business Partner save.

2. Request standard localization via SAP Customer Influence

If no standard category exists for the country, the only fully supported path that enables automatic CVI replication is delivery of a new standard category by SAP.

Please note that if this is a critical issue, it should be addressed with your SAP Cloud Representative. Otherwise, if you would like to propose it to SAP development through the correct channels, SAP Customer Influence enables customers to submit improvement requests and openly vote on them. These voting results inform SAP of the product enhancements and changes customers are most interested in seeing in future releases.

Get started by:

  1. Opening SAP Customer Influence.
  2. Registering and accepting the Terms of Use.
  3. Choosing a session of your interest.
  4. Taking a look at existing improvement requests and starting to vote and comment.
  5. Creating and submitting your improvement request.

Please refer to the User Guide Documentation for a detailed description of SAP Customer Influence, and to 2963059 — How to Submit Feature Requests for SAP S/4HANA Cloud Product.

3. Read tax numbers directly from Business Partner APIs

As an interim measure, or where population of the classic STCD fields is not strictly required, tax number data can be retrieved directly from the Business Partner layer — table DFKKBPTAXNUM, the Business Partner OData API, or the corresponding SOAP service — rather than from KNA1 or LFA1. This requires adapting any report or integration that currently reads from the classic fields, but it provides access to the data without dependency on CVI replication.

See Also

  • 3163497 - BP CVI: Tax numbers not mapped from BP to Customer/Vendor; establishes non-replication of 9* as by design
  • 3022106 - CVI mapping for custom tax category; reversed by 3163497; prerequisite of 3163497
  • 2865204 - Mapping Business Partner tax number categories to customer/vendor tax number fields; 9* naming convention and field mapping rules
  • 775919 - SAP-delivered standard tax number category reference list
  • SAP Help Portal — Define Tax Number Categories (S/4HANA Cloud Public Edition)

Keywords

STCD1, STCD2, STCEG, tax number, tax category, custom tax category, 9*, CVI, Customer-Vendor Integration, KNA1, LFA1, Business Partner, replication, blank, missing, S/4HANA Cloud Public Edition, tax declaration, SSCUI 102415, SSCUI 104758, BP, localization , KBA , LO-MD-BP-2CL , Business Partners for Public Cloud , Problem

Product

SAP S/4HANA Cloud Public Edition all versions