Search Results pa_pm_control_actions_u1

Overview

PA.PA_PM_CONTROL_ACTIONS is a seed-data reference table in the Oracle Projects (PA) schema that defines the set of control actions available for governing project and budget data imported from external systems into Oracle E-Business Suite. Each row represents an action that Oracle Projects can intercept and validate, ensuring that data published back to a source system — or received from it — remains consistent with the records held within Oracle Projects. Because the table resides in the APPS_TS_SEED tablespace with a PCT Free of 10, it is populated at installation and is not intended for routine transactional growth.

Based on the foreign key and primary key structure mined from the schema, PA_PM_CONTROL_ACTIONS exhibits hub-leaning characteristics in a Data Vault model. Its unique, relatively static CONTROL_RULE_ID and low expected row count make it a natural candidate for a hub or reference table, with dependent rules and configuration data modeled as satellites or links. This classification is a modeling suggestion rather than a documented Oracle construct.

Key Information Stored

The table is narrow by design, holding ten documented columns. The most significant include:

• CONTROL_RULE_ID — the numeric surrogate primary key (PA_PM_CONTROL_ACTIONS_PK) that uniquely identifies each control action.
• ACTION — the intended action subject to control, stored as a VARCHAR2(30) code (for example, budget or project publication actions).
• DESCRIPTION — a VARCHAR2(80) human-readable label for the action, used in setup and reporting.
• FIELD_VALUE_ALLOWED_FLAG — indicates whether field values may be supplied for the action; the metadata notes this is pertinent only to actions involving budgets.
• ZD_EDITION_NAME — part of the unique index PA_PM_CONTROL_ACTIONS_U1 alongside CONTROL_RULE_ID, serving as a business-key candidate and supporting edition-based definitions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO columns that track audit and concurrency information.

The pairing of CONTROL_RULE_ID with ZD_EDITION_NAME in the unique index distinguishes the surrogate primary key from the composite business-key candidate, a common pattern in 12.2.x editioned dictionaries.

Common Use Cases and Queries

Functional consultants and developers query this table to enumerate valid control actions when configuring external system integration, and to confirm whether field values are permitted for a given budget-related action. A typical lookup retrieves the action code and description:

• SELECT ACTION, DESCRIPTION, FIELD_VALUE_ALLOWED_FLAG FROM PA.PA_PM_CONTROL_ACTIONS;
• Filtering for actions that accept field values: WHERE FIELD_VALUE_ALLOWED_FLAG = 'Y'.
• Joining to dependent rules on CONTROL_RULE_ID to report which product controls bind to each action.

Reporting use cases include auditing which control actions are active in a given edition and validating inbound integration payloads against the defined ACTION values.

Related Objects

The principal dependent object is PA_PM_PRODUCT_CONTROL_RULES, which references this table through the CONTROL_RULE_ID foreign key; joining the two exposes the mapping between product-level controls and their governing actions. The synonym APPS.PA_PM_CONTROL_ACTIONS provides application-layer access, and the base table is referenced by Oracle Projects integration and publication APIs that enforce the controls during import and export. Because the recipient objects documented are limited, other consumers such as concurrent programs and validation packages should be confirmed in a specific environment, but the FK relationship to PA_PM_PRODUCT_CONTROL_RULES is the most significant documented dependency.