Search Results pa_product_functions_u1




Overview
Explore in AI Chat

Overview

PA.PA_PRODUCT_FUNCTIONS is a seeded reference table in the Oracle Projects (PA) schema that defines the functional object associations available for each product within the Oracle Projects suite. It acts as a configuration map: for a given product short code (such as Projects, Grants, or Labor), it records the object types and object codes that the product exposes as functions. The table resides in the APPS_TS_SEED tablespace, confirming that its content is delivered as seed data rather than transactional user data, and it carries a status of VALID in the ETRM documentation for both Oracle EBS 12.1.1 and 12.2.2.

From a data modelling perspective, the mined dependency classification suggests treating this object as a standalone structure. It neither references nor is referenced by other database objects through foreign keys, so it does not naturally resolve into a hub, link, or satellite pattern. Instead, it behaves as a low-volume, slowly changing reference set that is typically replicated in full into downstream warehouses and BI layers, where it is used to validate and label other Projects data.

Key Information Stored

The table contains ten documented columns. The functional content is concentrated in three business columns, which together form both the primary key and the basis of the unique index:

  • PRODUCT_CODE (VARCHAR2, 30) — The product short code within Oracle Projects, identifying which application or product line the function belongs to.
  • OBJECT_TYPE (VARCHAR2, 30) — The type of object associated with the product, describing the category of the function.
  • OBJECT_CODE (VARCHAR2, 30) — The name of the object associated with the product, providing the specific functional identifier.

The primary key is documented as PA_PRODUCT_FUNCTIONS_PK over (PRODUCT_CODE, OBJECT_TYPE, OBJECT_CODE). The unique index PA_PRODUCT_FUNCTIONS_U1 covers the same three columns and, in the 12.2.2 physical schema, includes the additional column ZD_EDITION_NAME. This edition column is significant because Oracle EBS 12.2.x introduced edition-based redefinition (EBR), and ZD_EDITION_NAME allows the same logical product function to exist in multiple editions during online patching. Analysts joining this table in a 12.2.2 environment should therefore filter or group on ZD_EDITION_NAME to avoid duplicated rows.

The remaining columns are administrative. RECORD_VERSION_NUMBER supports the locking strategy used by self-service applications. CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN are the standard WHO audit columns, enabling lineage tracking of when a seeded row was created or last modified.

Common Use Cases and Queries

The primary use case is validation and labelling. When reporting on Projects transactions, developers join PA_PRODUCT_FUNCTIONS to confirm that a given product/object combination is a supported function, or to translate internal object codes into user-facing descriptions.

  • Listing all functions for a specific product: SELECT OBJECT_TYPE, OBJECT_CODE FROM PA.PA_PRODUCT_FUNCTIONS WHERE PRODUCT_CODE = :product_code;
  • Checking uniqueness across the business key: SELECT PRODUCT_CODE, OBJECT_TYPE, OBJECT_CODE, COUNT(*) FROM PA.PA_PRODUCT_FUNCTIONS GROUP BY PRODUCT_CODE, OBJECT_TYPE, OBJECT_CODE HAVING COUNT(*) > 1;
  • Auditing seeded changes by date: SELECT * FROM PA.PA_PRODUCT_FUNCTIONS WHERE LAST_UPDATE_DATE >= :since_date;
  • Edition-aware extraction in 12.2.2: SELECT * FROM PA.PA_PRODUCT_FUNCTIONS WHERE ZD_EDITION_NAME = SYS_CONTEXT('USERENV','DB_EDITION');

Typical reporting scenarios include building a function reference dimension for Projects subject areas, comparing seeded function coverage across releases during an upgrade, and diagnosing configuration mismatches when a product function appears missing from self-service pages.

Related Objects

Because the dependency metadata states that PA_PRODUCT_FUNCTIONS does not reference any database object and is referenced only by its own APPS synonym, PA.PA_PRODUCT_FUNCTIONS, the relationship set is narrow. The object is accessed through the APPS synonym PA_PRODUCT_FUNCTIONS, which is the standard mechanism by which application code and concurrent programs reference seeded Projects tables without hard-coding schema names. In practice, it is most usefully joined to other Projects product-configuration and object-level tables on the PRODUCT_CODE column, since that column is the natural linkage to the broader Oracle Projects product registry. The unique index PA_PRODUCT_FUNCTIONS_U1 serves as the primary enforcement point for the business key and, together with PA_PRODUCT_FUNCTIONS_PK, defines the integrity constraints relied upon by any downstream consumer of this reference data.