Search Results pm_product_name




Overview
Explore in AI Chat

Overview

APPS.PA_PM_PRODUCT_CONTROL_RULES_V is a supplementary Oracle E-Business Suite view owned by the APPS schema. In Oracle EBS 12.1.1 and 12.2.2 it belongs to the Project Management product control framework and is classified by Oracle as a "supplementary view used to simplify forms coding." It presents a denormalized, form-friendly projection of the product control rule configuration that governs how Project Management products behave in a given operating context — which configuration actions are permitted, for which PM product, and against which field value. This view is central to the Oracle Product Management (OPM) and Projects product control setup, where product-level rules determine the allowed values and actions available when a user configures a PM product. Because the view joins the control rule base table to the action definition table and to the PA_LOOKUPS lookup view, it supplies human-readable action descriptions and product names alongside coded identifiers. Oracle explicitly warns that this view is not intended for direct query or data modification by customers, and that its definition may change substantially between releases. Consequently it should be treated strictly as a documented integration and reporting surface, not as a supported DML target. The view is documented in ETRM with a status of VALID.

Underlying Base Objects

The view is defined over three documented objects. The primary base object is PA_PM_PRODUCT_CONTROL_RULES, exposed to the view through a synonym and supplying the core control rule rows keyed by CONTROL_RULE_ID. The second is PA_PM_CONTROL_ACTIONS, also referenced via synonym, which provides the ACTION and ACTION_DESCRIPTION definitions that describe what each rule permits or restricts. The third is PA_LOOKUPS, a view over the FND_LOOKUPS foundation, which resolves coded values into their display meanings. The published query text lists all fifteen columns directly, confirming the view is a straightforward projection rather than one involving runtime parameters. Importantly, ETRM records that PA_PM_PRODUCT_CONTROL_RULES_V is not referenced by any other database object, so it is a terminal reporting object with no downstream dependents inside the APPS schema. The view carries the FND Design Data identifier PA.PA_PM_PRODUCT_CONTROL_RULES_V.

Key Columns

Common Use Cases and Queries

Typical uses include verifying which actions are enabled for a given PM product, auditing effective-dated control rules, and validating product configuration during integrations or data conversions. Because the view exposes PM_PRODUCT_NAME directly, users searching on that term can resolve product codes to names in a single query. A representative query is:

SELECT CONTROL_RULE_ID, PM_PRODUCT_CODE, PM_PRODUCT_NAME, ACTION, ACTION_DESCRIPTION, FIELD_VALUE_ALLOWED_FLAG, FIELD_VALUE_CODE FROM APPS.PA_PM_PRODUCT_CONTROL_RULES_V WHERE PM_PRODUCT_NAME = :product_name AND SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);

For a full inventory of currently active rules, omit the product predicate and filter on the effective dates. Oracle's guidance to avoid querying or altering data through this view should be observed; read-only reporting against it is the supported pattern.