Search Results gl_batch_name




Overview
Explore in AI Chat

Overview

The APPS.PA_UBR_UER_PROJ_DTLS_V view is a reporting-only database object within the Oracle E-Business Suite Projects (PA) module. Its name reflects its purpose: it consolidates project-level summary details for Unbilled Receivables (UBR) and Unearned Revenue (UER) processing. In Oracle Projects, UBR represents revenue that has been recognized but not yet invoiced, while UER represents cash received or billed amounts for which revenue has not yet been recognized. Both conditions arise from timing differences between revenue recognition and invoicing, and both require reconciliation against the General Ledger.

The view is documented as VALID in the APPS schema and is explicitly described in the ETRM metadata as being used for reporting purposes in UBR and UER. It does not store data itself; rather, it projects and reformats data drawn from underlying summary and transaction tables, applying currency rounding and a package-driven lookup to resolve General Ledger references. This makes it particularly valuable to financial analysts, revenue accountants, and technical consultants building reconciliation reports that tie Projects subledger activity back to GL batches and journals.

Underlying Base Objects

The view is defined over a combination of Projects tables, lookups, and a PL/SQL package. The documented referenced base objects are:

The view joins these objects primarily on project ID, summary IDs, and system reference, using DECODE logic to assign invoice and revenue amounts to the correct UBR or UER bucket.

Key Columns

Common Use Cases and Queries

The view is typically queried to reconcile UBR and UER balances to GL, and the user-supplied search term gl_batch_name corresponds directly to the GL_BATCH_NAME column, which is derived from the package call GET_INV_GL_HEADER_ID_LINE_NUM('GL_BATCH_NAME', ...). This supports locating the GL batch into which a given UBR or UER transaction was posted.

A typical query for a specific batch:

  • SELECT project_number, project_name, gl_period_name, gl_batch_name, ubr_amount, uer_amount FROM apps.pa_ubr_uer_proj_dtls_v WHERE gl_batch_name = :batch;

Other practical uses include reporting period-end UBR/UER activity by project, filtering by TYPE to isolate the UBR or UER population, and joining to GL_JE_BATCHES/GL_JE_HEADERS on GL_HEADER_ID for drill-down. Because the view calls PA_UBR_UER_SUMM_PKG per row, performance is best served by filtering on PROJECT_ID or GL_PERIOD_NAME before consuming the calculated columns.