Search Results gl_cons_segment_actions_pkg




Overview
Explore in AI Chat

Overview

The APPS.GL_CONS_SEGMENT_ACTIONS_PKG package body supports the Consolidation segment mapping framework in Oracle General Ledger. Its business purpose is to manage the rules that determine how individual segments of a source (from) chart of accounts are translated to corresponding segments of a target (to) chart of accounts during consolidation. Each stored row represents a consolidation segment action: a definition of the criteria against which a from-segment value is evaluated and the resulting to-segment value that should be substituted when the criteria are satisfied. The package therefore underpins both the maintenance of these mapping rules through the Consolidation workbench and the runtime validation logic applied when consolidation data is generated.

Because the package body operates directly against the consolidation mapping tables and the flexfield value set definitions, it serves as the low-level persistence and validation layer for segment-level consolidation actions. It is classified as an OTHER API rather than a public open-interface API, indicating that it is intended for internal use by Oracle Consolidation forms, concurrent processes, and dependent consolidation packages rather than as a documented integration entry point for external applications.

Key Procedures and Functions

The package exposes eleven documented procedures and functions. INSERT_ROW, UPDATE_ROW, and DELETE_ROW perform the standard DML lifecycle on consolidation segment action records, while LOCK_ROW provides the pessimistic locking behavior used to serialize concurrent edits of a single action row, typically from the Consolidation workbench form. CHECK_DUPLICATE_RULES enforces uniqueness constraints so that conflicting segment action definitions cannot be saved for the same consolidation context.

GET_VALIDATION_TYPE returns the validation mode associated with a segment action, indicating how the from-segment value is matched (for example, by exact value, range, or hierarchy). SET_CRITERIA establishes the comparison criteria used by that validation logic. VALIDATE_FROM_SEGMENT applies the configured validation to a supplied from-segment value and determines whether the action's mapping criteria are met.

GET_COA_MAPPING_ID, GET_FROM_COA_ID, and GET_TO_COA_ID are lookup functions that resolve the chart of accounts mapping identifier and the source and target chart of accounts identifiers associated with a given segment action or mapping context. Together these accessors allow calling code to navigate between a segment action definition and the higher-level mapping and chart of accounts structures that own it.

Tables Accessed

The package reads and writes GL_CONS_SEGMENT_MAP, the base table that stores consolidation segment mapping action definitions, and its companion GL_CONS_SEGMENT_MAP_S, which holds the corresponding translated (short) text or descriptive columns used for multi-language display. GL_CONS_FLEX_HIERARCHIES is referenced to support hierarchy-based validation, allowing a from-segment value to be matched against a defined parent-child hierarchy rather than a single literal value. FND_FLEX_VALUE_SETS is consulted to confirm that segment values belong to the appropriate key or descriptive flexfield value set. DUAL is used for single-row evaluations and parameter defaults. Error and message handling draws on APP_EXCEPTION and FND_MESSAGE.

Usage Notes

GL_CONS_SEGMENT_ACTIONS_PKG is invoked indirectly by the Oracle General Ledger Consolidation forms and by the concurrent programs that build consolidation mappings, rather than through a published open interface. The presence of LOCK_ROW and the row-level DML procedures reflects an interactive form usage pattern in which a single segment action is queried, locked, edited, and committed within one transaction. The duplicate-rule and validation functions run during data entry to prevent inconsistent mappings.

Custom code should treat the package as internal: the supported integration surface for consolidation mappings is the Consolidation workbench and its associated concurrent processes. Direct calls should only be made when extending consolidation behavior in a controlled development environment, with careful attention to the locking and duplicate-checking routines. The package is documented as being referenced by one other database object and itself depends on the APP_EXCEPTION and FND_MESSAGE utility packages, so modifications must preserve those dependencies to remain valid.