Oracle Warehouse Management Cloud
What's New
  1. Update 19C
  1. Revision History
  2. Overview
  3. Feature Summary
    1. Technical Enhancements
        1. Provision Production Environments in Oracle Cloud Infrastructure (OCI)
        2. Adopt Oracle Autonomous Transaction Processing
        3. Performance Optimization in Sequence Counter UI
        4. Support for Enterprise Single Sign On with Oracle Identity Cloud Service
    2. Functional Enhancements
      1. Receiving
        1. Mark LPNs for Quality Control Using Receive LPN and Receive Entire Shipment Buttons
        2. New Mobile RF Single SKU Receiving Option
        3. Receive Single SKU with Batch/Expiry/Attribute Number Tracked
      2. Outbound
        1. Perform Ship Load from RF Load OBLPN
        2. Prevent Loading/Shipping a Load with No OBLPNs
        3. Control Waving and Loading of Expired Inventory
        4. Control Packing of One or Multiple Orders with the Same Destination Facility
      3. Inventory Management
        1. Prompt Location in RF Modify Cancel OBLPN
        2. Customize Reference Text in RF Direct Consume LPN Transaction
        3. Enhancements to Split Inbound Container Transaction
        4. New Inbound LPN Type Set Up
      4. Replenishment
        1. Configure Destination Location Type in Standalone Replenishment
        2. Round Up Allocations for Replenishment
        3. Consider Weight Check During Replenishment
      5. Putaway
        1. Consider Dimension Check During Putaway
        2. Consider Weight Check During Putaway
      6. Sorting
        1. Validate Critical Dimensions in Sorting
      7. Label Designer
        1. Image-Based Barcode Support in Label Designer
        2. New Fields and Barcode in Document Label Designer
        3. Print Preview in Document Label Designer
        4. Support Pallet Labels in Label Designer
      8. Cycle Count
        1. Support Tasking Mode for Cycle Count by Number of LPNs
        2. Cycle Count Approval Process
      9. Reporting
        1. Create Web Reports Including New Categories
      10. Kitting
        1. Cancel Wave in Work Order Template
        2. Inventory Message in Lock Code UI
        3. Configure Email Notification
    3. User Experience and Usability Enhancements
      1. Receiving
        1. Verify Shipment by LPN/Pallet Number
      2. Inventory Management
        1. Add Permissions to Reason Code UI
        2. Lock/Unlock All LPNs on a Pallet
      3. Task Management
        1. New Recalculate Task Button
      4. Outbound Load Management
        1. Provide Additional Information on Outbound Load UI
        2. Provide Additional Information on Shipment Manifest UI
        3. Ship Load on Load OBLPN Mobile RF UI
        4. Capture Reference Information on Direct Consume LPN Mobile RF UI
      5. Rule Criteria
        1. Enable Additional Fields as Selection Criteria for Rules
        2. Match Date Columns Based on Difference from Current Date
      6. Fulfillment
        1. Hide Internal Picking Orders
    4. Integration Enhancements
      1. REST APIs
        1. Print Labels Using REST APIs
        2. Copy Putaway and Facility-Related Configurations Using REST APIs
        3. Update Stop Receiving Flag in Purchase Order Detail Via API Request
        4. Palletize and Depalletize Using a REST API
      2. Interfaces
        1. Allow Extract File in Output Interface Configuration UI
        2. Send Header Level Request Using Input Interface
        3. Removal of Post to URL Job Type from Scheduled Job UI
        4. Upload Messages in Bulk
        5. Improvements to Re-Processing of Inventory History Transaction Records
      3. Inventory History
        1. New IHT Activity to Cancel Work Order
        2. New IHT Activity to Unload Container
        3. Enable Auto-Send of Inventory History
        4. Enable Auto Process of Inventory History

Update 19C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes
29 OCT 2019 New Mobile RF Single SKU Receiving Option Updated document. Revised feature information.
29 OCT 2019 Receive Single SKU with Batch/Expiry/Attribute Number Tracked Updated document. Delivered feature in update 19C.
29 OCT 2019 Enable Auto Process of Inventory History Updated document. Delivered feature in update 19C.
29 OCT 2019 Control Packing of One or Multiple Orders with the Same Destination Facility Updated document. Delivered feature in update 19C.
29 OCT 2019 Round Up Allocations for Replenishment Updated document. Revised feature information.
07 OCT 2019 Print Labels Securely Using IPPS/HTTPS Secure Protocol Removed feature from update 19C.
13 SEP 2019 Configure Email Notification Updated document. Revised feature information.
13 SEP 2019 Support Pallet Labels in Label Designer Updated document. Revised feature information.
01 JUL 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at owms-cloud-comms_us@oracle.com.

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.


Customer Action Required = You MUST take action before these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Customer Action Required

Technical Enhancements

Provision Production Environments in Oracle Cloud Infrastructure (OCI)

Adopt Oracle Autonomous Transaction Processing

Performance Optimization in Sequence Counter UI

Support for Enterprise Single Sign On with Oracle Identity Cloud Service

Functional Enhancements

Receiving

Mark LPNs for Quality Control Using Receive LPN and Receive Entire Shipment Buttons

New Mobile RF Single SKU Receiving Option

Receive Single SKU with Batch/Expiry/Attribute Number Tracked

Outbound

Perform Ship Load from RF Load OBLPN

Prevent Loading/Shipping a Load with No OBLPNs

Control Waving and Loading of Expired Inventory

Control Packing of One or Multiple Orders with the Same Destination Facility

Inventory Management

Prompt Location in RF Modify Cancel OBLPN

Customize Reference Text in RF Direct Consume LPN Transaction

Enhancements to Split Inbound Container Transaction

New Inbound LPN Type Set Up

Replenishment

Configure Destination Location Type in Standalone Replenishment

Round Up Allocations for Replenishment

Consider Weight Check During Replenishment

Putaway

Consider Dimension Check During Putaway

Consider Weight Check During Putaway

Sorting

Validate Critical Dimensions in Sorting

Label Designer

Image-Based Barcode Support in Label Designer

New Fields and Barcode in Document Label Designer

Print Preview in Document Label Designer

Support Pallet Labels in Label Designer

Cycle Count

Support Tasking Mode for Cycle Count by Number of LPNs

Cycle Count Approval Process

Reporting

Create Web Reports Including New Categories

Kitting

Cancel Wave in Work Order Template

Inventory Message in Lock Code UI

Configure Email Notification

User Experience and Usability Enhancements

Receiving

Verify Shipment by LPN/Pallet Number

Inventory Management

Add Permissions to Reason Code UI

Lock/Unlock All LPNs on a Pallet

Task Management

New Recalculate Task Button

Outbound Load Management

Provide Additional Information on Outbound Load UI

Provide Additional Information on Shipment Manifest UI

Ship Load on Load OBLPN Mobile RF UI

Capture Reference Information on Direct Consume LPN Mobile RF UI

Rule Criteria

Enable Additional Fields as Selection Criteria for Rules

Match Date Columns Based on Difference from Current Date

Fulfillment

Hide Internal Picking Orders

Integration Enhancements

REST APIs

Print Labels Using REST APIs

Copy Putaway and Facility-Related Configurations Using REST APIs

Update Stop Receiving Flag in Purchase Order Detail Via API Request

Palletize and Depalletize Using a REST API

Interfaces

Allow Extract File in Output Interface Configuration UI

Send Header Level Request Using Input Interface

Removal of Post to URL Job Type from Scheduled Job UI

Upload Messages in Bulk

Improvements to Re-Processing of Inventory History Transaction Records

Inventory History

New IHT Activity to Cancel Work Order

New IHT Activity to Unload Container

Enable Auto-Send of Inventory History

Enable Auto Process of Inventory History

Technical Enhancements

Provision Production Environments in Oracle Cloud Infrastructure (OCI)

Starting with the 19C update, Oracle WMS Cloud production environments are provisioned in Oracle Cloud Infrastructure (OCI), which is the latest generation of the Oracle Cloud.  In addition to patching not requiring planned downtime, now that Oracle WMS Cloud environments are hosted in OCI, product updates do not require planned downtime.

Steps to Enable

19C is an important update that requires specific actions by you:  

  1. For the production update, the URL, Hostname, and IPs will change.
  2. You will receive your update schedule and PROD environment configuration details via a separate email.  The login credentials for each will not change.

See the Update 19C Release Announcement for more details. If you need more information or have misplaced the email with your credentials, please contact support.

Key Resources

Adopt Oracle Autonomous Transaction Processing

All Oracle WMS Cloud environments now run on the Oracle Autonomous Transaction Processing version of the Oracle database.

In a mission critical application like Oracle WMS Cloud, Oracle Autonomous Transaction Processing Cloud Service brings customers unprecedented uptime including maintenance. The latest security patches are applied without compromising availability.

Next generation of on-demand resource scalability and auto-scaling are some of the features that can benefit Oracle WMS Cloud customers.  Do not worry again about seasonal high volume or running short notice promotions.  Gone are the days where your data growth or operational growth means downtime to upsize database hardware or any compromise on performance.

  • Oracle Autonomous Transaction Processing is built on top of world class Exadata infrastructure to provide extreme performance. This means faster execution of WMS business operations.
  • Oracle Autonomous Transaction Processing is a self-healing and self-driving database, which means self-tuning, auto-indexing and parallelism as data patterns change over time.
  • Oracle Autonomous Transaction Processing is a fully encrypted database that includes machine learning-based detection/prevention against any malicious activity.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Performance Optimization in Sequence Counter UI

When using WMS sequence counters, the system is capable of generating sequence numbers in multiple transactions concurrently while making sure that no number gets used twice. Oracle WMS Cloud sequence counters use specific database features to ensure this for optimum performance. With the change to the Oracle database there is a cosmetic difference in how these features work. The sequence numbers will be generated correctly and incrementally in sequence, but the value shown in “next sequence number” column may not increase by the “increment” value each time, but may jump by larger values.

For example, after fetching just one number, this column may increase by 20 and then stay unchanged for the next 19 numbers that are fetched. Then when the 20th number is fetched, it may increase by a further 20. Regardless of this visual difference, the actual numbers generated and used will honor the “increment” value each time.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Support for Enterprise Single Sign On with Oracle Identity Cloud Service

You can now use Oracle WMS Cloud with the Enterprise Single Sign On feature of the Oracle Identity Cloud Service.  This makes it easier for you to manage your sign on to multiple Oracle solutions.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Functional Enhancements

Receiving

Mark LPNs for Quality Control Using Receive LPN and Receive Entire Shipment Buttons

Currently in Oracle WMS Cloud, the inbound LPNs that are marked for quality check in the IB Shipment details are updating the LPN status to ‘Received’ instead of ‘Quality Check’ when the entire shipment is received from the UI. Additionally, on the IB Shipment details screen, the ‘Receive LPN’ action button is disabled if the shipment detail is marked for quality check. Some of the customers want to perform the quality check related operations from the UI.

As a part of update 19C, a new screen parameter ‘consider-mark-for-qc-flg’  is available in the "IBShipmentView"  UI Screen. Also, the ‘Receive LPN’ action button will not be disabled if a shipment detail has the quality check as yes. By default, the newly added screen parameter ‘consider-mark-for-qc-flg’ is set to ‘No’ and the ‘Receive Entire shipment’ at the IB Shipment header level, will mark the LPN status as ‘Received’ even if the shipment details has quality check as ‘Yes’. Also, receiving an LPN from the ‘Receive LPN’ Action button in the IB shipment details screen will mark the LPN status as ‘Received’.

