Search Results oe_workflow_assignments_n1
Overview
ONT.OE_WORKFLOW_ASSIGNMENTS is a seed data table in the Oracle Order Management (ONT) schema that associates Oracle Workflow processes with Order Transaction Types and Line Transaction Types. It defines which workflow process is launched when an order or order line of a given type is processed, providing the linkage between the transactional configuration in Order Management and the workflow engine that drives order and line lifecycles.
Because each row binds an order type and a line type to a workflow process, the table occupies a central position in order orchestration and fulfillment configuration. It carries the standard seed tablespace assignment (APPS_TS_SEED) and includes standard WHO audit columns plus a reserved descriptive flexfield (DFF) block, indicating that customers may extend the assignment with attribute columns without altering the underlying structure.
From a Data Vault modeling perspective, the metadata's heuristic classification is link. This reflects the table's role as a junction between two transaction-type entities and a workflow process identifier, rather than a standalone descriptive hub.
Key Information Stored
The table stores 32 documented columns. The most operationally significant are:
- ASSIGNMENT_ID — Surrogate primary key (OE_WORKFLOW_ASSIGNMENTS_PK) and the column in unique index OE_WORKFLOW_ASSINGMENTS_U1. Despite the unique index, the name in the ETRM metadata contains a known misspelling ("ASSINGMENTS") that occasionally surfaces in user searches such as "oe_workflow_assingments_u1".
- ORDER_TYPE_ID — Foreign key to OE_TRANSACTION_TYPES_ALL; identifies the order transaction type this assignment applies to.
- LINE_TYPE_ID — Foreign key to OE_TRANSACTION_TYPES_ALL; identifies the line transaction type.
- PROCESS_NAME — Internal name of the assigned workflow process (VARCHAR2(30)).
- WF_ITEM_TYPE — Workflow item type that owns the process.
- ITEM_TYPE_CODE — Companion code linking the assignment to a workflow item type.
- START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating that controls when the assignment is active.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
- PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID — Concurrent program context for the last update.
- CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield segments reserved for customer-defined extensions.
The business-key candidates most useful for lookup are the combination of ORDER_TYPE_ID, LINE_TYPE_ID, ITEM_TYPE_CODE, and PROCESS_NAME; the surrogate key remains ASSIGNMENT_ID.
Common Use Cases and Queries
Typical uses include diagnosing which workflow process is wired to an order or line type, auditing assignment changes over time using the effective dates, and reporting the full matrix of order type / line type / process combinations.
A representative query joining the assignment to transaction types:
SELECT a.assignment_id, a.order_type_id, a.line_type_id, a.process_name, a.wf_item_type, a.start_date_active, a.end_date_active FROM ont.oe_workflow_assignments a WHERE a.order_type_id = :order_type_id;SELECT * FROM ont.oe_workflow_assignments WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);SELECT a.assignment_id, t.name order_type, l.name line_type, a.process_name FROM ont.oe_workflow_assignments a, ont.oe_transaction_types_all t, ont.oe_transaction_types_all l WHERE a.order_type_id = t.transaction_type_id AND a.line_type_id = l.transaction_type_id;
Because the table resides in APPS_TS_SEED, changes are typically performed through supported Order Management setup forms or via carefully controlled data fixes, not ad hoc DML.
Related Objects
- ONT.OE_TRANSACTION_TYPES_ALL — Referenced twice by OE_WORKFLOW_ASSIGNMENTS (ORDER_TYPE_ID and LINE_TYPE_ID). This is the primary setup table for order and line transaction types.
- OE_WORKFLOW_ASSIGNMENTS_PK — Primary key index on ASSIGNMENT_ID.
- OE_WORKFLOW_ASSINGMENTS_U1 — Unique index on ASSIGNMENT_ID (note the historical spelling).
- OE_WORKFLOW_ASSIGNMENTS_N1 — Nonunique index on ORDER_TYPE_ID.
- OE_WORKFLOW_ASSIGNMENTS_N2 — Nonunique index on LINE_TYPE_ID.
- Oracle Workflow (WF) item types — The workflow item type and process names referenced here are defined in the Workflow schema and drive order and line processing.
- Order Management setup forms and public APIs that maintain transaction types and their associated workflow processes.
-
INDEX: ONT.OE_WORKFLOW_ASSIGNMENTS_N1
12.1.1
owner:ONT, object_type:INDEX, object_name:OE_WORKFLOW_ASSIGNMENTS_N1, status:VALID,
-
INDEX: ONT.OE_WORKFLOW_ASSIGNMENTS_N1
12.2.2
owner:ONT, object_type:INDEX, object_name:OE_WORKFLOW_ASSIGNMENTS_N1, status:VALID,
-
TABLE: ONT.OE_WORKFLOW_ASSIGNMENTS
12.2.2
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_WORKFLOW_ASSIGNMENTS, object_name:OE_WORKFLOW_ASSIGNMENTS, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
TABLE: ONT.OE_WORKFLOW_ASSIGNMENTS
12.1.1
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_WORKFLOW_ASSIGNMENTS, object_name:OE_WORKFLOW_ASSIGNMENTS, status:VALID,
-
eTRM - ONT Tables and Views
12.2.2
description: OM WorkFlow Activity Skip Log. ,
-
eTRM - ONT Tables and Views
12.1.1
description: OM WorkFlow Activity Skip Log. ,