Search Results gcs_cons_eng_utility_pkg




Overview
Explore in AI Chat

Overview

GCS_CONS_ENG_UTILITY_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Financial Consolidation Hub (FCH) product family, identified by the GCS prefix, which governs consolidation processing across legal entities, balancing segments, and management reporting hierarchies. The package functions as a supporting utility layer beneath the primary consolidation engine, GCS_CONS_ENGINE_PKG, providing reusable helper routines for balance handling, translation, elimination processing, adjustment validation, journal creation, and workflow notification. Its classification in the ETRM repository is OTHER, indicating it is an internal implementation package rather than a published public API. The package is documented as VALID in the ETRM metadata and exposes fourteen procedures and functions, all designed to be called programmatically rather than through a user-facing interface.

Key Procedures and Functions

The documented procedures and functions are grouped by consolidation activity:

Tables Accessed

The package interacts with consolidation configuration, transaction, and run-tracking tables through APPS synonyms. GCS_CONS_ENG_RUNS and GCS_CONS_ENG_RUN_DTLS hold run-level and detail-level execution records. GCS_ENTRY_HEADERS and GCS_ENTRY_HEADERS_S store consolidation journal entries and their statuses. Translation and elimination logic relies on GCS_ELIM_RULES_B, GCS_ELIM_RULE_RELS, GCS_CONS_RELATIONSHIPS, and GCS_ENTITY_CONS_ATTRS. GCS_CATEGORIES_B and GCS_DATASET_CODES support category and dataset validation. GCS_AD_TRANSACTIONS and GCS_CONS_IMPACT_ANALYSES capture adjustment and impact analysis data, while FEM_ENTITIES_ATTR and PLITBLM are referenced for entity attributes and PL/SQL table buffering respectively.

Usage Notes

GCS_CONS_ENG_UTILITY_PKG is invoked indirectly. The ETRM metadata confirms it is referenced by GCS_CONS_ENGINE_PKG and by itself, meaning consolidation engine calls route through these utilities rather than being called by end users. Typical invocation paths include the Financial Consolidation Hub concurrent programs, consolidation workflow activities, and any custom code extending consolidation behavior. Because the package is internal (classification OTHER), Oracle does not guarantee signature stability across patches, so customizations should avoid direct calls and instead extend consolidation through supported setup and extension points.