When the newly added screen parameter is set to 'Yes' the system exhibits the followings:

  • If you click the ‘Receive Entire shipment’ action button at the Inbound Shipment header, the system marks the LPN status as ‘Quality Check’ if the shipment details has quality check as ‘Yes’.  
  • If you click the ‘Receive LPN’ Action button at the Inbound Shipment Dtl UI screen, the system marks the LPN status as ‘Quality Check’ if the shipment detail has quality check as ‘Yes’.

A corresponding IHT activity 72 gets generated for each detail present in an LPN on the Inventory History when an LPN takes the ‘Quality Check’ status.

Steps to Enable

The screen parameter ‘consider-mark-for-qc-flg’ should be set as ‘yes’ in the "IBShipmentView " UI screen.

Key Resources

New Mobile RF Single SKU Receiving Option

In normal receiving option the Oracle WMS Cloud prompts you to scan the LPN, followed by the SKU and enter the quantity. While receiving LPNs with same SKU and quantity you have to scan the SKU after scanning the ASN and provide the same quantity multiple times. To reduce the number of scan's and quantity entry we have introduced a new RF Module ‘rf.inbound.cwrfrecvsinglesku’ as a part of the version 19C.

With the new RF module, you need to scan the shipment first, followed by the SKU and provide the SKU quantity, before you scan the LPN. The SKU and the quantity stay populated along with the shipment. Hence you can keep scanning the LPNs alone until you need to change the SKU to receive the shipment.  The LPN receipt updates are done as soon as an LPN is scanned. The ‘rf.inbound.cwrfrecvsinglesku’ RF module is controlled by three screen parameters. The details of the parameters are highlighted below:

  1. default-sku-from-ASN – Selection type parameter with ‘Yes’ or ‘No’ (default value) option, defaults the SKU if an ASN contains single SKU. Prompts the control to the SKU field in case of multi SKU ASNs.
  1. allow_sku_not_on_shipment_flg- Selection type parameter with ‘Yes’ or ‘No’ (default value) option, controls if SKUs which are not part of a shipment can be received.
  1. default_qty (blank by default)- you can provide a default quantity which is defaulted for each SKU.

In update 19C, if the SKU being received is part of a shipment which has multiple details with different purchase orders, the system prompts the purchase order selection screen so that you can select the correct purchase order number while performing the RF single LPN receive transaction.

Additionally, the existing tolerance validation checks set from the ‘Shipment Type’ UI screen or the “allow_sku_not_on_shipment_flg” parameter get performed when the LPN is scanned.  Also, the ‘rf.inbound.cwrfrecvsinglesku’  RF module will follow the similar updates as the normal receiving operation and existing IHT records for Shipment updates, container updates, lHT related to lock codes will be written.

In case you receive an LPN with a different SKU, you can change the defaulted SKU by selecting the Change SKU buttons ‘CTRL-S’. However, to change the SKU, either the shipment should have multiple SKUs or the ‘allow_sku_not_on_shipment_flg’ screen parameter should be set to ‘Yes’. Additionally, all the LPNs should go through the current LPN check validations for the ‘rf.inbound.cwrfrecvsinglesku’ RF module as well. Furthermore, over receiving is allowed for the single SKU receiving mode. However, the transaction will honor the percentage set in the ‘Shipment Type’ UI.

NOTE: The newly introduced RF module ‘rf.inbound.cwrfrecvsinglesku’  supports only non cartonized shipments and single SKU LPN receipt. You should use the regular Receive Shipment RF screen if you need to perform the following tasks as these are NOT supported by the new RF module.

  • Cartonized Shipment detail
  • Pre-cartonized Pallet Receipt
  • Multi SKU LPN Receipts.
  • No Receiving XDOCK and Flow through allocation.
  • Palatalization (Upfront and Post).
  • Applying Lock (CTRL-L) as part of Receiving.
  • PO Based Receiving.
  • SKU Scan Mode of Receipt.
  • Launching QC and Inbound Sorting automatically post receiving.
  • Printing of LPN Labels automatically.
  • Entering in terms of packs or cases.
  • Generation of MHE messages
  • Default-lock code
  • Receipt of Transfer Shipment and relevant updates.
  • Infer-prepack-parent-item
  • Capture date type.
  • QC based on Vendor QC Percentage Rules.

Steps to Enable

You should enable the ‘default-sku-from-ASN’ screen parameter from the ‘rf.inbound.cwrfrecvsinglesku’ RF module to default the SKU and the ‘allow_sku_not_on_shipment_flg’ flag to receive SKUs not present in the shipment.

Key Resources

Receive Single SKU with Batch/Expiry/Attribute Number Tracked

When you are using the RF Receiving Single SKU transaction, you can now receive a SKU that is batch/expiry/attribute tracked.

NOTE:  When items that are batch/expiry/inventory attribute tracked need to be received, you must populate the corresponding batch number/expiry date/inventory attributes on the shipment details. The system does not allow you to scan the items with conflicting values and throws an error message. Also, the system does not allow you to receive items via this RF transaction if the item is serial number tracked.

When multiple SKUs are in an ASN, the system receives the items that do not have any conflicting batch/expiry date or inventory attributes.

The following table details the RF Receiving Single SKU behavior:

Scenario Behavior

If the ASN detail has a batch tracked SKU with an existing batch number populated and the batch management UI has the expiry as null for the batch...

The Batch management is not updated with the expiry date provided in the IB shipment. The IB Container takes the expiry date from the shipment detail.

If the ASN detail has a batch and expiry tracked SKU with an existing batch number populated with the expiry date and the batch management UI has the expiry as null for the batch...

The Batch management is updated with the expiry date provided in the IB shipment. The IB Container takes the expiry date from the shipment detail.

If the ASN detail has a batch tracked SKU with an existing batch number populated and the batch management UI has the expiry date for the batch...

The Batch management is not updated with the expiry date provided in the IB shipment. The IB Container takes the expiry date from batch management.

If the ASN detail has a batch and expiry tracked SKU with an existing batch number populated with the expiry date and the batch management UI has the expiry date for the batch number...

The Batch management is not updated with the expiry date provided in the IB shipment. The IB Container takes the expiry date from batch management.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Outbound

Perform Ship Load from RF Load OBLPN

Now you will be able to Ship a load from the RF. This will increase productivity in your warehouse by minimizing the additional time it takes to ship from the UI screen.  the ‘Load OBLPN’ RF transaction has a hot key ‘CRTL-P’ to perform ship load via RF transaction. By selecting  'CRTL-P',  you will be prompted to  ‘Accept’ or Do not accept’ options. Selecting 'Accept' will ship your load. If you hit CTRL-P, but there is not a load number in the transaction field, you are prompted to scan the load number to proceed further.

'IHT 3- Container Shipped' is recorded for each OBLPN associated with the shipped load. If an OBLPN is associated with asset, corresponding 'IHT- 58- Asset Shipped' gets generated for that particular shipped OBLPN. 'IHT-60 - Load Shipped File' is recorded for Load Shipped File generation.

NOTE: Facility parameter "AUTOLOAD_AND_SHIP" is not supported via the RF "Load OBLPN" Ship Load transaction. Generating multiple outbound file on shipload is also not supported from the RF.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Prevent Loading/Shipping a Load with No OBLPNs

In update 19C, you will not have the option to ship a load without an OBLPN in it. The system now displays an error message if you try to ship a load which does not contain any OBLPN. Additionally, in case you select multiple loads on the Outbound Load UI screen, the ‘Ship Load’ button will stay disabled irrespective of the number of OBLPNs present in each load selected.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Control Waving and Loading of Expired Inventory

There are situations where you may have expired inventory that you do not want to be shipped. Oracle WMS Cloud has a flag available in the Order Type screen that allows you to prevent expired inventory from being shipped out of the warehouse.

If you want to prevent expired inventory from getting allocated, picked, substituted, or shipped you can create orders with the order_type allow_expired_inventory_flag not selected. While performing allocation, the system looks at the expiration date of the inventory, and if the date is greater than the expiration date it won’t allocate this inventory.

If you want to pick expired inventory and ship it, you can create orders with the order_type allow_expired_shipping_flag deselected. While picking allocated inventory, the system will look at the order type flag. If the inventory is expired, the system will show the error "Inventory is expired".

WAVE SEARCH

From the Wave Template UI search option, while doing a wave search, if the new Allow Expired Inventory flag is set to yes, the system looks at the order and only select order types with the Allow Expired Inventory flag is set to yes, and selected these orders  to be allocated by that wave.

NOTE: Allocation of orders will be based on the configuration of the  allow_expired_inventory flag in both the Order Type and Wave Template search screens. Oracle WMS Cloud will only allocate inventory that have the same set up for the allow_expired_inventory flag.

There are occasions where you may pick or pack inventory on a different day  than the wave was run.  Now, the following transactions will check if the inventory to be picked or packed is part of an allocation that does not allow expired inventory.

  • Pack OBLPN
  • Pack OBLPN from IBLPN
  • Pick Cart
  • Pack NC Active
  • Direct Allocation
  • Pick and Allocate
  • RF Distribute LPN
  • RF Move
  • RF Repack

NOTE: If inventory being picked/packed is expired and the underlying order type does not allow expired inventory, the system alerts you with a message. During Cross Dock Receiving, when an LPN being received has expired-tracked items, and inventory is not expired, then any order types that have the "allow_expired_inventory" flag set to No will be considered.

PREVENT LOADING EXPIRED INVENTORY 

You can also prevent loading expired inventory with the allow_expired_inventory_flag using the following transactions:

  • RF Load OBLPN
  • Load LPN API
  • Auto Load If the allow_expired_inventory_flag is disabled, the LOAD LPN API will fail and alert you with an error message that inventory is expired.

STANDALONE AND WAVE BASED REPLENISHMENT 

So that you can control allocation of expired inventory during standalone order based replenishment and wave based replenishment,  from the Wave Template UI search option, you can select/unselect the Allow Expired Inventory flag.

  • If your replenishment rule has Allow Expired Inventory set to Yes, the system allocates expired inventory to the replenishment location during allocation.
  • If your replenishment rule has the Allow Expired Inventory set to No, the system will not allocate expired inventory to the replenishment location during allocation.

Steps to Enable

Select the Allow Expired Inventory flag in the Order type and Wave Template

Key Resources

Control Packing of One or Multiple Orders with the Same Destination Facility

Oracle WMS Cloud now includes the new facility parameter "SHIPTO_DEST_HANDLING_FOR_DISTRIBUTION_MHE_PACKING" which allows you to handle ship to and destination facility checks while performing packing through the FROM_MHE_DISTRIBUTION_OBLPN_PACK Interface. This parameter allows you to control the packing of one or multiple order(s) into the same OBLPN when the order's destination facility is the same. This is true when the facility parameter is set to Match Destination Only.

The facility parameter "SHIPTO_DEST_HANDLING_FOR_DISTRIBUTION_MHE_PACKING" has two parameter values:

  • Match Destination Only: The behavior remains unchanged when the system allows the packing of one or multiple order(s) into the same OBLPNs as long as the underlying destination facilities for the order are the same, irrespective of whether the ship to facility is the same as the destination facility.   
  • No Value Configured (Blank): The system allows the packing of one or more orders into the same OBLPN when the destination facility and ship to facility combination is the same for all of the orders determined to be packed.

The following table describes the facility parameter (SHIPTO_DEST_HANDLING_FOR_DISTRIBUTION_MHE_PACKING) value behavior for different destination and ship to combinations:

