Results for “pa_gl_rev_xfer_audit_v”

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

Overview

PA_GL_REV_XFER_AUDIT_V is an Oracle Projects (PA) reporting view owned by the APPS schema. Its documented purpose is to support Revenue Audit by GL Account, presenting the revenue distribution lines generated in Oracle Projects side by side with the corresponding journal entries created in Oracle General Ledger. In EBS 12.1.1 and 12.2.2 the view is marked VALID and serves as a reconciliation and audit instrument rather than a transactional table. It allows subledger accounting and revenue recognition specialists to trace how a project's customer revenue events were transferred to the GL, spanning the pre-XLA and XLA accounting models through the presence of both GL_JE_* and XLA_* base objects.

The user search term transaction_type maps directly to the view's TRANSACTION_TYPE column, which is populated from PA_EVENTS.EVENT_TYPE. This is the primary attribute used to distinguish the nature of the originating revenue transaction.

Underlying Base Objects

The view is defined over a blend of Oracle Projects, Oracle General Ledger, and Subledger Accounting objects, joined through the documented view text and metadata:

• Projects core: PA_PROJECTS, PA_TASKS, PA_EVENTS, PA_DRAFT_REVENUES_ALL, PA_CUST_EVENT_RDL_ALL, PA_CUST_REV_DIST_LINES_ALL.
• Expenditure linkage: PA_EXPENDITURES_ALL, PA_EXPENDITURE_ITEMS_ALL (used by the UNION ALL branches that expose expenditure-based lines).
• General Ledger: GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES, GL_JE_SOURCES.
• Subledger Accounting (XLA): XLA_AE_HEADERS, XLA_AE_LINES, XLA_DISTRIBUTION_LINKS.
• Human Resources / Security: HR_GENERAL, HR_ORGANIZATION_UNITS, HR_PERSON_NAME, HR_SECURITY, PER_PEOPLE_F — used to resolve employee or organization names and to apply HR security.

The documented SQL joins PA_DRAFT_REVENUES_ALL (filtered to TRANSFER_STATUS_CODE = 'A') with PA_CUST_EVENT_RDL_ALL on PROJECT_ID and DRAFT_REVENUE_NUM, then to PA_EVENTS on PROJECT_ID, EVENT_NUM, and TASK_ID (using NVL both sides). GL_JE_LINES is matched to GL_JE_HEADERS and GL_JE_BATCHES, restricted to JE_SOURCE_NAME = 'PROJECT ACCOUNTING' and JEH.REVERSED_JE_HEADER_ID IS NULL, and the RDL batch name is matched against JEL.REFERENCE_1. This is a UNION ALL view combining multiple accounting line types.

Key Columns

• TRANSACTION_TYPE — sourced from PA_EVENTS.EVENT_TYPE; identifies the revenue event type behind each audited line.
• LINE_TYPE — literal 'ERDL' in the documented branches, indicating Event Revenue Distribution Line.
• CODE_COMBINATION_ID — the GL account combination used for distribution and journal comparison.
• PERIOD_NAME — the GL accounting period of the journal entry.
• PROJECT_ID / PROJECT_NUMBER — project identity.
• DRAFT_REV_NUMBER / RDL_LINE_NUM / RDL_EVENT_NUM — draft revenue and RDL identifiers for drill-down.
• TRANSFERRED_DATE / GL_DATE / TRANSACTION_DATE — transfer, GL, and event completion dates.
• DEBIT_AMOUNT / CREDIT_AMOUNT — amounts shown with debit nulled in the first branch to present the credit distribution.
• TASK_ID / TASK_NUMBER — task-level detail; EMP_OR_ORG_NAME and EXPENDITURE_ITEM_ID populated in other branches.

Common Use Cases and Queries

Typical scenarios include reconciling revenue transferred from Projects to GL, investigating lines that failed to post, and auditing by transaction type or account.

• List revenue by transaction type for a project:
  SELECT transaction_type, project_number, period_name, code_combination_id, credit_amount FROM pa_gl_rev_xfer_audit_v WHERE project_number = :project;
• Reconcile debits and credits for a GL period:
  SELECT period_name, code_combination_id, SUM(debit_amount), SUM(credit_amount) FROM pa_gl_rev_xfer_audit_v WHERE period_name = :period GROUP BY period_name, code_combination_id;
• Filter unreconciled lines for a date range using TRANSFERRED_DATE or GL_DATE.
• Analyze a specific event type via WHERE transaction_type = :event_type.

Because the view is read-only and joins secured HR objects, access is governed by APPS privileges and HR security profiles. Always join to PA_PROJECTS for current project attributes rather than relying solely on denormalized columns.