Search Results gl_cons_segment_map_s

Overview

GL_CONS_FLEX_HIER_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite (validated in 12.1.1 and 12.2.2). It supports the consolidation functionality within Oracle General Ledger, specifically the definition and maintenance of flexible hierarchies used when mapping consolidation segment values between parent and subsidiary ledgers. Consolidation in EBS requires that the chart of accounts segments of a subsidiary be remapped to a corresponding segment in the parent ledger; the consolidation hierarchy defines how those segment values roll up or align. This package encapsulates the low-level data manipulation operations against the consolidation flex hierarchy and segment map tables, providing controlled insert, update, delete, and locking behavior rather than requiring callers to issue direct DML. The dependency list confirms its tight coupling to GL_CONS_FLEX_HIERARCHIES, GL_CONS_SEGMENT_MAP, the GL_CONS_SEGMENT_MAP_S sequence, and the underlying FND_FLEX_VALUE_HIERARCHIES foundation table. The presence of FND_MESSAGE and APP_EXCEPTION indicates that errors are surfaced through the standard Oracle Application Object Library message and exception framework.

Key Procedures and Functions

The documented API surface comprises seven procedures and functions:

• OVERLAP — Evaluates whether two consolidation segment value ranges intersect. This is essential for validating hierarchy definitions so that overlapping mappings are detected and rejected before data is committed.
• COUNT_RANGES — Returns a count of the ranges defined for a given hierarchy or mapping context, used to drive validation and display logic.
• INSERT_ROW — Inserts a new consolidation flex hierarchy or segment map record, applying the sequence and defaulting rules required by the consolidation model.
• LOCK_ROW — Acquires a row-level lock to serialize concurrent maintenance of hierarchy records, preventing lost updates from simultaneous session activity.
• UPDATE_ROW — Modifies an existing hierarchy or segment map record.
• UPDATE_PARENT_VALUES — Propagates or recalculates parent segment values when hierarchy structure changes, maintaining consistency between child assignments and their parent rollups.
• DELETE_ROW — Removes a hierarchy or map record, typically after dependent validation.

These routines form a cohesive maintenance layer, with OVERLAP and COUNT_RANGES acting as analytical validators and the remaining procedures performing persistence operations guarded by LOCK_ROW.

Tables Accessed

• GL_CONS_FLEX_HIERARCHIES — Stores the consolidation hierarchy definitions themselves; the primary target of INSERT_ROW, UPDATE_ROW, and DELETE_ROW.
• GL_CONS_SEGMENT_MAP — Holds the mapping of segment values between source and target ledgers, maintained alongside the hierarchy.
• GL_CONS_SEGMENT_MAP_S — The sequence supplying unique identifiers for segment map rows created through INSERT_ROW.
• FND_FLEX_VALUE_HIERARCHIES — The Oracle Flexfields foundation table providing the value hierarchy definitions referenced by consolidation hierarchies.
• DUAL — Used for scalar evaluations, such as range counts and overlap checks.

Usage Notes

This package is an internal maintenance component rather than a public integration API. It is referenced by no other database object, indicating that it is invoked from consolidation setup forms (such as the consolidation hierarchy maintenance UI) or from consolidation concurrent programs that build and refresh segment mappings. Custom code should not call these procedures directly, because they assume form context, WHO columns, and locking semantics. Applications instead interact with consolidation hierarchies through standard GL forms, which delegate the underlying DML to this package. Because its logic depends on the FND Flexfields hierarchy model and the APP_EXCEPTION/FND_MESSAGE framework, any direct invocation bypassing those layers risks inconsistent exception handling. When troubleshooting consolidation mapping errors, particularly overlap or orphaned parent value conditions, the procedures OVERLAP, COUNT_RANGES, and UPDATE_PARENT_VALUES are the relevant entry points to inspect.