Search Results budgetary_control_status




Overview
Explore in AI Chat

Overview

GL_JE_BATCHES_POST_V is an APPS-owned database view in the Oracle E-Business Suite General Ledger (GL) module. It exposes a filtered projection of journal entry batches that are candidates for posting, joining batch header information from GL_JE_BATCHES to the GL_PERIODS calendar and applying an access-set security predicate. Its defining characteristic is the filter (JB.STATUS < 'P' OR JB.STATUS > 'P'), which deliberately excludes batches already carrying the posted status ('P'), so the view returns only batches that remain unposted, in error, or otherwise pending posting processing.

Because the view surfaces the columns needed by the posting engine — control totals, running debit and credit totals, period identifiers, and budgetary control state — it functions as the reporting and integration surface for the Journal Posting program and for custom extract routines that need to identify postable work. In ETRM releases 12.1.1 and 12.2.2 the object carries VALID status in the APPS schema.

Underlying Base Objects

The view is defined over the following documented objects:

  • GL_JE_BATCHES (synonym to the base table) — the primary source, aliased JB, supplying batch identity, ledger context, period set, status, control and running totals, and posting request attributes.
  • GL_PERIODS (synonym) — aliased PER, joined on PERIOD_SET_NAME, ACCOUNTED_PERIOD_TYPE, and DEFAULT_PERIOD_NAME to supply PERIOD_YEAR and PERIOD_NUM.
  • GL_JE_HEADERS (synonym) — referenced inside a NOT EXISTS subquery to evaluate journal-level display and ledger association.
  • GL_ACCESS_SET_LEDGERS (table) — the access-set/ledger privilege table used in the security predicate, joined with the outer-join marker to the header ledger.
  • GL_JE_BATCHES_POST_PKG (package) — invoked as GL_JE_BATCHES_POST_PKG.GET_ACCESS_SET_ID in the subquery to resolve the current access set at runtime.

The NOT EXISTS clause excludes batches whose headers reference a ledger where the caller lacks 'R' (read) privilege within the active access set for the batch effective date window, thereby enforcing data security at the row level.

Key Columns

Common Use Cases and Queries

Typical uses include identifying unposted batches prior to running the posting program, reconciling control totals against running debit and credit totals, and feeding downstream extracts.

  • List postable batches with totals:
    SELECT je_batch_id, name, default_period_name, control_total, running_total_dr, running_total_cr FROM gl_je_batches_post_v WHERE status = 'U';
  • Detect imbalance where control total does not equal debits plus credits:
    SELECT je_batch_id, name, control_total, running_total_dr, running_total_cr FROM gl_je_batches_post_v WHERE control_total <> (running_total_dr + running_total_cr);
  • Report by period for a given calendar:
    SELECT period_year, period_num, name, control_total FROM gl_je_batches_post_v ORDER BY period_year, period_num;

Because access-set filtering is embedded, results automatically honor the responsibility's data access privileges, making the view suitable for both concurrent-program logic and ad hoc reporting without additional security joins.