Search Results pa_pm_product_control_rules




Overview
Explore in AI Chat

Overview

PA_PM_PRODUCT_CONTROL_RULES is a Projects (PA) module configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the set of control actions that the Product Manager (PM) import processing engine must evaluate when records are received from a specific external product. Each row represents a rule linking an external product code to a predefined control action, together with the field value that triggers or qualifies that action. The table therefore acts as the policy layer that governs how imported project, resource, or assignment data is validated, defaulted, or rejected before it is written into the Projects schema.

The ETRM relationship metadata classifies this object heuristically as satellite-leaning. In Data Vault modeling terms, the table behaves more like a satellite than a pure hub or link: its identity is dependent on the parent control action definition, and its rows carry descriptive, version-like attributes such as activation dates and field value codes. The classification is a modeling suggestion only and should be validated against the actual business keys used during implementation.

Key Information Stored

The table is documented with 10 columns under the PA schema. The most significant are:

  • CONTROL_RULE_ID – Surrogate identifier for the control rule. It is the leading column of the composite primary key PA_PM_PRODUCT_CONTROL_RULES_PK and is also a foreign key to PA_PM_CONTROL_ACTIONS, linking the rule to the action it governs.
  • PM_PRODUCT_CODE – Code identifying the external product whose imported records are subject to the rule. This is the second column of the composite primary key and functions as the business-key candidate alongside CONTROL_RULE_ID.
  • FIELD_VALUE_CODE – The specific field value used to qualify or trigger the control action for that product.
  • START_DATE_ACTIVE – Date from which the rule becomes effective.
  • END_DATE_ACTIVE – Date on which the rule expires; a null value typically indicates an open-ended rule.
  • CREATION_DATE, CREATED_BY – Standard audit columns recording when and by whom the row was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard audit columns recording the most recent modification and the login that performed it.

The composite primary key PA_PM_PRODUCT_CONTROL_RULES_PK (CONTROL_RULE_ID, PM_PRODUCT_CODE) enforces that a given control action is configured at most once per external product, while the surrogate component preserves integration integrity with the action definition table.

Common Use Cases and Queries

Typical usage centers on diagnosing and reporting import behavior. Administrators query effective rules for a product before a data load, and support analysts trace why a record was rejected or defaulted by joining the rule to its parent action.

  • List all currently active rules for a product:
    SELECT control_rule_id, pm_product_code, field_value_code, start_date_active, end_date_active FROM pa.pa_pm_product_control_rules WHERE pm_product_code = :product_code AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);
  • Join rules to their parent action definition to see rule descriptions:
    SELECT r.control_rule_id, r.pm_product_code, r.field_value_code, a.* FROM pa.pa_pm_product_control_rules r, pa.pa_pm_control_actions a WHERE r.control_rule_id = a.control_rule_id;
  • Audit recently changed rules using LAST_UPDATE_DATE for SOX or change-management reporting.
  • Detect orphaned or conflicting rules where overlapping activation date ranges exist for the same product and action.

Related Objects

The most significant related objects, based on the documented foreign-key relationship and standard Projects Product Manager structures, include:

  • PA_PM_CONTROL_ACTIONS – Parent table of the control action definitions; joined on CONTROL_RULE_ID.
  • PA_PM_PRODUCT_CONTROL_RULES_PK – The primary key constraint enforcing uniqueness of rule per product.
  • PA_PM_PRODUCT_CONTROL_RULES_N1 – Supporting index, where implemented, on PM_PRODUCT_CODE for product-based lookups.
  • PA_PM_PRODUCTS and related PM product definition tables – Provide the product code context.
  • PA_PM_IMPORT_* interface tables and the Product Manager import concurrent programs – Consume these rules during data validation and transformation.
  • PA_INTERFACE_CONTROLS style validation tables – Complementary configuration governing import processing.

Because the table is configuration rather than transactional, downstream dependencies are principally the PM import engine and reporting views rather than high-volume fact tables.