Search Results output_method

Overview

WMS_DEVICES_VL is a Multi-Lingual Support (MLS) view owned by the APPS schema in Oracle E-Business Warehouse Management (WMS). It presents the translated, user-facing representation of the WMS_DEVICES entity, joining the base table WMS_DEVICES_B to its translation table WMS_DEVICES_TL so that device NAME and DESCRIPTION are returned in the session's language as resolved by USERENV('LANG'). WMS_DEVICES stores the physical and logical devices configured for warehouse operations, including radio-frequency (RF) terminals, barcode readers, printers, and other data-collection hardware.

Because it exposes decoded meaning values rather than raw lookup codes, the view is the preferred reporting and integration source for warehouse device configuration. The user search term "input_method" maps directly to one of its decoded columns: INPUT_METHOD_ID is the stored lookup code, and INPUT_METHOD is the display meaning resolved from MFG_LOOKUPS. The same pattern applies to DEVICE_TYPE and OUTPUT_METHOD. This makes the view well-suited for reports, extracts, and interfaces that must present human-readable device metadata without performing additional lookup joins.

Underlying Base Objects

The view is defined over a synonym/table and lookup set documented in ETRM 12.2.2:

• WMS_DEVICES_B (synonym) — the base entity holding all device attributes, keyed by DEVICE_ID.
• WMS_DEVICES_TL (synonym) — the MLS translation table supplying NAME and DESCRIPTION for the current language.
• MFG_LOOKUPS (view) — referenced three times (ML1, ML2, ML3) to decode DEVICE_TYPE_ID, INPUT_METHOD_ID, and OUTPUT_METHOD_ID.
• MTL_PARAMETERS (synonym) — outer-joined on ORGANIZATION_ID to return ORGANIZATION_CODE.
• WMS_MSG_TEMPLATES (synonym) — outer-joined on MESSAGE_TEMPLATE_ID to return TEMPLATE_NAME.

Joins are: B.DEVICE_ID = T.DEVICE_ID with T.LANGUAGE = USERENV('LANG'); ML1/ML2/ML3 on lookup type and code (ML2 and ML3 outer-joined); MP and WMT outer-joined. The outer joins preserve devices lacking an organization, input/output method, or message template.

Key Columns

• DEVICE_ID — primary identifier of the device record.
• NAME, DESCRIPTION — translated device labels from WMS_DEVICES_TL.
• DEVICE_TYPE_ID / DEVICE_TYPE — lookup code and decoded meaning for the device type.
• INPUT_METHOD_ID / INPUT_METHOD — code and decoded meaning of the device input method (lookup type WMS_DEVICE_IO_TYPES). This is the column of interest for the "input_method" search.
• OUTPUT_METHOD_ID / OUTPUT_METHOD — corresponding output method code and meaning.
• ENABLED_FLAG, LOT_SERIAL_CAPABLE, FORCE_SIGN_ON_FLAG, MULTI_SIGN_ON, NOTIFICATION_FLAG — behavioral controls for the device.
• SUBINVENTORY_CODE, ORGANIZATION_ID, ORGANIZATION_CODE, LOCATOR_ID — inventory and location context.
• BATCH_LIMIT, OUT_DIRECTORY, OUT_FILE_PREFIX, DEVICE_MODEL — output and device characteristics.
• MESSAGE_TEMPLATE_ID, TEMPLATE_NAME — assigned message template.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns, plus ROW_ID.

Common Use Cases and Queries

Typical uses include listing enabled devices and their input/output methods, building RF device inventories per organization, and validating message template assignments. To examine input methods specifically:

SELECT device_id, name, input_method, output_method, organization_code FROM apps.wms_devices_vl WHERE input_method IS NOT NULL ORDER BY name;

Filtering by organization and type:

SELECT name, device_type, input_method, subinventory_code FROM apps.wms_devices_vl WHERE organization_code = :org AND enabled_flag = 'Y';

Because translation depends on USERENV('LANG'), query results reflect each user's language setting. Reporting on raw lookup codes should use the underlying WMS_DEVICES_B table instead.