Results for “so_actions”

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

Overview

The SO_ACTIONS table, owned by the OE (Order Entry) schema, is a core configuration object within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores the definitions of cycle actions that drive the Order Management order cycle workflow. Order cycles sequence order and line processing steps — booking, scheduling, picking, shipping, invoicing, and closing — and each discrete processing step available to a cycle is defined once in SO_ACTIONS and then attached to specific cycles through the SO_CYCLE_ACTIONS intersection table.

Physically the table contains 30 columns, most of which are standard Oracle EBS WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus 15 descriptive flexfield (DFA) attribute columns. Two unique indexes are documented: SO_ACTIONS_PK on ACTION_ID and SO_ACTIONS_U1 (a unique constraint on ACTION_ID), while SO_ACTIONS_U2 on (RESULT_COLUMN, RESULT_TABLE) acts as the primary business-key candidate, enforcing that the result target of an action is unique. Under a heuristic Data Vault classification, SO_ACTIONS behaves as a hub: its stable surrogate action identifier is referenced by eight downstream tables, which function as links and satellites carrying clauses, prerequisites, results, and approvals.

Key Information Stored

• ACTION_ID — Surrogate primary key (SO_ACTIONS_PK). Referenced by every dependent child table and is the value used in joins throughout the order cycle engine.
• NAME — The user-facing name of the cycle action as presented in the Order Management setup windows.
• RESULT_COLUMN and RESULT_TABLE — Together they form the business-key candidate (SO_ACTIONS_U2). They identify the database column and table populated when the action executes, defining the action's processing result.
• ACTION_APPROVAL — Flag indicating whether the action requires approval before processing proceeds.
• PASSING_RESULT_ID — Foreign key to SO_RESULTS_B; links the action to the passing result record it generates or consumes.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Effective dating that controls when the action may be included in an active cycle.
• DESCRIPTION — Free-form explanation of what the action does.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield segments reserved for customer-specific extension.

Common Use Cases and Queries

Typical uses include auditing which actions exist in the system, rebuilding cycle configuration, and tracing why an order stalled at a particular step. A basic query lists actions with their active window:

• SELECT action_id, name, result_table, result_column, action_approval, start_date_active, end_date_active FROM oe.so_actions WHERE sysdate BETWEEN nvl(start_date_active, sysdate) AND nvl(end_date_active, sysdate+1);
• To relate an action to the cycles that use it: SELECT a.action_id, a.name, ca.cycle_id FROM oe.so_actions a, oe.so_cycle_actions ca WHERE a.action_id = ca.action_id;
• To inspect prerequisites and clauses for diagnosis: join SO_ACTION_PRE_REQS and SO_ACTION_CLAUSES on ACTION_ID.
• To identify approval-driven actions: filter on ACTION_APPROVAL and join SO_LINE_APPROVALS or SO_ORDER_APPROVALS on ACTION_ID.

These patterns support setup verification, order hold analysis, and approval workflow reporting.

Related Objects

• SO_CYCLE_ACTIONS — Intersection linking actions to order cycles (SO_CYCLE_ACTIONS.ACTION_ID → SO_ACTIONS.ACTION_ID).
• SO_ACTION_CLAUSES — Stores conditional clauses evaluated before an action runs (ACTION_ID foreign key).
• SO_ACTION_PRE_REQS — Defines prerequisite actions that must complete first (ACTION_ID).
• SO_ACTION_RESULTS — Records the outcomes produced by an action (ACTION_ID).
• SO_RESULTS_B — Parent of PASSING_RESULT_ID, holding result definitions consumed by actions.
• SO_HOLDS — Associates hold definitions with the actions that apply them (ACTION_ID).
• SO_LINE_APPROVALS and SO_ORDER_APPROVALS — Approval records tied to line-level and order-level actions (ACTION_ID).
• SO_SECURITY_RULES — Security constraints attached to specific actions (ACTION_ID).

Collectively these tables form the order cycle execution framework that SO_ACTIONS anchors.