Search Results gl_header_name

Overview

PA_UBR_UER_ACCT_DTLS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PA (Projects) product family. Its documented purpose is to support reporting for Unbilled Receivables (UBR) and Unearned Revenue (UER) processing. Specifically, it presents an accounting summary detail view that reconciles summarized UBR/UER accounting entries held in Projects with the corresponding General Ledger journal lines generated when draft invoices are transferred to Receivables and posted to GL. The view therefore acts as a bridge between the Projects subledger summary tables and the GL journal headers, lines, and batches that carry the financial impact.

The view is defined in the APPS schema and is recorded as VALID. In 12.1.1 and 12.2.2 the object exists as a standard seed view; because 12.2.2 introduces the Online Patching (adop) architecture, the underlying editioned objects such as the synonyms and PA packages may be editioned, but the view name and column interface remain consistent for reporting consumers. The view is read-only in practice and is intended for inquiry and reporting rather than for transaction processing.

Underlying Base Objects

The view is constructed from a join across Projects, Receivables, and General Ledger objects. The documented referenced base objects are:

• PA_UBR_UER_SUMM_ACCT (SYNONYM) — the summarized UBR/UER accounting driver table, supplying the period, summary identifiers, transaction type, and zero balance flag.
• PA_PROJECTS, PA_PROJECT_TYPES_ALL, PA_IMPLEMENTATIONS_ALL (SYNONYMS) — project identification, project type classification, set of books, and operating unit context.
• PA_DRAFT_INVOICES_ALL, PA_DRAFT_INVOICE_ITEMS, PA_DRAFT_REVENUES_ALL (SYNONYMS) — draft invoice header, lines, and revenue lines used to derive the invoice revenue number, transaction text, and line number.
• PA_LOOKUPS (VIEW) — resolves the UBR/UER transaction type meaning through lookup type PA_UBR_UER_TRANS_TYPE.
• GL_JE_HEADERS, GL_JE_LINES, GL_JE_BATCHES (SYNONYMS) — journal header, line, and batch detail providing GL_HEADER_NAME, GL_HEADER_ID, GL_LINE_NUM, and GL_BATCH_NAME.
• RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_LINE_GL_DIST_ALL (SYNONYMS) — Receivables transaction lines and their GL distributions, joined to GL lines via REFERENCE_2, REFERENCE_3, CODE_COMBINATION_ID, and PERIOD_NAME.
• PA_CURRENCY and PA_UBR_UER_SUMM_PKG (PACKAGES) — currency rounding via PA_CURRENCY.ROUND_CURRENCY_AMT, and supporting summary logic.

Key Columns

• SEGMENT1, NAME, PROJECT_ID, PROJECT_TYPE — project number, name, internal identifier, and type.
• COST_CENTER_SEGMENT, ACCOUNT_SEGMENT — accounting flexfield segments associated with the summary.
• TYPE — decoded transaction type meaning from PA_LOOKUPS.
• INV_REV_NUM (RA_INVOICE_NUMBER), UBR_SUMMARY_ID, UER_SUMMARY_ID — the invoice revenue reference and the UBR/UER summary identifiers used to correlate summaries to invoices.
• GL_PERIOD_NAME, GL_PERIOD_START_DATE — the GL period in which the accounting was recognized.
• AMOUNT — the currency-rounded amount derived by DECODE logic over ACCOUNTED_DR and ACCOUNTED_CR, direction depending on whether the row represents a UBR or UER summary.
• GL_HEADER_ID, GL_LINE_NUM, GL_HEADER_NAME, GL_BATCH_NAME — the GL journal header, line number, header name (the column commonly searched as GL_HEADER_NAME), and batch name, allowing drill-down from Projects to GL.
• TEXT, LINE_NUM — descriptive text and line number from the draft invoice items.
• ZERO_BALANCE_FLAG, SET_OF_BOOKS_ID, ORG_ID — balance indicator and ledger/organization context for filtering and security.

Common Use Cases and Queries

This view is typically used to reconcile UBR and UER balances by project and GL period, to trace a summary amount to its GL batch and journal header, and to produce audit extracts that pair Project accounting with GL postings. A common query filtering by the GL header name is:

• SELECT project_id, segment1, gl_period_name, gl_header_name, gl_batch_name, amount FROM apps.pa_ubr_uer_acct_dtls_v WHERE gl_header_name = :header_name;
• SELECT segment1, gl_period_name, SUM(amount) FROM apps.pa_ubr_uer_acct_dtls_v WHERE org_id = :org_id GROUP BY segment1, gl_period_name;
• SELECT project_id, inv_rev_num, gl_header_id, gl_line_num, amount FROM apps.pa_ubr_uer_acct_dtls_v WHERE zero_balance_flag = 'N' AND gl_period_name = :period;

Because PA_UBR_UER_ACCT_DTLS_V joins summarized Projects accounting to GL and Receivables distributions, queries should be scoped by ORG_ID, SET_OF_BOOKS_ID, and GL_PERIOD_NAME to control volume. The view is not a substitute for the GL reconciliation reports but provides a convenient, pre-joined source for custom UBR/UER reporting and reconciliation extracts.