Search Results project_attribute1

Overview

PA_XLA_PROJECT_REF_V is a seeded APPS schema view in the Oracle E-Business Suite Projects (PA) module. Its name indicates its purpose: it supplies the project-side reference data required by the Subledger Accounting (XLA) engine when generating accounting entries for project-related transactions. In EBS 12.1.1 and 12.2.2, Subledger Accounting resolves descriptive and analytical information about a transaction's source object through dedicated reference views, and PA_XLA_PROJECT_REF_V is the project reference used during the accounting derivation and journal line creation process.

The view consolidates data from project definitions, project type definitions, and organization classification information into a single denormalized row per project. It exposes both the standard descriptive attributes of a project (number, name, type, class) and the ten descriptive flexfield (DFF) attribute columns for the project itself and for its project type. Because Subledger Accounting can map any DFF attribute to an accounting attribute or use it in a mapping rule, the view is the documented source of project descriptive flexfield values within the XLA context. This is the object queried when a user investigates how a value such as project_attribute1 is obtained for accounting purposes.

Underlying Base Objects

The view is defined over four base tables, each referenced through an APPS synonym:

• PA_PROJECTS_ALL — the primary source of project rows, aliased P. Supplies the project identifier, name, number, organization, location, public sector flag, operating unit, and the project DFF columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE10.
• PA_PROJECT_TYPES_ALL — the project type definition, aliased PT. Joined on PROJECT_TYPE and ORG_ID, supplying the project type name, type class code, burden cost flag, burden display method, and the project type DFF columns.
• HR_ALL_ORGANIZATION_UNITS — aliased HROU2, joined on ORGANIZATION_ID = P.ORG_ID to obtain the organization unit definition.
• HR_ORGANIZATION_INFORMATION — joined twice, as I1 for the carrying-out organization and as I2 for the operating unit, both restricted to the 'COMPANY COST CENTER' information context, to retrieve the COMPANY and COST_CENTER organization information segments.

The joins to PA_PROJECT_TYPES_ALL and HR_ALL_ORGANIZATION_UNITS are inner joins on ORG_ID, while the two HR_ORGANIZATION_INFORMATION joins are outer joins, so a project is returned even when carrying-out organization or operating unit cost center information is not defined.

Key Columns

• PROJECT_ID, PROJECT_NAME, PROJECT_NUMBER — the unique project identifier, the project name, and SEGMENT1 (the project number) respectively.
• PROJECT_TYPE, PROJECT_TYPE_CLASS_CODE — the project type name and its classification code, used to drive accounting rules.
• PROJECT_ORGANIZATION_ID, PROJECT_LOCATION_ID — the carrying-out organization and project location.
• PROJ_PUBLIC_SECTOR_FLAG, PROJ_BURDEN_COST_FLAG, PROJ_BURDEN_DISPLAY_METHOD — public sector indicator and burden cost handling attributes; the display method is derived by a DECODE that defaults to 'S' when burden costing is enabled and no method is stored.
• PROJECT_ORG_COMPANY, PROJECT_ORG_COST_CENTER — company and cost center segments of the carrying-out organization.
• PROJECT_OPERATING_UNIT_ID, PROJECT_OU_COMPANY, PROJECT_OU_COST_CENTER — the operating unit identifier and its company and cost center segments.
• PROJECT_ATTRIBUTE_CATEGORY, PROJECT_ATTRIBUTE1–10 — the project descriptive flexfield context and segment values. project_attribute1 maps to PROJECT_ATTRIBUTE1.
• PROJ_TYPE_ATTRIBUTE_CATEGORY, PROJ_TYPE_ATTRIBUTE1–10 — the project type descriptive flexfield context and segment values.

Common Use Cases and Queries

The principal use case is tracing the source of project descriptive flexfield values in Subledger Accounting. To inspect the DFF value for a specific project:

• SELECT project_id, project_number, project_name, project_attribute_category, project_attribute1 FROM apps.pa_xla_project_ref_v WHERE project_id = :p_project_id;
• To list projects carrying a particular DFF value: SELECT project_number, project_name, project_attribute1 FROM apps.pa_xla_project_ref_v WHERE project_attribute1 = 'CONSTRUCTION';
• To review burden and organization classification data: SELECT project_number, proj_burden_cost_flag, proj_burden_display_method, project_org_company, project_org_cost_center FROM apps.pa_xla_project_ref_v;

Because the view is a seeded APPS object referenced by Subledger Accounting, it should be queried rather than modified. Customizations that add project DFF segments used in accounting should be configured through the flexfield and accounting setups so that the values remain accessible through this view.