Results for “so_action_pre_reqs”

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

Overview

The SO_ACTION_PRE_REQS table is an Order Entry (OE) module data object owned by the OE schema in Oracle EBS 12.1.1 and 12.2.2. Its documented purpose is to store cycle action prerequisites — the conditions that must be satisfied before a given cycle action (a processing step within an order cycle) can be executed by the order management workflow engine. In practical terms, the table defines the dependency graph between actions: for a target cycle action, it lists the preceding actions and their qualifying result values that must have already occurred. Without these prerequisite records, Oracle Order Management would have no basis for sequencing action processing, evaluating whether a cycle can progress, or triggering downstream actions when prior steps complete successfully.

From a Data Vault modeling perspective, the mined FK structure classifies SO_ACTION_PRE_REQS as a link table. It does not own descriptive business attributes of its own; instead it connects three independent entities (cycle actions, results, and actions) and records the associative relationship plus a grouping identifier. This heuristic classification is a modeling suggestion rather than a documented Oracle position.

Key Information Stored

The table comprises nine documented columns. The most significant are the three foreign key columns that form the semantic core of each row:

• CYCLE_ACTION_ID — Foreign key to SO_CYCLE_ACTIONS. Identifies the cycle action whose prerequisites are being defined; this is the dependent (target) side of the rule.
• ACTION_ID — Foreign key to SO_ACTIONS. Identifies the prerequisite action that must precede the target cycle action.
• RESULT_ID — Foreign key to SO_RESULTS_B. Specifies the qualifying result or outcome of the prerequisite action required for the rule to be satisfied.
• GROUP_NUMBER — Groups related prerequisite rows, allowing multiple prerequisite conditions to be associated as a logical set.

The remaining columns are standard Oracle EBS audit and concurrency attributes: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. No dedicated surrogate primary key column (such as a sequence-generated ID) is documented in the ETRM metadata; the effective uniqueness of a row is derived from the combination of the foreign key columns and GROUP_NUMBER. Business-key candidates therefore center on CYCLE_ACTION_ID together with ACTION_ID, RESULT_ID, and GROUP_NUMBER.

Common Use Cases and Queries

Typical use cases include diagnosing why an order cycle action did not fire, auditing prerequisite configurations during implementation or upgrade, and migrating seeded versus custom cycle action rules between environments.

A representative query listing prerequisites for a cycle action:

• SELECT p.CYCLE_ACTION_ID, p.ACTION_ID, p.RESULT_ID, p.GROUP_NUMBER FROM OE.SO_ACTION_PRE_REQS p WHERE p.CYCLE_ACTION_ID = :cycle_action_id ORDER BY p.GROUP_NUMBER;

A joined query resolving prerequisite details against the referenced tables:

• SELECT a.ACTION_ID, a.ACTION_NAME, r.RESULT_NAME FROM OE.SO_ACTION_PRE_REQS p, OE.SO_ACTIONS a, OE.SO_RESULTS_B r WHERE p.ACTION_ID = a.ACTION_ID AND p.RESULT_ID = r.RESULT_ID AND p.CYCLE_ACTION_ID = :cycle_action_id;

Because the FK structure forms a dependency graph, recursive reporting — tracing multi-level chains of prerequisites — is a common analytical pattern, often implemented with hierarchical CONNECT BY queries over CYCLE_ACTION_ID and ACTION_ID.

Related Objects

The following objects are most significant in relation to SO_ACTION_PRE_REQS, based on the documented foreign keys:

• SO_CYCLE_ACTIONS — joined on CYCLE_ACTION_ID; defines the target cycle action.
• SO_ACTIONS — joined on ACTION_ID; defines the prerequisite action.
• SO_RESULTS_B — joined on RESULT_ID; defines the acceptable result.
• SO_CYCLES and other OE cycle definition tables — contextual parents of cycle actions that indirectly constrain these prerequisite rules.
• Order Management workflow / processing APIs that evaluate cycle action sequencing and consult this table at runtime.

Because prerequisite records gate action execution, incorrect or missing rows in this table frequently surface as stalled order cycles, making it a routine target during Order Management troubleshooting.