Search Results gl_bis_segval_int

Overview

APPS.GL_SECURITY_PKG is the core server-side package in Oracle General Ledger that enforces data security for accounting flexfield combinations and ledger access. Its principal business purpose is to determine, for the currently connected application user and responsibility, which ledgers, access sets, charts of accounts, and individual segment values that user is permitted to view and transact against. The package acts as the gatekeeper consulted before any GL transaction entry, inquiry, or reporting activity proceeds, ensuring that users are restricted to the accounting data authorized by the access set or security rules assigned to their responsibility. In the EBS 12.1.1 and 12.2.2 releases the specification exposes the procedures INIT, INIT_SEGVAL, VALIDATE_ACCESS, VALIDATE_SEGVAL, LOGIN_LED_ID, and LOGIN_ACCESS_ID, together with a private worker, INIT_GLOBAL_VAR, that bootstraps package state.

Key Procedures and Functions

• INIT — The primary initialization entry point. It loads the responsibility-to-access-set mapping and caches the ledger, chart of accounts, and security segment identifiers into the package-level global variables so that subsequent validations avoid repeated profile lookups.
• INIT_GLOBAL_VAR — A private procedure invoked by INIT during first-time setup. It declares local holders for application, responsibility, ledger, and segment-attribute values, then assigns the package globals ACCESS_ID, RESPONSIBILITY_ID, and related identifiers from the FND profile and FND_GLOBAL session context.
• INIT_SEGVAL — Initializes the segment-value caching structures used by the validation routines, marking which of the flexfield segments are security enabled so their values can be filtered efficiently.
• VALIDATE_ACCESS — Determines whether the current responsibility holds a legitimate access-set assignment, establishing the ledger and chart-of-accounts context for the session.
• VALIDATE_SEGVAL — Verifies a given segment value against the security rules applicable to the user, returning whether the combination may be used. This drives segment value list-of-values filtering in GL forms.
• LOGIN_LED_ID — Returns the ledger identifier associated with the logged-in access context, used by callers that must default a ledger without hard-coding it.
• LOGIN_ACCESS_ID — Returns the access set identifier established for the current session, complementing LOGIN_LED_ID for callers needing the governing access set.

Tables Accessed

The package reads FND_RESPONSIBILITY to resolve the responsibility and its application, and GL_ACCESS_SETS, GL_ACCESS_SET_ASSIGNMENTS, and GL_LEDGERS to establish the ledger, chart-of-accounts, and security segment context. Security rule evaluation draws on FND_FLEX_VALUE_SETS, FND_FLEX_VALUE_RULE_LINES, FND_FLEX_VALUE_RULE_USAGES, FND_FLEX_VALUE_HIER_ALL, and FND_FLEX_VALIDATION_TABLES. Segment metadata comes from FND_ID_FLEX_SEGMENTS, while GL_CODE_COMBINATIONS and GL_BIS_SEGVAL_INT support combination and segment-value validation. V$SESSION is consulted to confirm the active session identity. Because the package references these objects through APPS synonyms, no direct schema qualification appears in the source.

Usage Notes

GL_SECURITY_PKG is normally invoked indirectly. General Ledger entry and inquiry forms call INIT during form startup, then rely on VALIDATE_SEGVAL and VALIDATE_ACCESS to filter lists of values and reject unauthorized combinations. Concurrent programs and the bis segment-value integration path use VALIDATE_SEGVAL and the LOGIN_* functions. Five other documented packages reference GL_SECURITY_PKG, making it a shared dependency; custom code should call the public procedures rather than manipulate the package globals directly. The source header ($Header: gluoaseb.pls 120.21) reflects the shipped build lineage common to the 12.1.1 and 12.2.2 file systems.