Results for “sug_to_sub_code”

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

Overview

The WMS_OP_OPERATION_INSTANCES table resides in the WMS (Warehouse Management) schema of Oracle E-Business Suite and records discrete, executable warehouse operations generated from an operation plan. Each row represents a single operation instance—such as a putaway, replenishment, move, or picking task—assigned to a specific LPN, resource, or employee within an organization. The table is central to the warehouse execution layer, translating planned material handling activities into trackable, time-stamped work records.

The ETRM documentation notes that this object was "not intended for use in Release 11.5.9," indicating it is a feature of later releases and is fully present in the 12.1.1 and 12.2.2 code lines. The documented physical schema in 12.2.2 carries 45 columns mapped to owner WMS. From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is standalone, meaning the table is not mined as a dependent satellite around a separate hub; it functions as a self-contained transactional entity anchored by its own surrogate key.

Key Information Stored

The primary key is the surrogate OPERATION_INSTANCE_ID, enforced by constraint WMS_OP_OPERATION_INS_PK and mirrored by unique index WMS_OP_OPERATION_INS_U1. The following columns define the operational content of each row:

• OPERATION_INSTANCE_ID — surrogate primary key uniquely identifying the operation instance.
• OPERATION_TYPE and OPERATION_TYPE_ID — classification of the work (e.g., move, putaway, replenishment).
• OP_PLAN_INSTANCE_ID — the parent plan instance from which this task originated.
• OPERATION_PLAN_DETAIL_ID — foreign key to WMS_OP_PLAN_DETAILS, linking the task to its plan definition.
• OPERATION_STATUS — lifecycle state of the task (e.g., pending, active, complete).
• ORGANIZATION_ID — the warehouse organization carrying out the operation.
• LPN_ID — the license plate number of the handled material.
• FROM_ZONE_ID, FROM_SUBINVENTORY_CODE, FROM_LOCATOR_ID — source location of the move.
• TO_ZONE_ID, TO_SUBINVENTORY_CODE, TO_LOCATOR_ID — destination location of the move.
• EMPLOYEE_ID — foreign key to PSB_EMPLOYEES identifying the assigned resource.
• ACTIVATE_TIME and COMPLETE_TIME — timestamps marking task activation and completion.

Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the fifteen ATTRIBUTE flex columns support change tracking and customer extension.

Common Use Cases and Queries

Typical usage centers on warehouse task monitoring, labor performance reporting, and throughput analysis. A common pattern joins operation instances to plan details to trace task lineage:

• Listing open tasks for an organization: SELECT operation_instance_id, operation_status, lpn_id FROM wms_op_operation_instances WHERE organization_id = :org AND operation_status < 3;
• Tracing tasks back to their plan: join on operation_plan_detail_id = wms_op_plan_details.operation_plan_detail_id.
• Measuring completion performance using the delta between ACTIVATE_TIME and COMPLETE_TIME, grouped by EMPLOYEE_ID or OPERATION_TYPE.

Reports frequently aggregate LPN movement by source and destination zone, or reconcile in-flight tasks flagged by IS_IN_INVENTORY and suggested target columns (SUG_TO_SUB_CODE, SUG_TO_LOCATOR_ID).

Related Objects

The documented foreign keys and surrounding execution model tie this table to several key objects:

• WMS_OP_PLAN_DETAILS — joined via OPERATION_PLAN_DETAIL_ID; defines the planned operation.
• PSB_EMPLOYEES — joined via EMPLOYEE_ID; identifies the assigned worker.
• WMS_OP_OPERATION_INSTANCES (self) — related through OP_PLAN_INSTANCE_ID to group sibling tasks.
• Zone, locator, and subinventory reference tables implied by FROM_/TO_ columns and SUG_TO columns.
• LPN master data referenced by LPN_ID.
• Equipment and activity reference data via EQUIPMENT_ID and ACTIVITY_TYPE_ID.

These relationships make WMS_OP_OPERATION_INSTANCES the execution bridge between warehouse planning objects and physical inventory movement records.