Search Results wms_device_io_types

Overview

APPS.WMS_DEVICES_VL is a language-dependent (VL, "view language") reporting view within the Oracle Warehouse Management System (WMS) module of Oracle E-Business Suite. It presents a denormalized, translation-aware representation of the warehouse device master defined in WMS_DEVICES_B and WMS_DEVICES_TL. The view joins the base device definition to translated name and description text, resolves several lookup codes to their display meanings, and enriches each row with organization and message-template context. Its primary role is to support reports, concurrent programs, and integration queries that must display human-readable device information — such as device type, input method, output method, and organization code — rather than the underlying coded identifiers.

The "_VL" suffix indicates that the view honors the session language through a call to userenv('LANG'), ensuring name and description columns are returned in the user's current language. This makes it the preferred access point for any client that must respect multilingual device descriptions, as opposed to querying the underlying tables directly.

Underlying Base Objects

The documented ETRM metadata identifies the following referenced base objects for the 12.2.2 definition:

• MFG_LOOKUPS (VIEW) — joined three times (aliases ML1, ML2, ML3) to resolve lookup meanings. ML1 uses lookup type WMS_DEVICE_TYPES for the device type; ML2 and ML3 use lookup type WMS_DEVICE_IO_TYPES for the input and output methods respectively. This is the object directly relevant to the query term "wms_device_io_types" — the lookup type that governs valid device input/output method codes.
• WMS_DEVICES_B (SYNONYM) — the base table (alias B) holding the core, non-translated device attributes, including device_id, device_type_id, enabled flag, I/O method IDs, organization, batch limit, and the descriptive flexfield attribute columns.
• WMS_DEVICES_TL (SYNONYM) — the translation table (alias T) supplying NAME and DESCRIPTION, filtered to the session language.
• MTL_PARAMETERS (SYNONYM) — the inventory organization parameters table (alias MP), outer-joined on ORGANIZATION_ID to return ORGANIZATION_CODE. The outer join allows device records with a null organization to still be returned.
• WMS_MSG_TEMPLATES (SYNONYM) — the message template table (alias WMT), outer-joined on MESSAGE_TEMPLATE_ID to supply TEMPLATE_NAME.

Key Columns

• DEVICE_ID — primary identifier for the device; also the join key between the base and translation tables.
• NAME / DESCRIPTION — language-dependent device name and description from WMS_DEVICES_TL.
• DEVICE_TYPE_ID / DEVICE_TYPE — the coded device type and its decoded MEANING from the WMS_DEVICE_TYPES lookup.
• INPUT_METHOD_ID / INPUT_METHOD and OUTPUT_METHOD_ID / OUTPUT_METHOD — coded I/O methods and their decoded meanings, resolved via the WMS_DEVICE_IO_TYPES lookup (outer-joined, so nulls are permitted).
• ENABLED_FLAG, LOT_SERIAL_CAPABLE, FORCE_SIGN_ON_FLAG, MULTI_SIGN_ON, NOTIFICATION_FLAG — device behavior control flags.
• ORGANIZATION_ID / ORGANIZATION_CODE — owning inventory organization and its code.
• SUBINVENTORY_CODE, LOCATOR_ID — default subinventory and locator assignment.
• BATCH_LIMIT, OUT_DIRECTORY, OUT_FILE_PREFIX — output and batching configuration.
• MESSAGE_TEMPLATE_ID / TEMPLATE_NAME — associated message template.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield columns.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include: listing all enabled devices in an organization, auditing device I/O configuration, and joining device data to integrations that drive labels, RF transactions, or automated output files.

List enabled devices with decoded types and methods:

SELECT device_id, name, device_type, input_method, output_method,
       organization_code, enabled_flag
  FROM apps.wms_devices_vl
 WHERE enabled_flag = 'Y'
   AND organization_id = :p_org_id
 ORDER BY name;

Find all devices using a specific input method, which exercises the WMS_DEVICE_IO_TYPES lookup resolution:

SELECT device_id, name, input_method, output_method
  FROM apps.wms_devices_vl
 WHERE input_method = 'KEYBOARD';

Audit devices missing organization or template assignments, relying on the outer joins:

SELECT device_id, name, organization_code, template_name
  FROM apps.wms_devices_vl
 WHERE organization_code IS NULL
    OR template_name IS NULL;

Because the view performs lookup decoding and outer joins at query time, it should be used for reporting and light integration rather than high-volume transactional processing.