Results for “category_code”

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

Overview

GCS_CATEGORIES_VL is a multilingual (VL) reporting view owned by the APPS schema within the GCS – Financial Consolidation Hub product. Financial Consolidation Hub provides consolidation, intercompany reconciliation and reporting capabilities. The view presents category definitions used by the consolidation engine to classify balance sheet and income statement activity. In EBS terminology a "category" is an operational grouping that is mapped to a General Ledger category and, in the GCS context, drives intercompany matching, translation and consolidation rules.

The view exposes descriptive attributes (name, description) alongside control flags and identifiers. Because the VL suffix indicates language-dependent translation, the view returns the category name and description for the language of the current session (USERENV('LANG')), while the underlying B (base) table stores language-independent attributes. This makes GCS_CATEGORIES_VL suitable for concurrent programs, OAF pages, forms-based inquiries, and transactional SQL where the user-facing label must reflect the operating language. It is the primary reference for the CATEGORY_TYPE_CODE and associated control columns referenced throughout GCS consolidation logic.

Underlying Base Objects

The ETRM metadata documents the view definition as a join between two tables:

• GCS_CATEGORIES_B – the base table holding all language-independent columns, including CATEGORY_TYPE_CODE, GL_CATEGORY_CODE, NET_TO_RE_FLAG, ENABLED_FLAG and audit columns.
• GCS_CATEGORIES_TL – the translation table supplying CATEGORY_NAME and DESCRIPTION for each CATEGORY_CODE.

The join predicate is B.CATEGORY_CODE = T.CATEGORY_CODE AND T.LANGUAGE = USERENV('LANG'). The view text is documented in the ETRM record, but no referenced base objects were separately catalogued for 12.2.2 beyond the two tables implied by the SELECT. The VL pattern ensures that one row is returned per category in the active language session, avoiding duplicates that could arise if all language rows were joined.

Key Columns

• CATEGORY_CODE – primary business key linking the B and TL tables; foreign key reference used by consolidation and intercompany tables.
• CATEGORY_NAME / DESCRIPTION – translated (language-specific) labels sourced from GCS_CATEGORIES_TL.
• CATEGORY_TYPE_CODE – the key discriminator the user searched for; classifies the category by type (for example, translation, elimination or consolidation category). Lookups consuming this column are typically defined in GCS lookup types.
• GL_CATEGORY_CODE – the corresponding General Ledger category used to reconcile GCS categories to GL reporting categories.
• NET_TO_RE_FLAG – controls treatment in retention/elimination processing.
• TARGET_ENTITY_CODE / ASSOCIATED_OBJECT_ID – identify the target entity or associated object for the category configuration.
• SUPPORT_MULTI_PARENTS_FLAG – indicates whether multiple parents are permitted in the consolidation hierarchy.
• SPECIFIC_INTERCOMPANY_ID – ties the category to a specific intercompany definition.
• ENABLED_FLAG – standard EBS enablement flag.
• Audit columns – CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER (used for optimistic locking in OAF).

Common Use Cases and Queries

Typical scenarios include validating category-to-GL mappings, driving intercompany reconciliation reports, and populating LOVs keyed on CATEGORY_TYPE_CODE. A simple query by category type:

SELECT category_code, category_name, gl_category_code, category_type_code
FROM apps.gcs_categories_vl
WHERE category_type_code = :p_type
AND enabled_flag = 'Y'
ORDER BY category_name;

To retrieve the translated description for the current session language:

SELECT category_code, category_name, description
FROM apps.gcs_categories_vl
WHERE category_code = :p_category;

Because the view restricts rows to USERENV('LANG'), reports should not attempt to join additional language rows directly; use GCS_CATEGORIES_TL when a specific language other than the session language is required. Joins to the view should always use CATEGORY_CODE as the correlation key to the B and TL tables.