Search Results ben_tcs_cat_pk




Overview

BEN_TCS_CAT is a core configuration table in the Oracle Advanced Benefits (BEN) module of Oracle E-Business Suite, holding the definition of a compensation category. Compensation categories drive how the benefits engine treats different forms of compensation during eligibility determination, rate calculation, and flexible credit processing — for example standard salary, hourly wages, bonus, or imputed income. Each row represents one compensation category that can be attached to a benefit plan or program, and the table functions as a reference container that aggregates the compensation objects, columns, and rows that together describe how a specific compensation type is calculated. The object is documented as VALID in the BEN schema in both EBS 12.1.1 and 12.2.2. Heuristically, this table is best modeled as a Data Vault hub, since it holds the durable business key CAT_ID and the descriptive identity of each compensation category, with satellite-style attributes such as NAME and CHART_TYPE_CD attached to it and no upstream foreign keys for its own primary key.

Key Information Stored

The primary key is enforced by BEN_TCS_CAT_PK on CAT_ID, which is the surrogate identifier for a compensation category. BEN_TCS_CAT_U1 on CAT_ID is documented as a unique index and therefore acts as the strongest business-key candidate, though the NAME column typically provides a more human-readable business identity. The most significant columns are:

  • CAT_ID — primary key and internal identifier for the compensation category.
  • NAME — the user-defined name of the compensation category, displayed in the Benefits configuration UI.
  • CAT_TYPE_CD — code classifying the category type, governing how the category is interpreted by the engine.
  • CHART_TYPE_CD — the chart type used for the category's calculation structure.
  • CHART_ATTRIBUTE_CD — the chart attribute that anchors the category's column and row definitions.
  • COMP_TYPE_CD — the compensation type associated with the category.
  • CONTRIBUTOR_CD — the contributor source, identifying which party or system supplies the compensation.
  • CONTAINER_TITLE — the display title of the container that groups the category's objects.
  • NUMBER_OF_COLUMNS — count of columns defined for the category's calculation grid.
  • SHOW_CONTAINER_LINKS_FLAG — controls whether container links are rendered for the category.
  • NNMNTRY_UOM — the unit of measure for non-monetary compensation amounts.
  • BUSINESS_GROUP_ID — multi-tenant business group partitioning column.
  • OBJECT_VERSION_NUMBER — optimistic locking version, incremented on each update.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns.

Common Use Cases and Queries

The table is most commonly queried when troubleshooting compensation calculations, reviewing benefit configuration, or building extracts that need to resolve CAT_ID values carried on downstream transaction tables. A typical lookup joins the category to its named definition and describes active categories for a business group:

SELECT cat_id, name, cat_type_cd, comp_type_cd, contributor_cd FROM ben.ben_tcs_cat WHERE business_group_id = :p_bg_id ORDER BY name;

Because CAT_ID is propagated into many dependent tables, a frequent migration or reconciliation query counts references to each category to detect orphaned or unused definitions. Reporting on eligibility and rate configuration often starts here and fans out to BEN_TCS_ALL_OBJECTS_IN_CAT, BEN_TCS_COL_IN_CAT, and BEN_TCS_ROW_IN_CAT to reconstruct the full calculation grid. Data-conversion validation also uses this table to confirm that categories loaded via interface tables carry consistent CHART_TYPE_CD and CHART_ATTRIBUTE_CD combinations.

Related Objects

BEN_TCS_CAT is referenced by a broad set of dependent tables that carry CAT_ID as a foreign key. The most significant include:

Readers should note that several of these references originate outside the BEN module, so the CAT_ID column can denote a category identifier with a broader contract-terms or subledger meaning; joins should always be qualified by the owning product context.