Results for “pa_action_sets_ar”

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

Overview

PA_ACTION_SETS_AR is the audit/archive companion table to PA_ACTION_SETS in the Oracle Projects (PA) module. As its description states, PA_ACTION_SETS stores action set templates as well as action sets belonging to an object, such as projects, requirements, and similar entities; the _AR suffix designates the archived or purge-related counterpart used during data archiving and purge operations. In Oracle EBS 12.1.1 and 12.2.2, action sets define ordered collections of actions (for example, workflow or process steps) that are applied to project-related objects, and this table preserves that configuration history, including inactive, template, and object-specific instances.

From a heuristic Data Vault modeling perspective mined from the foreign key structure, the table is classified as standalone. This suggests it can be modeled as an independent satellite or reference structure rather than as a strict hub or link, since its relationships to parent tables are via nullable descriptive foreign keys rather than a clearly conformed business key. The two documented foreign keys reference PA_PURGE_BATCHES_ALL (via PURGE_BATCH_ID) and PA_ACTION_SETS (via ACTION_SET_ID), indicating the archive context and the source action set lineage.

Key Information Stored

The documented physical schema under ETRM 12.2.2 contains 38 columns owned by the PA schema. The most significant columns are:

• ACTION_SET_ID — foreign key to PA_ACTION_SETS; the primary linkage to the source action set record.
• ACTION_SET_NAME — the descriptive business name of the action set, a strong business-key candidate used in reporting and lookups.
• ACTION_SET_TYPE_CODE — classifies the action set (for example template versus object-specific).
• OBJECT_TYPE / OBJECT_ID — identify the owning entity (project, requirement, etc.) to which the set belongs.
• STATUS_CODE — lifecycle status of the action set.
• ACTION_SET_TEMPLATE_FLAG — distinguishes reusable templates from instance action sets.
• SOURCE_ACTION_SET_ID / MOD_SOURCE_ACTION_SET_FLAG — capture lineage when an action set was copied or modified from a source.
• START_DATE_ACTIVE / END_DATE_ACTIVE / ACTUAL_START_DATE — effective-dating for the set.
• RECORD_VERSION_NUMBER — optimistic locking version control.
• PURGE_BATCH_ID, PURGE_RELEASE, PURGE_PROJECT_ID — archive/purge attributes identifying the purge run that placed the row here.
• DESCRIPTION — free-text explanation of the set.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the flexible descriptive flexfield (DFF) segment columns.

While ACTION_SET_ID serves as the surrogate key linking to the parent, ACTION_SET_NAME combined with OBJECT_TYPE and OBJECT_ID is the practical business-key candidate for identification. The absence of a documented unique index in the provided metadata means uniqueness is enforced logically rather than physically in this archive table.

Common Use Cases and Queries

Typical uses include audit reporting, purge reconciliation, and action-set configuration analysis. A common query retrieves all archived action sets for a given purge batch:

• SELECT action_set_id, action_set_name, object_type, object_id, status_code FROM pa_action_sets_ar WHERE purge_batch_id = :batch_id;
• Reconcile archived versus live records by joining ACTION_SET_ID back to PA_ACTION_SETS to detect orphanced or fully purged entries.
• Report template versus instance sets using ACTION_SET_TEMPLATE_FLAG and ACTION_SET_TYPE_CODE.
• Analyze source lineage via SOURCE_ACTION_SET_ID to trace how action sets were cloned or modified.

Because this is the archive companion, queries are usually restricted to purge-run context and are frequently executed by DBAs and auditors rather than end users.

Related Objects

• PA_ACTION_SETS — the primary parent, joined on ACTION_SET_ID.
• PA_PURGE_BATCHES_ALL — purge batch header, joined on PURGE_BATCH_ID.
• PA_PROJECTS_ALL — project context via OBJECT_ID where OBJECT_TYPE indicates a project.
• PA_ACTION_SET_ACTIONS / action set steps — define the ordered actions within each set.
• PA_PURGE_PROJECTS — related purge project entities referenced by PURGE_PROJECT_ID.
• FND_FLEX_VALUES / DFF views — resolve ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 segments.
• PA_ACTION_SETS_V / archive views — reporting-layer views exposing archived action sets.
• PA purge/archive concurrent programs — populate this table during purge execution.