Search Results gcs_create_levels_pkg




Overview
Explore in AI Chat

Overview

GCS_CREATE_LEVELS_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Enterprise Performance Foundation / Financial Consolidation Hub (ETRM) product family, where the GCS prefix designates objects used by the Global Consolidation System. The package supports the creation and maintenance of consolidation hierarchies by generating hierarchy "levels" — the ranked groupings of parent and child dimension members that the consolidation engine uses to determine the order in which entities are aggregated.

In the consolidation model, dimensions such as Company, Account, and Cost Center are organized into dimension groups, and each dimension group may have one or more hierarchies. Consolidation must proceed level by level, from the lowest members upward, so that a parent is not processed before all of its children have been aggregated. GCS_CREATE_LEVELS_PKG provides the programmatic mechanism that inspects the hierarchy definition or a staged set of hierarchy members and materializes the derived level assignments that the consolidation processes consume.

Key Procedures and Functions

The ETRM repository documents a single entry point for this package:

  • GCS_CREATE_LEVEL — the principal routine of the package. Its purpose is to derive and populate level assignments for the members of a consolidation hierarchy. The procedure resolves the hierarchy structure and writes the resulting level information into the staging table used by downstream consolidation processing. No parameter list is documented in the ETRM metadata, so the exact signature should be confirmed by reviewing the package specification in the database (for example, by querying ALL_ARGUMENTS or by displaying the package source).

Because the package body is marked VALID and the specification exposes only this one program unit, the package should be treated as a focused utility rather than a broad consolidation API. The single-procedure design suggests that callers are expected to invoke it directly, passing the identifying context of the hierarchy to be leveled.

Tables Accessed

The documented dependencies show that the package reads from the Enterprise Performance Foundation dimension and hierarchy tables and writes to a consolidation staging table:

  • FEM_DIMENSIONS_B — the base table holding dimension definitions. The package reads dimension metadata to identify the dimension that owns the hierarchy being processed.
  • FEM_DIMENSION_GRPS_B_T — base dimension group definitions in the current edition; supplies the dimension group context for level creation.
  • FEM_DIMENSION_GRPS_TL_T — the translated (language-specific) dimension group table, used when a level name or description must be resolved in the session language.
  • FEM_HIER_DIM_GRPS_T — the association between hierarchies and dimension groups; the package reads this to determine which hierarchies belong to the selected dimension group.
  • GCS_HIER_MEMBERS_T — the hierarchy member table, providing the parent-child relationships from which level numbers are computed.
  • GCS_EPB_LEVELS_GT — the levels staging table. This is the primary write target; the derived level records are inserted here for use by the consolidation batch.

Usage Notes

GCS_CREATE_LEVELS_PKG is an internal ETRM utility rather than a public integration API. The ETRM dependency report records no other packages referencing it, which indicates that it is invoked from outside the PL/SQL package layer — typically from the consolidation setup and administration forms in the Global Consolidation System, or from a concurrent program that refreshes hierarchy levels as part of the consolidation cycle.

Typical invocation occurs after hierarchy definitions or hierarchy members have changed and before consolidation is executed, ensuring that the level numbers in GCS_EPB_LEVELS_GT reflect the current structure. Because the package writes to a staging table, it is normally run within a controlled batch window. Custom code should not call this package directly; implementations requiring programmatic level generation should use the supported Enterprise Performance Foundation APIs or the standard consolidation concurrent programs, and should never modify the underlying FEM or GCS tables directly. Any diagnostics on the package should be performed by reading its source through ALL_SOURCE in the APPS schema.