Search Results pa_pm_product_control_rules_v




Overview
Explore in AI Chat

Overview

PA_PM_PRODUCT_CONTROL_RULES_V is an Oracle E-Business Suite view owned by the APPS schema within the PA (Projects) product family. The ETRM documentation classifies this object as a view with VALID status and annotates its description succinctly as "10Sc Only," indicating that it belongs to a legacy control-rule construct introduced with the earliest Projects releases and retained for backward compatibility rather than continued functional development. The view surfaces product-level control rules used by Oracle Projects to govern which field values are permitted on project-related transactions, segment combinations, and processing actions tied to a given PM product code.

The object is read-only by design. It consolidates rule definitions with their associated control actions and resolves the PM product code to a user-facing meaning through the PA_LOOKUPS view. This makes it particularly convenient for reporting, data extraction, and integration scenarios where the raw numeric or coded values stored in the underlying base tables are insufficient, and a decoded, human-readable representation is required.

Underlying Base Objects

The view is defined over three documented objects:

The join between the control rules and the lookups restricts output to product codes that have an active lookup definition of type PM_PRODUCT_CODE, effectively filtering orphaned or retired codes. Because PA_LOOKUPS is itself a view in Oracle EBS, the resolution implicitly honors lookup enablement and language semantics.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing which field values are allowed for a product, reconciling control rules during upgrades, and extracting rule metadata for integration or migration. A representative query filtering on the searched attribute pm_product_code is:

SELECT pm_product_code, pm_product_name, action, field_value_code,
       field_value_allowed_flag, start_date_active, end_date_active
  FROM apps.pa_pm_product_control_rules_v
 WHERE pm_product_code = :product_code
   AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE)
                AND NVL(end_date_active, SYSDATE);

Because the view joins PA_LOOKUPS, results are automatically decoded and restriction by PM_PRODUCT_CODE is indexed through the lookup join. This view should be treated as read-only; all maintenance is performed against the underlying base tables.