Search Results pa_product_functions




Overview
Explore in AI Chat

Overview

PA_PRODUCT_FUNCTIONS is a reference and configuration table owned by the PA (Projects) schema in Oracle E-Business Suite. It stores the functions defined for each product in the Oracle Projects suite, acting as the master registry that maps a business product to the functional capabilities delivered within it. Each row defines one function for one product, keyed by a composite of product, object type, and object code. The table supports the Oracle Projects architecture, where products such as Project Management, Project Costing, and Project Billing expose discrete functions that drive menu entries, security, and process behavior.

From a Data Vault modeling perspective, the mined relationship data classifies this object as standalone. In that heuristic classification it carries no foreign keys to parent hubs, so it is best treated as a self-contained configuration hub or reference construct rather than as a link or a dependent satellite. No satellite perspective applies because the table holds its own descriptive attributes and does not append change history to an external business key.

Key Information Stored

The documented physical schema contains 10 columns. The most important are the three business-key components that also form the primary key, PA_PRODUCT_FUNCTIONS_PK:

The surrogate-vs-business-key distinction is important here. Oracle documents PA_PRODUCT_FUNCTIONS_PK as the primary key (PRODUCT_CODE, OBJECT_TYPE, OBJECT_CODE), while PA_PRODUCT_FUNCTIONS_U1 provides the business-key candidate, extending those three columns with ZD_EDITION_NAME to allow edition-specific function definitions.

Common Use Cases and Queries

Typical uses include validating which functions are enabled for a product, driving security and menu configuration, and reconciling function definitions across editions. A common query retrieves all functions for a given product:

SELECT OBJECT_TYPE, OBJECT_CODE FROM PA.PA_PRODUCT_FUNCTIONS WHERE PRODUCT_CODE = :product_code;

To resolve a specific function, filter on the full primary key: PRODUCT_CODE = :p AND OBJECT_TYPE = :t AND OBJECT_CODE = :o. Administrators frequently audit rows for staleness using the audit columns, for example filtering on LAST_UPDATE_DATE to identify recently changed function definitions. Reporting on distinct OBJECT_TYPE values per PRODUCT_CODE helps document the functional footprint of each Oracle Projects product. Edition-aware queries should include ZD_EDITION_NAME to avoid returning definitions from multiple editions.

Related Objects

Because the mined metadata classifies this table as standalone with no documented foreign keys, related objects are inferred from the shared functional model rather than from FK constraints. Significant dependencies and counterparts include:

  • PA_PRODUCTS — the product master joined on PRODUCT_CODE.
  • PA_PRODUCT_FUNCTIONS_PK / PA_PRODUCT_FUNCTIONS_U1 — the primary and unique indexes that enforce uniqueness on the documented key columns.
  • Function and security tables in the Oracle Projects security model that consume PRODUCT_CODE and OBJECT_CODE values.
  • Oracle EBS FND menu, function, and responsibility tables that reference the same function codes.
  • Concurrent-program and process definitions within Oracle Projects that key off product functions.
  • Standard Oracle audit and edition columns shared across the PA schema.

All statements are grounded in the documented ETRM metadata for PA_PRODUCT_FUNCTIONS in Oracle EBS 12.1.1 and 12.2.2.