Results for “so_cycle_actions_pk”

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

Overview

SO_CYCLE_ACTIONS is an Order Entry (OE) configuration table in the Oracle E-Business Suite, owned by the OE schema and marked VALID in the ETRM data dictionary for releases 12.1.1 and 12.2.2. The table defines the association between order cycles and the actions that execute within them. In EBS Order Management, cycles (SO_CYCLES) represent reusable process flows that govern how order lines move from entry through booking, picking, shipping, and invoicing. SO_CYCLE_ACTIONS is the intersection table that records which specific actions (defined in SO_ACTIONS) are assigned to a given cycle, effectively assembling the ordered sequence of processing steps that constitutes the cycle definition. Each row represents one cycle-action assignment, and the table therefore acts as the authoritative mapping layer between two core configuration entities: cycles and actions.

From a dimensional modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. Because the table carries descriptive and audit attributes that vary with each cycle-action pairing rather than standing alone as a pure many-to-many key bridge, it is best treated as a satellite rather than a classical link table. This classification should be regarded as a modeling heuristic rather than a documented Oracle designation.

Key Information Stored

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

• CYCLE_ACTION_ID — the surrogate primary key, enforced by the index SO_CYCLE_ACTIONS_PK and also documented as a unique business-key candidate via SO_CYCLE_ACTIONS_U1. This column uniquely identifies each cycle-action assignment.
• CYCLE_ID — foreign key to SO_CYCLES, identifying the parent order cycle to which the action belongs.
• ACTION_ID — foreign key to SO_ACTIONS, identifying the action assigned to the cycle.
• CHANGE_CODE — a change indicator column, typically used to signal the nature of a modification to the cycle-action definition.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS "Who" audit columns recording initial creation and most recent update context.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program context columns recording which program and concurrent request performed the last update, essential for auditing configuration changes.

The surrogate key (CYCLE_ACTION_ID) should be distinguished from the composite business key formed by the parent references — CYCLE_ID and ACTION_ID together define the meaningful identity of the assignment, while CYCLE_ACTION_ID serves as the technical join anchor for dependent tables.

Common Use Cases and Queries

Administrators and developers query this table to enumerate the actions configured for a given cycle. A typical pattern joins to SO_ACTIONS to retrieve action names and joins to SO_CYCLES to confirm the parent cycle:

• Listing all actions in a cycle: SELECT sca.cycle_action_id, sa.action_id, sa.action_name FROM so_cycle_actions sca, so_actions sa WHERE sca.action_id = sa.action_id AND sca.cycle_id = :cycle_id;
• Confirming whether a specific action belongs to a cycle before runtime processing begins.
• Reporting on cycle configuration drift by examining PROGRAM_ID and LAST_UPDATE_DATE across environments.
• Auditing prerequisite setups through SO_ACTION_PRE_REQS, which references CYCLE_ACTION_ID, to verify ordering constraints between actions.

Related Objects

• SO_CYCLES — parent table; joined on SO_CYCLE_ACTIONS.CYCLE_ID = SO_CYCLES.CYCLE_ID.
• SO_ACTIONS — the action master; joined on SO_CYCLE_ACTIONS.ACTION_ID = SO_ACTIONS.ACTION_ID.
• SO_ACTION_PRE_REQS — prerequisite definitions; references SO_CYCLE_ACTIONS.CYCLE_ACTION_ID.
• OE_ACTION_PRE_REQS — Order Entry prerequisite table; also references CYCLE_ACTION_ID.
• SO_CYCLE_ACTIONS_PK / SO_CYCLE_ACTIONS_U1 — primary and unique indexes supporting fast lookup by CYCLE_ACTION_ID.