Results for “wms_label_requests_hist_v”

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

Overview

The APPS.WMS_LABEL_REQUESTS_HIST_V view is a Warehouse Management (WMS) reporting object that exposes historical label printing requests submitted within Oracle E-Business Suite. It is owned by the APPS schema and is defined as a VALID view in both EBS 12.1.1 and 12.2.2. Its stated purpose is to store and present label printing request history records, and it functions as a denormalized read layer over the base history table WMS_LABEL_REQUESTS_HIST along with numerous descriptive lookups.

The view resolves foreign-key identifiers into human-readable values by joining to lookup views (MFG_LOOKUPS), item and locator key flexfield views, delivery, supplier, customer, rule, and strategy translation tables. This makes it suitable for operational reporting, label reprinting analysis, and integration extracts where descriptive text is preferred over raw IDs. Because the view references FND_GLOBAL, it can also return session-based context values across the supported EBS releases.

Underlying Base Objects

Documented referenced base objects include:

• WMS_LABEL_REQUESTS_HIST — the primary history table supplying request, label content, and status data.
• FND_USER and FND_GLOBAL — user name resolution and session context.
• MFG_LOOKUPS — meaning text for request mode, business flow, and label type codes.
• MTL_SYSTEM_ITEMS_KFV, MTL_ITEM_LOCATIONS_KFV, MTL_CUSTOMER_ITEMS, MTL_PARAMETERS — item, locator, customer item, and organization context.
• OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL — sales order header and line details.
• PO_VENDORS, PO_VENDOR_SITES_ALL — supplier and supplier site information.
• HZ_CUST_ACCOUNTS, HZ_PARTIES, HZ_CUST_ACCOUNT_ROLES, HZ_ORG_CONTACTS, HZ_RELATIONSHIPS — customer, party, and contact resolution.
• WMS_LABEL_FORMATS, WMS_RULES_TL, WMS_STRATEGIES_TL, WMS_LICENSE_PLATE_NUMBERS — label format, rules, strategies, and LPN data.
• WSH_NEW_DELIVERIES — delivery name lookup.

Key Columns

• LABEL_REQUEST_ID / ORIGINAL_REQUEST_ID — request identity and link to the originating request for reprints.
• REQUEST_MODE_CODE / REQUEST_MODE, BUSINESS_FLOW_CODE, LABEL_TYPE, LABEL_FORMAT_NAME — classification and format of each request.
• REQUEST_DATE, REQUEST_USER, STATUS_FLAG, JOB_STATUS, PRINTER_STATUS, ERROR_MESSAGE — timing, ownership, and outcome status.
• ORGANIZATION_CODE, INVENTORY_ITEM_ID, ITEM, SUBINVENTORY_CODE, LOCATOR, LOT_NUMBER, REVISION, SERIAL_NUMBER — inventory context of the labeled material.
• SALES_ORDER_HEADER_ID / SALES_ORDER_HEADER, SALES_ORDER_LINE_ID / SALES_ORDER_LINE — order data used for outbound labeling and shipping documentation.
• DELIVERY, LICENSE_PLATE_NUMBER, PACKAGE_ID — shipping and packaging context.
• SUPPLIER, SUPPLIER_SITE, CUSTOMER_NUMBER, CUSTOMER_NAME, CUSTOMER_CONTACT_NAME, CUSTOMER_ITEM_NUMBER — trading partner details printed on labels.
• RULE_NAME, STRATEGY_NAME, RULE_WEIGHT, NO_OF_COPY, ENCODING, OUTFILE_NAME, OUTFILE_DIRECTORY — printing rules, strategy, and output file location.
• ATTRIBUTE1–ATTRIBUTE15 and ATTRIBUTE_CATEGORY — descriptive flexfield segments.

Common Use Cases and Queries

The view is commonly queried for audit and reprint operations. To retrieve label history for a specific sales order, filter by the header ID or order number:

• Order-level label audit: SELECT label_request_id, request_date, request_user, sales_order_header, sales_order_line, item, status_flag, error_message FROM wms_label_requests_hist_v WHERE sales_order_header_id = :sales_order_header_id ORDER BY request_date DESC;
• Reprint tracking: join label_request_id to original_request_id to trace repeated print attempts.
• Failure analysis: filter on status_flag, job_status, or non-null error_message to isolate failed print jobs.
• Customer/supplier reporting: aggregate by customer_number, supplier, or delivery to measure labeled shipment volumes.
• Item and organization analysis: group by organization_code, item, and label_format_name for throughput reporting.

Because the view is read-only and heavily joined, queries should constrain the leading columns (request date, organization, or sales order) to avoid full scans of the underlying history table.