Results for “business_flow_code”

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

Overview

WMS_LABEL_REQUESTS is a Warehouse Management (WMS) transactional table in the Oracle E-Business Suite, owned by the WMS schema. It stores information about label printing requests generated during warehouse operations such as receiving, put-away, picking, packing, shipping, and inventory movements. Each row captures the context of a single label request — what item, lot, serial, LPN, or delivery it pertains to — along with the printer destination and the label format that should be applied.

A defining characteristic of this table is its role as the input to the WMS rules engine. Records in WMS_LABEL_REQUESTS are evaluated against label format rules, and the engine uses the request attributes combined with rule configuration to resolve which label format applies. This makes the table both a transactional audit trail of label activity and a driver of runtime decision logic.

Applying Data Vault modeling heuristics to the documented foreign-key structure, WMS_LABEL_REQUESTS behaves as a link entity. It connects multiple business keys — organization, inventory item, label format, delivery, customer item, and label history — around a request event, rather than acting as a pure hub or a descriptive satellite.

Key Information Stored

The table contains 55 documented columns. The most significant are summarized below.

• LABEL_REQUEST_ID — Surrogate primary key, enforced by WMS_LABEL_REQUESTS_PK and uniquely indexed by WMS_LABEL_REQUESTS_U1. This is the sole documented unique business-key candidate.
• ORGANIZATION_ID — Foreign key to MTL_PARAMETERS; identifies the inventory organization owning the request.
• LABEL_FORMAT_ID — Foreign key to WMS_LABEL_FORMATS; the resolved label format for the request.
• LABEL_ID — Foreign key to GMO_LABEL_HISTORY; links the request to recorded label output history.
• INVENTORY_ITEM_ID, SUBINVENTORY_CODE, LOCATOR_ID — Identify the item and its storage context.
• LOT_NUMBER, REVISION, SERIAL_NUMBER — Lot, revision, and serial attributes for the labeled material.
• LPN_ID — License plate number, central to WMS labeling operations.
• CUSTOMER_ITEM_ID, CUSTOMER_ID, CUSTOMER_SITE_ID — Foreign keys capturing customer-specific labeling context; CUSTOMER_ITEM_ID references MTL_CUSTOMER_ITEMS.
• SUPPLIER_ID, SUPPLIER_SITE_ID, SUPPLIER_ITEM_ID — Supplier-side context for inbound labeling.
• DELIVERY_ID, DELIVERY_DETAIL_ID, PACKAGE_ID — Outbound shipment context.
• SALES_ORDER_HEADER_ID, SALES_ORDER_LINE_ID — Order references driving customer label rules.
• PRINTER_NAME — Destination printer for the label output.
• RULE_ID, RULE_WEIGHT, STRATEGY_ID, BUSINESS_FLOW_CODE — Rules engine metadata that determines format selection and precedence.
• REQUEST_ID, PROGRAM_ID, CREATION_DATE, LAST_UPDATE_DATE — Standard concurrent program and audit columns.

Common Use Cases and Queries

Typical use cases include label audit reporting, troubleshooting misrouted or misformatted labels, and reconstructing which format rule fired for a given request. Analysts frequently join the table to WMS_LABEL_FORMATS to confirm the format applied and to MTL_PARAMETERS to filter by organization.

• Label request by item and organization: SELECT label_request_id, inventory_item_id, label_format_id, printer_name FROM wms_label_requests WHERE organization_id = :org AND inventory_item_id = :item;
• Recent activity window: filter on CREATION_DATE or LAST_UPDATE_DATE to isolate label volume in a shift or day.
• Rule resolution trace: select RULE_ID, RULE_WEIGHT, STRATEGY_ID, LABEL_FORMAT_ID to explain why a given format was chosen.
• Outbound shipment labels: join DELIVERY_ID and PACKAGE_ID to delivery and shipping tables.
• Archive reconciliation: compare against WMS_LABEL_REQUESTS_HIST on LABEL_REQUEST_ID.

Related Objects

The documented relationships identify the following primary dependencies and dependents.

• MTL_PARAMETERS — joined on ORGANIZATION_ID; supplies organization definition.
• WMS_LABEL_FORMATS — joined on LABEL_FORMAT_ID; defines available label formats.
• GMO_LABEL_HISTORY — joined on LABEL_ID; records label output history.
• MTL_CUSTOMER_ITEMS — joined on CUSTOMER_ITEM_ID; customer item cross-reference.
• WMS_LABEL_REQUESTS_HIST — historical/archival table referencing LABEL_REQUEST_ID.
• MTL_SYSTEM_ITEMS_B, MTL_ITEM_LOCATIONS, WSH_DELIVERY_DETAILS, and WMS_LABEL_PRINT_REQUESTS — commonly joined via INVENTORY_ITEM_ID, LOCATOR_ID, DELIVERY_DETAIL_ID, and label printing APIs to complete end-to-end label reporting.