Search Results su_gl_period_start_date

Overview

APPS.PA_UBR_UER_PROJ_V is a reporting view in the Oracle E-Business Suite Projects (PA) module that consolidates Unbilled Receivable (UBR) and Unearned Revenue (UER) summary balances by project, cost center, and accounting period. UBR represents revenue that has been recognized but not yet invoiced, while UER represents cash received or invoiced amounts not yet recognized as revenue. The view flattens the balances stored in the PA_UBR_UER_SUMM_ACCT table and joins them to project, project type, implementation, and GL period status information, producing a period-by-period reconciliation-oriented result set. It is intended for operational reporting, period-close validation, and integration extracts where a user needs to see the current UBR/UER position for each project and account as of a given GL period.

Underlying Base Objects

The view is defined over the following documented objects: PA_UBR_UER_SUMM_ACCT (the driving summary balances table), PA_PROJECTS, PA_PROJECT_TYPES_ALL, PA_IMPLEMENTATIONS_ALL, GL_PERIOD_STATUSES, and the PA_CURRENCY package. The join path links each summary row to its project via project_id, to the project type via the project type code and org_id, and to the implementation record via set_of_books_id and org_id. GL_PERIOD_STATUSES supplies the GL period name, start date, and set of books context, and is restricted to application_id = 101 (General Ledger). The PA_CURRENCY package is invoked through round_currency_amt to apply currency rounding to the computed UBR and UER amounts. A NOT EXISTS subquery against PA_UBR_UER_SUMM_ACCT selects only the latest summary row per project, cost center, and account combination for the qualifying period, effectively returning the most recent balance snapshot at or before the GL period start date.

Key Columns

• PROJECT_NUMBER, PROJECT_NAME, PROJECT_ID, PROJECT_TYPE — Project identification and classification from PA_PROJECTS and PA_PROJECT_TYPES_ALL.
• UBR_UER_SUMMARY_ID, COST_CENTER, ACCOUNT — The summary record identifier and the cost center and account segments describing the balance.
• UBR_AMOUNT, UER_AMOUNT — The rounded UBR (debit) and UER (credit) balances, calculated from the prior-period balances plus current-period movements in PA_UBR_UER_SUMM_ACCT.
• GL_PERIOD, GL_PERIOD_START_DATE — The General Ledger period name and start date from GL_PERIOD_STATUSES.
• SU_GL_PERIOD, SU_GL_PERIOD_START_DATE — The period name and start date recorded directly on the summary record. The su_gl_period_start_date column is central to the view's selection logic: the view returns only rows where this date is less than or equal to the GL period start date, ensuring the latest available summary is presented.
• ZERO_BALANCE_FLAG, PROCESS_FLAG, REQUEST_ID, MULTI_COST_CENTER_FLAG — Status and processing attributes of the summary record.
• SET_OF_BOOKS_ID, ORG_ID — Multi-org and ledger context from PA_IMPLEMENTATIONS_ALL.

Common Use Cases and Queries

Typical uses include period-close reporting of unbilled and unearned balances, reconciliation of PA subledger balances to GL, and feeds for downstream data warehouses. The following query returns the latest UBR/UER position for a specific project and GL period:

• SELECT project_number, project_name, cost_center, account, gl_period, ubr_amount, uer_amount
• FROM apps.pa_ubr_uer_proj_v
• WHERE project_number = :project_number
• AND gl_period = :gl_period
• AND zero_balance_flag = 'N';

Because su_gl_period_start_date drives the row-selection logic, filtering on it or on the corresponding GL period start date ensures the returned balances reflect the intended reporting cut-off. Analysts should note that the view exposes only the most recent summary row per project, cost center, and account, so historical trend analysis requires querying the underlying PA_UBR_UER_SUMM_ACCT table directly.