Results for “pa_project_id”

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

Overview

The PA_OVERRIDE_FIELD_VALUES_V view is an Oracle Projects (PA) dictionary object owned by the APPS schema. Its ETRM description is recorded simply as "Retrofitted," indicating that it was preserved across release migrations (notably 12.1.1 to 12.2.2) to maintain backward compatibility for the Projects module. Functionally, the view exposes the current values of project attributes that originate from a source project template, together with the descriptive metadata that governs how those attributes are displayed and validated. It is therefore a reporting and integration layer over the project template override mechanism, allowing templates to be converted into live projects while preserving the field-level configuration defined at template time.

The view joins each project to the override field definitions derived from its creation template and returns both the field metadata (display name, sort order, data type, mandatory flag, LOV view name) and the corresponding runtime value from the project record.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the following objects:

• PA_PROJECTS (SYNONYM) — the primary project record, aliased as PAP, supplying project-level field values.
• PA_OVERRIDE_FIELDS_V (VIEW) — the override field definitions surfaced from the source template (PA_SOURCE_TEMPLATE_ID).
• HR_ORGANIZATION_UNITS (VIEW) — used to resolve the carrying-out organization name.
• PA_DISTRIBUTION_RULES (SYNONYM) — supplies the distribution rule meaning.
• PA_PROJECT_STATUSES (SYNONYM) — resolves the project status name for the PROJECT_STATUS_CODE field.
• PA_EMPLOYEES (VIEW) and PA_PROJECT_PLAYERS (VIEW) — resolve key member person identifiers and full names.
• PA_PROJECT_CLASSES, PA_PROJECT_CUSTOMERS_V — referenced by the broader override framework.
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY (PACKAGEs) — supporting HR security and name resolution.

The core join predicate links PA_PROJECTS.CREATED_FROM_PROJECT_ID to PA_OVERRIDE_FIELDS_V.PA_SOURCE_TEMPLATE_ID, so only projects created from a template are included. The view text is a UNION of three branches handling standard fields, project status, and key members respectively.

Key Columns

• PROJECT_ID — identifier of the project that inherited override fields.
• ORG_ID — operating unit / organization identifier for multi-org filtering.
• PA_FIELD_NAME — internal name of the overridden field (e.g. NAME, DESCRIPTION, START_DATE, COMPLETION_DATE, DISTRIBUTION_RULE, PUBLIC_SECTOR_FLAG, CARRYING_OUT_ORGANIZATION_ID, PROJECT_STATUS_CODE, KEY_MEMBER).
• PA_DISPLAY_NAME — user-facing label for the field.
• SORT_ORDER — display ordering; key member rows return 999.
• TYPE — data type of the field.
• MANDATORY_FLAG — whether the field requires a value.
• LOV_VIEW_NAME — the list-of-values view supplying valid entries.
• Field value column — the final DECODE column returning the actual value, resolved differently per field (e.g. status name, distribution rule meaning, or key member full name).

Common Use Cases and Queries

Typical uses include auditing which template-driven attributes a project retains, validating mandatory overrides, and building project setup or migration reports.

• List override metadata for a project:

  SELECT pa_field_name, pa_display_name, sort_order, type, mandatory_flag
  FROM   apps.pa_override_field_values_v
  WHERE  project_id = :p_project_id
  ORDER BY sort_order;

• Multi-org filtered extraction:

  SELECT project_id, pa_field_name, pa_display_name
  FROM   apps.pa_override_field_values_v
  WHERE  org_id = :p_org_id;

• Identify mandatory fields with unpopulated values for data-quality review, joining PROJECT_ID back to PA_PROJECTS.

Because the view restricts to template-derived projects, queries intended for all projects must fall back to PA_PROJECTS directly.