Search Results gl_je_posting_s




Overview
Explore in AI Chat

Overview

GL_JE_BATCHES_POST_PKG is an APPS-owned PL/SQL package body in the Oracle E-Business Suite General Ledger module. It encapsulates the server-side logic required to validate, lock, and post journal entry batches in the GL_JE_BATCHES and GL_JE_HEADERS tables. The package forms part of the posting engine that drives the Journal Posting program in Oracle EBS 12.1.1 and 12.2.2, providing the business rules that determine whether a batch is eligible for posting and performing the controlled update of batch and header rows to reflect posted status. Because it operates directly against core GL posting tables and the GL_JE_POSTING_S interface, it is a foundational element of the period-close and subledger transfer workflow.

Key Procedures and Functions

The package exposes eight documented procedures and functions. Their names reflect distinct stages of batch posting control:

  • SET_ACCESS_SET_ID — Assigns the access set identifier used to restrict posting operations to the appropriate data access security context.
  • GET_ACCESS_SET_ID — Retrieves the currently configured access set identifier, supporting security-filtered posting logic.
  • GET_UNIQUE_ID — Returns a system-generated unique identifier used to coordinate locking and posting operations across concurrent processes.
  • CHECK_BUDGET_STATUS — Validates the budget status associated with a batch, ensuring budget-related postings comply with defined control rules.
  • CHECK_UNBAL_MONETARY_HEADERS — Detects journal headers whose entered debit and credit monetary amounts are not in balance, preventing invalid postings.
  • CHECK_UNTAX_MONETARY_HEADERS — Detects journal headers that fail tax-related monetary validation checks before posting proceeds.
  • LOCK_ROW — Acquires a row-level lock on a batch or header record to serialize concurrent posting attempts and prevent contention.
  • UPDATE_ROW — Persists the post-posting status changes to the affected batch or header rows.

These procedures are invoked internally by the posting driver; they are not intended as standalone public APIs and no parameter lists are documented in ETRM.

Tables Accessed

The package reads and writes a focused set of GL and control tables, accessed through APPS synonyms:

  • GL_JE_BATCHES — The primary batch record; status and posting flags are updated here.
  • GL_JE_HEADERS — Journal header rows validated for balance and monetary consistency and updated to post status.
  • GL_JE_POSTING_S — The posting interface/shadow structure that supports the batch posting process, which is the object most directly associated with the user search term.
  • GL_BUDGETS, GL_BUDGET_VERSIONS — Read to evaluate budget status and version controls during posting validation.
  • GL_CONSOLIDATION_HISTORY, GL_ELIMINATION_HISTORY — Referenced to align posting activity with consolidation and elimination history.
  • DUAL — Used for singleton queries and sequence or constant evaluation.

The package also depends on infrastructure objects including APP_EXCEPTION, APP_EXCEPTIONS, FND_MESSAGE, and STANDARD, which provide error raising, message lookup, and standard API handling.

Usage Notes

GL_JE_BATCHES_POST_PKG is not a user-facing API in the conventional sense; its procedures are orchestrated by the Journal Posting concurrent program and by other glossary packages that require batch-level posting checks. The package is referenced by two other database objects, confirming that it is a shared utility invoked across GL posting and consolidation routines. Customizations and extensions should avoid modifying the package body directly, since upgrades replace it; instead, use standard GL posting APIs and concurrent program parameters. Because the package performs row-level locking and updates against critical GL tables, it must not be invoked outside the controlled concurrency framework of the posting program. Direct calls from custom code risk lock contention, unbalanced posting results, and corruption of GL_JE_POSTING_S state.