Results for “to_zone_id”

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

Overview

WMS_OP_OPERTN_INSTANCES_HIST is a Warehouse Management (WMS) history table in the Oracle E-Business Suite WMS schema. It stores historical execution records of operation instances generated by the Warehouse Management operation planning and task execution engine. Where its companion transactional table captures active operation instances in flight, this history table retains the completed, cancelled, or archived instances used for audit, performance analysis, and reconciliation of warehouse labor and material movement activity.

The ETRM metadata classifies this object, heuristically, as standalone under Data Vault modeling conventions. In practice this suggests the table behaves largely as a self-contained record set rather than a strict hub, link, or satellite; it can be treated as a satellite-like history of the operation instance business key (OPERATION_INSTANCE_ID), containing descriptive attributes and contextual references, without the multi-hub integration typical of a formal Data Vault link.

Note that the ETRM documentation states this table is "Not intended for use in Release 11.5.9," indicating it is relevant to later EBS releases such as 12.1.1 and 12.2.2.

Key Information Stored

The table contains 45 documented columns. The most operationally significant are:

• OPERATION_INSTANCE_ID — surrogate primary key (WMS_OP_OPERTN_INS_HIST_PK) and the unique business-key candidate (WMS_OP_OPERTN_INS_HIST_U1).
• OPERATION_TYPE / OPERATION_TYPE_ID — classification of the warehouse operation performed.
• OPERATION_STATUS — lifecycle state of the instance (e.g., completed, cancelled).
• OP_PLAN_INSTANCE_ID — the operation plan instance that generated this operation.
• OPERATION_PLAN_DETAIL_ID — foreign key to WMS_OP_PLAN_DETAILS, the plan detail driving the operation.
• OPERATION_SEQUENCE — ordering of the operation within the plan.
• ORGANIZATION_ID — inventory organization context.
• LPN_ID — license plate number of the handling unit involved.
• FROM_ZONE_ID / FROM_SUBINVENTORY_CODE / FROM_LOCATOR_ID — source zone, subinventory, and locator.
• TO_ZONE_ID / TO_SUBINVENTORY_CODE / TO_LOCATOR_ID — destination zone, subinventory, and locator.
• SUG_TO_SUB_CODE / SUG_TO_LOCATOR_ID — system-suggested destination subinventory and locator.
• EMPLOYEE_ID — operator, foreign key to PSB_EMPLOYEES.
• EQUIPMENT_ID — material handling equipment used.
• ACTIVATE_TIME / COMPLETE_TIME — timestamps for activation and completion.
• IS_IN_INVENTORY — inventory status flag.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 for extension data.

Common Use Cases and Queries

Typical uses include warehouse labor productivity reporting, operation throughput analysis between ACTIVATE_TIME and COMPLETE_TIME, audit trails for LPN movement, and reconciliation of historical operations against inventory balances.

Sample query — count completed operations per organization within a date range:

SELECT organization_id,
       COUNT(*) AS op_count
FROM   wms.wms_op_opertn_instances_hist
WHERE  operation_status = 'COMPLETED'
AND    complete_time BETWEEN :start_date AND :end_date
GROUP BY organization_id;

A join-driven variant links employees to their completed work, using the documented FK to PSB_EMPLOYEES:

SELECT h.operation_instance_id,
       h.operation_type,
       e.full_name,
       h.complete_time
FROM   wms.wms_op_opertn_instances_hist h,
       psb.psb_employees e
WHERE  h.employee_id = e.employee_id
AND    h.complete_time >= :start_date;

Planners may correlate history with plan details to evaluate plan effectiveness using OPERATION_PLAN_DETAIL_ID.

Related Objects

The most significant related objects, based on the documented relationships, are:

• WMS_OP_PLAN_DETAILS — joined via OPERATION_PLAN_DETAIL_ID; the plan detail governing each operation instance.
• PSB_EMPLOYEES — joined via EMPLOYEE_ID; identifies the operator performing the operation.
• WMS_OP_OPERTN_INSTANCES (implied companion) — the active instance table that this history table mirrors for completed operations.
• WMS_OP_PLAN_INSTANCES (implied) — referenced through OP_PLAN_INSTANCE_ID.
• WMS_LICENSE_PLATE_NUMBERS (implied) — referenced through LPN_ID.
• INV_SUBINVENTORIES / INV_LOCATORS (implied) — resolved through the FROM and TO subinventory/locator columns for reporting.

Because the table is classified as standalone, it is generally queried directly or joined to the referenced dimension entities above rather than being integrated through a typical Data Vault link structure.