Results for “pa_action_set_lines_ar”

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

Overview

PA_ACTION_SET_LINES_AR is a Projects (PA) module table in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores the individual lines that belong to an action set or an action set template. Action sets are reusable collections of ordered actions that Oracle Projects executes against project-related entities, and each row in this table represents one action line within such a set. The "_AR" suffix indicates that the object participates in Oracle's purge and archive infrastructure, evidenced by the PURGE_BATCH_ID, PURGE_RELEASE, and PURGE_PROJECT_ID columns that link each row to a purge batch recorded in PA_PURGE_BATCHES_ALL.

From a data-vault modeling perspective, the table is heuristically classified as standalone because no downstream dependents were mined from its foreign-key structure. This suggests treating it as a satellite-like entity: the ACTION_SET_ID foreign key points to a parent hub (PA_ACTION_SETS), while the line-level descriptive attributes and purge metadata behave as dependent context. The physical schema documents 26 columns in Release 12.2.2, owned by the PA schema.

Key Information Stored

The surrogate primary key of the table is ACTION_SET_LINE_ID, which uniquely identifies each action set line. The composite of ACTION_SET_ID and ACTION_SET_LINE_NUMBER functions as a business-key candidate, since a line number is unique within its parent action set. ACTION_SET_ID is the foreign key to PA_ACTION_SETS and determines the parent action set or template to which the line belongs.

• ACTION_CODE – identifies the action to be performed on the line.
• STATUS_CODE – current processing status of the action set line.
• DESCRIPTION – free-text description of the line.
• RECORD_VERSION_NUMBER – optimistic locking version for concurrent updates.
• LINE_DELETED_FLAG – soft-delete indicator, allowing lines to remain auditable.
• ACTION_ATTRIBUTE1 through ACTION_ATTRIBUTE10 – ten descriptive flexfield-style attributes holding action-specific parameters.
• PURGE_BATCH_ID, PURGE_RELEASE, PURGE_PROJECT_ID – purge/archive bookkeeping linking the row to PA_PURGE_BATCHES_ALL.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard WHO audit columns.

Common Use Cases and Queries

Typical reporting retrieves the ordered actions for a given action set. A representative query joins the lines to their parent set and excludes soft-deleted rows:

• SELECT l.ACTION_SET_LINE_NUMBER, l.ACTION_CODE, l.STATUS_CODE, l.DESCRIPTION FROM PA_ACTION_SET_LINES_AR l WHERE l.ACTION_SET_ID = :p_action_set_id AND NVL(l.LINE_DELETED_FLAG,'N') = 'N' ORDER BY l.ACTION_SET_LINE_NUMBER;
• Purge reconciliation: join to PA_PURGE_BATCHES_ALL on PURGE_BATCH_ID to audit which action set lines were archived in a given purge run.
• Status monitoring: aggregate counts by STATUS_CODE and ACTION_CODE to detect stalled or failed actions across sets.

Related Objects

• PA_ACTION_SETS – parent table; join on ACTION_SET_ID = PA_ACTION_SETS.ACTION_SET_ID.
• PA_PURGE_BATCHES_ALL – purge batch header; join on PURGE_BATCH_ID to trace archive batches.
• PA_ACTION_SET_LINES – the non-archive operational line table referenced by the description.
• PA_PURGE_ENTITIES_ALL / PA_PURGE_PROJECTS – related purge infrastructure for the PURGE_RELEASE and PURGE_PROJECT_ID columns.
• PA_ACTION_SET_LINE_ATTRS – attribute detail rows referencing ACTION_SET_LINE_ID where extended attributes are stored.

Because the table is documented as standalone, most dependency analysis centers on the two inbound foreign keys rather than on child tables.