Search Results so_action_results_pk

Overview

The SO_ACTION_RESULTS table is a core data object within the Oracle E-Business Suite (EBS) Order Entry (OE) module, specifically for versions 12.1.1 and 12.2.2. It functions as a junction or mapping table that defines the permissible relationships between order cycle actions and their potential outcomes. In the context of Oracle Order Management, an order cycle represents a sequence of steps (actions) an order can go through, such as "Book" or "Ship." Each action can lead to one or more defined results, which in turn determine the next state or action in the cycle. This table is essential for enforcing and tracking the valid workflow paths an order can follow, ensuring process integrity and enabling complex order lifecycle management.

Key Information Stored

The table's structure is relatively simple, as its primary role is to link two key identifiers. The documented primary key is a composite of two columns, which together uniquely identify each valid action-result pairing. The ACTION_ID column stores the unique identifier for a specific order cycle action, as defined in the SO_ACTIONS table. The RESULT_ID column stores the unique identifier for a possible result of that action, as defined in the SO_RESULTS_B table. This two-column design allows a single action to be associated with multiple potential results, providing flexibility in defining order workflows.

Common Use Cases and Queries

The primary use case is to query the valid next steps or results for a given order action, which is fundamental for workflow determination and user interface logic. For instance, when a user attempts to perform an action on an order, the application will reference this table to present only the valid resulting statuses. A typical query would join SO_ACTION_RESULTS with SO_ACTIONS and SO_RESULTS_B to get the descriptive names for IDs. For reporting and analysis, developers might query this table to understand the configured workflow paths or to audit which results are available for critical actions like order cancellation or hold application.

SELECT a.action_name, r.result_name
FROM oe.so_action_results ar,
     oe.so_actions a,
     oe.so_results_b r
WHERE ar.action_id = a.action_id
  AND ar.result_id = r.result_id
  AND a.action_name = 'BOOK_ORDER';

Related Objects

As indicated by the foreign key metadata, SO_ACTION_RESULTS has direct, documented relationships with two key tables in the Order Entry schema. The table is a child of both SO_ACTIONS and SO_RESULTS_B. The ACTION_ID column is a foreign key referencing SO_ACTIONS.ACTION_ID, ensuring every entry points to a valid, defined action. Similarly, the RESULT_ID column is a foreign key referencing SO_RESULTS_B.RESULT_ID, ensuring every entry points to a valid, defined result. These relationships are critical for maintaining referential integrity in the order cycle configuration. The table itself is referenced by the primary key constraint SO_ACTION_RESULTS_PK.