Results for “proj_progress_attr_id”

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

Overview

PA_FINANCIAL_OPTIONS_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes project-level financial structure configuration by joining the project element hierarchy to the workplan attributes and progress attributes that govern how financial structures are displayed, weighted, and tracked. In effect, the view presents the intersection of a project's financial structure definition and the progress/workplan options assigned to that structure, allowing report developers and integration specialists to query a single object rather than performing multi-table joins manually.

The view is commonly consumed in project reporting, structure validation, and progress-attribute-driven integrations. Because it is defined entirely over PA base tables, it inherits the transactional consistency of those tables and reflects changes committed to the underlying structures in real time.

Underlying Base Objects

The view is defined over three PA base objects, which appear in the ownership metadata as synonyms resolved to the underlying tables:

• PA_PROJ_WORKPLAN_ATTR — Supplies workplan display-level defaults and record versioning for the project element.
• PA_PROJ_ELEMENTS — The project element definition table, supplying the element name and project association. The view explicitly filters where PROJECT_ID is not zero and links elements to their projects.
• PA_PROJ_PROGRESS_ATTR — Supplies progress tracking attributes, including the progress attribute identifier, task weight basis, and structure-type scoping.

The join conditions are materially constrained: elements must match workplan and progress attributes on PROJ_ELEMENT_ID, the progress attribute must be scoped with OBJECT_TYPE = 'PA_STRUCTURES', must match on PROJECT_ID, and must be restricted with STRUCTURE_TYPE = 'FINANCIAL'. Consequently, the view returns only rows for elements belonging to the financial structure, not for other structure types such as budgetary or planning structures.

Key Columns

• PROJECT_ID — Identifier of the project to which the financial structure element belongs.
• PROJ_ELEMENT_ID — Identifier of the project element (structure node) within the financial structure.
• STRUCTURE_NAME — The element name, sourced from PPE.NAME, representing the financial structure element label.
• DEFAULT_DISPLAY_LVL — Workplan default display level from PPWA.WP_DEFAULT_DISPLAY_LVL, indicating the level at which the element is displayed by default.
• PROJ_PROGRESS_ATTR_ID — Identifier of the associated progress attribute record.
• PROG_RECORD_VERSION_NUMBER, PPWA_RECORD_VERSION_NUMBER, PPE_RECORD_VERSION_NUMBER — Optimistic locking record version numbers from the progress-attribute, workplan-attribute, and element tables respectively. These are used to validate that the row has not been modified concurrently.
• TASK_WEIGHT_BASIS_CODE — The basis used for weighting tasks within the progress configuration.

Common Use Cases and Queries

Typical scenarios include identifying the default display level for financial structure elements, verifying progress attribute assignments for a project's financial structure, and extracting record version numbers for controlled updates against PA_PROJ_PROGRESS_ATTR or PA_PROJ_WORKPLAN_ATTR.

Sample query to list financial structure options for a specific project:

SELECT project_id,
       proj_element_id,
       structure_name,
       default_display_lvl,
       proj_progress_attr_id,
       task_weight_basis_code
FROM   apps.pa_financial_options_v
WHERE  project_id = :p_project_id
ORDER  BY structure_name;

Query to retrieve version numbers ahead of an update:

SELECT proj_element_id,
       prog_record_version_number,
       ppwa_record_version_number,
       ppe_record_version_number
FROM   apps.pa_financial_options_v
WHERE  proj_element_id = :p_element_id;

Because the view enforces STRUCTURE_TYPE = 'FINANCIAL' and excludes PROJECT_ID = 0, queries do not require additional structure-type filtering. All access should occur through a correctly configured APPS responsibility or a synonym granting SELECT privilege.