Search Results check_duplicate_rules
Overview
APPS.GL_CONS_SEGMENT_MAP_PKG is a consolidated PL/SQL package that supports the Consolidation Setup form in Oracle General Ledger, specifically the Consolidation Segment Rules block. Its primary business purpose is to manage the mapping between source and target accounting flexfield segment values used during consolidation, so that balances from one or more subsidiary ledgers can be translated into the chart of accounts structure of a parent ledger. The package encapsulates the standard insert, update, delete, and lock operations against the GL_CONS_SEGMENT_MAP entity, and it also provides validation logic that ensures consolidation segment rules remain internally consistent. The package header carries a header comment dated 2005, indicating a long-standing component of the E-Business Suite code line; it remains present and documented in both release 12.1.1 and 12.2.2. ETRM classifies it as an OTHER API, meaning it is not a public, externally supported interface but rather an internal package used by the consolidation setup forms. It is not referenced by any other documented package, which confirms its role as a form-driven, self-contained utility rather than a shared service.
Key Procedures and Functions
- INSERT_ROW — Inserts a new segment mapping record into GL_CONS_SEGMENT_MAP, populating the mapping identifier, chart of accounts mapping reference, source and target value set identifiers, application column names, segment map type, single value, descriptive attributes, context, and parent rollup value.
- LOCK_ROW — Obtains a row-level lock on an existing segment mapping record, used by the form to implement optimistic locking before an update or delete.
- UPDATE_ROW — Modifies an existing segment mapping record in GL_CONS_SEGMENT_MAP.
- DELETE_ROW — Removes a segment mapping record from GL_CONS_SEGMENT_MAP.
- CHECK_DUPLICATE_RULES — This is the procedure most directly associated with the user's search term. It validates whether a proposed consolidation segment rule duplicates an existing rule definition, guarding against conflicting or redundant segment mappings before they are committed.
- GET_VALIDATION_TYPE — Returns the validation type applicable to a segment rule, allowing the form and related logic to determine how source values should be validated against the target structure.
- CHECK_ANY_PARENT_RULES — Determines whether any parent-level rollup rules exist for the mapping under consideration, which is significant because parent rollup values affect how child segment values are aggregated during consolidation.
Tables Accessed
The package operates primarily on GL_CONS_SEGMENT_MAP, the base table holding segment mapping definitions, and its companion GL_CONS_SEGMENT_MAP_S, which stores the translated (TL) descriptive columns. It reads FND_FLEX_VALUE_SETS to resolve and validate the source and target value set identifiers, and FND_FLEX_VALUE_HIERARCHIES to support hierarchy-based parent rollup evaluations. GL_CONS_FLEX_HIERARCHIES is used to link consolidation mappings to flexfield hierarchies. DUAL is referenced for simple single-row computations, such as generating or checking values within PL/SQL logic. All these objects are accessed through APPS synonyms, consistent with standard EBS coding conventions in the APPS schema.
Usage Notes
GL_CONS_SEGMENT_MAP_PKG is invoked primarily from the Consolidation Setup form when users define, change, or remove consolidation segment rules. The CHECK_DUPLICATE_RULES procedure typically fires during rule entry or save processing to prevent the creation of duplicate consolidation rules, while CHECK_ANY_PARENT_RULES and GET_VALIDATION_TYPE support validation and defaulting behavior in the same block. Because it is classified as an OTHER API and is not referenced by other packages, it should be treated as an internal, form-support package rather than a supported integration point. Custom code that calls it directly assumes responsibility for maintaining compatibility across patches and upgrades; the safer approach for extensions is to model consolidation data through the supported consolidation and mapping APIs instead. In both 12.1.1 and 12.2.2 the package remains available in the APPS schema for form-driven processing.
-
PACKAGE: APPS.GL_CONS_SEGMENT_MAP_PKG
12.1.1
-
PACKAGE: APPS.GL_CONS_SEGMENT_MAP_PKG
12.2.2
-
PACKAGE BODY: APPS.GL_CONS_SEGMENT_MAP_PKG
12.2.2
-
PACKAGE: APPS.GL_CONS_SEGMENT_ACTIONS_PKG
12.2.2
-
PACKAGE BODY: APPS.GL_CONS_SEGMENT_MAP_PKG
12.1.1
-
PACKAGE: APPS.GL_CONS_SEGMENT_ACTIONS_PKG
12.1.1
-
APPS.GL_CONS_SEGMENT_MAP_PKG SQL Statements
12.2.2
-
APPS.GL_CONS_FLEX_HIER_PKG SQL Statements
12.1.1
-
APPS.GL_CONS_SEGMENT_MAP_PKG SQL Statements
12.1.1
-
APPS.GL_CONS_FLEX_HIER_PKG SQL Statements
12.2.2
-
PACKAGE: APPS.OE_ITORD_PUB
12.1.1
-
PACKAGE: APPS.OE_ITORD_PUB
12.2.2
-
PACKAGE BODY: APPS.GL_CONS_SEGMENT_ACTIONS_PKG
12.1.1
-
PACKAGE BODY: APPS.GL_CONS_FLEX_HIER_PKG
12.1.1
-
PACKAGE BODY: APPS.GL_CONS_SEGMENT_ACTIONS_PKG
12.2.2
-
PACKAGE BODY: APPS.GL_CONS_FLEX_HIER_PKG
12.2.2
-
PACKAGE: APPS.OE_ITORD_UTIL
12.1.1
-
PACKAGE: APPS.OE_ITORD_UTIL
12.2.2
-
PACKAGE BODY: APPS.OE_ITORD_PUB
12.1.1
-
PACKAGE BODY: APPS.OE_ITORD_PUB
12.2.2
-
APPS.GL_CONS_SEGMENT_MAP_PKG dependencies on DUAL
12.2.2
-
APPS.GL_CONS_SEGMENT_MAP_PKG dependencies on GL_CONS_SEGMENT_MAP_S
12.1.1
-
APPS.GL_CONS_SEGMENT_MAP_PKG dependencies on DUAL
12.1.1
-
APPS.GL_CONS_SEGMENT_MAP_PKG dependencies on GL_CONS_SEGMENT_MAP_S
12.2.2
-
PACKAGE BODY: APPS.OE_ITORD_UTIL
12.2.2
-
PACKAGE BODY: APPS.OE_ITORD_UTIL
12.1.1
-
APPS.OE_ITORD_PUB dependencies on OE_ITORD_PUB
12.1.1
-
APPS.OE_ITORD_PUB dependencies on OE_ITORD_PUB
12.2.2
-
APPS.GL_CONS_SEGMENT_MAP_PKG dependencies on GL_CONS_SEGMENT_MAP
12.1.1
-
APPS.GL_CONS_SEGMENT_MAP_PKG dependencies on GL_CONS_SEGMENT_MAP
12.2.2
-
APPS.OE_ITORD_PUB dependencies on FND_API
12.1.1
-
APPS.OE_ITORD_PUB dependencies on FND_API
12.2.2