Search Results oebv_actions

Overview

OEBV_ACTIONS is a reporting view in the Oracle E-Business Suite Order Entry (OE) module whose definition is documented in the ETRM repository for releases 12.1.1 and 12.2.2. The object is explicitly flagged as "Retrofitted" in the ETRM metadata, indicating that it is a legacy Order Entry object carried forward across release boundaries rather than a newly introduced database object. The same metadata records the object as "Not implemented in this database," meaning the view may not exist in every environment; DBAs should verify its presence in ALL_VIEWS before relying on it.

Functionally, OEBV_ACTIONS presents Oracle Order Management action definitions in a denormalized, human-readable form. Action definitions identify the processing steps that can be taken against an order or order line (for example, booking, scheduling, shipping, or invoicing). The view joins the base action table to two lookup tables in order to translate opaque lookup codes into descriptive meanings, making the object suitable for reporting, ad-hoc queries, and integration extracts that require descriptive action metadata.

Underlying Base Objects

The view text recorded in the ETRM metadata defines the object over three base tables:

• SO_ACTIONS — the primary table of order management action definitions, aliased ACTION.
• SO_LOOKUPS — the Order Entry lookup table, aliased LOOKUP, used to resolve the RESULT_TABLE column against lookup type SO_ACTION_LEVEL.
• FND_LOOKUPS — the Oracle Application Object Library lookup table, aliased LOOKUP2, used to resolve ACTION_APPROVAL against lookup type YES_NO.

Both lookups are applied as inner joins in the WHERE clause rather than as ANSI join syntax, so an action row is returned only when matching lookup codes exist for both the action level and the approval flag. The view is declared WITH READ ONLY, preventing DML through the view and underscoring its purpose as a query-only reporting object.

Key Columns

• NAME — the action name from SO_ACTIONS, identifying the action definition.
• ACTION_LEVEL — the meaning of the RESULT_TABLE lookup code, derived from SO_LOOKUPS where LOOKUP_TYPE = 'SO_ACTION_LEVEL'.
• APPROVAL_ACTION — the Yes/No meaning of the ACTION_APPROVAL flag, derived from FND_LOOKUPS.
• DESCRIPTION — the descriptive text of the action.
• "_DF" — a constant literal, '_DF:OE:SO_ACTIONS:ACTION', retained from the original Oracle Forms-based descriptive flexfield convention and of little value in SQL-only reporting.
• ACTION_ID — the primary key of the underlying SO_ACTIONS row.
• PASSING_RESULT_ID — the identifier passed as the result of the action; this column is the direct match for the search term "passing_result_id" and links the action to the result it propagates in the order processing flow.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard Oracle audit columns describing when and by whom the action definition was created and last modified.

Common Use Cases and Queries

The view is typically used to report on configured order management actions and their approval characteristics, or to resolve a PASSING_RESULT_ID to a descriptive action for troubleshooting order flow behavior.

List all configured actions with their level and approval flag:

SELECT name, action_level, approval_action, description
FROM   oebv_actions
ORDER BY name;

Locate the action associated with a specific passing result:

SELECT action_id, name, action_level, passing_result_id
FROM   oebv_actions
WHERE  passing_result_id = :result_id;

Identify approval-required actions:

SELECT name, description
FROM   oebv_actions
WHERE  approval_action = 'Yes';

Because the view is read-only and joins two lookup tables, queries perform best when filtered on indexed columns such as ACTION_ID or PASSING_RESULT_ID. Where the object is not implemented, equivalent results can be obtained by joining SO_ACTIONS to SO_LOOKUPS and FND_LOOKUPS directly, replicating the documented view text.