Search Results project_operating_unit_id

Overview

PA_XLA_INVOICE_REF_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module, registered as VALID in the ETRM metadata for release 12.2.2 and consistent with 12.1.1. The view supplies the reference and descriptive information required by the Subledger Accounting (XLA) engine when accounting events are generated for project draft invoices. Its name and structure indicate it functions as a lookup view that XLA uses to enrich invoice accounting events with project, agreement, customer, and organization context that is not otherwise carried on the draft invoice line itself.

For users searching on the term invoice_source, this view is relevant because it exposes a literal INVOICE_SOURCE column. The view text hard-codes the value 'PROJECTS INVOICES' for that column, derived through a TO_CHAR expression alongside the draft invoice number. Practically, this means every row returned by the view identifies its originating document category as a Projects invoice, which allows downstream XLA event processing and reporting to distinguish project invoice sources from other subledger transaction sources.

Underlying Base Objects

The view is defined over seven documented base objects, all referenced through APPS synonyms:

• PA_DRAFT_INVOICES_ALL — the driving table, supplying PROJECT_ID, DRAFT_INVOICE_NUM, and AGREEMENT_ID.
• PA_AGREEMENTS_ALL — joined on AGREEMENT_ID to provide customer, agreement type, agreement number, and descriptive attributes.
• PA_PROJECTS_ALL — joined on PROJECT_ID to supply project name, number, type, organization, location, and descriptive flexfield attributes.
• PA_PROJECT_TYPES_ALL — joined on PROJECT_TYPE and ORG_ID to provide project type class and burden cost configuration.
• HZ_CUST_ACCOUNTS and HZ_PARTIES — joined to resolve the customer account to a party name.
• HR_ORGANIZATION_INFORMATION — outer-joined twice, once for the carrying-out organization and once for the project organization, each restricted to the 'COMPANY COST CENTER' context.

The use of outer joins on HR_ORGANIZATION_INFORMATION ensures that invoice rows are not lost when organization classification data is absent.

Key Columns

• PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME — identify the project associated with the draft invoice.
• DRAFT_INVOICE_NUM, INVOICE_SOURCE — the invoice reference, with INVOICE_SOURCE returned as the constant 'PROJECTS INVOICES'.
• PROJECT_TYPE, PROJECT_TYPE_CLASS_CODE — project classification used for accounting rule derivation.
• PROJ_BURDEN_COST_FLAG and burden display logic — a DECODE expression returns the burden amount display method only when burden costing is enabled.
• AGREEMENT_ID, AGREEMENT_NUM, AGREEMENT_TYPE, CUSTOMER_ID, PARTY_NAME — customer and contract context.
• PROJECT_ORGANIZATION_ID, PROJECT_LOCATION_ID, ORG_ID, and related organization information columns — supporting organizational and cost center references.
• Attribute columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE10) — descriptive flexfield values from the project, project type, and agreement records.

Common Use Cases and Queries

The primary use case is XLA event enrichment for project invoice accounting. Secondary uses include reconciliation and audit reporting where the invoice source must be confirmed.

To list draft invoices and their source:

• SELECT project_number, draft_invoice_num, invoice_source, project_name FROM pa_xla_invoice_ref_v;

To filter by invoice source as found through a search on "invoice_source":

• SELECT project_id, draft_invoice_num, party_name FROM pa_xla_invoice_ref_v WHERE invoice_source = 'PROJECTS INVOICES';

To join with XLA event data, the PROJECT_ID and DRAFT_INVOICE_NUM columns provide the correlation keys back to the originating draft invoice records.