Results for “je_batch_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The PA_SRS_REV_BATCH_NAME_V view is a reporting-support object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is supplied by the Oracle Projects (PA) product family and is described in the ETRM metadata as a "View used by SRS to select Journal Entry Batch names in GL created by Revenue programs - Retrofitted." In practical terms, this view provides a filtered, pre-joined list of General Ledger journal entry batch names that originate from Project Accounting revenue recognition and revenue generation programs.

Its primary role is to serve Oracle Reports-based concurrent programs and other SRS components that need to identify the specific GL batches created when revenue is transferred from Projects into the General Ledger. Because revenue batches are created dynamically with names that incorporate the journal source, the view abstracts the join logic required to isolate those batches, allowing downstream reports to simply select the exposed JE_BATCH_NAME column without reconstructing the underlying GL schema relationships. The "Retrofitted" identifier in the description indicates the view was migrated or re-created for compatibility with the current release level, preserving the original SRS reporting interface.

Underlying Base Objects

According to the documented view text, PA_SRS_REV_BATCH_NAME_V is defined over four GL objects, all referenced through APPS-owned synonyms:

• GL_JE_BATCHES — aliased as JEB, supplies the batch identifiers and batch names.
• GL_JE_HEADERS — aliased as JEH, links batches to their journal headers and categories.
• GL_JE_CATEGORIES — aliased as CAT, provides the journal category definitions used to restrict results to the REVENUE category.
• GL_JE_SOURCES — aliased as JES, provides journal source attributes, including the concatenation prefix used in Project Accounting batch names.

The view joins these objects on JE_BATCH_ID (between batches and headers) and on the journal category and source names. No PA-module tables appear in the definition; the view is entirely a GL-backed construct that exists to satisfy Projects reporting requirements.

Key Columns

The view exposes a single column:

• JE_BATCH_NAME — the NAME value from GL_JE_BATCHES, representing the journal entry batch name in General Ledger. Only batches matching the read of the Revenue category and the PROJECT ACCOUNTING source are returned, and the DISTINCT keyword ensures each qualifying batch name appears exactly once.

Because only one column is projected, the view functions as a lookup or validation source rather than a detailed transaction report. Filtering and display attributes such as batch date, period, or status are not exposed and must be obtained directly from GL_JE_BATCHES when required.

Common Use Cases and Queries

The view is typically invoked by SRS reports and by custom reconciliation queries to confirm that revenue batches were created in GL for a given accounting period. A straightforward retrieval of all qualifying batch names is:

• SELECT je_batch_name FROM apps.pa_srs_rev_batch_name_v;
• SELECT je_batch_name FROM apps.pa_srs_rev_batch_name_v WHERE je_batch_name LIKE 'PROJECT ACCOUNTING%';

A common integration pattern joins the view to GL_JE_BATCHES or GL_JE_HEADERS to enrich the batch name with posting dates, periods, or amounts for period-close and audit activities:

• SELECT v.je_batch_name, b.status, b.posted_date FROM apps.pa_srs_rev_batch_name_v v, apps.gl_je_batches b WHERE v.je_batch_name = b.name;

Users searching for "je_batch_name" typically reach this view while investigating where a revenue batch name is sourced in Projects-to-GL reporting. The answer is that it derives from GL_JE_BATCHES.NAME, filtered through Project Accounting's journal source and the Revenue category.