Search Results stop_processing

Overview

APPS.GL_FLATTEN_LEDGER_SETS is a server-side PL/SQL package that supports the General Ledger ledger set and access set flattening process. In Oracle EBS, a ledger set is a grouping of ledgers (or other ledger sets) that is used for consolidated reporting and processing, while an access set controls the set of ledgers a responsibility may access. The "flattening" concept refers to the resolution of hierarchy — expanding nested ledger set membership down to the leaf-level ledger assignments and recording those expanded relationships in normalized assignment tables so that downstream features such as consolidated reporting, cross-ledger inquiries, and security enforcement can operate against a stable, denormalized view of ledger membership.

The package operates against the shared GL_FLATTEN_SETUP_DATA session state (referenced in the source via GLSTFL_COA_ID and GLSTFL_Debug) and is coupled to the GL_MESSAGE logging utility, which records progress and diagnostic messages during processing. The header comment (glufllsb.pls, version 120.9) confirms the package has been shipped and maintained since at least Release 11i era and remains current through 12.1.1 and 12.2.2.

Key Procedures and Functions

• FIX_EXPLICIT_SETS — The central routine for processing changes in explicit ledger sets. Per the inline documentation, its flow is: (1) clean up GL_LEDGER_SET_ASSIGNMENTS, (2) clean up GL_ACCESS_SET_NORM_ASSIGN, (3) for all newly created ledger sets, populate implicit access set information into GL_ACCESS_SET_NORM_ASSIGN, (4) mark outdated mappings in GL_LEDGER_SET_ASSIGNMENTS for delete, (5) insert new mappings into GL_LEDGER_SET_ASSIGNMENTS, and (6) detect looping within the ledger set assignments and raise an error (GLSTFL_fatal_err) if a cycle is found. It returns a BOOLEAN indicating success. The routine logs a Func_Ent message on entry and writes diagnostic messages through GL_MESSAGE.Write_Log when GL_FLATTEN_SETUP_DATA.GLSTFL_Debug is enabled.
• CLEAN_UP_EXPLICIT_SETS — The companion routine that removes stale or partially processed ledger set assignment data. It supports the idempotent re-run behaviour of FIX_EXPLICIT_SETS by clearing residual rows from prior failed invocations before new mappings are built.

Tables Accessed

• GL_LEDGER_SET_ASSIGNMENTS — The primary target of the flattening logic. It stores the resolved ledger-to-ledger-set mappings and is both read and written (delete of stale rows, insert of new mappings) by FIX_EXPLICIT_SETS.
• GL_ACCESS_SET_NORM_ASSIGN and GL_ACCESS_SET_NORM_ASSIGN_S — Normalized access set assignment tables, cleaned and repopulated with implicit access set information so that responsibility-level access to ledgers is correctly derived from ledger set membership.
• GL_LEDGERS — Used to identify ledger sets (rows where OBJECT_TYPE_CODE = 'S') and to restrict processing to the current chart of accounts (GLSTFL_COA_ID).
• GL_LEDGER_SET_NORM_ASSIGN — Normalized ledger set assignment storage, part of the same flattening normalization scheme.
• DUAL — Used for simple single-row queries, typically to seed loop counters or validation checks.

Usage Notes

GL_FLATTEN_LEDGER_SETS is not an end-user-facing API. It is invoked internally by the General Ledger ledger set and access set maintenance flows, typically triggered when ledger sets or their membership are created, modified, or deleted through the Ledger Sets setup form, and by the concurrent programs that flatten ledger set hierarchies. One other package references it. Because the routines depend on GL_FLATTEN_SETUP_DATA being populated (chart of accounts and debug flag), custom code should not call these routines directly unless it first initialises that shared state and accepts the package's commit/rollback semantics. Debug output can be enabled via GLSTFL_Debug to trace the flattening sequence through GL_MESSAGE logs.