Results for “wms_objects_strategy_v”

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

Overview

WMS_OBJECTS_STRATEGY_V is a read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Warehouse Management (WMS) product family and is defined as a "WMS business object with strategy assigned LOV view." Its purpose is to expose the set of warehouse business objects that have a strategy assignment, in a flattened form suitable for list-of-values (LOV) presentation and for querying and integration. The view returns distinct combinations of organization, object type, and object identity, allowing reports and forms to present the objects for which a strategy has been configured. Because it is documented as a valid view and is based on the strategy assignment data, it serves as the standard read interface for discovering which objects participate in strategy-driven warehouse operations. The column OBJECT_TYPE_MEANING, which users frequently search for, provides the user-facing label corresponding to the internal OBJECT_TYPE_CODE, making the view convenient for LOVs and inquiry screens.

Underlying Base Objects

The view is defined over WMS_STRATEGY_ASSIGNMENTS_V and is documented as referencing the WMS_ASSIGNMENT_PVT package as a base object. The defining query selects from WMS_STRATEGY_ASSIGNMENTS_V using the alias WSAV, and applies SELECT DISTINCT across the projected columns. In effect, WMS_OBJECTS_STRATEGY_V is a presentation-layer projection of the strategy assignments view: it carries forward the organization, object type metadata, object identity, primary key value columns, and value name from the assignment source, while eliminating duplicate rows. The WMS_ASSIGNMENT_PVT package underpins the logic that populates and maintains strategy assignments, so the view reflects data governed by that package's processing. Consumers should treat the view as derived and non-updatable; DML against strategy assignments is performed through the packaged APIs rather than through the view.

Key Columns

• ORGANIZATION_ID — Operating unit / warehouse organization that owns the object and its strategy assignment.
• OBJECT_TYPE_CODE — Internal code identifying the business object type (for example, a pick or putaway rule target).
• OBJECT_TYPE_MEANING — User-facing meaning of the object type; the column most commonly used in LOVs and reporting labels.
• OBJECT_TYPE_DESCRIPTION — Descriptive text for the object type.
• OBJECT_NAME and OBJECT_DESCRIPTION — Name and description of the specific business object instance.
• OBJECT_ID — Identifier of the business object.
• PK1_VALUE through PK5_VALUE — Generic primary key segments that flexibly identify the underlying object across heterogeneous object types.
• VALUE_NAME — Name associated with the assigned value, giving a readable label for the object/strategy context.

Common Use Cases and Queries

The view is typically used to build LOVs, validation queries, and inquiry reports that need to present objects already associated with a strategy. A common pattern resolves the object type meaning for a given organization:

SELECT DISTINCT object_type_code, object_type_meaning FROM apps.wms_objects_strategy_v WHERE organization_id = :org_id ORDER BY object_type_meaning;

To list all assigned objects for a specific object type in an organization:

SELECT object_id, object_name, object_description, value_name FROM apps.wms_objects_strategy_v WHERE organization_id = :org_id AND object_type_code = :type_code;

Because PK1_VALUE through PK5_VALUE are generic, integration queries often select them together with OBJECT_ID to reconstruct the full key of the target entity. The DISTINCT projection makes the view safe for LOV queries where duplicates would be undesirable, but it also means the view is not a substitute for the base assignment tables when every assignment row is required. All queries should filter by ORGANIZATION_ID, since strategy assignments are organization-scoped.