Results for “gcs_categories_b”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GCS_CATEGORIES_B is a base table within the Oracle E-Business Suite Financial Consolidation Hub (GCS) product family. Its documented description identifies it as the repository for non-translatable information for processing categories, which in Oracle Applications naming conventions distinguishes it from a companion _TL table that would store language-dependent, translatable attributes. The _B suffix confirms that the columns in this table hold language-independent data, so join logic to a translation table is not required for category code resolution.

The table is flagged in the source ETRM metadata as obsolete and explicitly marked "Not implemented in this database." In EBS 12.1.1 and 12.2.2 environments, this indicates the object is retained as a legacy definition from earlier Consolidation Hub releases and may exist only in certain certified environments or prior patch levels. Practitioners should verify existence in DBA_TABLES before relying on it in custom code or reports.

Under the heuristic Data Vault classification mined from the foreign key structure, the object is hub-leaning. This suggests modeling it conceptually as a hub entity — a central catalogue of processing categories keyed by a single business identifier — rather than as a transactional or link table. Consolidation engine run detail records attach to this hub through their CATEGORY_CODE foreign key.

Key Information Stored

The table contains seventeen documented columns. The most significant include:

• CATEGORY_CODE — the primary key column and the sole business-key candidate, backed by unique index GCS_CATEGORIES_B_U1 and enforced by GCS_CATEGORIES_B_PK. This is the value foreign-keyed from downstream consolidation detail tables.
• CATEGORY_NUMBER — a numeric identifier used for sequencing or display.
• CATEGORY_TYPE_CODE — classifies the processing category, driving which consolidation engine logic applies.
• TARGET_ENTITY_CODE and ASSOCIATED_OBJECT_ID — identify the consolidation entity and related object context for the category.
• NET_TO_RE_FLAG and SPECIFIC_INTERCOMPANY_ID — control intercompany netting and specific intercompany matching behaviour.
• SUPPORT_MULTI_PARENTS_FLAG — governs whether hierarchical multi-parent structures are permitted.
• ENABLED_FLAG — the standard Oracle active/inactive indicator.
• GL_CATEGORY_CODE and ORG_OUTPUT_CODE — linkage to General Ledger and organisational output dimensions.
• Standard WHO/audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER (used for optimistic locking).

No separate surrogate numeric key exists; the primary key is the natural business code, which is why the Data Vault heuristic treats the table as a hub.

Common Use Cases and Queries

Functional use cases centre on consolidation setup validation and reporting. A typical query lists active categories:

SELECT category_code, category_number, category_type_code
FROM   gcs_categories_b
WHERE  enabled_flag = 'Y';

Analysts frequently join the category hub to the run-detail table to attribute consolidation activity to a category:

SELECT d.category_code, c.category_type_code, COUNT(*)
FROM   gcs_cons_eng_run_dtls d,
       gcs_categories_b c
WHERE  d.category_code = c.category_code
GROUP  BY d.category_code, c.category_type_code;

Setup administrators also interrogate the flags (NET_TO_RE_FLAG, SUPPORT_MULTI_PARENTS_FLAG, ENABLED_FLAG) to confirm configuration before running a consolidation. Because the object is obsolete, any query should be wrapped in configuration-safe logic or validated against the target instance.

Related Objects

The documented relationship data establishes one inbound foreign key and several logical associations:

• GCS_CONS_ENG_RUN_DTLS — references GCS_CATEGORIES_B.CATEGORY_CODE via GCS_CONS_ENG_RUN_DTLS.CATEGORY_CODE; this is the sole documented dependent table and the principal transactional consumer.
• GCS_CATEGORIES_TL — the expected companion translation table (by naming convention) holding language-dependent description columns.
• GL_CODE_COMBINATIONS — logically linked through GL_CATEGORY_CODE for ledger account derivation.
• GCS consolidation engine programs — the concurrent programs and APIs consuming category configuration at runtime.
• Other GCS_% setup tables sharing the CATEGORY_CODE naming pattern, which frequently appear alongside this hub in configuration extracts.

Given the obsolete status, any dependency analysis should be confirmed against the live instance's actual FK constraints rather than the metadata alone.