Search Results is_ledger_set

Overview

APPS.GL_ACCESS_DETAILS_PKG is a server-side PL/SQL package in Oracle E-Business Suite that encapsulates the business logic governing General Ledger access set assignments. The package header lineage indicates it was created in February 2001 to support server routines related to the GL_ACCESS_SET_NORM_ASSIGN table, the repository that stores the relationship between access sets and the ledgers, segment values, and privileges assigned to them. Its primary business function is to maintain and validate access detail records so that users and responsibilities may query and report only against the ledgers or segment value ranges for which they are authorized. The package is classified as OTHER within the documented ETRM metadata and is referenced by one other package, confirming it acts as a supporting utility within the GL access control layer rather than as a top-level application entry point.

Key Procedures and Functions

The package exposes seven documented program units:

• GET_RECORD_ID (Function) — Retrieves the next unique record identifier from the GL_ACCESS_SET_NORM_ASSIGN_S sequence. It is used to supply the primary key value required when a new access detail row is created.
• IS_LEDGER_SET (Function) — Accepts a ledger identifier and determines whether the specified ledger is a ledger set rather than a standalone ledger. This distinction is important because access privileges behave differently for ledger sets than for individual ledgers.
• INSERT_ROW (Procedure) — Inserts a new access detail record into GL_ACCESS_SET_NORM_ASSIGN. Documented history shows the parameter list was revised in October 2001, and the signature accommodates access set, ledger, segment value, privilege code, status, date range, descriptive flexfield context and attribute columns, and standard WHO columns.
• LOCK_ROW (Procedure) — Issues a locking read against an existing access detail row, serializing concurrent updates so that validation and modification of the same record do not collide.
• DELETE_ROW (Procedure) — Removes an access detail record, typically when an access set assignment is revoked or redefined.
• CHECK_DUPLICATE (Procedure) — Detects whether a proposed access detail assignment duplicates an existing row, preventing contradictory or redundant privileges from being stored.
• VALIDATE_ACCESS_DETAIL (Procedure) — The routine most relevant to the search term "validate_access_detail." It performs the validation logic applied to an access detail record before it is accepted, ensuring that the referenced ledger, segment value type, privilege code, and related attributes form a coherent and permitted assignment.

Tables Accessed

The package operates on a small, focused set of objects:

• GL_ACCESS_SET_NORM_ASSIGN — The primary transactional table holding normalized access set assignments. INSERT_ROW, LOCK_ROW, DELETE_ROW, CHECK_DUPLICATE, and VALIDATE_ACCESS_DETAIL read and write here.
• GL_ACCESS_SET_NORM_ASSIGN_S — The sequence supplying unique record identifiers, consumed by GET_RECORD_ID.
• GL_LEDGERS — Consulted by IS_LEDGER_SET and by validation logic to confirm ledger existence and to establish whether an identifier refers to a ledger set.
• DUAL — Used for single-row selection of sequence values and similar scalar operations.

Usage Notes

GL_ACCESS_DETAILS_PKG is not a concurrent program itself but is invoked indirectly. In practice it is called from the Oracle Forms-based setup and administration screens that maintain GL access sets, from other PL/SQL packages in the GL security layer (the metadata records one package reference), and from custom code that programmatically provisions access set assignments. Typical invocation patterns include calling GET_RECORD_ID before INSERT_ROW, calling LOCK_ROW before an update to guarantee serialization, and calling CHECK_DUPLICATE or VALIDATE_ACCESS_DETAIL to enforce integrity before committing. Because the package is owned by APPS and relies on APPS synonyms, custom callers must be granted execute privileges and should respect the WHO columns passed through INSERT_ROW. The behavior is consistent across Oracle EBS 12.1.1 and 12.2.2, as the package header revision predates both releases.