Search Results lov_view_name




Overview
Explore in AI Chat

Overview

The APPS.PA_OVERRIDE_FIELD_VALUES_V view is a reporting and integration object within the Oracle E-Business Suite Projects (PA) module. It exposes the current override field values that apply to individual projects, resolved against the organization, project type, and configuration metadata that governs project definition. Rather than storing data independently, the view consolidates override-related attributes from multiple transactional and descriptive base objects into a single, queryable result set, allowing reporting tools, OA Framework pages, and external integrations to retrieve project-level override values without joining the underlying tables directly.

The view is owned by the APPS schema, carries an internal status of VALID, and is classified as an internal (non-public) view. Oracle documents it as being for Oracle Internal Use Only and states that Oracle does not support direct access to application data through this object except from standard Oracle Applications programs. Its FND design data reference is PA.PA_OVERRIDE_FIELD_VALUES_V, confirming it is registered in the Applications dictionary.

Underlying Base Objects

The view is defined over a combination of Projects and Human Resources objects. The dependency chain includes PA_OVERRIDE_FIELDS_V and PA_OVERRIDE_FIELD_VALUES_V's supporting Projects objects: PA_PROJECTS, PA_PROJECT_CLASSES, PA_PROJECT_STATUSES, PA_PROJECT_CUSTOMERS_V, PA_PROJECT_PLAYERS, PA_EMPLOYEES, and PA_DISTRIBUTION_RULES. Human Resources components contribute organizational and security context through HR_GENERAL, HR_ORGANIZATION_UNITS, HR_PERSON_NAME, and HR_SECURITY.

  • PA_OVERRIDE_FIELDS_V supplies the field definitions and display metadata that describe each overridable field.
  • PA_PROJECTS, PA_PROJECT_CLASSES, and PA_PROJECT_STATUSES provide project identity, classification, and lifecycle context for scoping the override values.
  • PA_PROJECT_CUSTOMERS_V and PA_PROJECT_PLAYERS link customer and project personnel information.
  • PA_DISTRIBUTION_RULES and PA_EMPLOYEES relate to how override values are applied and to personnel attribution.
  • HR_ORGANIZATION_UNITS and HR_GENERAL resolve the operating unit and organization attributes; HR_SECURITY and HR_PERSON_NAME enforce access and resolve person display names.

The view is not referenced by any other database object, indicating it functions as a terminal reporting layer rather than a building block for additional views or synonyms.

Key Columns

  • PA_PROJECT_ID (NUMBER): the unique identifier of the project the override value applies to.
  • ORG_ID (NUMBER): the operating unit that owns the record, used for multi-organization security and reporting filteration.
  • PA_FIELD_NAME (VARCHAR2, 30): the internal name of the overridable project field.
  • PA_DISPLAY_NAME (VARCHAR2, 80): the user-facing label for the field, typically surfaced in the project definition UI.
  • SORT_ORDER (NUMBER): controls the presentation sequence of fields.
  • TYPE (VARCHAR2, 30): classifies the field type for rendering and validation.
  • MANDATORY_FLAG (VARCHAR2): indicates whether the field requires a value.
  • LOV_VIEW_NAME (VARCHAR2, 27): identifies the list-of-values view used to populate permitted inputs.
  • CODE (VARCHAR2, 40) and FIELD_VALUE (VARCHAR2, 360): the stored code and resolved value for the override.

Common Use Cases and Queries

Typical uses include auditing which override fields are populated per project, validating that mandatory overrides are complete, and driving dynamic project definition screens where field metadata is required alongside the stored value. A basic query retrieves the field metadata and values for a specific project:

  • SELECT pa_project_id, org_id, pa_field_name, pa_display_name, mandatory_flag, field_value FROM apps.pa_override_field_values_v WHERE pa_project_id = :project_id ORDER BY sort_order;
  • Filter by operating unit for multi-org reporting: WHERE org_id = :org_id.
  • Isolate incomplete mandatory overrides: WHERE mandatory_flag = 'Y' AND field_value IS NULL.

Because the object is documented as internal and unsupported for direct access, production use should be limited to standard Oracle Applications programs, or accessed with the understanding that behavior and structure are not guaranteed across releases.