Search Results wms_op_plans_b




Overview
Explore in AI Chat

Overview

WMS_OP_PLANS_B is the header-level master table for Operation Plans within the Oracle Warehouse Management (WMS) module of Oracle E-Business Suite. It resides in the WMS schema and stores the defining attributes of an operation plan, which governs how warehouse execution tasks are generated, sequenced, and dispatched. Operation plans are fundamental to WMS-directed activities such as picking, put-away, replenishment, and crossdocking, since they determine the task types, activity types, and plan types that drive warehouse labor and material movement.

The table is owned by WMS and holds 35 documented columns in the 12.2.2 ETRM schema. Its primary key is WMS_OP_PLANS_B_PK, defined on the OPERATION_PLAN_ID column. A secondary unique index, WMS_OP_PLANS_B_U1, spans OPERATION_PLAN_ID and ZD_EDITION_NAME, supporting the editioning model introduced in 12.2. Based on the foreign key structure, the heuristic Data Vault classification for this object is standalone, suggesting it functions as a hub-like reference table for operation plan headers rather than as a transactional link or satellite.

Key Information Stored

The most significant columns in WMS_OP_PLANS_B include the following:

  • OPERATION_PLAN_ID — the surrogate primary key uniquely identifying each operation plan header.
  • ORGANIZATION_ID — the warehouse or inventory organization to which the plan belongs.
  • SYSTEM_TASK_TYPE — the system-defined task category that the plan governs.
  • ACTIVITY_TYPE_ID — reference to the activity type associated with the plan.
  • PLAN_TYPE_ID — reference to the plan type classification.
  • USER_DEFINED — flag indicating whether the plan is user-defined versus seeded.
  • ENABLED_FLAG — indicates whether the plan is active and usable.
  • EFFECTIVE_DATE_FROM and EFFECTIVE_DATE_TO — the validity window for the plan.
  • TEMPLATE_FLAG — identifies the plan as a reusable template.
  • DEFAULT_FLAG — marks the plan as the default for its context.
  • COMMON_TO_ALL_ORG — indicates whether the plan applies across all organizations.
  • CROSSDOCK_TO_WIP_FLAG — governs crossdocking behavior toward work-in-process.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard Oracle flexfield descriptive columns for extensibility.
  • ZD_EDITION_NAME — the editioning column supporting 12.2 edition-based redefinition.

The surrogate key is distinct from the business-key candidate captured by the unique index WMS_OP_PLANS_B_U1, which combines OPERATION_PLAN_ID with ZD_EDITION_NAME to ensure uniqueness across editions. Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

Operation plans are typically queried to identify which plans are active for an organization, to determine default or template plans, and to drive task generation logic. Common SQL patterns include:

  • Retrieving active plans for an organization: SELECT operation_plan_id, system_task_type FROM wms_op_plans_b WHERE organization_id = :org AND enabled_flag = 'Y' AND SYSDATE BETWEEN effective_date_from AND NVL(effective_date_to, SYSDATE + 1);
  • Locating default or template plans: filtering on DEFAULT_FLAG = 'Y' or TEMPLATE_FLAG = 'Y'.
  • Joining to WMS_OP_PLAN_DETAILS on OPERATION_PLAN_ID to obtain the task-level configuration lines for a given header.
  • Reporting on plans that are organization-specific versus shared, using COMMON_TO_ALL_ORG.

Reporting use cases include warehouse configuration audits, migration validation between environments, and analysis of plan coverage across warehouses.

Related Objects

WMS_OP_PLANS_B is referenced by numerous child and transactional tables through the OPERATION_PLAN_ID column, reflecting its role as a header. Significant related objects include:

These relationships confirm that WMS_OP_PLANS_B serves as the central reference anchor for warehouse operation plan definitions across execution, labor, and reporting layers.