Parameter Values Single Order Present Shipto <> destination Multiple Candidate Orders with Same Destination and Different Ship To Multiple Candidate Orders with different Destination and same Ship To Single Order with dest=shipto
Match Destination only Allow Packing Allow Packing Do not Allow Packing Allow Packing
No Value Configured (Blank) Default behavior Allow Packing Do not Allow Packing Do not Allow Packing Allow Packing

Steps to Enable

  1. From the Facility Parameter UI, click the Parameter Key (SHIPTO_DEST_HANDLING_FOR_DISTRIBUTION_MHE_PACKING).
  2. Click Edit.
  3. In the Parameter Value field, enter Match Destination Only. Otherwise, No Value specified in the fields triggers different mechanisms in the system as mentioned above.
  4. Click Save.

Key Resources

Inventory Management

Prompt Location in RF Modify Cancel OBLPN

Currently, once you modify or cancel an Outbound LPN, the corresponding Inbound LPN created does not have a location and stays in received status. The option to scan a location for a created inbound LPN will help to trace LPNs in the warehouse..

In update 19C, a new parameter “Prompt-Location-Cancel-Oblpn"  is available in the "rf.outbound.cwrfmodcancelobcntr" screen to identify the scanned IBLPN location if the parameter selection is marked as Prompt location. The location type for the corresponding IBLPN in this case should be the following:  Active, Reserve, Drop and Dock.

By default, the screen parameter is marked as blank which implies nothing is selected. If the parameter value is set to Blank or ‘Do Not Prompt Location’ the scan location option will not be prompted to you after scanning the IBLPN once the OBLPN gets cancelled/modified.

If the parameter value is set to ‘Prompt Location’ the scan location option will be prompted to you after scanning the IBLPN once the OBLPN gets cancelled/modified. Corresponding locate LPN updates will happen once you scan the location. You can not skip the location field as it is  mandatory.

Steps to Enable

The screen parameter “Prompt-Location-Cancel-Oblpn" should be set as ‘Prompt Location’ from the RF "Mod cancel OBLPN" screen.

Key Resources

Customize Reference Text in RF Direct Consume LPN Transaction

Currently, the Consume LPN API allows you to provide a reference text, such as a transaction reference number that may be useful for External Host Systems. Now, you are able to provide a reference text or information when consuming an IBLPN using RF-Direct Consume LPN.

As part of 19C, a new parameter 'Display Ref text' is available with the selection type options "Yes/No". If set to Yes, You can view this reference text before scanning the IBLPN field in the RF screen. By default, the selection type is set to No.

After the LPN is scanned, you need to provide the reason code to directly consume the LPN. The reference text captured is populated in the “Ref value 3” column of the Inventory history screen with the IHT activity 2 - Container Consumed.

Steps to Enable

  1. Go to Display Ref Text" in the "Direct Consume LPN" RF screen.
  2. Click Selection > Edit > Set the  'Display Ref text' parameter type to Yes.

Key Resources

Enhancements to Split Inbound Container Transaction

Currently the “rf.inbound.cwrfsplitcntr” module allows you to split the contents from one LPN to another LPN by inventory. In update 19C, we have expanded the ability to perform Split to transfer all the contents without scanning the SKUs. Additionally, if you have to transfer all the units of an individual SKU, you can perform that without entering the quantity. Productivity improvements have been made along with prompting for batch and expiry enabled items. We have updated the module with a new screen parameter ‘split-mode’ of selection type.  The screen parameter have the following options

  1. By Inventory (default behavior)
  2. By SKU
  3. All SKUs

If the newly added screen parameter ‘split-mode’ is not configured the system will split the LPNs by inventory as a default selection. Earlier, in Oracle WMS Cloud, if inventory was tracking attributes, the system prompted for relevant inventory attributes that were being tracked. Now when split_mode is performed by inventory, the system prompts for the batch number/expiry date if the item is tracking batch or expiry dates.. Additionally, the batch prompt comes if the scanned SKU has multiple batches or different expiry.

When the parameter ‘split_mode’ is set with "By Inventory" and the ‘to-lpn-confirmation-mode’ is set as ‘Confirm before SKU Scan’, the system displays the From IBLPN and To IBLPN followed by the SKU scan in RF Split IBLPN screen. If the ‘to-lpn-confirmation-mode’ is set as ‘Confirm for each Split’, configuring the screen parameter split_mode’ with "By Inventory" the system displays the SKU scan right after the source LPN scan. Upon the SKU scan you need to provide the batch number (in case the SKU is batch number tracked) followed by the move quantity and the destination LPN scan.

Scanning the source LPN number populates the SKU if the LPN contains a single LPN. You need to provide with the quantity you want to split and the destination LPN number to perform the split operation. In case of multi SKU LPN, you need to scan the SKU followed by the quantity and the destination LPN number. You can skip the current SKU by selecting the hot key ‘CTRL-P’ and select the next SKU content present in the LPN. The hot key ‘CTRL-V’ now shows the values of the inventory attributes available instead of the scanned attributes.

If the screen parameter is configured with the ‘All SKUs’ option, the RF Split IBLPN transaction transfers all the contents to the targeted LPN scanned. The destination LPN value stays populated so that you can transfer contents from multiple source LPN to a single destination LPN. If the source LPN has serial numbers, all the underlying serial numbers will be transferred to destination LPN. If source LPN has serial number discrepancy a message will be displayed. If the destination LPN have SKU with the same batch number, expiry date, Inventory attributes, Case Qty, Pack Qty, Manufacturing Date and Priority Date as the source LPN; then the system will merge them into single record.

When the parameter ‘split_mode’ is set with ‘By SKU’, the entire inventory of the scanned SKU gets transferred from the source LPN to the destination LPN. With the option selected as ‘By SKU’, when the parameter ‘‘to-lpn-confirmation-mode’ is set as ‘Confirm before SKU Scan’, you need to scan the source IBLPN and destination IBLPN followed by the SKU in RF Split IBLPN screen. If the ‘to-lpn-confirmation-mode’ is set as ‘Confirm for each Split’, the system displays the SKU scan right after the source LPN scan. Upon the SKU scan you can scan the destination LPN scan to move all the inventories of the scanned SKU. If the source LPN has serial numbers, all the underlying serial numbers will be transferred to destination LPN. If source LPN has serial number discrepancy a message will be displayed. If the destination LPN have SKU with the same batch number, expiry date, Inventory attributes, Case Qty, Pack Qty, Manufacturing Date and Priority Date as the source LPN; then the system will merge them into single record.

NOTE:

  • The screen parameters qty-entry-mode and split-uom are not considered when the screen parameter split_mode is configured with ‘By SKU’ or with 'All SKU' and the system does not prompt for attribute scanning as all the inventories of the scanned SKU get transferred.
  • Existing validation on the capacity check is honored and the validation takes place only if the perform-capacity-check screen parameter is configured as ‘yes’.
  • Existing IHT records for split container will continue getting generated irrespective of the screen parameter options.

Steps to Enable

Select the options available for the screen parameter split_mode on the “rf.inbound.cwrfsplitcntr” module to enable the updated feature. However, if the screen parameter is not configured, by default the system will split the LPNs by inventory honoring corresponding updates.

Key Resources

New Inbound LPN Type Set Up

LPN Type Updates

When you define your LPN type, the system validates the SKU dimensions associated with the LPN type dimensions during cartonize LPN. Also during Directed/Manual putaway, dimensions for the scanned IBLPN LPN type are evaluated for location dimensions.

A new field, LPN Type, and a new button Update LPN Type are now available in the following screens:

  • IBLPN Inquiry
  • IB Shipment Detail

In the IB Shipment UI, LPN Type is added to the following button pop-up screens:

  • Cartonize
  • Cartonize LPN by Cases

NOTE: LPN Type is not mandatory in the Cartonize LPN by Cases screen. LPN Type is also visible from the search option in the IB Shipment and IBLPN screens. This LPN Type drop-down contains a list of available LPN types from the facility.

UPDATE LPN TYPE BUTTON 

You can update the LPN Type for Inbound LPNs with all statuses except for Consumed, Cancelled, or In receiving.

NOTE: If the LPN types isn’t set up with correct values, the associated item will not be able to fit into an LPN type. To help prevent this from happening, capacity checks are ignored in the system for any dimensions that are set to zero.

Once the LPN type is set successfully for an Inbound Shipment, the following message displays, “Selected IBLPNs are updated with LPN Type: XYZ”

When you click Update LPN Type for the selected record(s), a new window opens displaying a list of LPN types configured for the logged in company.

PERMISSIONS 

The Update LPN Type button is not assigned to any role. From Group Configuration, you must set the permissions set Container / Update LPN Type.

UNSET LPN TYPE FOR IBLPN 

During daily warehouse operations, in cases where you may have mistakenly set the LPN type on the IBLPN or you want to define dimensions for the IBLPN and use those values for computation purposes, you may need to clear the LPN type defined for the IBLPN. You can set or clear the LPN type from the Set LPN type pop-up.

When you click Submit without defining an LPN type value, a warning message displays. You can click OK to remove the LPN type for the selected record in the IBLPN Inquiry Screen.

NOTE: You can remove the LPN type for all statuses except IBLPNs in Consumed or Cancelled status.

When an LPN type is removed for only some selected records, the system displays the error message "LPN type is cleared for only few selected records." Next, the detail section displays a list of IBLPN's where the LPN type is not cleared due to invalid status.

RF UPDATE LPN TYPE 

You can also scan an IBLPN from the RF Update LPN Type screen to update the LPN type for an IBLPN. This helps with critical dimension checks during putaway.

From the RF Update LPN Type screen, once you select "Validate Critical Dimension" if all the item unit dimensions are less than or equal to the LPN type dimensions, then the LPN type is updated for the respective container.

NOTE: If the item unit dimensions are greater than the LPN type dimension the following error message displays: "Item:%sku% unit dimensions exceeds LPN Type:%Scanned LPN Type% dimensions".

REMOVE DIMENSION VALIDATION WHEN DIMENSION IS SET AS 0   

Now, validation checks are removed when dimensions (length, width, height) are set to '0' for the TO entities for that dimension.

This update is visible in the following screens:

  • 'Inbound Shipment Detail' UI - Update LPN type 
  • 'Inbound Shipment Detali' UI - Cartonize LPNs by Cases- Update LPN type
  • 'IBLPN Inquiry' UI - Update LPN type 
  •  Edit Inbound Shipment Detail Transaction

You have the option to store items for LPNs where one of the dimensions is '0'.

For example:

If an item has the dimensions as (L= 4, W= 3, H= 2) and an LPN has the dimension (L= 0, W= 3, H= 2), then the system should allow you to place the item in the targeted LPN.

In order to determine the dimension:

The system compares the Length,Width, and Height of the LPN type for the LPN against the unit dimensions for each item (unit_len, unit_width, unit_height) associated with the container.

If the LPN type is not defined for the IBLPN, then the system considers the IBLPN dimension (L/W/H) to compare values.

NOTE: If all of the dimensions for the 'TO' entities are set to '0', then no capacity check is performed.

Steps to Enable

To enable the Update LPN Type button, set permission Container / Update LPN Type.

Key Resources

Replenishment

Configure Destination Location Type in Standalone Replenishment

Today when we configure a standalone replenishment template, the destination location type is applicable for replenishment is both reserve and active. Previously, you could not control which location type to replenish in standalone mode.

Now, in Standalone Replenishment, you can configure the Destination Location Type to be either Reserve, Active, or both.

NOTE: This update is applicable for standalone replenishment only and not wave-based replenishment. This new Destination Location Type drop-down is available from Replenishment Template View, in the Replenishment Rule UI. The default is Reserve and Active.

