Results for “revtrans_ubr_dr”

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

Overview

PA_XLA_REV_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined over the Project Accounting (PA) revenue recognition and draft revenue data model. It is not a standalone transactional entity; rather, it is a denormalized projection that joins draft revenue headers, draft revenue items, agreements, customers, project definitions, project statuses, organizations, and lookup values into a single queryable surface. Its principal role is to support inquiry, reconciliation, and subledger accounting (XLA) reporting for revenue and its associated realized gains and losses, including the realized_losses_amount column. In 12.1.1 and 12.2.2 the view remains a read-only reporting object, and because it joins PA_DRAFT_REVENUES_ALL and PA_DRAFT_REVENUE_ITEMS, it exposes revenue distributions before or after transfer to General Ledger depending on the transfer status of each draft revenue.

Underlying Base Objects

The view is defined with an explicit FROM clause and joins across the following documented objects:

• PA_PROJECTS_ALL — project master data (name, segment1, project_id, project_type, project_status_code, carrying_out_organization_id).
• PA_DRAFT_REVENUES_ALL — draft revenue header records, including GL dates, transfer status, UBR/UER account assignments, and realized gain/loss columns.
• PA_DRAFT_REVENUE_ITEMS — revenue line amounts by currency (revproc, project, projfunc, funding, revtrans).
• PA_AGREEMENTS_ALL and PA_CUSTOMERS_V — agreement number and customer identification.
• PA_PROJECT_STATUSES, PA_PROJECT_TYPES_ALL, PA_LOOKUPS — descriptive status, type, and lookup meanings.
• HR_ORGANIZATION_UNITS (with HR_GENERAL/HR_SECURITY), PA_SECURITY, and DUAL — implementing organization and project security enforcement via PA_SECURITY.ALLOW_QUERY.

The security predicate 'Y' IN (SELECT PA_SECURITY.ALLOW_QUERY(P.PROJECT_ID) FROM SYS.DUAL) means the view only returns rows for projects the querying user is permitted to see.

Key Columns

The projection includes descriptive identifiers and a substantial set of financial columns:

• Project/Customer identifiers: PROJECT_ID, PROJECT_NAME (derived as name and segment1), CUSTOMER_ID, CUSTOMER_NUMBER, CUSTOMER_NAME, AGREEMENT_ID, AGREEMENT_NUM, ORGANIZATION_ID and organization name.
• Draft revenue identity: DRAFT_REVENUE_NUM, DRAFT_REVENUE_NUM_CREDITED, PA_DATE, GL_DATE, ACCRUE_THROUGH_DATE, RELEASED_DATE, TRANSFERRED_DATE, TRANSFER_STATUS_CODE, ADJUSTING_REVENUE_FLAG.
• Revenue amounts by currency: SUM(RI.AMOUNT), SUM(PROJFUNC_REVENUE_AMOUNT), SUM(PROJECT_REVENUE_AMOUNT), SUM(FUNDING_REVENUE_AMOUNT), and SUM(REVTRANS_AMOUNT), each paired with its respective currency code — REVPROC_CURRENCY_CODE, PROJFUNC_CURRENCY_CODE, PROJECT_CURRENCY_CODE, FUNDING_CURRENCY_CODE.
• Realized gain/loss columns: REALIZED_GAINS_AMOUNT, REALIZED_LOSSES_AMOUNT, REALIZED_GAINS_CCID, REALIZED_LOSSES_CCID.
• Accounting references: CUSTOMER_BILL_SPLIT, UNBILLED_RECEIVABLE_DR, UNEARNED_REVENUE_CR, UNBILLED_CODE_COMBINATION_ID, UNEARNED_CODE_COMBINATION_ID, REVTRANS_UBR_DR, REVTRANS_UER_CR.

Common Use Cases and Queries

Because the user search term was "realized_losses_amount," the most direct use case is reporting realized foreign-exchange or rounding losses on revenue, by project, customer, and period.

• Listing realized losses by project and draft revenue.
• Reconciling revenue distributions to GL transfer status.
• Summarizing revenue by currency and organization.

A representative query follows:

SELECT project_id, DRAFT_REVENUE_NUM, REVPROC_CURRENCY_CODE,
       REALIZED_GAINS_AMOUNT, REALIZED_LOSSES_AMOUNT, REALIZED_LOSSES_CCID
FROM APPS.PA_XLA_REV_V
WHERE REALIZED_LOSSES_AMOUNT IS NOT NULL
ORDER BY project_id, DRAFT_REVENUE_NUM;

Because PA_DRAFT_REVENUE_ITEMS is aggregated, users should expect one row per draft revenue header (plus currency and lookup dimensions) rather than per item line, and should verify security-enabled visibility before using results for cross-project reporting.