Results for “oefv_sales_order_cycle_actions”

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

Overview

OEFV_SALES_ORDER_CYCLE_ACTIONS is a read-only database view registered under the Oracle Order Entry (OE) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view exposes the relationship between sales order cycles and the order actions assigned to them, presenting the descriptive names of both the cycle and the action alongside the surrogate primary keys that link them. In ETRM metadata the object is annotated as "Retrofitted," indicating it was introduced or carried forward as part of the EBS compatibility layer rather than as a native ETRM entity. The implementation note "Not implemented in this database" further indicates that the view is documented for reference purposes and may not be physically present in every environment unless the corresponding OE schema objects have been deployed.

Functionally, the view serves as a denormalized join surface for reporting and integration. Rather than requiring report authors or interfaces to resolve the numeric ACTION_ID and CYCLE_ID values against SO_ACTIONS and SO_CYCLES separately, the view returns human-readable ACTION_NAME and CYCLE_NAME values in the same row as the identifiers, along with standard audit columns. This design makes it suitable for ad hoc querying, concurrent program data sources, and outbound interface extracts where descriptive labels are required.

Underlying Base Objects

The view text documents three base tables joined within the OE schema:

• SO_CYCLE_ACTIONS (alias CYACTION) — the transactional intersection table that stores each cycle-to-action assignment, providing CYCLE_ACTION_ID as the primary key plus ACTION_ID and CYCLE_ID foreign keys.
• SO_ACTIONS (alias ACTION) — the action definition table, contributing ACTION.NAME, which the view exposes as ACTION_NAME.
• SO_CYCLES (alias CYCLE) — the sales order cycle definition table, contributing CYCLE.NAME, exposed as CYCLE_NAME.

The join conditions are CYACTION.ACTION_ID = ACTION.ACTION_ID and CYACTION.CYCLE_ID = CYCLE.CYCLE_ID. Because these are inner joins, a row appears only when both the referenced action and the referenced cycle exist. The view carries a WITH READ ONLY clause, so no DML can be issued against it; all maintenance must be performed on SO_CYCLE_ACTIONS.

Key Columns

• ACTION_NAME — the descriptive name of the order action, sourced from SO_ACTIONS.NAME. This is the column most commonly referenced when users search by action terminology.
• CYCLE_NAME — the descriptive name of the sales order cycle, sourced from SO_CYCLES.NAME. This is the column returned when a user searches for "cycle_name" against this view.
• CYCLE_ACTION_ID — the unique identifier of the cycle-action assignment row in SO_CYCLE_ACTIONS.
• ACTION_ID — the foreign key to the action definition in SO_ACTIONS.
• CYCLE_ID — the foreign key to the cycle definition in SO_CYCLES.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS audit columns reflecting the most recent change and original insert of the underlying SO_CYCLE_ACTIONS row.

Common Use Cases and Queries

The view is typically used to enumerate the actions configured for each sales order cycle, to resolve CYCLE_NAME from a known CYCLE_ID, or to drive validation and reconciliation reports for order management setup. A representative query retrieving all cycles and their assigned actions is:

SELECT cycle_name, action_name, cycle_action_id, cycle_id, action_id FROM oefv_sales_order_cycle_actions ORDER BY cycle_name, action_name;

To locate a specific cycle by name, the following filter applies:

SELECT cycle_name, action_name FROM oefv_sales_order_cycle_actions WHERE cycle_name = :cycle_name;

Because the view is READ ONLY, any corrective maintenance identified through these queries must be applied directly to SO_CYCLE_ACTIONS using the appropriate Order Management setup responsibility. Where the object is reported as "Not implemented in this database," queries will fail with an ORA-00942 error until the OE schema is fully installed, and administrators should confirm object status in ALL_VIEWS before relying on it in reports or interfaces.