Destination Location Type

Description

Reserve and Active

The designated destination location types determined for replenishment can be either Reserve or Active for the area corresponding to the Area and Replenishment zone provided on the Replenishment Template.

Reserve

The designated destination location types determined for replenishment will be Reserve location only for the area corresponding to the Area and Replenishment zone provided on the Replenishment Template.

Active

The designated destination location types determined for replenishment will be Active location only for the area corresponding to the Area and Replenishment zone provided on the Replenishment Template.

Steps to Enable

From Replenishment Template View, go to Replenishment Rule and select an option from the Destination Location Type drop-down.

Key Resources

Round Up Allocations for Replenishment

During Replenishment with a picking wave, sometimes even though inventory is available in the source location, the system may not allocate inventory for replenishment when the replenishment UOM is LPNs, cases, or packs (where the order need is not a multiple of the source location’s inventory quantity.) Due to this behavior in the system, the underlining orders may not get allocated for picking, especially when the partial allocation flag is disabled on the order type for the underlying order. This results in order shorts. Prior to update 19C, Oracle WMS Cloud would allow you to replenish more than the location’s capacity if the ignore capacity for last permanent location flag was set to yes on the replenishment template. Even though the system allowed you to replenish more than the locations capacity for the last location, the order need would not be met if the replenishment UOM was set to LPN’s/Cases/Packs. The following is an example of the prior system behavior:

Example: Ignore Capacity for Last Permanent Location Flag is set to Yes

  • The Order Need = 110
  • Destination Active Location’s Max: 100
  • Current Inventory in Destination Active is: 0
  • Source Location has three LPN’s with 60 units each.

Result: The system would allocate only 60 units as each LPN had 60 units and the remaining need of 40 could not be allocated due to the LPN UOM. This would result in the Sales Order not getting satisfied.

* Even if the order need is 90 less than the location’s max, the system would replenish only 60 units.

In order to overcome instances of orders not getting satisfied, the Round Up One UOM flag is now available in Oracle WMS Cloud (19C) in the Replenishment Rule Header. The Round Up One UOM flag allows you to replenish beyond the need by one extra UOM (LPNs/cases/packs) for all of the eligible locations. When the Round Up One UOM flag is configured in the Replenishment Rule Header, the system replenishes by one extra UOM compared to the outstanding need of the location (see example below). When the Round Up one UOM flag is combined with the Ignore Capacity for Last Permanent Location Flag, the required need is replenished to the destination location when the replenishment UOM is LPNs/cases/packs. If the Ignore Capacity for Last Permanent Location Flag is set to no and the Round Up one UOM flag is enabled, then the destination location is replenished by one extra UOM when the need is not an integral multiple of the LPN/case/pack quantity.

When the Round Up One UOM flag is set to yes and there are multiple permanent locations to be replenished, replenishment occurs until the order need or location max is met and can potentially exceed by one UOM. For Dynamic Active locations, replenishment occurs until the order need is met and can exceed the order need by one UOM. You can use the Round Up one UOM flag when the location’s capacity is less and the order need is more and when the order need is not an integral multiple of the LPN/pack/case quantity. You can use the Multi-level Replenishment Module (introduced in 18C) for excess inventory that needs to be replenished beyond a location’s max.

NOTE: During the initial release of this feature in 19C, the Round Up One UOM flag worked in conjunction with the Ignore Capacity for Last Permanent Location flag for the last permanent location for the SKU. As an update to 19C in the 9B patch bundle, the Round Up One UOM flag is now applicable even for initial locations while replenishing when there are multiple candidate locations to be replenished. This new flag will only work if the replenishment UOM is either LPN, cases, or packs.

The following examples illustrates the behavior of the updates to the Round Up One UOM flag:

  • Order need = 280
  • Two Candidate Permanent Locations for replenishment = Location 1 and Location 2
  • Current Inventory destination Locations = 0
  • Replenishment UOM =LPN
  • Source Reserve locations all have LPNs with 60 units each.

Based on the above conditions, the following table depicts the behavior of the system when the Round Up One UOM and Ignore Capacity for Last Permanent Location flags are enabled/disabled:

Round Up One UOM and Ignore Capacity for Last Permanent Location flags = Yes

During Replenishment, the system allocates =>

Location 1 = 120 units are allocated for replenishment by adding one extra UOM.

Location 2 = 180 units are allocated for replenishment. Since the Ignore Capacity for Last Permanent Location flag is set to yes, the remaining need of 180 units is replenished.

Result

Since the Round Up One UOM flag is enabled, we replenished 120 units to location-1 (by one excess UOM). The outstanding need of 180 units was replenished to location-2 since the Ignore Capacity for Last Permanent Location flag was set to yes.

Round Up One UOM and Ignore Capacity for Last Permanent Location flags = No

During Replenishment, system allocates =>

Location 1 = 120 units are allocated for replenishment by adding one extra UOM to Loc 1.

Location 2 = 120 units are allocated for replenishment by adding one extra UOM to Loc 2.

Result

The total order need is 280, whereas the system replenishes only 240 units to the permanent location. Since the Ignore Capacity for Last Permanent Location flag is set to No, the system replenished beyond the location’s max by one extra UOM.

Steps to Enable

From the Replenishment TemplateReplenishment Rules header, enable the Round_up_one_uom_flag.

Key Resources

Consider Weight Check During Replenishment

Oracle WMS Cloud now includes a weight based check in the replenishment rule in the existing capacity check method. These weight based check includes two fields in the Capacity Check Method drop- down in the replenishment rule of replenishment template UI.

  • Weight, Fall Back to Units
  • Volume, Weight, Fall Back to Units

WAVE BASED REPLENISHMENT

If the weight based capacity check is done during allocation from wave based replenishment and you select the replenishment rule with capacity check method = "Weight, Fall Back to Units", then system consider the location max weight in Units for capacity check. However,  if location max weight is greater than zero, then the quantity to replenishes =< available capacity on the location with respect to max weight & max units.

If the weight based capacity check is done during allocation from wave based replenishment and you select the replenishment rule with capacity check method = " Weight, Volume, Fall Back to Units", then system consider the location max weight in Units & Volume for capacity check. However,  if location max weight is greater than zero, then the quantity to replenishes =< available available capacity on the location with respect to max weight, max volume & max units.

STANDALONE REPLENISHMENT

If the weight based capacity check is done during allocation from standalone replenishment and you select the replenishment rule with capacity check method = "Weight, Fall Back to Units", then the system considers the location max weight in Units for capacity check. However,  if location max weight is greater than zero, then the quantity to replenishes =< available capacity on the location with respect to max weight & max units.

If the weight based capacity check is done during allocation from standalone replenishment and you select the replenishment rule with capacity check method = " Weight, Volume, Fall Back to Units", then system considered the location max weight in Units & Volume for capacity check. However,  if location max weight is greater than zero, then the quantity to replenishes =< available available capacity on the location with respect to max weight, max volume & max units.

The weight based capacity check is done during execution of Replenishment template, when  capacity check method is defined based on weight and Replenishment Trigger Mode is selected to any of below defined value:

  • Minimum Capacity
  • Percentage of Max
  • Order Based Replenishment
  • Reactive Replenishment : When you scan the location using RF:Reactive Replenishment for replenishment, perform capacity check based on weight, and the replenishment rule for reactive replenishment triggered is configured with:
    • Weight, Fall Back to Units: System considers the location max weight in Units for capacity check. However,  if location max weight is greater than zero, then the quantity to replenishes =< available capacity on the location with respect to max weight & max units.
    • Weight, Volume, Fall Back to Units: System considers the location max weight in Units & Volume for capacity check. However,  if location max weight is greater than zero, then the quantity to replenishes =< available available capacity on the location with respect to max weight, max volume & max units.

REPLENISHMENT TASK EXECUTION

You can perform weight based capacity check during execution of replenishment task, even though capacity check happens during allocation. In the mean time when replenishment task is picked for execution, there are chances that the target location may be filled with inventory from different  transactions, for example, Locate LPN, Putaway. Hence, replenishment task execution Weight based capacity check takes places when corresponding replenishment rule is configured with capacity check:

  • "Weight, Fall Back to Units" 
  • "Volume, Weight, Fall Back to Units"

During replenishment task execution, the weight based capacity check also considered for following  the task types.

  • REPLEN-CS-PK-UNITS (Replenishment of Cases, Packs & Units)
  • REPLEN-LPN   (Replenishment of Full LPN)
  • Internal Bulk Pick (Consolidate & Replenish)

SUPPRESS CAPACITY CHECK DURING END LPN OF CONSOLIDATE AND DISTRIBUTE TASK EXECUTION 

You can also suppress the capacity check during end LPN (Intermediate LPN) when you execute Consolidate & Replenishment task. During consolidate & replenishment task execution, system does not perform capacity check (Units/Weight/Volume) at the end LPN (Intermediate), but it display the allocated quantity. When you scan the Quantity to replenish, system then performs capacity check on following scenarios:

  • If replenishment location has capacity to move all the allocated inventory, then replenishment takes place.
  • If replenishment location doesn't hold the incoming inventory, then system displays Insufficient Capacity error message.

REPLENISHMENT RULES 

  • Oracle Warehouse Management Cloud now perform critical dimension checks while determining candidate locations for replenishment.
  • You can enable Perform Critical Dimension Check from the Replenishment Template View, Replenishment Rules screen so that you can determine replenishment space available for incoming IBLPN/Items. 
  • During allocation from Standalone replenishment, Wave Based, and Reactive Replenishment, as long as Perform Critical Dimension Check is enabled in the replenishment rule, the system will perform LPN type critical dimension checks of the LPN with location dimensions.

While replenishing to Reserve locations, we consider the LPN type or length/width/height of the container and for Active locations we consider the unit dimensions.Steps to enable: configure the replenishment rule capacity check.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Putaway

Consider Dimension Check During Putaway

Putaway and replenishment now perform a critical dimension check (length, width, height) of the item and LPN to ensure that it does not exceed the dimensions of the stock location.  This may be important for irregular shaped items or LPNs (e.g. long and skinny).

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Consider Weight Check During Putaway

Whenever any inventory reached the warehouse, system did not have an ability to check if the location could hold the weight of the incoming inventory. Because of this, any inventory that was brought would overload any rack types in the locations that resulted in damage to the location and sometimes it would be becomes difficult to remove heavy containers(inventory) from locations. Thereby, system did not an ability for capacity checks based on weight that location can hold.

To overcome these scenarios, Oracle WMS Cloud now allows you to evaluate container (inventory) weight with location weight during Putaway and Replenishment, so that the system can direct you to an appropriate location available to hold the incoming inventory within the defined weigh. You can search Locations by most empty (by weight) and least empty (by weight) during directed putaway.

This enhancement is implemented in the following categories:

LOCATION

On the location UI, two new fields "Max Weight" and "Min Weight" columns are introduced that allows you to configure the maximum and minimum weight on location that helps you in perform capacity check during putaway and replenishment. For you to be able to process the location interface file with max_weight & min_weight fields, the location interface file is now expanded with two new columns "max_weight" & "min_weight". The supported file format are:

  • Excel
  • XML (Input interface & Init stage interface)

PUTAWAY - WEIGHT BASED CAPACITY CHECK

During directed putaway,  when you scan a LPN/Pallet, system considers weight capacity check to determine the location. Similarly, when you scan location during suggested putaway, weight based capacity check is done against the scanned location.

DIRECT PUTAWAY FOR LPN/PALLET

