Multi-Allocation Units of Measure
TheMobile Outbound Audit (rf.outbound.cwrfauditlpnplt) transaction supports auditing OBLPNs with multi-allocation UOMs in SKU-Qty mode. During Outbound Audit, if an OBLPN has multi UOM allocation, you can scan a SKU and select the allocation UOM to audit the scanned SKU.
- The Outbound Audit flow supports auditing both multi-SKU and single-SKU with mixed allocation UOMs only in SKU-Qty mode (qty-entry-mode = SKU-Qty).
- If the screen parameter qty-entry-mode is set to Blank or “SKU-Scan”, Outbound Audit with multiple allocation UOMs is not supported. This is because prompting for allocation UOM selection on every SKU scan is not practical in this mode. To audit OBLPNs with multiple allocation UOMs, we recommend using SKU-Qty mode.
Screen Flow
When using the Outbound Audit transaction in SKU-Qty mode, if the scanned SKU has multiple allocation UOMs, the system displays an Allocation UOM selection list (for example, LPNS, UNITS, CASES, PACKS).
- Select a UOM from the list, then scan the quantity for the selected SKU in that UOM. The system processes the count in the selected UOM and performs required conversions within the transaction.
- You can select and scan same SKU for different allocation UOMs multiple times in an Outbound Audit transaction.
- When you scan a SKU with multiple allocation UOM quantities, the system updates the LPN Qty (UOM) field.
Example for single SKU with different allocation UOMs: An auditor audits OBLPN “SSOBLPN45” that contains SKUA allocation in 2 CASES and 3 UNITS. The auditor selects the appropriate UOM for each line and enters the counted quantity in the Outbound Audit transaction.
- You can use UOM Literal Translated UOM Codes to display in the Outbound Audit History UI. If UOM literals are configured for the system language, the UI displays the literal translated UOM code; otherwise, it displays the UOM code. Changes to literals updates the displayed “Allocation UOM” automatically.