Search Results oe_workflow_assignments_pk

Overview

OE_WORKFLOW_ASSIGNMENTS is an Oracle E-Business Suite Order Management (ONT) configuration table that associates workflow process definitions with order types and line types. It is the mechanism by which the Order Management application determines which Oracle Workflow process to execute when an order or order line is entered, booked, or otherwise transitioned through its lifecycle. By binding a PROCESS_NAME and WF_ITEM_TYPE to a specific combination of ORDER_TYPE_ID and LINE_TYPE_ID, the table supplies the routing logic that drives order and line flow orchestration.

In Data Vault terms, the documented foreign key structure supports classifying OE_WORKFLOW_ASSIGNMENTS as a link entity. The heuristic derives this from the fact that the table resolves relationships between order transaction types and workflow definitions rather than storing a single business entity with descriptive attributes. This classification should be treated as a modeling suggestion rather than an authoritative designation.

Key Information Stored

• ASSIGNMENT_ID — Surrogate primary key defined by OE_WORKFLOW_ASSIGNMENTS_PK. A separate unique index, OE_WORKFLOW_ASSINGMENTS_U1, also exists on this column.
• ORDER_TYPE_ID — Foreign key to OE_TRANSACTION_TYPES_ALL; identifies the order type to which the workflow assignment applies.
• LINE_TYPE_ID — Foreign key to OE_TRANSACTION_TYPES_ALL; identifies the line type scoped by the assignment.
• PROCESS_NAME — The internal name of the Oracle Workflow process invoked for the assignment.
• WF_ITEM_TYPE — The workflow item type associated with the process definition.
• ITEM_TYPE_CODE — Item type code used to resolve the workflow definition at runtime.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Date-range columns that control the effective period during which the assignment is active.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns maintained by the application.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID — Concurrent program context identifying the process that created or last updated the row.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segments reserved for customer-specific extensions.

The table contains 32 documented columns in the 12.2.2 schema, with the columns above representing the operationally significant subset.

Common Use Cases and Queries

The most frequent requirement is determining which workflow process drives a given order type and line type, typically during order entry troubleshooting or workflow customization. A representative query joins the assignments to the transaction types table:

• SELECT a.assignment_id, a.process_name, a.wf_item_type, t.name order_type FROM oe_workflow_assignments a, oe_transaction_types_all t WHERE a.order_type_id = t.transaction_type_id AND a.line_type_id = :line_type_id;
• Reporting queries often filter on START_DATE_ACTIVE and END_DATE_ACTIVE to return only currently effective assignments.
• Audit and migration scripts compare the PROCESS_NAME and WF_ITEM_TYPE values across environments to verify that workflow customizations were transported consistently.
• Data warehouse extractions use the LAST_UPDATE_DATE column to identify incrementally changed configuration rows.

Related Objects

• OE_TRANSACTION_TYPES_ALL — Referenced twice, via ORDER_TYPE_ID and LINE_TYPE_ID, supplying the order and line type definitions.
• OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — Transaction tables whose workflow routing resolves through the order and line types configured here.
• WF_ITEM_TYPES and the Oracle Workflow engine tables — Resolve the process and item type named on each assignment row.
• OE_WORKFLOW_ASSIGNMENTS_PK and OE_WORKFLOW_ASSINGMENTS_U1 — Primary key constraint and unique index enforcing the assignment identifier.
• Order Management concurrent programs and the Order Management setup forms that insert and maintain assignment records.