Oracle Cloud WMS is enhanced to perform capacity check during directed putaway for Pallet. That is, when you perform directed putaway, system directs you to an appropriate location that can hold an incoming pallet into the respective location.

On scanning the LPN/pallet, system determines the location for putaway based on putaway method priority, validates location max weight with pallet weight and considers the location eligible. Also, system encourages you to perform volume based capacity check on items during directed putaway of pallet. On scanning LPN/pallet and determining the location for putaway based on putaway method priority, system validates location max volume with pallet volume and consider the location to be eligible.

Putaway Search Mode to include weight based search

In the Putaway Search Mode drop-down, two new modes “most empty by weight” and “least empty by weight” are introduced that help you to define your putaway search.

SPLIT LPN INTO ACTIVE LOCATIONS

During Directed Putaway, when you are splitting LPNs into Active Locations (with the "multi-sku-lpn-mode" parameter set to "Split LPN Into Active Locations"), and then you scan the LPN, the system will validate the item’s unit weight (sum of items unit weight present in the container) with the location maximum weight for the location determined through putaway method priority.

If the location’s max weight has the capacity to accommodate all of the items (sum of all items unit weight for the scanned LPN), then putaway will happen for that respective location.

Also, Split enabled putaway to active locations is enhanced to perform capacity check based on volume.

WEIGHT-BASED VALIDATION DURING SUGGESTED PUTAWAY 

Once you implement suggested putaway, the system allows you to validate location max weight against the IBLPN/Pallet weight and considered the location to be eligible.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Sorting

Validate Critical Dimensions in Sorting

A new screen parameter Validate Critical Dimension is available in the RF IB Sort module to perform critical dimension checks during IB Sorting. When Validate Critical Dimension is set to Yes for IB Sorting, then the system performs critical dimension checks for LPNs being sorted with the Location when putaway logic is called to determine the location. If the location dimension is less than the LPN type dimension, the message "Location dimension is less than LPN type dimension" displays to make you aware.

Steps to Enable

Set up screen parameter validate-critical-dims to yes in RF IB Sorting.

Key Resources

Label Designer

Image-Based Barcode Support in Label Designer

Oracle WMS Cloud now includes support in Document Label Designer for image-based barcodes and QR codes which can be used on labels and documents.  This is helpful for GS1 labels and documents.

The following functions have been added to Document Label Designer:

  • Python expressions for GS1 now work with image-based barcodes.
  • Compatibility for Linear Barcode Code 128 and Data Matrix.
  • AI Code Function support for ZInt, Zebra, and ID Automation.
  • QR Code Support.
  • Support for Linear And Data Matrix code.
  • New GS1 Code function support that does not require you to have to choose a particular function for a particular output such as Zebra, ZInt, or ID Automation.
  • Adjusted font scaling for pdf documents that are using the ID Automation font.

Document Label Designer now includes an examples template called gs1_doc_sample for GS1 barcodes available from the standard template list. If you select this standard template, Label Designer creates a template with a whole set of example barcode expressions for GS1 and also examples for doing sample data expressions.

The following are examples of expressions you can use for Linear and 2D barcodes:

  • Use this expression for Linear Barcode Code 128 Text Barcode:
    • gs1_code("FNC1") + gs1_ai("01") + "98898765432106" + gs1_ai("3202") + "012345" + gs1_ai("15") + "991231"

  • Use this expression for 2D Barcode Data Matrix Text Barcode:
    • gs1_code("FNC1") + gs1_ai("01") + "98898765432106" + gs1_ai("3202") + "012345" + gs1_ai("15") + "991231"

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

New Fields and Barcode in Document Label Designer

A new feature is available in Document Label Designer that allows you to turn off dynamic scaling for font based barcodes, so that you have an extra option to fine tune barcode sizes. You also now have the option to toggle to a view that renders/prints sample data.

After you select barcode and you are using the Edit Barcode pane, the following fields are now available to assist you with more detailed barcode editing:

Edit Barcode Field

Function

Dynamic scaling

Allows you to do dynamic scaling for Zebra text-based label barcodes versus fixed sizes.

NOTE: when you turn off Dynamic Scaling, the barcode is a fixed barcode size and will not resize with the data.

Sample data

Test expressions for print preview to test the template.

Sample data as expression

Test expressions for print preview to test the template.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Print Preview in Document Label Designer

VIEW AND PRINT SAMPLE DATA 

You can now actively test out your expressions in print preview without having to print a label while you are designing your label template.

Once you have selected a barcode or text element, you can use the Sample data option in Edit Barcode and put in the data you want to see for print preview. This sample data is a useful feature if you are setting up a new warehouse and you don’t have any existing data.

NOTE: Currently print preview does not work for languages (such as Arabic) that read right to left. For these languages, print your label to confirm correctness.

If you use the Sample data as expression option, then you can use the same data to workout your expressions however, there is no data lookup in the sample data for the print preview because there is no existing data.

NOTE: expressions need to be test written with the data already looked up in the expression

For example:

Instead of adding "\~container.container_nbr" in a data expression like you can in a real expression, you should add "LPN000001."

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Support Pallet Labels in Label Designer

Well designed pallet labels can help to speed your product’s time to market, giving you better inventory control and time and cost savings. Oracle WMS Cloud now includes the option to design OB Pallet, IB Pallet, and Blind Pallet Labels from the Label Designer UI. You can access the OB Pallet Label template from the Standard Templates drop-down.

You can also access the OB Pallet, IB Pallet, and Blind Pallet labels you have created in the Label Template View UI, (Label Type drop-down.)

NOTE: Oracle WMS Cloud only supports printing Pallet Labels from the Web UI and via REST API.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Cycle Count

Support Tasking Mode for Cycle Count by Number of LPNs

Updates in cycle count allow you to perform cycle count for counting number of LPN's through task creation rules. This helps you in creating tasks for reserve locations, so that you can cross verify the number of LPNs without scanning or to break open the boxes.

Some of the important features of the enhancements are:

TASK CREATION RULE 

  1. Introducing new task type "CC-LOCN-LPN-CNT" where you can create task type for location type "Reserve" only. 

NOTE: An existing task types CC_LOCATION and CC_LOCATION_DTL also creates task and underlying module associated with such tasks are performed at detailed count.

  1. You can create tasks with task type of "CC-LOCN-LPN-CNT" only if the selection criteria provided for the task rule sequence results in eligible reserve locations.
  2. You can create records in CC Run View for tasks created based on new task type "CC-LOCN-LPN-CNT".
  3. You can proceed with CC tasks creation until you reach the Max Number of Tasks that is configured on the task template.
  4. If you create tasks type CC-LOCN-LPN-CNT and "CC-LOCATION"/"CC-LOCATION-DTL", and task creation template has sequences for both the task types, then system creates the task with task type CC-LOCN-LPN-CNT and then proceeds to create "CC-LOCATION" or "CC-LOCATION-DTL" as per the sequence rule. The tasks initially created by the system of task type CC-LOCN- LPN-CNT will be canceled and new tasks get created with task type "CC-LOCATION" or "CC-LOCATION-DTL".
  5. When task creation template has multiple sequences pointing to LPN Count, system still creates tasks of type "CC-LOCN-LPN-CNT" based on the first priority sequence that has different selection criteria than the second sequence.

IN TASKING MODE 

  1. Introducing an ability in the system to create tasks with screen "rf.inbound.cwrfccresvnbrcount", so that you can count the number of LPNs through tasking mode. System prompts you to confirm the location if you execute in tasking mode.
  2. When the screen is invoked in tasking mode, system prompts you to confirm the location and performs location validation.
  3. Appropriate WMS Activity records is written when the count is performed with/without any discrepancy separately.

DEFERRED INVENTORY ADJUSTMENT 

  1. Through this enhancement, let's says there is a task type of an existing CC task that is less detailed than the task type configured in the trigger management screen. In such scenarios, system cancels an already existing CC task and create a new one with the task type configured in the trigger.
  2. Generally, system cancels the task of type "CC-LOCN-LPN-CNT", if the trigger invoked has more detailed count. That is, system gives a precedence for task "CC-LOCATION-DTL" and "CC-LOCATION".
  3. System cancels an existing task whose Status = HELD/Ready and creates a new detailed task for following CC trigger
    1. Recount Location
    2. Recount Location Detail
    3. Approve "Location Mismatch" record
    4. Set Location "To be counted" from Location screen
    5. De-allocate IBLPN from UI
    6. Short pick full LPN
    7. Alternate location for Putaway
    8. Substitute Lpn from different Location

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Cycle Count Approval Process

If your warehouse has low cost items that do not require a Cycle Count approval process, you can now configure your cycle count adjustment threshold for higher cost items or other specific attributes that you need to approve. All the adjustments related to items such as lower cost, or those that are not meeting your criteria can be set for automatic approval.

You can skip writing CC adjustment records and post inventory adjustments even though the company and facility settings are configured for deferred mode. Now, in deferred mode, you can set up tolerance rules for cycle count approval regardless of the count variation.

For example, while counting in deferred mode, let’s say "bolts", you find a variance of 1 unit. Supervisors no longer have to approve the cycle count if it falls under the tolerance setting set in the CC Adjustment Approval Rule.

The following is the configuration needed for the Cycle Count Approval process:

  1. A new rule screen CC Adjustment Approval Rule that allows you to create your own rule where you can define your criteria/attributes and tolerances for item approval.

The CC Adjustment Approval Rule detail screen consists of the following fields that allow you to define thresholds:

  • Approval Rule Name - You can set the rule name for CC approval.
  • Priority - Specifies the sequence.
  • Approval choice - Select the value from the drop-down, "Manual Approval", or "Auto Approve based on Tolerance".
  • Approval based on - Select the approval type from the drop-down: "Quantity" and "Cost".
  • Value or Percentage - Select the approval type from the drop-down: "Value" or "Percentage". If you select percentage, two fields are enabled for you to specify the minimum and maximum quantity tolerance.
  • Tolerance Value - The field is enabled only when "Value" is selected. You can specify the tolerance, if the delta in the "total adjusted cost" is above/below the tolerance value, then the system processes for approval.
  • Tolerance check by - Select the type of tolerance. If "Inventory" is selected, then the tolerance check is at the inventory level in the Location/IBLPN. If "SKU" is selected, then the tolerance check is at each SKU level in the Location/IBLPN.

A new button "Selection" is available in the Cycle Count Adjustment Rule Detail screen. This screen allows you to define your rule grouping criteria based on item and location related fields.

The approved records for this rule display the "CC Deferred adjustment" screen.

  1. Changes to the RF Cycle Count IBLPN and RF Cycle Count Location screens include:
  • Rename screen parameter "auto-approve-mode" to "deferred_approval_mode". Deferred_approval_mode consists of the following values where you can select either and set your preference to display the records in the "CC Deferred Adjustment" screen. The values are:
    • Manual approval (Default)
    • Auto approve
    • Skip CC deferred adjustments
    • Approval by Rule
  • The new screen parameter "auto-approval-rule-name".  Auto-approval-rule-name checks for the rules before writing to the "CC Deferred Adjustment" table and wait for approval when the screen  parameter is set to "Approval by Rule".
  1. New columns are added at the header level in the CC Deferred Adjustment screen to display the values stored in the respective database columns to identify the source of approval for the CC deferred adjustment record. The columns include:
  • Eligible for Auto Approval: Search by selecting any of the value and the, respective CC deferred adjustment records displays.
  • Rule Evaluated: The default value for this field is blank. Search with the rule name, and the system displays respective CC deferred adjustment records containing the respective rule name.
  • Approval Rule Choice Result: Search by selecting any of the following values, and the respective CC deferred adjustment records displays.
    • Tolerance Check Passed
    • Tolerance Check Failed
    • Manual Approval, and
    • None

