Results for “date_required”

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

Overview

PA_CI_ACTIONS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that functions as the action log for control items managed within the Control Item framework. A control item represents a tracked project control activity, and every action taken against that control item — whether a request, submission, response, sign-off, or reassignment — is recorded as a discrete row in this table. Each record captures the complete requesting information and the corresponding response, producing a full auditable history of control item activity.

From a dimensional modeling perspective, the FK structure (references to PA_CONTROL_ITEMS, PA_PROJECT_STATUSES, HZ_PARTIES, and a self-reference) suggests a satellite-leaning classification. In a Data Vault model, this table would most naturally be treated as a satellite hanging off a control item hub, with the self-referencing SOURCE_CI_ACTION_ID indicating a possible link relationship when actions derive from prior actions.

Key Information Stored

The table contains 17 documented columns. The primary key is a system-generated surrogate, CI_ACTION_ID, enforced by PA_CI_ACTIONS_PK. Two unique indexes identify business-key candidates: PA_CI_ACTIONS_U1 (CI_ACTION_ID) and PA_CI_ACTIONS_U2 (CI_ID, CI_ACTION_NUMBER), meaning CI_ACTION_NUMBER combined with the parent control item provides a natural business identifier.

• CI_ACTION_ID — surrogate primary key and unique identifier for each action log entry.
• CI_ID — foreign key to PA_CONTROL_ITEMS, linking the action to its parent control item.
• CI_ACTION_NUMBER — sequence number of the action within the control item, forming the business key with CI_ID.
• STATUS_CODE — current status of the action, validated against PA_PROJECT_STATUSES.
• TYPE_CODE — classifies the nature of the action recorded.
• ASSIGNED_TO — party (HZ_PARTIES) responsible for the action.
• SIGN_OFF_REQUIRED_FLAG — indicates whether the action requires approval.
• SIGN_OFF_FLAG — records whether sign-off was granted.
• DATE_REQUIRED — due date for completing the action.
• DATE_CLOSED — date the action was closed.
• SOURCE_CI_ACTION_ID — self-referencing FK to the originating action, supporting derived or follow-on actions.
• RECORD_VERSION_NUMBER — optimistic locking/version control column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical reporting retrieves the action history for a given control item, tracks outstanding sign-offs, or reports overdue actions. A representative query joining to the parent control item follows:

• SELECT a.CI_ACTION_ID, a.CI_ACTION_NUMBER, a.STATUS_CODE, a.ASSIGNED_TO, a.DATE_REQUIRED, a.DATE_CLOSED FROM PA_CI_ACTIONS a WHERE a.CI_ID = :p_ci_id ORDER BY a.CI_ACTION_NUMBER;
• SELECT a.* FROM PA_CI_ACTIONS a WHERE a.SIGN_OFF_REQUIRED_FLAG = 'Y' AND a.SIGN_OFF_FLAG = 'N'; — outstanding approvals.
• SELECT a.* FROM PA_CI_ACTIONS a WHERE a.DATE_CLOSED IS NULL AND a.DATE_REQUIRED < SYSDATE; — overdue actions.
• Recursive traversal of SOURCE_CI_ACTION_ID to trace action lineage using a CONNECT BY clause.

Related Objects

• PA_CONTROL_ITEMS — parent object; joined via PA_CI_ACTIONS.CI_ID = PA_CONTROL_ITEMS.CI_ID.
• PA_PROJECT_STATUSES — status validation reference; joined via STATUS_CODE.
• HZ_PARTIES — assignee reference; joined via ASSIGNED_TO.
• PA_CI_COMMENTS — child table storing comments; joined via PA_CI_COMMENTS.CI_ACTION_ID = PA_CI_ACTIONS.CI_ACTION_ID.
• PA_CI_ACTIONS (self) — parent/derived action linkage via SOURCE_CI_ACTION_ID.

These relationships make PA_CI_ACTIONS the central transactional record within the Control Item subsystem, providing both the audit trail and the operational state for project controls.