Search Results pa_source_template_id




Overview
Explore in AI Chat

Overview

APPS.PA_OVERRIDE_FIELDS_SS_V is a VALID internal Oracle Applications view owned by the APPS schema. It exposes the set of override fields associated with a given source template used during project and template copy operations in Oracle Projects. The view is a single-select (SS) construction, as indicated by its suffix, and is registered under FND Design Data as PA.PA_OVERRIDE_FIELDS_SS_V. It presents a denormalized, presentation-ready projection of override field metadata: the source template identifier, the underlying field name, the translatable meaning, a display name, the specification value, the field type, a sort order, a mandatory indicator, and a record version number. Because the view joins lookup and setup utility logic, it is the mechanism by which the application resolves the displayable and behavior-defining attributes of each override field for a project copy or template setup template.

The ETRM metadata carries an explicit Oracle Internal Use Only warning: Oracle Corporation does not support access to Oracle applications data using this object except from standard Oracle Applications programs. Consequently, the view is intended for consumption by Oracle Projects forms, concurrent programs, and setup utilities rather than as a supported customer-facing reporting interface.

Underlying Base Objects

The documented dependency list identifies three referenced objects:

  • PA_LOOKUPS (VIEW) — supplies the meaning, display name, and lookup-derived attributes that give each override field its user-visible label and descriptive text.
  • PA_PROJECT_COPY_OVERRIDES (SYNONYM) — the base storage for project copy override definitions; the view filters and presents the override fields applicable to a source template.
  • PA_PROJ_TEMPLATE_SETUP_UTILS (PACKAGE) — provides the setup utility logic used to derive field specifications, type classification, ordering, and mandatory flags for template setup.

The view is read-only from the perspective of dependents: the ETRM metadata states that APPS.PA_OVERRIDE_FIELDS_SS_V is not referenced by any other database object. It therefore functions as a terminal presentation layer rather than as a component in a larger dependency chain. Access is restricted to standard Oracle Applications programs.

Key Columns

The view exposes ten columns, all with documented names:

  • PA_SOURCE_TEMPLATE_ID (NUMBER(15)) — the identifier of the source template to which the override field belongs. This is the primary filter column and the object of the user's search term "pa_source_template_id".
  • PA_FIELD_NAME (VARCHAR2(30)) — the internal field name of the override.
  • MEANING (VARCHAR2(80)) — the translatable meaning of the field, typically resolved through PA_LOOKUPS.
  • PA_DISPLAY_NAME (VARCHAR2(80)) — the display label shown for the field.
  • SPECIFICATION (VARCHAR2(4000)) — the field specification or override specification value.
  • TYPE (VARCHAR2(30)) — the classification of the override field.
  • SORT_ORDER (NUMBER) — controls the display sequence of fields.
  • MANDATORY_FLAG (VARCHAR2) — indicates whether the field is required.
  • RECORD_VERSION_NUMBER (NUMBER) — the optimistic locking / record version value.
  • ROW_ID (ROWID(10)) — the physical row identifier.

Common Use Cases and Queries

The view is principally queried to enumerate and describe override fields for a specific source template, for example when rendering the copy-override setup form or when validating mandatory overrides before a project copy. A representative query is:

SELECT PA_SOURCE_TEMPLATE_ID, PA_FIELD_NAME, MEANING, PA_DISPLAY_NAME, SPECIFICATION, TYPE, SORT_ORDER, MANDATORY_FLAG, RECORD_VERSION_NUMBER, ROW_ID FROM APPS.PA_OVERRIDE_FIELDS_SS_V;

To isolate the fields of one template, constrain PA_SOURCE_TEMPLATE_ID and order by SORT_ORDER. To find required fields, add MANDATORY_FLAG = 'Y'. To obtain user-facing labels, select PA_DISPLAY_NAME alongside MEANING. Because the object is internal and unsupported for direct customer access, any diagnostic use should be limited to read-only investigation and should not be embedded in supported customizations; supported integration should occur through the standard Oracle Projects copy and template setup programs.