Steps to Enable

From the Cycle Count Adjustment Approval Rule, you can set up approval rules. In the RF transactions RF Cycle Count IBLPN and RF Cycle Count Location screens, configure screen parameters auto-approve-mode and auto approval-rule-name.

Key Resources

Reporting

Create Web Reports Including New Categories

As part of 19C, we have introduced new categories and fields that help you to create a detailed report that tracks all relevant metrics for daily operations. These new Web Report categories are available in Oracle Warehouse Management Business Intelligence Cloud.

Categories decide what kind of data is fetched from the database in order to build the report.

The following are the new categories added:

  1. Trailer - This is a new category introduced where you can generate reports using trailer to track relevant metrics. Also, you can join this "Trailer" category with InboundShipmentLoad / ContainerRcvdLoad / OutBoundLoad / Appointment categories to generate a report of joined category. 

NOTE: The system generates the Web Report only when the trailer number is present.

  1. QC Verification History - This is a new category introduced where you keep track of relevant metrics related to Quality check. The QC verification history captures the details of the Quality Check such as if QC is passed or failed, user who performed the check, When was the QC performed. It also captures the answers given to the verification questions while performing the QC.
  1. WMS Activity - This is a new category introduced where you can track the performance of the warehouse workforce, in case you are not using the WFM for checking the details of the floor user’s performance. New fields have been added in the header and detail.The "WMSActivityHdr" category establishes join with "WMSActivityDtl" category and vice versa. You can also generate separate reports with the new category "WMSActivityHdr" & "WMSActivityDtl” and join the two categories to create a report.
  1. Location - This is a new category introduced where the location report will give you broader view of all the locations that are occupied in the warehouse with respect to inventory & allocation. You can use this data further in optimizing the available location for better inventory management. You can also generate proper reports for the Location Category joined with 'Company' and/or 'Item' Categories.
  1. Work Orders - This category allows you to create detailed reports using Work Orders to keep track of relevant metrics for daily operations.

The following are the new fields added to existing categories:

  1. In Order Category, new fields are added (Sort, Filter, and Layout) in Web Reports for "Order" Category. Following are the new fields:
  • Hdr Cust Short Text 3
  • Hdr Work Order Kit Id
  • Hdr Externally Planned Load Flg
  • Hdr Order Nbr To Replace
  • Hdr Billto Carrier Account Nbr
  • Hdr Duties Carrier Account Nbr
  • Hdr Erp Source Hdr Ref
  • Hdr Erp Source System Ref
  • Hdr Tms Order Hdr Ref
  • Hdr Group Ref
  • Original Item Code
  • Dtl Unit Declared Value
  • Dtl Externally Planned Load Nbr
  • Dtl Erp Source Line Ref
  • Dtl Erp Source Shipment Ref
  • Dtl Erp Fulfillment Line Ref
  • Dtl Sales Order Line Ref
  • Dtl Sales Order Schedule Ref
  • Dtl Tms Order Dtl Ref
  1. In Expand Inbound Shipment Category, three new filed are added (Sort, Filter, andLayout) in Web Reports for "InboundShipment" Category. Following are the new fields:
  • HDR Return From Facility Code
  • HDR Return From Facility Name
  • HDR Return From Facility Type

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Kitting

Cancel Wave in Work Order Template

In update 19C, you have an option to cancel unallocated Work order kits and components if the components are not available at the time the wave is run. The Cancel Unallocated flag is available in the Work Order Wave Template UI.

The 'Work Order' wave should perform the following updates if the Cancel Unallocated flag is enabled:

  • If no components are allocated for a particular work order kit after the wave is run, then the system cancels the order quantity for the corresponding work order kit. The system also cancels the required quantity for the work order component.
  • If the work order is partly allocated, the wave is run for the particular order, and no components are allocated for the particular work order kit after the wave run, then the system deducts the unallocated quantity from the order quantity for the work order kit. It also updates the corresponding required quantity for the work order component. When the order quantity units are reduced, the work order is updated to the corresponding status.

STATUS UPDATES

The following describes the status updates that happen when a Work Order has Cancel Unallocated set to Yes or No:

In Work Order Wave, when Cancel Unallocated = Yes

  • If the whole work order is not allocated in the Wave, the work order updates to Cancelled status.
  • If the work order is partly allocated, the system updates the order quantity = 0 for that detail and the work order goes to Allocated status.

In Work Order Wave, when Cancel Unallocated = No

  • If the whole work order is not allocated in the Wave, the work order updates to Created status.
  • If the work order is partly allocated, then the work order remains in Partly Allocated status.

NEW INVENTORY HISTORY RECORDS

  • The system should write IHT "82 - Work Order Cancellation" for kits, components, and order detail that are cancelled as part of a work order wave. The adjusted quantity for the kit/component/order detail should be the negative value of the 'unallocated ord qty'. The adjusted quantity for each component should be the negative value of the 'unallocated required qty' for each component.
  • When work order status is changed while reducing/updating the order quantity of the kit, the system should write IHT 67 - Work Order Status Changed and must be generated with the corresponding 'Old status' in reference value 1 and 'New status' in reference value 2.
  • When work order status is changed while reducing/updating the order quantity of the order detail, the system should write IHT 20 - Order Status Change and must be generated with the corresponding 'Old status' in reference value 1 and 'New status' in reference value 2.

Steps to Enable

Set up Cancel Unallocated flag to yes in the Work Order Wave Template UI.

Key Resources

Inventory Message in Lock Code UI

Changes have been made to the functionality of treat as attribute in the Lock UI. If you currently have set up an inventory attribute a to o in this field, the system displays a new message when the replenished location has the lock code and treat as attribute fields as not blank (i.e. replenishments done through a picking wave) and the updated attribute field has a value different than the order's attributes.

Once the replenishment task is completed, if the location has a lock with a treat as attribute value (a to o), the replenished inventory will update the attribute value (a to o) with the lock code. If you are running a replenished wave, and your picking allocations are now affected due to updated inventory, the system will show you the message, so you are aware that inventory has been changed and picking allocations have been impacted.

Steps to Enable

From the Lock Code screen, select a Lock Code, click Edit, and enter an attribute from a-o in the Treat as Attribute field.

Key Resources

Configure Email Notification

Oracle WMS Cloud has introduced a new mechanism to handle outbound email notification during input interface for entities. As part of 19C,  a new screen “Input Interface Configuration" allows you to configure your email notifications only for those entities that have the "Send Failure Email" check box enabled.

By default, the triggering of emails when you interface an input file is disabled from 19C. Also, the system will not send emails if there are no existing records with the “Send Failure Email” flag disabled.

Steps to Enable

  1. Go to the Input Interface Configuration Screen.
  2. Click (+) and select the entity from the Interface Type drop-down menu.
  3. Check the "Send Failure Email" check box and click Save.

NOTE: To send the failure emails to a Distribution List (DL), or include multiple mailer ID's, you need to configure email addresses in the company parameter "INT_ERROR_EMAIL_LIST".

Key Resources

User Experience and Usability Enhancements

Receiving

Verify Shipment by LPN/Pallet Number

Prior to update 19C, you could use the RF Verify Shipment transaction to verify a shipment. You could use the shipment number to verify the shipment without reaching a computer. Now, you can use the LPN/Pallet number. Sometimes shipment labels might not be handy for the users on the floor to initiate verification of shipment. Now that the LPN/Pallet number option is available, Oracle WMS Cloud allows you to verify the shipment by scanning the LPN or the pallet number from the RF menu.

If the new screen parameter "prompt-lpn-pallet"  is set to yes, then you are prompted to scan LPN/Pallet number. if set to no, you are prompted to scan the shipment number. No is the default value for this parameter. You need to accept the verify shipment message to complete the transaction. The message for any SKU which is not received will continue to be shown for this transaction.

In case multiple shipments are associated with a Pallet, scanning the pallet number would show the list of the eligible shipment numbers. You need to select the shipment number that requires to be verified.  Once the verification is done, the receivers can view a pop up confirming the same.

Steps to Enable

The screen parameter "prompt-lpn-pallet" should be set as yes from the "RF-Text: rf.inbound.cwrfverifyshipment" module.

Key Resources

Inventory Management

Add Permissions to Reason Code UI

Currently, any user can add/edit/delete reason codes from the Reason code UI screen. Reason codes are used across Oracle WMS Cloud and usually user must type the reason code, so if there is an update or delete a Reason Code, this can cause discrepancies or errors to user preventing you from finishing a transaction.

In Update 19C, new group permissions allow you to add, delete, and edit Reason codes, so only if your roles has this permission enabled you can modify them.

The newly introduced reason code permissions are stated below:

  • Reason Code/ Add Reason Code
  • Reason Code/ Edit Reason Code
  • Reason Code/ Delete Reason Code

For the ‘ADMINISTRATOR’ role, these permissions are granted by default. For the user roles other than the ‘ADMINISTRATOR’, the reason code add/delete/edit permissions will be unchecked by default and you should not be able to modify the reason codes. You can modify the reason codes if the newly added permissions are enabled from the ‘Group’ UI screen.

Steps to Enable

Users with roles other than the 'ADMINISTRATOR' should navigate to the group permissions and enable the permissions for the Reason Code.

Key Resources

Lock/Unlock All LPNs on a Pallet

Now, you can lock or unlock all the LPNs on a pallet with just one click. This saves you time, as prior to this change you needed to lock or unlock each individual LPN.

In update 19C, a new screen parameter "lock-unlock-lpn-screen" is available in the “rf.inbound.cwrfpalletinquiry” screen. This parameter takes the screen name of the RF Lock Unlock Container screen "rf.inbound.cwrflockunlockcontainer" . The RF Lock Unlock Container screen will be call  upon selecting the newly introduced hot key “CTRL-L”.  This allows you to bulk lock/unlock LPNs in a pallet from the “rf.inbound.cwrfpalletinquiry”transaction screen. Upon selecting the lock/unlock option You can select any lock code from the list of all the lock codes displayed. A confirmation message appears after every transaction showing the number of LPNs locked or unlocked out of the total number of LPNs present in the Pallet.

Steps to Enable

You need to provide the RF lock Unlock Container screen name as the parameter value on the “rf.inbound.cwrfpalletinquiry” transaction screen for the hot key to appear on the RF.

Key Resources

Task Management

New Recalculate Task Button

There are instances where a task can get stuck in Processing Started status or a wrong status, but its allocations have been completed or canceled.  A new Recalculate Task Status button is available in the Task Inquiry UI. This new button allows you to recalculate tasks in Processing Started status or put the status back to the correct status based on underlying allocations.

NOTE: The Recalculate Task Status button is not applicable to cycle count tasks.

Once you click Recalculate Task Status, the system checks to see if any of the selected tasks have been modified in the last 24 hours. If so, the system displays a message to confirm that tasks have been modified. If you choose to proceed with changing the status, Oracle WMS Cloud checks the allocations of the task, and updates the task to their correct status. You will receive a success message once updates are complete. If you selected multiple tasks, and the system fails to clean up a task, then the system will rollback all the changes and you may have to recalculate status for a smaller number of selections.

NOTE: This feature has also been backported to 18C.

Steps to Enable

  1. From the Group Configuration UI > click Permissions, select Task / recalculate_task_status.
  2. Click Save. 

Key Resources

Outbound Load Management

Provide Additional Information on Outbound Load UI

