Search Results get_access_set_id

Overview

GL_JE_BATCHES_POST_PKG is an Oracle EBS General Ledger server-side PL/SQL package owned by APPS and classified as OTHER in the ETRM metadata for release 12.2.2 (compatible with 12.1.1). It supports the batch-level posting process for journal entries in Oracle General Ledger. The package provides the supporting infrastructure that the Journal Posting form and posting concurrent programs rely on when validating and submitting batches of journals: it holds the session-level Access Set context, generates unique posting run identifiers, and evaluates batch integrity before posting is permitted. Its declared AUTHID CURRENT_USER attribute means that stored objects execute under the privileges of the invoking user, which is relevant to how Access Set security and data restriction are enforced at runtime.

Key Procedures and Functions

• SET_ACCESS_SET_ID — Assigns the package-level global variable access_set_id for the current database session. The documented example is gl_je_batches_post_pkg.set_access_set_id(221). This establishes the Access Set context used to filter the ledger and batch data visible to the posting logic.
• GET_ACCESS_SET_ID — Returns the numeric value of the package global variable set by SET_ACCESS_SET_ID, as in l_access_set_id := gl_je_batches_post_pkg.get_access_set_id. The function carries PRAGMA RESTRICT_REFERENCES(...,WNDS,WNPS), confirming it has no side effects and writes no package state, which makes it safe to call from SQL and from within other server-side code.
• GET_UNIQUE_ID — Returns a unique posting_run_id, used to tag each posting execution so that the concurrent posting run, its output, and associated rows in GL_JE_POSTING_S can be correlated.
• CHECK_BUDGET_STATUS — Evaluates a journal batch against budget controls. It returns BF when the batch contains journals whose budget is frozen, BU when the budget year is unopened, and OK when neither condition applies. Documented arguments are the JE batch id and the batch period year.
• CHECK_UNBAL_MONETARY_HEADERS — Returns TRUE if the specified batch contains unbalanced monetary headers and FALSE if it is balanced. Static (STAT) headers that are not balanced are tolerated.
• CHECK_UNTAX_MONETARY_HEADERS — Performs the equivalent balance check for untaxed monetary journal headers.
• LOCK_ROW — Provides the row-level locking primitive used to serialize access to batch and header records during posting.
• UPDATE_ROW — Performs the documented row update operations against the posting-related records managed by the package.

Tables Accessed

The package references the following objects through APPS synonyms:

• GL_JE_BATCHES — the parent batch record; source of batch status, period year, and the batch identifier used by the validation functions.
• GL_JE_HEADERS — header-level balance and control checks performed by CHECK_UNBAL_MONETARY_HEADERS and CHECK_UNTAX_MONETARY_HEADERS.
• GL_JE_POSTING_S — the posting work table populated during a posting run and linked to the run via the identifier produced by GET_UNIQUE_ID.
• GL_BUDGETS and GL_BUDGET_VERSIONS — consulted by CHECK_BUDGET_STATUS to determine budget freeze status and budget year state.
• GL_CONSOLIDATION_HISTORY and GL_ELIMINATION_HISTORY — consolidation and elimination tracking records read during batch evaluation.
• DUAL — used for single-row evaluation and unique id derivation.

Usage Notes

The package is invoked primarily from Oracle General Ledger's journal posting interface and from the posting concurrent programs. Two other packages reference GL_JE_BATCHES_POST_PKG per the ETRM metadata, so it is normally consumed as a supporting layer rather than called directly by end users. The canonical call sequence begins with SET_ACCESS_SET_ID to fix the Access Set context, followed by CHECK_BUDGET_STATUS and the monetary header balance checks, and finally GET_UNIQUE_ID to stamp the posting run. Custom code that performs batch posting should call GET_ACCESS_SET_ID rather than reading the global directly, because the function is pragma-restricted and therefore valid in SQL contexts. Note that the access set value is a session-level global: callers must set it explicitly before each posting operation that crosses Access Set boundaries, as there is no automatic reset indicated in the documented source.