Search Results so_actions_u2

Overview

APPS.SO_ORDER_STATUS_V is a reporting view in Oracle E-Business Suite (12.1.1 and 12.2.2) that consolidates the status history of Order Management documents into a single, denormalized result set. It presents one row per action performed against a sales order header or a sales order line, together with the resulting status value and the date on which that action occurred. Because Order Management stores statuses in a set of "S1" through "S30" result columns on SO_HEADERS and SO_LINES, the view translates those positional codes into human-readable action names, result names, and action levels by joining to the workflow action and lookup definitions. The view is owned by APPS and is intended for inquiry, reporting, and integration rather than for transactional updates.

Underlying Base Objects

The view is defined as a UNION of two branches. The first branch selects from SO_HEADERS (a view over the sales order headers) and the second from SO_LINES (a view over the sales order lines). Both branches join to SO_ACTIONS, SO_RESULTS, and SO_LOOKUPS, which are exposed in the APPS schema as synonyms. FND_GLOBAL is referenced in the documented dependency list for context and date handling.

• SO_ACTIONS provides the action definition, including ACTION_ID, NAME, RESULT_TABLE, and RESULT_COLUMN. The predicate A.RESULT_TABLE = 'SO_HEADERS' limits the header branch, and the SO_ACTIONS_U2 index is forced by hint.
• SO_RESULTS supplies the result name and RESULT_ID, joined by decoding A.RESULT_COLUMN to the corresponding S1–S30 column on the header or line. The SO_RESULTS_U1 index is forced.
• SO_LOOKUPS, filtered on LOOKUP_TYPE = 'SO_ACTION_LEVEL' and LOOKUP_CODE = 'SO_HEADERS', yields the ACTION_LEVEL meaning.
• SO_HEADERS and SO_LINES supply the S1–S30 status columns and the S1_DATE–S30_DATE timestamps. The SO_HEADERS_U1 and SO_LINES_U1 indexes are forced.

Key Columns

• ORDER_SOURCE_ID — H.HEADER_ID in the header branch and L.LINE_ID in the line branch, identifying the source document.
• ACTION_ID / ACTION — the numeric action identifier and its NAME from SO_ACTIONS.
• RESULT / RESULT_ID — the resulting status name and identifier from SO_RESULTS.
• ACTION_LEVEL — the meaning of the action level lookup (for example, header-level actions).
• ACTION_CODE — a literal 'ORDER' for headers or 'LINE' for lines, distinguishing the originating entity.
• ACTION_DATE — derived by DECODE over A.RESULT_COLUMN, mapping to the matching S1_DATE through S30_DATE column on the header or line.
• DUMMY_ID — a constant 0 placeholder column retained for consumer compatibility.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, ROW_ID — standard audit columns and the ROWID of the underlying header or line record.

Common Use Cases and Queries

The view is typically used to report order and line status progression, to audit when a given status was reached, and to feed downstream integration or analytics. A header-only listing can be produced as follows:

• SELECT ORDER_SOURCE_ID, ACTION, RESULT, ACTION_DATE FROM APPS.SO_ORDER_STATUS_V WHERE ACTION_CODE = 'ORDER' ORDER BY ORDER_SOURCE_ID, ACTION_DATE;
• SELECT ORDER_SOURCE_ID, ACTION, RESULT FROM APPS.SO_ORDER_STATUS_V WHERE RESULT = :status AND ACTION_CODE = 'LINE';
• SELECT ACTION, COUNT(*) FROM APPS.SO_ORDER_STATUS_V GROUP BY ACTION;

Because the view is read-only and joins several Order Management objects, queries should filter on ACTION_CODE, ORDER_SOURCE_ID, or RESULT to limit the union branches and leverage the forced index hints. In 12.2.2 the documented base objects and structure are unchanged from 12.1.1, so the same SQL remains portable across both releases.