Results for “oebv_sales_order_cycle_actions”

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

Overview

The view OEBV_SALES_ORDER_CYCLE_ACTIONS is an Order Entry (OE) reporting object that exposes the relationship between sales order cycle actions and the cycles to which they belong. In Oracle EBS 12.1.1 and 12.2.2, the "OEBV" prefix denotes a seeded, read-only Order Entry view typically delivered for backward compatibility, reporting, or integration exposure of underlying OE configuration data. The metadata classifies this object as "Retrofitted," meaning it was reintroduced or remapped to preserve compatibility across releases rather than newly authored. The view surfaces the operational link between a cycle action identifier and its parent cycle identifier, together with the standard Oracle EBS who-columns (creation and update audit fields).

Underlying Base Objects

Per the documented ETRM metadata, this view is defined directly over a single source object: SO_CYCLE_ACTIONS, aliased in the view text as CACTION. The view is constructed as a restricted projection with the WITH READ ONLY clause, ensuring no DML is permitted through it. No additional base objects are documented; the view does not join to header, line, or other order-entry tables, and therefore presents a flattened projection of the underlying configuration table. The ETRM metadata records the object as "Not implemented in this database," which indicates the extract was captured from a reference environment where the view was not physically created. The documented owner is blank and no referenced base objects are enumerated beyond the SO_CYCLE_ACTIONS source identified in the view text.

Key Columns

• CYCLE_ACTION_ID — Primary surrogate key identifying each cycle-action assignment. This is the column a user searching for "cycle_action_id" is most likely seeking.
• ACTION_ID — Foreign reference to the discrete action executed at a given step of the order cycle.
• CYCLE_ID — Foreign reference to the parent sales order cycle definition.
• LAST_UPDATE_DATE — Timestamp of the most recent modification to the row.
• LAST_UPDATED_BY — User ID of the last modifier.
• CREATION_DATE — Timestamp when the row was first created.
• CREATED_BY — User ID of the original creator.

Common Use Cases and Queries

Typical usage involves resolving the action set associated with a cycle, or tracing a known cycle_action_id back to its cycle and action. Because the view is read-only and unjoined, it is best suited for lightweight lookups and configuration audits.

Retrieve all actions for a given cycle:

SELECT cycle_action_id, action_id, cycle_id
FROM   oebv_sales_order_cycle_actions
WHERE  cycle_id = :p_cycle_id;

Resolve a specific cycle_action_id:

SELECT cycle_action_id, action_id, cycle_id,
       creation_date, created_by
FROM   oebv_sales_order_cycle_actions
WHERE  cycle_action_id = :p_cycle_action_id;

Audit recent configuration changes:

SELECT cycle_action_id, cycle_id, action_id,
       last_update_date, last_updated_by
FROM   oebv_sales_order_cycle_actions
WHERE  last_update_date >= :p_since_date
ORDER  BY last_update_date DESC;

Because the view is a direct projection of SO_CYCLE_ACTIONS, queries against it can generally be redirected to the base table when additional columns or joins are required.