Search Results oe_wf_line_assign_v




Overview
Explore in AI Chat

Overview

OE_WF_LINE_ASSIGN_V is an APPS-owned database view within the Oracle Order Management (ONT) module. Its documented purpose is to display workflow assignments for a line transaction type, and it is referenced directly by the Order Management user interface. In practice, the view exposes the mapping between a specific line transaction type and the workflow process that should be initiated for it, joining the workflow assignment records to the descriptive transaction type name so that the UI and downstream processes can present human-readable information rather than raw identifiers.

Because the object is a view rather than a table, it stores no data of its own. It is a read-only projection over two underlying objects and inherits the security and accessibility profile of the APPS schema. This makes it well suited to reporting, reconciliation, and integration scenarios where an external system or concurrent program must determine which workflow process is active for a given order line transaction type during a particular date range.

Underlying Base Objects

The ETRM metadata documents two referenced base objects. The first is OE_WORKFLOW_ASSIGNMENTS, exposed through a synonym, which holds the core assignment records including the order type, line type, process name, and the item type and attribute columns associated with the workflow configuration. The second is OE_TRANSACTION_TYPES_VL, a view that provides the translated, user-facing name of the transaction type.

The view joins these objects on the condition that WF.LINE_TYPE_ID equals VL.TRANSACTION_TYPE_ID, and it explicitly filters to rows where WF.LINE_TYPE_ID IS NOT NULL. Consequently, assignments that are defined without a specific line type are excluded from this view. This join and filter combination is what scopes the view to line-level workflow assignments as opposed to the broader set of assignments that may exist at other levels.

Key Columns

Common Use Cases and Queries

A frequent use case is identifying which workflow process is currently assigned to a given line transaction type, respecting the active date window. A sample query follows:

  • SELECT assignment_id, line_type_id, line_type, process_name FROM oe_wf_line_assign_v WHERE line_type_id = :p_line_type_id AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));

Another common scenario is auditing the complete set of configured assignments for reporting purposes, for example listing all active assignments with their process names ordered by transaction type. The view is also useful when troubleshooting why a particular workflow did not launch, since comparing the line type against the assignment records quickly reveals whether an active assignment exists and which process it points to. Given the presence of the ATTRIBUTE1 through ATTRIBUTE15 columns, the view additionally supports queries that inspect flexfield configuration for specific assignments.