A new  ‘Externally Planned Load' filter checkbox is available in the ‘Outbound load’ UI screen. By selecting this check box, it only displays ads which are planned with externally planned load.

In update 19C,  the following six hyperlinks from the Outbound Load UI have been enhanced to help you easily identify OBLPNs that are missing a tracking number, have a serial number mismatch, or are pending for audit:

  1. Num of LPN's 
  2. Num of OB LPN's No Location
  3. Num of OBLPN's in Consolidation
  4. Num of OBLPN's in Staging
  5. Num of OBLPN's in Pack & Hold
  6. Num of OBLPN's in Drop ­

The following hyperlinked fields are added to the UI:

  • 'Tracking Number' and ‘Audit Status’columns are introduced to the UI screens of the six hyperlinked fields mentioned in the Outbound Load UI, These newly introduced columns are not visible on the UI screens by default. You can add these columns on the UI screen for them to appear. 

Following updates are made to the six hyperlinked field's UI search criteria:

  • 'LPN's with serial number mismatch' filter checkbox is added to the search criteria. Enabling the checkbox displays only the LPN's with serial number mismatch.
  • 'LPN's without Tracking Number' drop-down filter is added with 'Yes' and 'No' Options.
  • ‘Orders with Shipping Blocked' filter checkbox is added to the search criteria. Enabling the checkbox displays only the LPN's whose associated orders are marked with shipping blocked.
  • Audit Status’ drop-down filter is added with ‘Not Required’, ‘Audit Complete’, ‘Audit Pending’ and ‘Audit Missing’ Options. 

Steps to Enable

By default the 'Tracking Number' and the ‘Audit Status’columns are not visible. You will have to add them to the view and save to make them appear on the UI.

Key Resources

Provide Additional Information on Shipment Manifest UI

Now, you can easily identify OBLPNs with a mismatch in serial numbers from the Manifest UI. This will allow you to check if there is an existing mismatch before closing your manifest. In update 19C, we are introducing a new check box 'LPN's with serial number mismatch' to the search filter of the 'OBLPN's' UI on the Manifest screen.

By default, the newly added checkbox is unchecked. Enabling the checkbox displays only the LPN's with serial number mismatch.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Ship Load on Load OBLPN Mobile RF UI

Now you will be able to Ship a load from the RF. This will increase productivity in your warehouse by minimizing the additional time it takes to ship from the UI screen.  the ‘Load OBLPN’ RF transaction has a hot key ‘CRTL-P’ to perform ship load via RF transaction. By selecting  'CRTL-P',  you will be prompted to  ‘Accept’ or Do not accept’ options. Selecting 'Accept' will ship your load. If you hit CTRL-P, but there is not a load number in the transaction field, you are prompted to scan the load number to proceed further.

'IHT 3- Container Shipped' is recorded for each OBLPN associated with the shipped load. If an OBLPN is associated with asset, corresponding 'IHT- 58- Asset Shipped' gets generated for that particular shipped OBLPN. 'IHT-60 - Load Shipped File' is recorded for Load Shipped File generation.

NOTE: Facility parameter "AUTOLOAD_AND_SHIP" is not supported via the RF "Load OBLPN" Ship Load transaction. Generating multiple outbound file on shipload is also not supported from the RF.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Capture Reference Information on Direct Consume LPN Mobile RF UI

Currently, the Consume LPN API allows you to provide a reference text, such as a transaction reference number that may be useful for External Host Systems. Now, you are able to provide a reference text or information when consuming an IBLPN using RF-Direct Consume LPN.

As part of 19C, a new parameter 'Display Ref text' is available with the selection type options "Yes/No". If set to Yes, You can view this reference text before scanning the IBLPN field in the RF screen. By default, the selection type is set to No.

After the LPN is scanned, you need to provide the reason code to directly consume the LPN. The reference text captured is populated in the “Ref value 3” column of the Inventory history screen with the IHT activity 2 - Container Consumed.

Steps to Enable

  1. Go to Display Ref Text" in the "Direct Consume LPN" RF screen.
  2. Click Selection > Edit > Set the  'Display Ref text' parameter type to Yes.

Key Resources

Rule Criteria

Enable Additional Fields as Selection Criteria for Rules

Additional fields are now available in the following selection criteria determination rules:

  • putaway type determination rules
  • task creation rules
  • cubing rules
  • inbound sorting rules

In the Putaway Determination Rule screen Selection Criteria, you can now use the Item Facility Putaway Type to define Putaway types based on Item Facility.

ADD SEARCH CRITERIA TO TASK UI 

You can define additional tasks using these fields available in the Task Creation Template Selection Criteria and Ordering Criteria:   10571

  • Order Hdr Externally Planned Load Flag 
  • Order Dtl Externally Planned Load Number
  • Order Hdr Required Shipped Date
  • Order Hdr Start Ship Date
  • Order Hdr Stop Ship Date
  • Order Hdr Ship date

From the Cubing Rules screen, Selection Criteria and Ordering Criteria, you can define Cubing rules with these additional fields:

  • Externally Planned Load Flag 
  • Externally Planned Load Number

From the Inbound Sorting Location Determination Criteria Rules, you have the option to add the following additional Inventory Criteria:

  • Inventory Priority Date
  • Inventory Manufacture Date
  • Inventory Expiry Date
  • Inventory Batch Number
  • Inventory Case Quantity
    • Inventory Pack Quantity

When you are managing tasks, you may need to search for and filter existing tasks based on the ship date. From the search option in the Task UI, the following date-related ship fields are now available:

  • From Required Ship Date
  • To Required Ship Date
  • From Start Ship Date
  • To Start Ship Date
  • From Stop Ship Date
  • To Stop Ship Date
  • From Ship Date

To assist you further in filtering items for the Quality Control process, the following fields have been added to the Vendor QC Determination Rule screen:

  • Item
  • Shipment

Once you select your newly added Item and Shipment fields, you can create a new Vendor QC rule.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Match Date Columns Based on Difference from Current Date

Now, you are able to create cycle count task for locations that where last counted 'x' days ago. This is an example of what you are able to do now that the selection criteria rule has been expanded to have a comparison in dates based on current date. In order to be able to compare dates, two new key words are introduced 'd' and 'm' where 'd' represents days and 'm' represents minutes. For example, if you need information about the location's last count time stamp in the last 10 days, you can enter d-10 in the column value of the selection criteria rule.

Or, if you need your wave order selection rules to select orders whose Ship date is 20 days older than the current date, you can enter d+20 in the column value of the selection criteria rule. Similarly, if you need to extract data in terms of minutes, you can enter m-60/m+60. The format accepted in the column value of the selection criteria rule is( d+x, d-x, dx, m+x, mx or m-x) where d is days, m is minutes, and x is comparison number.

NOTE: dx is considered an additional operation.

This update on the selection criteria is applicable on the following screens:

  • Putaway Type Determination Rules > Selection Criteria
  • Task Creation Template > Details> Task Selection Rules
  • Wave template> Wave Template Search > Dynamic Wave Search > Wave Order Selection Rules

NOTE: The dynamic wave search rules to select orders based on stop ship date/ required ship date/ start ship date/ order hdr cust date/ or order dtl cust date fields and supports only the date column.

  • Audit Rule > Audit Selection Rule

The highlights of this enhancement are:

  1. Introduce two new keywords "d" and "m" where 'd' signifies number of days and 'm' signifies minutes. The Date and Minutes are the only format supported in the system.  
  2. These keywords is applicable only for columns you select of type "date" and "date_ts".

For example, if the selected date or date_ts column is x days less/greater than current date, then the criteria value configured is d-<x>/ d+<x>, where, "d" signifies days,  '-/+' signifies subtraction/addition, and <x> days you want your data from current date.

NOTE: By default, if the (-) sign is not applied, then system adds the number of days from the current date.

The key word "m" is required to compare the data based on minutes. Use minutes (m) format if any event occurred in less than 24 hours and the requirement is to compare based on time difference from the current time.

For example, if the selected date_ts column is <x> minutes less/greater than current date_ts, then the criteria value configured is m-<x>/ m+<x>, where, "m" signifies minutes and '-/+' signifies subtraction/addition, and <x> is the minutes from current date_ts.

NOTE: The keyword "m" is not recommended to use against column of "date" type date.

Steps to Enable

  1. From any of the Selection Criteria Screens mentioned above..
  2. Choose an operation from the drop-down =,<,>,>=,<=. For example, you select <=.
  3. Select the column of "date" type or "date_time" type from the drop-down menu.
  4. Enter the value. i.e., If value = d5 (or d+5) (given current date per facility time zone is 30 April), then the orders whose ship date is 5 days from 30 April are captured.

Key Resources

Fulfillment

Hide Internal Picking Orders

As of now, Oracle WMS Cloud displays the ‘Internal Picking Orders’ along with the customer and the store orders on the Order Header and the OB Order UI screens. The ‘Internal Picking Orders’ are created by the Oracle WMS Cloud for internal picks and might not be relevant for some customers, and cause confusion.

We have provided an ‘Exclude Internal Picking Order’ checkbox as a search option for the Order Header and the OB Order UI screens in the  version 19C. By default, the checkbox is unchecked, and you can view all the orders including the Internal Picking Orders on the Order Header and the OB Orders UI. If the 'Exclude Internal Picking Order' checkbox is selected the system will not display the internal picking orders.

Steps to Enable

Enable the ‘Exclude Internal Picking Order’  on the Order Header and the OB Order UI screens

Key Resources

Integration Enhancements

REST APIs

Print Labels Using REST APIs

Oracle WMS Cloud now has a new print model and label printing functionality. This option is great if you have an automated warehouse, and you want to trigger the printing of labels. Currently, Oracle WMS Cloud supports printing  the following labels using an API call:

PRINT SHIPPING LABELS API

Now, you can trigger printing a shipping label for one or more OBLPNs to a specific printer using an API.  This API does not do any template verification logic, and you need to have the label template already configured and provide this information in the “label_designer_code” parameter. If the printer is not defined in the parameter section, the system uses your default printer.

You can submit a label for printing using a POST request:

POST .../wms/lgfapi/v10/print/label/shipping

You can get a ZPL representation of the label using a GET request:

GET.../wms/lgfapi/v10/print/label/shipping/?label_designer_code=foo

PRINT LPN LABELS API

Now, you can trigger printing an LPN label for printing one or more IBLPNS. This API does not do any template verification logic, and you need to have the label template already configured and provide this information in the “label_designer_code” parameter. If the printer is not defined in the parameter section, the system will use your default printer.

You can submit a label for printing using a POST request:

POST .../wms/lgfapi/v10/print/label/ib_container

You can get a ZPL representation of the label using a GET request:

GET.../wms/lgfapi/v10/print/label/ib_container/?label_designer_code=foo

PRINT PALLET LABELS API

Now, you can trigger printing a Pallet label to a specific printer using an API. This API does not do any template verification logic, and you need to have the label template already configured and provide this information in the “label_designer_code” parameter. If the printer is not defined in the parameter section, the system will use your default printer.

You can submit a label for printing using a POST request:

POST .../wms/lgfapi/v10/print/label/pallet

You can get a ZPL representation of the label using a GET request:

GET.../wms/lgfapi/v10/print/label/pallet/?label_designer_code=foo

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

Copy Putaway and Facility-Related Configurations Using REST APIs

Previously, you could not read company, facility and other related configuration data when copying the configuration from one facility or company to another. You can accomplish this by reading the configuration using a GET request and then using a POST request to create the configuration in the target facility/company. This allows you to copy your facility configuration over to additional facilities.

