Results for “common_to_all_org”
30 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
WMS_OP_PLANS_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, exposed under the Warehouse Management (WMS) product family. It presents header-level Operation Plan information — the definitions that govern how warehouse operations such as receiving, put-away, picking, packing, and cross-docking are executed within a warehouse. Operation plans act as templates that bind system task types to activities and rules, and they are consumed by the WMS execution engine as well as by downstream modules including Inventory, Shipping, and Manufacturing.
The "VL" designation indicates that the view joins the transactional base table with its translation table and filters the translation rows by the session language using USERENV('LANG'). As a result, each query returns a single, language-appropriate row per operation plan, delivering translated values for OPERATION_PLAN_NAME and DESCRIPTION alongside the untranslated attributes. This makes the view suitable for both concurrent-program reports and direct SQL-based reporting in EBS 12.1.1 and 12.2.2.
Underlying Base Objects
Per the ETRM metadata, the view is defined over two SYNONYM-referenced base objects:
- WMS_OP_PLANS_B — the base (non-translated) table holding the operational attributes, keyed by
OPERATION_PLAN_ID. It is aliased asBin the view definition. - WMS_OP_PLANS_TL — the translation table supplying
OPERATION_PLAN_NAMEandDESCRIPTION, aliased asT.
The join predicate is B.OPERATION_PLAN_ID = T.OPERATION_PLAN_ID AND T.LANGUAGE = USERENV('LANG'). The view also surfaces the ROWID of the base table row as ROW_ID. Because the view is a VL construct, no insert, update, or delete DML should be issued against it; modifications belong to the base tables through the standard WMS APIs.
Key Columns
- OPERATION_PLAN_ID — primary identifier of the operation plan; the principal join key to
WMS_OP_PLANS_TLand to related detail tables. - OPERATION_PLAN_NAME — the translated, user-facing name of the plan.
- DESCRIPTION — translated descriptive text for the plan.
- SYSTEM_TASK_TYPE — the task type the plan drives (e.g., receiving-related or picking-related system task).
- ORGANIZATION_ID — the warehouse/inventory organization to which the plan applies.
- EFFECTIVE_DATE_FROM / EFFECTIVE_DATE_TO — the active date range for the plan.
- ENABLED_FLAG / DEFAULT_FLAG / TEMPLATE_FLAG — status and behavior indicators: whether the plan is active, whether it is the default for its task type, and whether it serves as a template.
- COMMON_TO_ALL_ORG — indicates whether the plan is shared across organizations.
- PLAN_TYPE_ID / ACTIVITY_TYPE_ID — foreign keys to the plan type and activity type definitions that further classify the plan.
- CROSSDOCK_TO_WIP_FLAG — indicates cross-docking behavior directed to work-in-process.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard EBS descriptive flexfield (DFF) columns for user-defined extensions.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
Common Use Cases and Queries
The view is most frequently used to report on the enabled operation plans configured for a given warehouse, to identify the default plan for a system task type, and to confirm effective dating. A typical query lists enabled plans for an organization:
- Retrieve enabled plans by organization:
SELECT operation_plan_id, operation_plan_name, system_task_type, effective_date_from, effective_date_to FROM wms_op_plans_vl WHERE organization_id = :org_id AND enabled_flag = 'Y' ORDER BY operation_plan_name; - Find the default plan for a task type:
SELECT operation_plan_id, operation_plan_name FROM wms_op_plans_vl WHERE organization_id = :org_id AND system_task_type = :task_type AND default_flag = 'Y'; - Join to detail tables using
OPERATION_PLAN_IDto obtain activity and rule-level configuration for reporting or integration extracts.
Because the translation join filters on USERENV('LANG'), callers should be aware that results reflect the session language; integrations expecting a fixed language should set the environment language explicitly or query the base and translation tables directly.
-
View: WMS_OP_PLANS_VL 12.1.1
Header level Operation Plan Information
APPS.WMS_OP_PLANS_VL·↳ WMS_OP_PLANS_B·↳ WMS_OP_PLANS_TL·Explore WMS module →
-
Table to store header level Operation Plan Information
-
View: WMS_OP_PLANS_V 12.1.1
Header level Operation Plan Information. This view is used in the Operation Plan definition form WMSOPDFN.fmb
APPS.WMS_OP_PLANS_V·↳ MFG_LOOKUPS·↳ WMS_OP_PLANS_B·↳ WMS_OP_PLANS_TL·Explore WMS module →
-
View: WMS_OP_PLANS_V 12.2.2
Header level Operation Plan Information. This view is used in the Operation Plan definition form WMSOPDFN.fmb
APPS.WMS_OP_PLANS_V·↳ MFG_LOOKUPS·↳ WMS_OP_PLANS_B·↳ WMS_OP_PLANS_TL·Explore WMS module →
-
Table to store header level Operation Plan Information
-
View: WMS_OP_PLANS_VL 12.2.2
Header level Operation Plan Information
APPS.WMS_OP_PLANS_VL·↳ WMS_OP_PLANS_B·↳ WMS_OP_PLANS_TL·Explore WMS module →
-
VIEW: WMS.WMS_OP_PLANS_B# 12.2.2
-
VIEW: WMS.WMS_OP_PLANS_B# 12.2.2
-
TABLE: WMS.WMS_OP_PLANS_B 12.2.2
-
TABLE: WMS.WMS_OP_PLANS_B 12.1.1
-
VIEW: APPS.WMS_OP_PLANS_VL 12.1.1
-
VIEW: APPS.WMS_OP_PLANS_VL 12.2.2
-
VIEW: APPS.WMS_OP_PLANS_V 12.2.2
-
VIEW: APPS.WMS_OP_PLANS_V 12.1.1
-
eTRM - WMS Tables and Views 12.1.1
-
eTRM - WMS Tables and Views 12.2.2