Search Results control_rule_id




Overview
Explore in AI Chat

Overview

The PA.PA_PM_CONTROL_ACTIONS table is a Projects (PA) module data object that stores the set of controlled actions applied to data imported into Oracle E-Business Suite from external systems. It functions as a configuration and validation mechanism within the Project Management integration flow, allowing administrators to define which actions the import process may take when external project or resource data is loaded, and under what conditions a controlled action is permitted.

Under the ETRM 12.2.2 physical schema, the table resides in the PA schema and contains ten documented columns. Its primary key is the PA_PM_CONTROL_ACTIONS_PK constraint, keyed on CONTROL_RULE_ID. A unique index, PA_PM_CONTROL_ACTIONS_U1, spans CONTROL_RULE_ID and ZD_EDITION_NAME, confirming that the table is edition-enabled in the 12.2.x multitenant and editioning architecture.

Based on the foreign key topology, the ETRM Data Vault classification heuristic suggests this object is hub-leaning. In Data Vault modeling terms, the table behaves as a hub of controlled-action definitions referenced by dependent rules, rather than as a pure transactional satellite.

Key Information Stored

The table's most significant columns are:

  • CONTROL_RULE_ID — The surrogate primary key and the identifying attribute for each controlled action definition. It is also the business-key candidate paired with edition name.
  • ACTION — The controlled action itself; the operation or behavior applied to imported data when the associated control rule is triggered.
  • DESCRIPTION — Free-text description clarifying the purpose or business meaning of the controlled action.
  • FIELD_VALUE_ALLOWED_FLAG — A flag indicating whether a specific field value is permitted for the action, governing validation behavior during import.
  • ZD_EDITION_NAME — The editioning column introduced in EBS 12.2, used with CONTROL_RULE_ID to form the unique business key and to support edition-based redefinition.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle who-columns capturing audit metadata for row creation and maintenance.

The surrogate key (CONTROL_RULE_ID) provides the technical row identity, while the unique combination of CONTROL_RULE_ID and ZD_EDITION_NAME serves as the documented business-key candidate.

Common Use Cases and Queries

Typical scenarios include verifying which controlled actions are configured for imported data, auditing action definitions against their descriptions, and joining control actions to the product control rules that reference them.

A representative query lists all controlled actions for a given control rule:

  • SELECT ca.control_rule_id, ca.action, ca.description, ca.field_value_allowed_flag FROM pa.pa_pm_control_actions ca WHERE ca.control_rule_id = :p_rule_id;

Because the table is edition-enabled, queries in a 12.2.x environment should be aware of ZD_EDITION_NAME when operating under editioning semantics. A join to the controlling rule table demonstrates the parent-child relationship:

  • SELECT pcr.control_rule_id, ca.action, ca.description FROM pa_pa_pm_product_control_rules pcr, pa_pa_pm_control_actions ca WHERE pcr.control_rule_id = ca.control_rule_id;

Reporting use cases include producing a catalog of controlled actions for integration governance, confirming that flags are set appropriately before an import run, and reconciling actions against the rules that drive them.

Related Objects

The following objects are most relevant to PA_PM_CONTROL_ACTIONS based on the documented FK relationships:

  • PA_PM_PRODUCT_CONTROL_RULES — The primary referencing table; its CONTROL_RULE_ID foreign key column points to PA_PM_CONTROL_ACTIONS.CONTROL_RULE_ID, establishing the core parent-link relationship.
  • PA_PM_CONTROL_ACTIONS_PK — The primary key constraint enforcing uniqueness of CONTROL_RULE_ID.
  • PA_PM_CONTROL_ACTIONS_U1 — The unique index over CONTROL_RULE_ID and ZD_EDITION_NAME, supporting the business-key candidate.

Additional Project Management integration objects that participate in the same import control framework may reference this table directly or indirectly, but the documented FK evidence centers on PA_PM_PRODUCT_CONTROL_RULES as the definitive dependent object.