NOTE: Bulk create is not currently supported so this will only support creating a single object per request.

This update adds several POST entities including:

  • Company Parameter
  • Facility Parameter
  • Location Size Type
  • Putaway Priority
  • Putaway Type
  • Putaway Type Calc Rule
  • Replenishment Zone
  • SQL Selection (Rule Tree)

The following are some examples of available POST requests:

Company Parameter 

POST .../entity/company_parm

Facility Parameter

POST .../entity/facility_parm

Location Size Type

POST .../entity/location_size_type

Putaway Priority 

POST .../entity/putaway_priority

SQL Selection (Rule Tree)

This entity is unique in that this API allows you to create the entire rule tree in a single request instead of needing to create and link each parent/child object individually. You can use the `children` list field to accomplish this. This is an abstract field that does not exist on the object itself, but rather defines the `parent_id` link, which will be handled by the API automatically.

To illustrate a complex example, the following request body could be used to create this rule structure as seen from the UI:

POST .../entity/sql_selection

{

"fields": {

"facility_id": 1,

"sql_operator_id": 2,

"children": [

{

"column_name_id": 107,

"sql_operator_id": 5,

"column_value": "B"

},

{

"sql_operator_id": 1,

"children": [

{

"column_name_id": 1379,

"sql_operator_id": 7,

"column_value": "100"

},

{

"column_name_id": 35,

"sql_operator_id": 7,

"column_value": "50"

}

]

}

]

}

}

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

Update Stop Receiving Flag in Purchase Order Detail Via API Request

Now, you have the option to update the stop receiving flag via an lgfapi request. If the flag is set to Yes, the system will not allow you to receive inventory against the Purchase Order Detail. This change gives you flexibility to decide what inventory should and should not be received into the warehouse . This can be done by using a PATCH request in the Purchase Order Detail entity.

For example:

PATCH .../entity/purchase_order_dtl/{id}

"fields" section of the request body:

{

"fields": {

"stop_recv_flg": True/False

}

}

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

Palletize and Depalletize Using a REST API

A new palletization API  is available. This is a great feature for automated warehouses where robots or other external systems do the palletization. You no longer need a user with an RF gun to use this transaction. The new API links an inbound or outbound LPN to a pallet. For Inbound LPNs, the system only allows located LPNs unless  ALLOW_PALLETIZE_OF_ALLOCATED_LPNS is set to yes which will allow allocated LPNs as well.

For Outbound LPNs, the system only allows picked or packed LPNs. Once the LPN is palletized successfully, the pallet number is updated in the LPN. A new record is added to the Pallet History UI to confirm the LPN has been added. When the Pallet number is new for the facility, a new record is available in the Pallet UI. The status of the pallet is set to In-facility, and a new record is added to the Pallet History UI which shows the pallet is created.

Palletize API can be called using the following requests:

Identifying the container to be palletized by ID:

POST .../entity/container/{id}/palletize/

Identifying the container to be palletized by filter:

POST .../entity/container/palletize/

DEPALLETIZE SINGLE LPN 

You also have the option now to depalletize an inbound or outbound LPN so that you do not have to use RF guns to perform depalletization.

The Depalletize API allows you to dissociate inbound or outbound LPNs to a pallet. Use the following POST requests to depalletize an LPN:

Identifying the container to depalletize by ID:

POST .../entity/container/{id}/depalletize/

NOTE: No additional `parameters` data in the request body is required.

Identifying the container to depalletize by Filter:

POST .../entity/container/depalletize/

The `parameters` section of the request body will allow for the users to identify the specific OBLPN:

{

"parameters": {

"facility_id": 1,

"company_id": 1,

"container_nbr": "LPN-1"

}

}

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

Interfaces

Allow Extract File in Output Interface Configuration UI

Currently, while running an Extract operation, you need to configure both extract and copy files in the scheduled job UI. As a part of update 19C, a new Extract interface is available for you to configure for the data extract scheduled job. Hence, you need not configure the PUT SFTP files scheduled job separately. This newly introduced interface type helps you to specify a target directory to store the files generated from the data extract without running any other jobs.

Once the interface is configured, you should be able to specify a target directory from the “Output Interface Configuration” detailed UI. All the CSV files thus generated by the scheduled jobs gets reflected on the target directory configured in the output interface target screen. However, the current update also maintains the backward compatibility. Hence, you can continue using the copy file job and select a target directory if you do not wish to configure the target directory at the extract file operation.  The new Data Extract Interface Type currently allows only ‘Flat files’.

NOTE:

  1. Once you select "Data Extract" type from the Interface type drop down on the “Output Interface Configuration” UI screen, the ‘Interface Format’ field displays only the " Extract flat files" option on the drop down.
  2. Web service interface protocol is not supported for the Data extract in the output interface configuration.
  3. The current copy files schedule job works as is. The existing users should be able to continue using this job for copying files from the Output interface to the targeted SFTP directories, but you need to configure the GET SFTP files job to access the files generated by the Copy files job.
  4. All different types of data extracts go through the same Output Interface Configuration.

Steps to Enable

You should select Interface protocol type as per the source requirement and provide your SFTP credentials and the SFTP target directory to enable this feature.

Key Resources

Send Header Level Request Using Input Interface

There are instances where you may need to update or delete header records for entities such as Purchase Order/IB Shipment. Prior to update 19C, to accomplish this task, you needed to send both header and detail request while interfacing the files.

Now, Oracle WMS Cloud allows you to only send header level information and perform UPDATE /DELETE action. Please refer to the Interface Specifications document to identify the values required to send in the header level request.

This is applicable in the following entities:

  • IB Shipment
  • Purchase Order
  • Order
  • Work Order
  • Route

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Removal of Post to URL Job Type from Scheduled Job UI

As part of 19C updates, we have decommissioned the “Post to URL” job type as we no longer support Oracle hosted Jitterbit, which was a previously supported integration customization option that was removed earlier this year. Thereby, users will not be able to view or use the “Post to URL” job type from the Scheduled Job UI.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Upload Messages in Bulk

Earlier you could edit or modify single system messages from the Message UI screen.  However, there was no interface for you to update the long or short messages in bulk.

Update 19C allows you to modify short and long messages in bulk. Now, you can upload the modified/edited xls file into the system using the new message input interface. The system currently supports three types of file formats namely XML, XLS and PSV through the input interface screen and only the XML format via Init Stage interface API.

NOTE: for the supported language and valid field values, please refer to the Interface Specification document.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Improvements to Re-Processing of Inventory History Transaction Records

In Update 19C, you are able to revert the already processed/processing IHT activity statuses to Unprocessed or Not Ready status. By setting the status to unprocessed or not ready, the system is able to pick these records and process them.

To facilitate this feature, the action button “Mark Unprocessed” is now available in the Inventory History screen. You can select multiple IHT entries that they want to revert to the ‘Not Ready’ Status. We have also introduced a new permission “InventoryHistory/Can mark Inventory History unprocessed”. By default, the Administrators can view and use the button. However, for the existing user roles other than the Administrator, you need to activate the feature by configuring the newly introduced Permission “InventoryHistory/ Can mark Inventory History unprocessed”.

NOTE: The IHT activities that are subjected to auto-process in the Inventory History Activity Parameter module, will not go to an unprocessed state using this button. To mark those activities as unprocessed, a user must turn the Auto-Process flag off for those IHT activities.

Steps to Enable

The “InventoryHistory/ Can mark Inventory History unprocessed” permission should be checked at the respective group level for the user roles other than the Administrator.

Key Resources

Inventory History

New IHT Activity to Cancel Work Order

Prior to 19C,  there was no IHT activity created when a work order or the kites within get cancelled from the Input interface, 'Work Order Inquiry View UI', 'Work Order Kit View' (at Kit level) or from the RF WorkOrder Kit Processing Screen. Therefore, there was no way to communicate to other systems when the Work order had been canceled.

As part of update 19C, a new activity "82-Work Order Cancellation” is available. The cancellation of the work order happens at the individual kit level. For example, if your work order contains 3 kits and you cancel 2 of them, then 2 records with the "82-Work Order Cancellation” get generated on the inventory history. Similarly, if a work order kit has 2 components, and if we cancel the work order kit, the system will generate 3 records with  "82-Work Order Cancellation” on the inventory history. For more details on the populated fields on the Inventory History, please refer to the Interface Specifications document.

NOTE: If the auto process flag is enabled, the work order entry will be marked as processed and these entries will not be considered in the next cycle by the host system. When there is a disabled auto flag, the entries will have a Not Ready status.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

New IHT Activity to Unload Container

In Oracle WMS Cloud, when an OBLPN gets unloaded, the corresponding details are not recorded on the inventory history. Providing Inventory History for Unload of container could help you to use this event for additional processing in external systems.

As a part of the 19C update, a new inventory history activity ‘IHT83- Container Unloaded’ is being introduced in OCWMS to capture the unloading of the OBLPNs. The Auto process flag for the newly introduced IHT activity is ‘Enabled’ by default. However, if you want to use these records, you need to disable the auto process flag as Disabled from the ‘Inventory Activity History Parameter’. Disabling the auto flag will make the IHT activity status as not ready.

Additionally, IHT83 supports split by serial number flag which is un-checked by default. If the split by serial number flag is checked from the ‘Inventory Activity History Parameter’ screen, the activity will be generated for each serial number.

NOTE: ‘IHT83- Container Unloaded’ will be followed by ‘IHT51- Inventory Movement’ in case of any location scan during the unloading. In this case, the IHT83 will be written before the IHT51 activity.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

Enable Auto-Send of Inventory History

Inventory history records various WMS transactions taking place in the facility for purposes of informing the ERP or any other external system that may be interested. In the past the main way to extract these would be via scheduled jobs at pre-determined intervals. Scheduling too frequently may place unnecessary load on the system and scheduling too infrequently may caused delays in notifying the ERP or other systems of critical WMS updates. With 19C you can now automatically send inventory history records as and when they are created.

They are sent via the Output Interface setup just like other outgoing messages. The new fields "enable_auto_send" and "disable_auto_send" are available in the Inventory History Activity Parameter.  From the Inventory History Activity Parameter screen, you can select all history activities that are crucial for you to monitor.  If the enable_auto_send flag is enabled, then the system will post the relevant IHT records as soon as the records are written to the relevant webservice end point setup in the Output Interface Configuration screen.

NOTE: If the auto-send is enabled for an IHT record, the auto-send takes precedence. The default value for the flag is No. Auto send is supported if the file format is XML and also if the interface type is Rest WebServices.

Steps to Enable

  1. From the Inventory History Activity Parameter screen > Select the IHT Record.
  2. Click on enable_auto_send

Key Resources

Enable Auto Process of Inventory History

The Enable Auto Process flag allows you to select IHT records that do not need to be processed by your Enterprise Resource System (ERP). In 18C, these records used to be created in a "Processed" status. As a result, when scheduled purges were executed, there was an increased load on the system as it could not differentiate between auto processed and general IHT records. Now, the records will be created in Cancelled status, and this will reduce the load while increasing system performance.

In order to increase system performance, the Enable Auto Process flag is available. Once you select the Enable Auto Process flag, the system processes the IHT records to a “Cancelled” status. When the flag is disabled, the system writes the IHT record with a "Not Ready" status.

Steps to Enable

  1. From the Inventory History Activity Parameter UI, select the History Activity.
  2. Click Enable Auto Process for the selected IHT. The system will prompt you to enter your WMS password. Otherwise, click Disable Auto Process.
  3. Enter your WMS password and click Submit. Otherwise, click Cancel.

Key Resources