Search Results business_event




Overview
Explore in AI Chat

Overview

APPS.WMS_BUS_EVENT_DEVICES_V is a business-event-to-device assignment view in the Oracle Warehouse Management (WMS) module, available in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the configuration that links warehouse business events (identified by lookup codes of type WMS_BUS_EVENT_TYPES) to physical devices such as scanners, printers, scales, and radio-frequency terminals. In effect, the view answers the operational question: for a given warehouse event, which device is expected to participate, at which organizational level, and under what verification or automation rules?

The view is defined in the APPS schema and serves reporting and integration purposes. Functional users and technical consultants query it to audit device assignment configuration, troubleshoot transaction failures, or drive customized labels, automation flows, and third-party WMS integrations. Because the view resolves lookup meanings and joins organization and device master data, it presents fully denormalized, human-readable output rather than raw IDs, making it well suited to Oracle Reports, BI Publisher, OBIEE, and ad-hoc SQL.

Underlying Base Objects

Per the ETRM metadata, the view is defined over four referenced base objects:

All joins are inner joins expressed through the WHERE clause, so a row is returned only when matching lookup, organization, and device records exist. The metadata notes the base synonym WMS_BUS_EVENT_DEVICES; other referenced names are views or synonyms within APPS.

Key Columns

  • ROW_ID — Rowid of the underlying WMS_BUS_EVENT_DEVICES row.
  • BUSINESS_EVENT_ID / BUSINESS_EVENT — lookup code and decoded meaning of the assigned business event.
  • DEVICE_ID / DEVICE_NAME / DEVICE_TYPE_ID — device identifier, descriptive name, and device type from WMS_DEVICES_VL.
  • LEVEL_TYPE / LEVEL_VALUE — scope at which the assignment applies (e.g., organization, subinventory, or warehouse level).
  • ORGANIZATION_ID / ORGANIZATION_CODE — inventory organization identifier and its code from MTL_PARAMETERS.
  • SUBINVENTORY_CODE — subinventory context, where the level requires it.
  • AUTO_ENABLED_FLAG / ENABLED_FLAG / VERIFICATION_REQUIRED — control flags indicating automatic triggering, active status, and whether operator verification is required.
  • COMMENTS — free-text notes on the assignment.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments carried from the base table.

Common Use Cases and Queries

Typical uses include auditing active device assignments per organization, verifying whether a business event requires operator confirmation, and supporting integration extracts that push event-to-device mappings to external systems.

  • List all enabled assignments for one organization, showing device, event, and verification requirements:

SELECT business_event, device_name, level_type, level_value, subinventory_code, verification_required FROM apps.wms_bus_event_devices_v WHERE organization_code = 'M1' AND enabled_flag = 'Y' ORDER BY business_event, device_name;

  • Find events configured for automatic triggering without verification, useful for troubleshooting unattended device flows:

SELECT business_event, device_name, auto_enabled_flag FROM apps.wms_bus_event_devices_v WHERE auto_enabled_flag = 'Y' AND NVL(verification_required,'N') = 'N';

  • Inventory of all devices associated with a specific business event across organizations:

SELECT organization_code, device_name, device_type_id, enabled_flag FROM apps.wms_bus_event_devices_v WHERE business_event_id = :p_event_id ORDER BY organization_code;

Because the base object set is narrow and the joins are inner, query performance is generally acceptable for configuration-scale data volumes. For reporting that must include unassigned events or inactive devices, the underlying WMS_BUS_EVENT_DEVICES table should be queried directly.