Results for “action_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_PROJECT_STATUS_CONTROLS is a configuration table in the Oracle Projects (PA) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the set of allowed actions that may be performed against a project when that project is in a given system status. In effect, it is the business rule matrix that governs status-driven behavior: for each combination of a project status code and a project system status code, the table records which project actions (for example, initiating a change, closing, or copying) are permissible.

The table resides in the PA schema and is classified as VALID in the ETRM repository. Its primary key, PA_PROJECT_STATUS_CONTROLS_PK, is a composite over PROJECT_STATUS_CODE, PROJECT_SYSTEM_STATUS_CODE, and ACTION_CODE, meaning a single row represents one distinct action within one status/system-status pairing. From a Data Vault modeling perspective, the mined foreign key structure suggests this object is satellite-leaning — it extends the descriptive and behavioral attributes associated with the parent status definition rather than acting as an independent hub or as a pure associative link.

Key Information Stored

The table contains 16 documented columns. The most significant are:

• PROJECT_STATUS_CODE — the user-facing project status; a foreign key to PA_PROJECT_STATUSES.
• PROJECT_SYSTEM_STATUS_CODE — the internal system-level status that the user status maps to; part of the composite primary key.
• ACTION_CODE — the specific action being permitted or denied; completes the composite primary key.
• SORT_ORDER — controls the sequence in which these actions are presented or processed.
• ALLOW_OVERRIDES_FLAG — indicates whether the action may be overridden for this status combination.
• ENABLED_FLAG — enables or disables the control row without deleting it.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range during which the control is valid.
• STATUS_TYPE — categorizes the status/action control for filtering and reporting.
• COPY_TO_USER_STATUS_FLAG — determines whether the action is carried across when a user status is copied.
• Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture row-level change history; ZD_EDITION_NAME supports edition-based redefinition in 12.2.x.

The surrogate/natural composite key is the three-column primary key noted above. PROJECT_STATUS_CODE is the only documented foreign key column, referencing PA_PROJECT_STATUSES.

Common Use Cases and Queries

This table is primarily consumed by the Projects application logic to validate whether an action is allowed for a project's current status. Reporting and validation scenarios include:

• Identifying all enabled actions available for a given status: SELECT action_code FROM pa_project_status_controls WHERE project_status_code = :code AND enabled_flag = 'Y' ORDER BY sort_order;
• Auditing which controls permit overrides via ALLOW_OVERRIDES_FLAG.
• Checking currently effective controls using START_DATE_ACTIVE and END_DATE_ACTIVE against the current date.
• Bulk comparison of system status transitions for security or workflow analysis.
• Validating that a proposed status/action combination exists before attempting a project operation.

Related Objects

• PA_PROJECT_STATUSES — parent status definition; joined on PA_PROJECT_STATUS_CONTROLS.PROJECT_STATUS_CODE = PA_PROJECT_STATUSES.PROJECT_STATUS_CODE.
• PA_PROJECTS_ALL — project entities whose statuses are governed by these controls.
• PA_PROJECT_CLASSES — determines which statuses apply to a given project class.
• PA_PA_PROJECT_STATUS_CONTROLS — the implementation synonym referenced in ETRM DBA data.
• PA action-handling PL/SQL APIs that read these controls at runtime to enforce permitted project operations.

Together, these objects form the status-control framework that constrains and routes project lifecycle actions within Oracle Projects.