TACT table — Activity Text Table for Authorization Codes

One row in TACT represents the language-specific text for a single activity code. Activity codes are the two-digit values held in the ACTVT field, which is present in a very large share of SAP authorization objects because it is the field that says whether a given authorization check permits create, change, display, delete, execute, and so on. TACT is not part of the authorization check itself. It exists so that PFCG, SU21 and related maintenance transactions can show a human-readable label instead of a raw two-digit number whenever an ACTVT value has to be displayed to an administrator building or reviewing a role. Standard activity codes (01, 02, 03, 06, 16, 08, and others) are delivered with SAP content; the customer-reserved range in the 90s is left for local extensions and is where text gaps most often appear.

TACT is cross-client and tiny, on the order of a few hundred rows covering roughly ninety activity codes across the installed languages, so there is no performance concern in selecting from it directly. The only thing worth restricting on is SPRAS, because selecting without a language filter returns one row per language for the same activity code and produces duplicates in a report or a join. There is nothing to tune here; if a select against TACT feels slow, the problem is in what it is being joined to, not in TACT itself.

Symptom: a role shows a blank or unreadable label next to an activity value in PFCG's authorization data screen. Select from TACT where ACTVT equals the code shown in the role (for example 90) and SPRAS equals the logon language. No row returned confirms the code simply has no maintained text in that language; the authorization itself, and its check at runtime, is completely unaffected by this gap.

TACT continues to exist in S/4HANA in the same cross-client, text-table shape. The concept of a two-digit activity code driving the ACTVT field across authorization objects is unchanged from ECC, so TACT keeps exactly the same supporting role in PFCG and SU21 rendering. There is no compatibility view replacing it and no structural change to plan for.

Questions about missing or wrong activity text belong to whoever owns authorization object design, usually the security or GRC team maintaining custom objects, not Basis and not a business data owner. Any fix means adding or correcting a text entry as part of the same change process used for the authorization object itself, since the two are maintained together.

TOBC holds the permitted activities per authorization object and is the table that actually governs validity, with TACT supplying its display text. AGR_1251 carries the ACTVT values assigned inside a role's authorization data and is the most common join target when reporting on role content. USOBT_C and USOBX_C hold the SU24 default value proposals per transaction, including ACTVT defaults, and are maintained through SU24 and read during PFCG role building.