Search Results proj_public_sector_flag

Overview

APPS.PA_XLA_INVOICE_REF_V is an internal Oracle Projects view owned by the APPS schema and registered in FND Design Data as PA.PA_XLA_INVOICE_REF_V. It exposes project, project type, agreement, customer, and organization attributes for draft invoices, providing a flat reference structure consumed by the Subledger Accounting (XLA) engine when generating accounting events and entries for Oracle Projects invoice transactions. The view name, prefixed with the XLA designation, indicates that its role is to supply descriptive and reference information to the accounting program rather than to serve as a general-purpose reporting object.

The view carries the standard Oracle warning: Oracle Internal Use Only — Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs. It is classified as an internal view type and holds VALID status in the APPS schema. Consultants and developers should treat it as a supporting object for SLA invoice accounting and not as a supported integration surface.

Underlying Base Objects

The view is defined over the following documented base objects:

• PA_DRAFT_INVOICES_ALL — the driving table supplying draft invoice numbers, invoice source, and project identifiers.
• PA_PROJECTS_ALL — supplies project name, number, organization, location, public sector and burden cost attributes, and descriptive flexfield attributes.
• PA_PROJECT_TYPES_ALL — supplies project type, project type class code, and project type descriptive flexfield attributes.
• PA_AGREEMENTS_ALL — supplies agreement and agreement customer identifiers.
• HZ_CUST_ACCOUNTS and HZ_PARTIES — resolve the customer account and party information associated with the agreement.
• HR_ORGANIZATION_INFORMATION — resolves organization classification details used for company and cost center derivations.

The joins follow the natural project-to-project-type and project-to-agreement relationships, with customer and organization information appended to complete the reference picture required by the accounting engine.

Key Columns

• PROJECT_ID, DRAFT_INVOICE_NUM — primary reference keys identifying the project and the sequential draft invoice within that project.
• INVOICE_SOURCE, PROJECT_NAME, PROJECT_NUMBER, PROJECT_TYPE, PROJECT_TYPE_CLASS_CODE — descriptive identification of the invoice source and the project against which it was generated.
• PROJ_PUBLIC_SECTOR_FLAG — indicates whether the project is a public sector project, affecting invoice and revenue treatment.
• PROJ_BURDEN_COST_FLAG — the column referenced in the user search. It indicates whether burden costs are applied and accounted for the project, and is used by XLA logic to determine how burden-related accounting lines are derived for invoice events.
• PROJ_BURDEN_DISPLAY_METHOD — determines how burden costs are displayed and, correspondingly, how they are presented in the accounting reference.
• PROJECT_ORGANIZATION_ID, PROJECT_LOCATION_ID, PROJECT_OPERATING_UNIT_ID — organizational context for the project, including the owning organization and operating unit.
• PROJECT_ORG_COMPANY, PROJECT_ORG_COST_CENTER, PROJECT_OU_COMPANY, PROJECT_OU_COST_CENTER — resolved company and cost center values for the project organization and operating unit.
• PROJECT_ATTRIBUTE1–10 and PROJ_TYPE_ATTRIBUTE1–10 — descriptive flexfield segments for the project and project type, available for accounting rule conditions.
• AGREEMENT_ID, AGREEMENT_CUSTOMER_ID — agreement and customer references tied to the invoice.

Common Use Cases and Queries

Typical use is diagnostic: confirming project attributes that influence invoice accounting, verifying the burden cost flag and display method for projects whose invoice entries appear incorrect, and tracing the agreement and customer reference carried into Subledger Accounting. As the object is internal and unsupported for direct access, queries should be limited to troubleshooting and analysis.

Example — inspect burden and organizational attributes for draft invoices of a project:

• SELECT project_id, draft_invoice_num, project_number, project_name, proj_burden_cost_flag, proj_burden_display_method, project_org_company, project_org_cost_center, project_ou_company, project_ou_cost_center FROM apps.pa_xla_invoice_ref_v WHERE project_id = :p_project_id;

Example — identify projects with burden costing enabled for a given invoice source:

• SELECT project_number, project_name, project_type, project_type_class_code, proj_burden_cost_flag, proj_burden_display_method FROM apps.pa_xla_invoice_ref_v WHERE invoice_source = :p_source AND proj_burden_cost_flag = 'Y';

Example — retrieve flexfield and agreement context for accounting rule evaluation:

• SELECT draft_invoice_num, project_attribute_category, project_attribute1, proj_type_attribute_category, proj_type_attribute1, agreement_id, agreement_customer_id FROM apps.pa_xla_invoice_ref_v WHERE project_id = :p_project_id AND draft_invoice_num = :p_draft_num;