Search Results pa_quick_entry_specs_ss_v




Overview
Explore in AI Chat

Overview

The PA_QUICK_ENTRY_SPECS_SS_V view is a Projects (PA) module dictionary view owned by the APPS schema. Its purpose is to consolidate the set of configurable "override fields" that the Oracle Projects Quick Entry / rapid project setup pages present to end users when a project specification is created or edited. In Oracle EBS 12.1.1 and 12.2.2, the Quick Entry flow allows a specifier to define which project attributes (for example, key member, classification, customer, or organization role) may be overridden at the template or project level. This view is the single source that supplies those available override fields and the values that legitimately constrain each one.

Because the view exposes a uniform, four-part row shape (field name, descriptive meaning, specification, and limiting value), it functions as a lookup and validation layer for the Quick Entry API and any custom reporting or integration built on top of it. Application code and reports query it to determine, for a given project type or role configuration, which override fields are enabled and what limit applies.

Underlying Base Objects

The view is defined as a UNION of several subselects over the following documented base objects:

Date effectiveness is enforced through TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE) on the lookup and role-type branches, so only currently active definitions are returned.

Key Columns

  • FIELD_NAME — the internal code of the override field. Documented literals include KEY_MEMBER, CLASSIFICATION, CUSTOMER_NAME, and ORG_ROLE.
  • FIELD_NAME_MEANING — the user-facing label retrieved from PA_LOOKUPS for the field code.
  • SPECIFICATION — the specific value permitted for that field (a role meaning, a classification category, or a customer relationship meaning).
  • DISPLAY_NAME — the presentation value shown on the Quick Entry page.
  • LIMITING_VALUE — the constraining value used for validation, such as PROJECT_ROLE_TYPE, CLASS_CATEGORY, or a lookup code.
  • OBJECT_TYPE_ID — populated for classification rows with the project type identifier; NULL elsewhere.
  • PROJECT_TYPE — the project type name associated with the row, where applicable.

Common Use Cases and Queries

Typical usage includes validating override field configuration, building custom Quick Entry integrations, and auditing which roles or classifications are available for a project type. A representative query listing all active override specifications is:

  • SELECT field_name, field_name_meaning, specification, display_name, limiting_value FROM apps.pa_quick_entry_specs_ss_v ORDER BY field_name, specification;

To isolate role-based override fields:

  • SELECT field_name, specification FROM apps.pa_quick_entry_specs_ss_v WHERE field_name IN ('KEY_MEMBER','ORG_ROLE');

To retrieve classification overrides for a specific project type:

  • SELECT specification, display_name FROM apps.pa_quick_entry_specs_ss_v WHERE field_name = 'CLASSIFICATION' AND project_type = :project_type;

Because the view is read-only and governed by APPS, no DML is permitted; extensions should be implemented through custom views that join it to project definitions or reporting tables.