Search Results line_action




Overview
Explore in AI Chat

Overview

APPS.SO_CYCLE_ACTION_NAMES_V is a reporting and integration view in the Oracle E-Business Suite Order Management (OM) module. It exposes the relationship between order cycle actions and their corresponding action definitions, providing a denormalized, human-readable representation of the workflow steps that can be attached to order or line processing cycles. The view is defined over the SO_ACTIONS and SO_CYCLE_ACTIONS tables and joins them on ACTION_ID to resolve the descriptive action name, result column, result table, and approval flag for each cycle action assignment.

The view is particularly significant because it includes a derived column, LINE_ACTION, which is produced by a DECODE expression: DECODE(A.RESULT_TABLE, 'SO_LINES', '*', NULL). This means the view explicitly flags which cycle actions operate against order lines (as opposed to order headers or other entities). Users searching for "line_action" in the context of ETRM are typically looking to identify cycle steps that affect the SO_LINES table, and this view is the canonical source for that determination.

Underlying Base Objects

The view text defines the following query:

Both SO_ACTIONS and SO_CYCLE_ACTIONS are referenced as synonyms in the APPS schema. SO_ACTIONS holds the master definition of each order cycle action, including its name and the table/column it results in. SO_CYCLE_ACTIONS stores the association of a given action to a processing cycle, keyed by CYCLE_ACTION_ID and CYCLE_ID. Because the join is a simple inner join on ACTION_ID, every row in this view represents one action as it is attached to a cycle. Actions defined in SO_ACTIONS but not yet assigned to any cycle will not appear. The view is owned by APPS and is documented in ETRM 12.2.2 with identical semantics in 12.1.1.

Key Columns

  • CYCLE_ACTION_ID — Primary key from SO_CYCLE_ACTIONS identifying the specific action instance within a cycle.
  • CYCLE_ID — The processing cycle to which the action is attached.
  • ACTION_ID — The action definition identifier from SO_ACTIONS.
  • ACTION_NAME — The descriptive name of the action (A.NAME), the primary human-readable identifier.
  • RESULT_COLUMN — The column that the action writes or evaluates.
  • RESULT_TABLE — The table the action operates against; the value 'SO_LINES' drives the LINE_ACTION flag.
  • ACTION_APPROVAL — Indicates whether the action requires approval before execution.
  • LINE_ACTION — Derived flag; contains '*' when RESULT_TABLE equals 'SO_LINES', otherwise NULL. Used to isolate line-level actions.

Common Use Cases and Queries

The view is most often used to enumerate the actions belonging to a specific cycle, and to quickly distinguish line-level actions from header-level ones. A typical query filters on CYCLE_ID and the LINE_ACTION marker:

  • SELECT CYCLE_ACTION_ID, ACTION_NAME, RESULT_TABLE, LINE_ACTION FROM APPS.SO_CYCLE_ACTION_NAMES_V WHERE CYCLE_ID = :cycle_id;
  • SELECT ACTION_NAME, RESULT_COLUMN FROM APPS.SO_CYCLE_ACTION_NAMES_V WHERE LINE_ACTION = '*';

Integration and reporting teams use it to build cycle configuration reports, to troubleshoot why a particular line-level business rule (for example, a pricing or validation action writing to SO_LINES) did or did not fire, and to map cycle actions to their target tables during migration or audit. Because the view resolves the action name and result metadata in a single pass, it eliminates the need to join SO_ACTIONS and SO_CYCLE_ACTIONS manually in custom concurrent programs and reports.