Results for “current_operation_instance_id”

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

Overview

WMS_OP_PLAN_INSTANCES_HIST is a WMS (Warehouse Management) schema table in Oracle E-Business Suite that stores historical execution records for operation plan instances. Functionally it mirrors the runtime planning structures used by Oracle Warehouse Management to track the lifecycle of operation plans — the higher-level plans that orchestrate tasks, moves, and resource activities within the warehouse. The "_HIST" suffix indicates that rows here represent historical or archived execution state rather than live operational data, making the table valuable for audit, cycle-time analysis, and post-execution reporting.

The ETRM metadata notes that this object was "Not intended for use in Release 11.5.9," which reflects its introduction or repurposing in later releases, including the 12.1.1 and 12.2.2 environments relevant to this discussion. The documented schema contains 39 columns owned by the WMS schema.

Based on the foreign key and primary key structure provided in the metadata, the heuristic Data Vault classification is standalone. As a modeling suggestion, this table does not participate in a classic hub-and-satellite pattern within the documented relationships; it functions as a self-contained keyed entity. One interpretation is a satellite-like historical store anchored on OP_PLAN_INSTANCE_ID with a single outgoing reference to WMS_OP_PLANS_B. This classification should be treated as a heuristic starting point, not an authoritative architectural determination.

Key Information Stored

The surrogate primary key is OP_PLAN_INSTANCE_ID, enforced by constraint WMS_OP_PLAN_INS_HIST_PK. The same column is also the sole business-key candidate documented through unique index WMS_OP_PLAN_INS_HIST_U1, meaning the instance identifier serves double duty as both the technical and logical key.

The most significant columns and what they hold:

• OP_PLAN_INSTANCE_ID — surrogate and business key identifying each historical plan instance.
• OPERATION_PLAN_ID — foreign key to WMS_OP_PLANS_B; links the instance to its parent operation plan definition.
• ORGANIZATION_ID — the inventory organization owning the plan instance, essential for multi-org filtering.
• STATUS — lifecycle state of the instance at the time of record.
• SYSTEM_TASK_TYPE — categorizes the system-driven task generated by the plan.
• TASK_SOURCE_ID — identifies the originating task source.
• CURRENT_OPERATION_INSTANCE_ID — points to the active operation instance within the plan.
• PARENT_PLAN_INSTANCE_ID / ROOT_PLAN_INSTANCE_ID — support hierarchical plan structures.
• PLAN_EXECUTION_START_DATE / PLAN_EXECUTION_END_DATE — execution window used for duration and throughput analysis.
• TRANSACTION_ID — correlates the instance with the inventory transaction that resulted.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE — standard audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield (DFF) segment set for extensibility.
• ACTIVITY_TYPE_ID, PLAN_TYPE_ID, ORIG_SOURCE_SUB_CODE, ORIG_DEST_SUB_CODE, ORIG_SOURCE_LOC_ID, ORIG_DEST_LOC_ID — classification and origin/destination locator references.

Common Use Cases and Queries

Typical scenarios include reviewing completed plan execution history for a given organization, reconstructing the provenance of a transaction, and measuring execution duration. For example, filtering recent history for an organization:

SELECT op_plan_instance_id, operation_plan_id, status, plan_execution_start_date, plan_execution_end_date
FROM wms.wms_op_plan_instances_hist
WHERE organization_id = :p_org_id
AND creation_date >= :p_from_date;

Joining to the parent plan for descriptive context:

SELECT h.op_plan_instance_id, p.* , h.status
FROM wms.wms_op_plan_instances_hist h
JOIN wms.wms_op_plans_b p ON p.operation_plan_id = h.operation_plan_id;

Reporting use cases include execution cycle-time trends, status distribution dashboards, and tracing plan instances back to inventory transactions via TRANSACTION_ID.

Related Objects

• WMS_OP_PLANS_B — joined on OPERATION_PLAN_ID = OPERATION_PLAN_ID; the base operation plan referenced by the foreign key.
• WMS_OP_PLAN_INSTANCES — the runtime counterpart whose historical records are persisted here.
• WMS_OP_PLAN_INSTANCE_TASKS — task-level detail associated with each instance.
• WMS_OP_PLAN_INSTANCE_OPERATIONS — operation-level detail referenced by CURRENT_OPERATION_INSTANCE_ID.
• MTL_TRANSACTIONS / MTL_MATERIAL_TRANSACTIONS — correlated via TRANSACTION_ID.
• INV_ORGANIZATION_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — resolve ORGANIZATION_ID.
• WMS public APIs and concurrent programs that archive executed plan instances into this history table.