Search Results reference_4




Overview
Explore in AI Chat

Overview

APPS.GL_BUDGET_JOURNALS_V is a General Ledger reporting view that consolidates posted budget journal activity from the journal entry batch, header, and line tables into a single denormalized result set. The view is documented in ETRM with the annotation "10SC ONLY," indicating it is a legacy artifact whose applicability is limited to specific 10SC-related configurations rather than the general Oracle E-Business Suite customer base. In EBS 12.1.1 and 12.2.2 the object is registered in the APPS schema with a status of VALID, and it references a set of base objects through synonyms, allowing it to remain valid across the multi-org and ledger architecture introduced with the 12.x releases.

Because the view filters exclusively on budget journals (JEH.ACTUAL_FLAG = 'B') that have been posted (JEH.STATUS = 'P'), it presents only committed budget entries rather than unposted or actual transactions. This makes it useful for reconciliation and audit reporting where the distinction between budgetary and actual balances must be preserved. The inclusion of the batch-level STATUS_VERIFIED lookup meaning, source name, and category name means the view can be consumed directly in reports and integrations without additional joins to the GL lookup and journal setup tables.

Underlying Base Objects

The documented base objects are GL_JE_BATCHES, GL_JE_CATEGORIES, GL_JE_HEADERS, GL_JE_LINES, and GL_JE_SOURCES, all resolved via synonyms in the APPS schema, plus GL_LOOKUPS, which is referenced as a view. The join topology is straightforward and follows the standard GL journal hierarchy:

  • GL_JE_LINES.JE_HEADER_ID = GL_JE_HEADERS.JE_HEADER_ID establishes the line-to-header relationship.
  • GL_JE_HEADERS.JE_BATCH_ID = GL_JE_BATCHES.JE_BATCH_ID establishes the header-to-batch relationship.
  • GL_JE_SOURCES.JE_SOURCE_NAME = GL_JE_HEADERS.JE_SOURCE resolves the user-facing journal source name.
  • GL_JE_CATEGORIES.JE_CATEGORY_NAME = GL_JE_HEADERS.JE_CATEGORY resolves the user-facing journal category name.
  • GL_LOOKUPS is joined on LOOKUP_TYPE = 'YES/NO' and LOOKUP_CODE = GL_JE_BATCHES.STATUS_VERIFIED, producing the STATUS_VERIFIED meaning.

Driver rows originate from GL_JE_LINES, so lines whose headers fail the ACTUAL_FLAG = 'B' and STATUS = 'P' predicates are excluded. The LEDGER_ID column is carried from GL_JE_HEADERS, tying each row to a specific ledger in the 12.x accounting model.

Key Columns

The view exposes identifiers, descriptive attributes, and amounts spanning all three levels of the batch/header/line hierarchy:

Common Use Cases and Queries

Typical uses include budget-versus-actual reconciliation, batch verification reporting, and export of posted budget lines to external reporting or ETL processes. A representative query filtering on a reference column and a ledger follows:

  • Retrieve posted budget lines for a ledger in a given period, projecting the account, amounts, and source/category names.
  • Reconcile batch totals by grouping on JE_BATCH_ID and summing ACCOUNTED_DR and ACCOUNTED_CR.
  • Audit status verification by filtering STATUS_VERIFIED = 'Yes' to isolate batches confirmed as verified.

Example:

SELECT ledger_id, batch_name, je_name, je_line_num, code_combination_id, entered_dr, entered_cr, accounted_dr, accounted_cr, reference_1, status_verified FROM apps.gl_budget_journals_v WHERE ledger_id = :p_ledger_id AND je_period_name = :p_period ORDER BY je_batch_id, je_header_id, je_line_num;

Because the view already applies the budget and posted filters, callers should not expect it to return unposted budgets or actual journals; additional filtering by ledger, period, or account is normally required to constrain result volume in production ledgers.