Results for “wms_bus_event_devices”

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

Overview

WMS_BUS_EVENT_DEVICES is a Warehouse Management (WMS) transactional and configuration table owned by the WMS schema. Its documented purpose is to store the mapping between business events and devices, thereby controlling which material handling or RF devices respond to which warehouse business events. In Oracle EBS 12.1.1 and 12.2.2, this table is part of the device integration framework used within warehouse execution, where events such as task dispatch, confirmation, or equipment signaling must be routed to the correct device within a given organization or subinventory context.

The ETRM metadata classifies this object heuristically as a link table in Data Vault modeling terms. This is a modeling suggestion rather than a physical design attribute: the table resolves a many-to-many style association between a business event and a device, with the optional qualifiers of organization and subinventory adding grain to the relationship. It does not function as a standalone hub of business keys nor as a pure descriptive satellite.

Key Information Stored

The table contains 31 documented columns in the ETRM 12.2.2 physical schema. The most significant are:

• BUSINESS_EVENT_ID — identifier of the business event being mapped; this is the principal business-key candidate on the event side of the link.
• DEVICE_ID — foreign key to WMS_DEVICES_B; the device side of the mapping.
• ORGANIZATION_ID — foreign key to MTL_PARAMETERS; scopes the mapping to a specific inventory organization.
• SUBINVENTORY_CODE — narrows the mapping to a subinventory within the organization.
• LEVEL_TYPE and LEVEL_VALUE — define the granularity at which the mapping applies, qualifying the link's grain.
• AUTO_ENABLED_FLAG — indicates whether the device is automatically enabled for the event.
• ENABLED_FLAG — controls whether the mapping is active.
• VERIFICATION_REQUIRED — flags whether operator or system verification is mandatory for the event-device interaction.
• COMMENTS — free-text annotation for the mapping.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the DFF-enabled descriptive flexfield segment set for extension.

The metadata documents foreign keys but does not enumerate a named surrogate primary key or unique index; the effective business key is the combination of BUSINESS_EVENT_ID, DEVICE_ID, ORGANIZATION_ID, and the level qualifiers.

Common Use Cases and Queries

Typical scenarios include auditing which devices are configured for a given business event, verifying that device mappings are enabled before go-live, and reporting device coverage by organization or subinventory.

To list active device mappings for an organization:

SELECT b.BUSINESS_EVENT_ID, b.DEVICE_ID, d.DEVICE_NAME, b.ORGANIZATION_ID, b.SUBINVENTORY_CODE, b.LEVEL_TYPE, b.ENABLED_FLAG FROM WMS.WMS_BUS_EVENT_DEVICES b, WMS.WMS_DEVICES_B d WHERE b.DEVICE_ID = d.DEVICE_ID AND b.ORGANIZATION_ID = :org_id AND b.ENABLED_FLAG = 'Y';

To identify mappings requiring verification or auto-enablement, filter on VERIFICATION_REQUIRED and AUTO_ENABLED_FLAG. Reporting extracts commonly join to MTL_PARAMETERS for organization names and to WMS_DEVICES_B to resolve device descriptions.

Related Objects

• WMS_DEVICES_B — referenced via WMS_BUS_EVENT_DEVICES.DEVICE_ID; the primary device master.
• MTL_PARAMETERS — referenced via WMS_BUS_EVENT_DEVICES.ORGANIZATION_ID; supplies organization context.
• WMS_DEVICES_TL — provides translated device names for reporting when org-default language differs.
• MTL_SYSTEM_ITEMS_B — related through inventory organization and subinventory reporting.
• WMS Business Event APIs / concurrent programs — consume this mapping when dispatching warehouse events to devices.