Search Results pa_override_fields_ss_v




Overview
Explore in AI Chat

Overview

PA_OVERRIDE_FIELDS_SS_V is an APPS-owned database view within the Oracle E-Business Suite Projects (PA) module. It exposes the set of project-copy override fields that can be applied when one project is duplicated or rolled over from a source template to a target project within Oracle Projects. The view presents a denormalized, presentation-ready representation of the override configuration defined in the underlying override table, joined to lookup values to supply human-readable field labels and specification metadata. Because the view resolves codes into meanings and applies the override utility function to derive limiting-value descriptions, it serves as the primary reference for reports, forms, and integrations that need to display or validate override field definitions without directly accessing the base override table.

Underlying Base Objects

The view is defined over three documented base objects. PA_PROJECT_COPY_OVERRIDES, referenced through a synonym, is the driving table holding the override records themselves, including the field name to be overridden, its limiting value, sort ordering, mandatory flag, record version number, and row identifier. PA_LOOKUPS is joined to restrict records to the lookup type 'OVERRIDE FIELD' and to translate the stored lookup code into its meaning for display. PA_PROJ_TEMPLATE_SETUP_UTILS is a PL/SQL package whose GET_LIMITING_VALUE_MEANING function is invoked in the select list to convert the stored limiting value into an interpretable specification string at query time. The join condition, PPCO.FIELD_NAME = PL.LOOKUP_CODE AND PL.LOOKUP_TYPE = 'OVERRIDE FIELD', ensures that only valid, defined override fields are returned with their associated display attributes.

Key Columns

The view projects column names that differ from the underlying table columns, providing a cleaner interface. PA_SOURCE_TEMPLATE_ID corresponds to PROJECT_ID and identifies the source template or project from which overrides are sourced. PA_FIELD_NAME carries the override field identifier, matched against the lookup code. MEANING supplies the lookup-derived description of that field. PA_DISPLAY_NAME provides the display label used on screens and reports. SPECIFICATION holds the result of GET_LIMITING_VALUE_MEANING, translating the raw LIMITING_VALUE into readable form. LIMITING_VALUE itself is retained for programmatic use, and SORT_ORDER governs display sequencing. MANDATORY_FLAG indicates whether the override is required, RECORD_VERSION_NUMBER supports optimistic locking, and ROW_ID exposes the row identifier for addressing individual records during maintenance.

Common Use Cases and Queries

Typical uses include enumerating available override fields when configuring project-copy or project-template operations, validating that mandatory overrides have been supplied prior to copying, and feeding lookup-driven lists into custom reports or integrations. A basic query to list override fields for a given source template follows:

  • SELECT pa_source_template_id, pa_field_name, meaning, pa_display_name, specification, mandatory_flag FROM apps.pa_override_fields_ss_v WHERE pa_source_template_id = :template_id ORDER BY sort_order;
  • Filtering mandatory overrides only: SELECT pa_field_name, pa_display_name FROM apps.pa_override_fields_ss_v WHERE mandatory_flag = 'Y';
  • Retrieving specification text for validation: SELECT pa_field_name, specification, limiting_value FROM apps.pa_override_fields_ss_v WHERE pa_source_template_id = :template_id;

Because the specification is computed by a PL/SQL function, queries invoking that column incur per-row package execution; result sets are therefore best scoped by source template or field name.