oracle warehouse management cloud · wms has the ability to store inventories with different...

Oracle Warehouse Management Cloud Update 18C

What’s New

2

TABLE OF CONTENTS

DOCUMENT HISTORY ······························································································································································································· 4

NOVEMBER MAINTENANCE PACK FOR 18C ···························································································································· 4

Revision History ························································································································································································ 4

Overview ······································································································································································································· 4

Feature Summary ····················································································································································································· 4

Functional Enhancements ······························································································································································ 5

Additional Fields in Allocation ·················································································································································· 5

Attribute Transfer Code ····························································································································································· 6

Case and Pack Quantity in OBLPN Type ··························································································································· 7

Consolidate Replenishment ····················································································································································· 7

Divert Confirmation API ····························································································································································· 8

Multiple UOMs in Cubing ·························································································································································· 9

Receiving for Unexpected LPN's ············································································································································ 9

RF Move LPN - Suppress Pallet Prompt ··························································································································· 10

RF Receiving by Shipment/Load ·········································································································································· 10

Support for Additional UOMs for Standalone and Wave-Based Replenishment ··············································· 10

Warning Message in Assign Load UI ································································································································· 12

User Experience and Usability Enhancements ·················································································································· 12

Recalculate OBLPN Status in OB Container UI ············································································································· 12

Appendix ····································································································································································································· 13

Treat as Attribute ··············································································································································································· 13

OCTOBER MAINTENANCE PACK FOR 18C ······························································································································ 14

Revision History ······················································································································································································ 14

Overview ····································································································································································································· 14

Feature Summary ··················································································································································································· 15

Functional Enhancements ···························································································································································· 15

Cubed Together Flag ································································································································································ 15

LPN Substitution in RF Pack NC Active ···························································································································· 16

Over-Replenishment for Active Locations ························································································································ 16

Wave Group ················································································································································································· 18


Custom Reference Text in Trailer UI ·································································································································· 19

IB LPN Inquiry ············································································································································································· 20

RELEASE 18C ··························································································································································································· 20

Revision History ······················································································································································································ 20

Overview ····································································································································································································· 20

Feature Summary ··················································································································································································· 21

Functional Enhancements ···························································································································································· 22

RF Receiving ··············································································································································································· 22

RF Print Item Label ··································································································································································· 23

Printer Selection ········································································································································································· 23

Return Facility on Inbound Shipment ································································································································· 24

Pack with Wave ·········································································································································································· 25

Enable / Disable Company Flag ··········································································································································· 26

Priority Date Traceability ························································································································································· 26

Additional Carrier Type Support ··········································································································································· 27

Inbound Shipment View ··························································································································································· 27

3

Lock Codes on Inbound Shipments ···································································································································· 27

Reference LPN Number Display ·········································································································································· 28

Oracle Cloud Migration ···························································································································································· 28

Update Route Number for Multiple Orders ······················································································································· 28

Oracle SCM Cloud Execution ···················································································································································· 28

Load Assignments for Orders Planned by OTM ············································································································· 28

Close Load ···················································································································································································· 29

Reset External Planned Load Number from Order Header Browser UI ································································ 29

Integration Enhancements ··························································································································································· 30

Outbound LPN Shipping Info Triggered at Status Change ························································································ 30

Generate Outbound LPN Info upon Manifest ·················································································································· 30

Generate Order Export at Order Packed ·························································································································· 31

XML Support for Additional Input Interfaces ···················································································································· 31

Expanded Selection Criteria in Output Interface ············································································································ 31

FedEx International Shipment ··············································································································································· 32

Output File Target Selection ·················································································································································· 32

Item Master Protected Fields ················································································································································· 33

Rearrangement of XLS File Format for Route Input Interface ·················································································· 33

Include Printer in Outbound LPN Shipping Info ·············································································································· 34

Auto Process Inventory History Records ·························································································································· 34

Oracle SCM Cloud Integration ··················································································································································· 35

Changes to Planned OB Load Interface ···························································································································· 35

New logic for Loading API ······················································································································································ 36

REST API ·························································································································································································· 36

Create LPN API ·········································································································································································· 36

Update Custom Fields for Current lgfapi REST API ····································································································· 36

New API to Bulk Update Inventory Attributes ·················································································································· 37


RF Screen Layout Realignment ··········································································································································· 37

Oracle WMS BI Cloud Reports ············································································································································· 37

Improved Literal Localization ················································································································································· 38

Improved Time Zone Localization ········································································································································ 39

Yard Management Improvements ······································································································································· 39

Oracle WMS BI Cloud Framework ······································································································································ 39

Order Detail Level Permissions ············································································································································ 40

Document Design and Printing ·················································································································································· 40

Price Label Support with Label Designer ·························································································································· 40

Case and Pack Labels Using Label Designer ················································································································· 40

OBLPN Number Labeling and Printing ······························································································································ 41

4

DOCUMENT HISTORY

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

Date Update Version Notes

30 NOV 2018 November Maintenance Pack for 18CDelivered new features in November Maintenance Pack for 18C.

27 NOV 2018 October Maintenance Pack for 18CDelivered new features in October Maintenance Pack for 18C.

31 AUG 2018 Release 18C Delivered new features in Release 18C.

NOVEMBER MAINTENANCE PACK FOR 18C

REVISION HISTORY


Date Feature Notes

30 NOV 2018 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 [email protected]

https://This%20guide%20outlines%20the%20information%20you%20need%20to%20know%20about%20new%20or%20improved%20functionality%20in%20this%20update,%20and%20describes%20any%20tasks%20you%20might%20need%20to%20perform%20for%20the%20update.%20Each%20section%20includes%20a%20brief%20description%20of%20the%20feature,%20the%20steps%20you%20need%20to%20take%20to%20enable%20or%20begin%20using%20the%20feature,%20any%20tips%20or%20considerations%20that%20you%20should%20keep%20in%20mind,%20and%20the%20resources%20available%20to%20help%20you.%20Give%20Us%20Feedback%20We%20welcome%20your%20comments%20and%20suggestions%20to%20improve%20the%20content.%20Please%20send%20us%20your%20feedback%20at%[email protected].


5

Action Required to Enable Feature

FeatureAutomatically

Available

End User Action

Required

Administrator Action

Required

Oracle Service Request Required

Functional Enhancements

Additional Fields in Allocation

Attribute Transfer Code

Case and Pack Quantity in OBLPN Type

Consolidate Replenishment

Divert Confirmation API

Multiple UOMs in Cubing

Receiving for Unexpected LPN's

RF Move LPN - Suppress Pallet Prompt

RF Receiving by Shipment/Load

Support for Additional UOMs for Standalone and Wave-Based Replenishment

Warning Message in Assign Load UI

User Experience and Usability Enhancements

Recalculate OBLPN Status in OB Container UI

FUNCTIONAL ENHANCEMENTS

ADDITIONAL FIELDS IN ALLOCATION

Update 18C includes the following new fields in the Allocation screen in the UI.

Batch NumberPriority DateExpiry DateAttributes (A to O)

These fields are also available on the Allocation screen in the Wave Inquiry UI.

You can search the allocations based on Batch Number and Attributes (A to O) from the Allocation screen as well as from the Allocation screen in the Wave Inquiry UI.

FEATURE SUMMARY

6

1. 2.

No steps are required to enable this feature.

ATTRIBUTE TRANSFER CODE

Prior to 18C, when a Treat as Attribute was enabled on a lock code, the corresponding lock code value was updated on the inventory attribute field set up in the Treat as Attribute.

To provide flexibility, this new feature allows you to define and populate an alias value on the inventory attribute instead of displaying the lock code value.

Salient features in this enhancement include the following:

A new field called “Attribute Transfer Code” in the Lock Code UI."Attribute Transfer Code" allows you to configure an alias value and populate that value on the inventory attribute.The “Attribute Transfer Code” field is visible on the data-grid, Create (+), Edit, and Search page of the Lock Code UI.

The following are additional characteristics of the “Attribute Transfer Code” field:

This field allows you to set the value in “Attribute Transfer Code” only when the corresponding lock code has Treat as Attribute column set to any attribute values (between a-o). If you attempt to define a value in the Attribute Transfer Code when a lock code has no attribute value, then Oracle WMS Cloud displays a “Treat as Attribute is Blank" message. The value in the "Attribute Transfer Code cannot be Configured” error message and records are not saved.The Lock Code applied or removed is applicable only from the IBLPN and Active location. The Lock Code functionality is not supported for OBLPNs.

When Lock Code is Applied:

If Lock Code applied has the Treat as Attribute value populated with any attribute value (between a-o) and the Attribute Transfer Code is blank, then the system will update the corresponding inventory Attribute value with the Lock Code.If Lock Code applied has Treat as Attribute value populated with any attribute value (between a-o) and Attribute Transfer Code is set to any alias value (for example, a name or number), then the system captures that value from Attribute Transfer Code field and updates the corresponding inventory attribute.If Lock Code applied has Treat as Attribute value set to blank and Attribute Transfer Code has also set to blank, then the system does not update with any corresponding inventory attribute value.

When Lock Code is Removed, the system nullifies the corresponding inventory attribute irrespective of the following scenarios:

If the Treat as Attribute value populates with any attributes value (between a-o) and Attribute Transfer Code is blank.If the Treat as Attribute value populates with any attributes value (between a-o) and Attribute Transfer Code is set to a value.If the Treat as Attribute value is not populated with any attribute value (between a-o) and Attribute Transfer Code is blank.

STEPS TO ENABLE

Navigate to Lock Code UIPopulate a value in attribute transfer code column for the lock codes which has treat as attribute enabled. By default, attribute transfer code column is blank.

STEPS TO ENABLE

7

CASE AND PACK QUANTITY IN OBLPN TYPE

Enhancements have been added in cubing logic so that when you are determining the OBLPN Type, Oracle WMS Cloud considers the Case/Pack quantity of the inventory (when the Allocation_UOM is Cases/Packs). Warehouses can receive inventories with different case/pack quantities. WMS has the ability to store inventories with different case/pack quantities. Case/pack quantities of the inventory will not always be same as the item's standard case/pack quantity. As such, during cubing, if inventory is allocated in cases/packs, Oracle WMS Cloud will always honor the case/pack quantity of the inventory while determining the OBLPN Type.

STEPS TO ENABLE


CONSOLIDATE REPLENISHMENT

Prior to 18C, replenishment with consolidate and distribute flow enabled did not honor case and pack qty from the inventory. In update 18C, consolidate and distribute flows in replenishment have been modified to consider case qty or pack qty from the corresponding inventory record while allocating inventory for replenishment with the consolidate and distribute flag set to yes. As part of update 18C, Oracle WMS Cloud supports allocating inventory with the same item having different case and pack quantities.

The following enhancements are added:

When you allocate inventory with a consolidate and distribute flow for replenishment (through wave based or standalone replenishment) Oracle WMS Cloud will consider the case or pack qty from corresponding inventory:

A new company parameter "CONSIDER_ITEM_STD_UOM_QUANTITY_FLG" has been added to support considering inventory.case or pack qty when allocating for replenishment using consolidate and distribute flow is set to yes.When “CONSIDER_ITEM_STD_UOM_QUANTITY_FLG” is set to YES, the system will always use the item's standard case or pack qty while determining the source inventory to be replenished. If inventory whose pack or case qty is the same as what has been configured on the item, then you should set this flag to yes. (For example: If Source LPN has qty of 20 units with std case qty of 20 and there are two locations of 10 units capacity to be replenished then the LPN will not be allocated for replenishment).When “CONSIDER_ITEM_STD_UOM_QUANTITY_FLG” is set to NO, the system will consider the corresponding inventory and case or pack qty while considering the source inventory to be replenished. If there are varying case quantities being picked into the intermediate LPN during distribution, there is no guarantee of maintaining the original UOM picked. Depending upon the need, inventory picked in the intermediate LPN in cases or packs might get broken. (If source LPN has qty of 20 units with inventory case qty of 20 and there are two locations of 10 units capacity to be replenished then system will allocate the LPN. You will be prompted to pick 1 case from the LPN, and during the distribution phase the case qty will be broken).

Update 18C now includes the option to allocate replenishment in terms of units and packs as well. While picking inventory into intermediate LPNs using a consolidate and distribute flow for replenishment, the system has been enhanced to maintain different inventory records in the intermediate LPN if allocations of cases and packs are picked or allocations of cases and packs are picked with varying case or pack qty. This will help to retain the original allocation UOM's as much as possible.

During a consolidate and distribute flow, upon ending the intermediate LPN picked, final replenishment allocations are created from the internal bulk pick allocations. Update 18C now supports picking different UOM's and inventory with varying case or pack quantities into intermediate LPN as part of consolidate and replenishment flow. Now, while you are creating final replenishment allocations upon

8

1.

2.

ending the tote, the system will order candidate locations in descending order of available space in the location. Once final replenishment allocations are created, during distribution, you are taken to different locations for replenishment based on the location's putaway sequence and then UOM. All Picks in different UOM's for one location will be completed before going to the next location for replenishment.

Upon ending the tote for replenishment with intermediate LPNs containing different UOM's or varying case or pack quantities, the system will strive to retain the original allocation UOM's. Depending upon the locations need, the system might end up breaking the UOMs or the case/pack quantities picked in the tote.

A new screen parameter "distribution-uom" is added to "rf.inbound.cwrfpickiblpnreplen" module which will control whether to create final distribution allocations in units or try to use UOM from the source inventory.

If distribution-uom is set to Units, then final distribution allocations will always be in Units, even though the tote has inventory picked in Packs or cases we end up creating allocations in units only.If distribution-uom is set to blank or Use Source Inventory UOM, then when you are creating final distribution allocations, the system will strive to maintain the UOM of the allocations picked into the intermediate LPN.

NOTE: There are some cases with the "distribution-uom" parameter where allocations could be created in terms of units even though picked inventory is in cases. This depends upon the outstanding need in the destination locations being replenished.

STEPS TO ENABLE

Configure the company parameter CONSIDER_ITEM_STD_UOM_QUANTITY_FLG to No if consolidate and distribute replenishment has to consider varying inventory case or pack qty.Navigate to the screen parameters for rf.inbound.cwrfpickiblpnreplen module. Set the screen parameter

to Units if the distribution phase of replenishment is handled in units even though the distribution-uomallocation was performed in cases or packs.

DIVERT CONFIRMATION API

In 18C, the Divert Confirmation API has been enhanced to include Pallet Nbr. This helps MHE systems like ASRS to send pallet information to Oracle WMS Cloud after it has been diverted to a location.

LPN Nbr has been a mandatory field for the Divert Confirmation API and will continue to remain a mandatory field. However, Pallet Nbr is an optional fieldIf only the LPN Nbr is populated in the API message, WMS locates the LPN to the drop location (if divert lane is provided in the message) OR to the destination location provided in the message.If both LPN Nbr and Pallet Nbr are populated in the API message:

WMS creates the pallet in the system if it does not already existThe LPN is then associated with the palletThe pallet and the LPN are located to the drop location (if divert lane is provided in the message) OR to the destination location provided in the message.IHT 51 – Inventory Movement is written for each LPN on the pallet.The pallet could be Inbound or Outbound, however WMS does not allow pallets to be located to an active location.If the pallet is new to the facility, it shows up on Pallet view. Newly added LPNs show up on Pallet History view with an activity type of ‘LPN Added’.

STEPS TO ENABLE


9

1. 2.

1. 2.

MULTIPLE UOMS IN CUBING

Prior to 18C, during cubing, OBLPN's were created based on UOM (Units or Cases or Packs) during wave allocation. In 18C, Oracle WMS Cloud allows you to create an OBLPN with a different UOM during wave allocation. Combining multiple UOM's in one OBLPN allows you to optimize your shipping efficiencies by allowing more cubing opportunities.

STEPS TO ENABLE

To create an OBLPN with different UOMs:

Configure "Alloc UOM" and set the break by quantity to 0 in the Ordering criteria of the cubing rule. If you want existing functionality of an OBLPN to be created based on UOM, you should not configure "Alloc UOM" in the Ordering criteria of the cubing rule.

NOTE:

OBLPNs which have different UOMs should be executed in a Non-Tasking mode for additional operations like Pick and Pack etc.Only cubing modes 'Use Predetermined OBLPN Type' and 'Calculate OBLPN Type and cube with wave' are supported for OBLPN's with different UOM during wave allocation.You should not use the cubing mode ‘Calculate OBLPN Type and cube at packing’ for OBLPN creation with different UOMs, because during Repack when you scan a SKU to create an OBLPN, Oracle WMS Cloud considers it as a single unit, even though the picked inventory is in cases/packs.Task creation is not supported during wave allocation for OBLPNs which have different UOMs.Task execution is not supported for OBLPNs which have different UOMs.Outbound audit is not supported for OBLPNs which have inventories with different UOMs.

RECEIVING FOR UNEXPECTED LPN'S

There can be cases where you may need to enable detailed receiving for remaining LPNs in a shipment after you start receiving a shipment.

You can now receive unanticipated LPNs for fully cartonised shipments. The action buttons "Select for Dtl Recv" or "Deselect from Dtl Recv" will get enabled in cases where the shipment status is > In Transit.

For example, if the vendor has sent LPN01 with 50 units for SKU1 and in reality, the vendor has sent in two different boxes (LPN01- 30 units and LPN02- 20 units), with this functionality, the vendor can still receive the shipment. This new feature includes the following details:

"Select for Dtl Recv" or "Deselect for Dtl Recv" action button is enabled if the selected LPN is in the status "Not Received" and the IB Shipment Status is <Verified.The action buttons "Select for Dtl Recv" or "Deselect for Dtl Recv" will not be enabled when multiple LPNs are selected and if one of the LPN's status is not "Not Received".If you click the "Select for Dtl Recv" button, Detail Receive flag is set to True for all the selected LPNs.If you click the "Deselect for Dtl Recv", the Detail Receive flag is set to False for all the selected LPNs.

STEPS TO ENABLE

Click "Select for Dtl Recv" button to set Detail Receive Flag to True for all selected LPNs.Click "Deselect for Dtl Recv" button to set Detail Receive Flag to False for all selected LPNs.

10

1. 2. 3.

RF MOVE LPN - SUPPRESS PALLET PROMPT

In 18C, the pallet prompt on the RF Move LPN screen has been made optional. This enhancement is useful when a single LPN is being handled as a part of a Full LPN Replenishment task. You can pick up the LPN, with a single scan of the LPN, versus scanning both the LPN and a pallet on which it is picked. It also helps save a pallet label.

A new screen parameter to-plt-display-behavior is used to control the behavior of pallet prompt:

When this parameter is set to , you will always be prompted for a pallet, no Pallet prompt mandatorymatter how many LPNs are on the task. This is also the default behavior.

When this parameter is set to , you will not be prompted to Skip pallet prompt for single LPN taskenter a pallet, if there is only one LPN on the task. The Ctrl key to end pallet ( ) is also suppressed Ctrl-Efrom the RF screen. However, if there is more than one LPN on the task, you will be prompted to enter a pallet number. This is because it allows you to group the LPNs onto a pallet.

STEPS TO ENABLE

Configure the to-plt-display-behaviour screen parameter by upgrading to the new release.Go to RF Move LPN screen -> to-plt-display-behaviour.Choose the module parm choice (Pallet prompt mandatory or Skip pallet prompt for single LPN task).

RF RECEIVING BY SHIPMENT/LOAD

Prior to 18C, if a shipment was fully cartonised and you scanned an LPN which was not on the shipment, then Oracle WMS Cloud threw an error message. In the warehouse, we might not have received the anticipated LPN, or the vendor might have sent same SKU's in a different LPN. In these scenarios, we are not able to receive such LPNs through the RF.

In 18C, you can scan an LPN, which is different from the anticipated LPN while receiving through RF Recv by Shipment /Load. When you scan an unanticipated LPN, Oracle WMS Cloud displays a warning message; you can accept the message if you want to proceed receiving with the unanticipated LPN. You have the flexibility to set the message as an error or warning or disable the message. By default, if you scan an unanticipated LPN, Oracle WMS Cloud displays a warning alert.

STEPS TO ENABLE


SUPPORT FOR ADDITIONAL UOMS FOR STANDALONE AND WAVE-BASED REPLENISHMENT

The Replenishment for Standalone (Lean-Time) is accomplished by pushing inventories from one place to another without creating any picking allocation against an order creation. The standalone replenishment is run based on the configuration in the replenishment template. Whereas, in wave-based replenishment, the system first runs the picking allocation based on the anticipated inventories and then creates a replenishment task.

The following are the general enhancements for replenishment:

For existing functionality, we continue to support standalone replenishment for Reserve to Reserve, For wave-based replenishment, we support Reserve to Active, Active to Reserve, and Active to Active.

and .Reserve to Active Active to Active

11

1. 2. 3.

1. 2. 3. 4.

Prior to 18C, replenishment with UOM supported only LPNs and Cases. Now, we have added support for the UOM for packs for both standalone and wave-based replenishment from Reserve to Active locations.In 18C, replenishment with UOM is supported in terms of Units. Previously, an error message was displayed when replenishment was attempted with UOM in terms of Units. The current enhancement supports replenishment with UOM in terms of Units for both standalone and wave-based replenishment.

NOTE: Replenishment with UOM for Packs and Units is supported for Reserve to Active locations. However, if allocation location type is Active to Active or Active to Reserve, then the system sets the Replenishment with UOM to Units only.

Prior to 18C, the Capacity Check Method was supported only in wave-based replenishment. In the current enhancement, the standalone replenishment rule is expanded to support Capacity Check Method for Units and Volume, and fall back to Units.

Previously, we supported the Ignore Order Details Attribute List in the Wave template that helped you to provide instructions to the system on which attribute to ignore when the wave was run. We have introduced the same function in 18C by adding a new field Ignore Order Details Attribute List, in the Replenishment Rule.

NOTE: If the Replenishment Rule is configured to ignore an attribute and meanwhile, if a wave is strict about the attribute, then replenishment with picking waves does not occur.

The following are the features of the new field Ignore Order Details Attribute List:

This field is added at the Replenishment Rule Header level and can be viewed on the data-grid, create, edit, and copy pane of the Replenishment Rule page. This field allows you to specify the attribute to be ignored in both wave-based and standalone replenishment.When the Replenishment Rule template for UOM is in terms of LPNs for both standalone and wave-based, the is set to blank. This is an existing behavior retained from Ignored Order Detail Attribute listthe wave template.When the Standalone Replenishment Rule template for UOM for Cases, Packs, and Units and the Consolidate and Distribute is set to (or blank/unchecked), then the Ignored Order Detail Attribute List Nofield displays an attribute value from a-o.When the Standalone Replenishment Rule template for UOM for Cases, Packs, and Units and the Consolidate and Distribute is set to , then the Ignored Order Detail Attribute List displays a blank Yesfield.

STEPS TO ENABLE

To Consider or Ignore Inventory Attributes for standalone or wave-based replenishment

Open Replenishment TemplateNavigate to Replenishment Rule from replenishment templatePopulate the ignore order attribute list with the relevant attributes which needs to be ignored.

To add support of replenishment in terms of units or pack

Open Replenishment TemplateNavigate to Replenishment Rule from replenishment templateNavigate to replenishment rule sequence.Create a rule sequence with UOM of units or packs.

12

WARNING MESSAGE IN ASSIGN LOAD UI

Update 18C includes an enhancement made in the OB Load screen. When you try to assign an OBLPN to a load through the "Add LPN on Stop" screen; Oracle WMS Cloud displays a warning message and requests for a confirmation in the following cases:

If the OBLPN selected to add has order(s) with the external planned load flag set to Yes and the external load number is blank.If the selected load is different from the load expected by the external system for the orders in the OBLPN.

The “Add LPNs to Stop” screen in the OB Load UI includes the following new fields in the data grid:

Externally Planned Load FlagExternally Planned Load Nbr

STEPS TO ENABLE


USER EXPERIENCE AND USABILITY ENHANCEMENTS

RECALCULATE OBLPN STATUS IN OB CONTAINER UI

In various material handling, warehouse managers may have a need to recalculate an OBLPN status.

A new action button, Recalculate OBLPN Status, is now available in the OB Container View UI. This button allows you to update an OBLPN’s status from an “In Packing” to “Packed” status.

There are some configurations which will automatically end an OBLPN and set it to pack when picks are completed. Some configurations don't automatically end the OBLPN and leave it to the user to complete manually.

Some examples of when you might use this button include the following:

When a user has finished picking, but forgot to end the OBLPN.A failure by the system. (Something went wrong while automatically ending the OBLPN and it remains in In-packing status instead of Packed).

NOTE: You should only use this button if you know for sure picking for the OBLPN is in fact complete and you know for sure you want the OBLPNs status to be Packed.

This button is available by default for ADMINISTRATOR and MANAGEMENT roles.You can add group permissions for SUPERVISOR/EMPLOYEE/GUARD roles.

STEPS TO ENABLE

From the OB Container View UI, click Recalculate OBLPN Status and update the status from “In Packing” to “Packed.”

13

APPENDIX

TREAT AS ATTRIBUTE

Certain business operations want to ship inventories with specific lock codes from the facility. To achieve this, clients interface Orders with the lock code value in the particular Inventory Attribute column. You should have lock code values applied in IBLPN or Active Inventory for Oracle WMS Cloud to allocate the inventory when running waves.Treat as Attribute functionality in the Lock Code UI helps to copy the Lock Code value to the Inventory Attribute field when locks are applied to IBLPN/Active Inventory.

When a lock is applied to IBLPN/Active Inventory and if the Lock Code has the Treat as Attribute field set to attribute (between a-o), then the Lock Code/Alias is recorded to the corresponding attribute field set in the Lock Code configuration. During any transaction, if Lock (having " " set to any Treat_As_Attributevalue between a-o) is applied to the LPN or Active Inventory and the LPN or Active Inventory already has value in any inventory attributes (a-o) then Oracle WMS Cloud will overwrite the inventory attribute value on the corresponding inventory record when Lock Codes are applied even though the item is tracking that particular attribute.

You need to populate Treat as Attribute with values which are not used in the workflow, otherwise there is a risk of losing the inventory attribute information as it may get overwritten by the lock code value or alias when Lock (having " " set to any value between a-o) is Treat_As_Attributeapplied. For example, Lock code (L1) is set with Treat as Attribute as “A”. LPN1 has Attribute A= Green ( ). While applying Lock to LPN with L1, Oracle WMS Cloud attribute A is used to track coloroverwrites Attribute A value with L1. Here the LPN lost the inventory information as it got overwritten with the lock code value.If the LPN/Active Inventory is locked (having " " set to any value between a-o), Treat_As_Attributethen when you remove that particular lock, Oracle WMS Cloud will remove respective attribute value from the inventory attribute irrespective of whether the value in the inventory attribute field matches with the lock code that is getting removed.

Case1: When an attribute value (a-o) is populated with Lock1 and later, the lock code (i.e.,Lock1) is removed, then attribute values become blank even though the item is tracking that particular inventory attribute.Case2: When an attribute value (a-o) is populated with Lock1, and the value is updated with new value from other transactions, and later, the lock code (i.e.,Lock1) is removed, then attribute value becomes blank even though the item is tracking that particular inventory attribute.Case3: LPN/Active Inventory has Lock1 (having Treat as Attribute set to any value between a-o) and Lock2 (having Treat as Attribute set to blank). Then while removing Lock2, theattribute values populated in the LPN/ Active Inventory will remain intact.

Treat as Attribute functionality is applicable for IBLPN and Active inventory. For example, if the Lock Code has a value on the treat as attribute field and the lock code is added/removed from an IBLPN/Active Inventory, then the lock code value or alias gets copied/removed from the corresponding attribute field for IBLPN/Active Inventory.Treat as Attribute is not applicable for OBLPNs. For example, if Lock Code has a value on the treat as attribute field, and lock code is added/removed from an OBLPN, then the lock code value WILL NOT get copied/removed from the corresponding attribute field for OBLPNs.If multiple Lock Codes are applied on Inbound LPN, with each of the Lock Code having the same inventory attribute populated in the Treat As Attribute field, then Oracle WMS Cloud will retain the value of the latest lock code or alias.

14

When any transactions that capture inventory attributes are executed, prompt for Inventory Attributes, and if you override the attribute value, then Oracle WMS Cloud will override the inventory attribute value regardless of whether the inventory/LPN has a Lock Code with Treat As Attribute set to any attribute.

For example, Lock Code L1 has Treat as Attribute set as “D” and LPN1 was locked with L1 so the LPN1 has Attribute D value as “L1”. LPN1 has SKUA and SKUA is tracking Attribute D. Now while performing cycle count through RF Cycle Count LPN, system prompts for Attribute D and if user captures the value for Attribute D with “BLUE”, then Attribute D value will get overwritten regardless of LPN been locked with L1 that has Treat as Attribute set as “D”.

During Replenishment or Putaway, if the destination location is locked with Lock (having " " set to any value between a-o), then the incoming inventory will have the Lock Code Treat_As_Attribute

in the corresponding attribute field.

If the location has “ ” set to Yes and the location already has an inventory with a restrict inv attrparticular attribute (which is different from the lock code value), then a new inventory comes to the location, and the lock code is copied to the corresponding inventory attribute. However, Oracle WMS Cloud will not restrict applying the lock code to the inventory attribute field. So, the location may have inventories with multiple inventory combination even though location does not honor multiple inventory attribute combination.During wave-based replenishment, Oracle WMS Cloud creates replenishment allocation and picking allocation for the inventory based on the order and if the order is reserved for a particular attribute, then allocation will happen for the particular attribute. However, while replenishing, if the destination location is locked with Lock (having "Treat_As_Attribute" set to any value between a-o), then the incoming inventory will get the Lock Code in the corresponding attribute field. Picking allocation will not get impacted with the change in the attribute value, it will still point to the particular attribute when it got allocated.

Order is reserved for SKU A, Attribute A= Green ( ). Lock attribute A is used to track colorcode (L1) is set with Treat as Attribute as “A”. Location(L1) has lock code LOCK1. LPN1 (Source Inventory) has Attribute A= Green. While replenishing LPN1 to location L1, system overwrites Attribute A value with L1. Picking allocation will be still pointing to Attribute A= Green.

OCTOBER MAINTENANCE PACK FOR 18C

REVISION HISTORY


Date Feature Notes

27 NOV 2018 Created initial document.

OVERVIEW


15

GIVE US FEEDBACK


FEATURE SUMMARY



Available

End User Action

Required


Required



Cubed Together Flag

LPN Substitution in RF Pack NC Active

Over-Replenishment for Active Locations

Wave Group


Custom Reference Text in Trailer UI

IB LPN Inquiry


CUBED TOGETHER FLAG

Cubing is the process of grouping inventory into outbound containers based on the maximum volume and maximum weight defined at the container type level. The computation of volume and weight is based on the items/weight/volume dimensions defined at the item's appropriate UOM level. The cubing rules feature allows customers to define how cubing should take place. It is based on various breaking criteria such as weight, volume, and other item attributes within the max volume and max weight limits. This feature now introduces an additional flag, Cubed together flag, in the ordering criteria for the cubing rules.

This flag allows you to group inventory within the container. In other words, if your ordering criteria is set to Order dtl cust field 1 and the flag cubed together is set to yes, all the order details for the unique order dtl cust field 1 will be in the same box without being limited by break by count. For example, your order is for a school and you are saving the class id in the Order dtl cust field 1, and you have the cubed together flag set to yes. If the complete class will fit in a box, all contents for that class will allocate to one box. If another class's contents can completely fit in the same box, then WMS will add the class contents to this box. However, if a complete class cannot fit into a box, it will get a full box and it's remaining items can still be combined with other classes that can fit completely in that box. This will reduce the occurrence of classes getting spread out and mixing with other classes.



16

1. 2. 3.

1. 2. 3.

STEPS TO ENABLE

To enable Cubing together order lines based on grouping criteria:

Navigate to Ordering Criteria section of cubing rules.Enable the Cube together flag for the column which is part of the ordering criteria.Enable the Cube together flag for the column which is part of the ordering criteria.

LPN SUBSTITUTION IN RF PACK NC ACTIVE

In 18C, you are able to substitute an LPN even if the batch or expire date doesn't match. This new feature gives more flexibility to customers that want to allow users to substitute inventory while using the RF Pack NC Active. A new parameter “req-lpn-sub-validations” is available that allows you to substitute an LPN based on the validation rule set in the screen parameter, even if the batch number or expiry date does not match with the allocated LPN.

The available validation rules include the following:

When this parameter is set to / : by default, the system is set to a Blank value. In this case, the All Blanksystem validates for both the batch number and the expiration date for the inventory in the substituted LPN with the batch number and expiration date of an allocated LPN.When this parameter is set to : the system matches the batch number for inventory in the Batchsubstituted LPN, with the batch number in an allocated LPN.When this parameter is set to : the system matches the expiration date for inventory in the Expirysubstituted LPN, with the expiration date in an allocated LPN.When this parameter is set to : the system substitutes the LPN even if the batch number or Noneexpiration date does not match with an allocated LPN.

NOTE: The substitution of LPN for inventory applies only for Reserve pick. When the company parameter ORD_DTL_BLANK_BATCH_NBR_IS_WILDCARD is set to Yes or No, the LPN substitution screen parameter takes precedence and validates the substitution of an LPN in the following scenarios:

ORD_DTL_BLANK_BATCH_NBR_IS_WILDCARD = / and screen parameter (req-lpn-sub-Yes No validations) is set to , Oracle WMS Cloud allows substitution of the LPN even if the order batch Nonenumber or expiration date of the substituted LPN does not match with the allocated LPN.ORD_DTL_BLANK_BATCH_NBR_IS_WILDCARD = / and screen parameter (req-lpn-sub-Yes No validations) is set to /Blank or , then you cannot substitute the LPN because the system All Batchvalidates the order batch number and the expiration date of the substituted LPN with the allocated LPN, and throws the error message “ ”.Sub LPN not possible

STEPS TO ENABLE

To enable the substitution functionality with the validation rule:

Configure the by upgrading to the new release.req-lpn-sub-validations Go to Pack NC Active screen > req-lpn-sub-validationsChoose the module parm choice (All, Batch, Expiry and None).

OVER-REPLENISHMENT FOR ACTIVE LOCATIONS

Some clients may have picking locations (active locations) that cannot accommodate the orders need or the incoming inventory from one or more reserve locations. Quantity that can be replenished to the location is limited to the corresponding pick locations maximum units defined. Customers may want to push the inventory

17

to the destination active locations in increments. Update 18C now allows customers to be able to replenish beyond configured location's max and provides an ability to replenish inventory going through multiple hops into corresponding destination locations using new RF Module.

REPLENISH BEYOND LOCATION'S MAX

New flag is added to replenishment rule " ". This drives Ignore Capacity for Last Permanent Locationwhether to allocate if the order's need is more than the determined location's capacity. By default the value is set to No.Replenishment beyond location's max will be performed only for locations of type "Active" and for permanent sku dedicated locations.Functionality to replenish beyond location's max is considered during wave-based replenishment only.If there are multiple permanent dedicated locations and if the order's need is more than combined locations capacity, then replenishment is performed until max for all the locations except for the last one.

NEW RF MODULE TO PICK INVENTORY FROM DROP LOCATIONS

The new RF Module "rf.inbound.cwrfmultistepreplen" does the following:

Allows you to support systemic movement of inventory between drop locations or drop locations to final destination locations.Prompts you for picking up inventory in the current drop locations and replenished to the final location or move the relevant inventory from one drop location to another.Can be used for movement of inventory from locations of type "drop" only. Internally creates task of type "CONSOL_REPLEN". So it’s required for users to create task zone movement rules against CONSOL_REPLEN task type.

If the picked inventory is from drop location and as per the task zone movement path if subsequent stop is a drop location, system will suggest the next drop zone. If the next hop is the final destination system will prompt user to scan the final destination location.

Determines whether there is inventory in the current task zone (inferred from the scanned location) and determine the requirement for the inventory in the destination location and prompt user to pick inventory from the current drop location.

Destination Location might not have space but there can be replenishment need as locations could be allocated for replenished beyond maximum capacity. After entering the source task zone and destination task zone system will try to determine how much of the inventory present in the source location (drop location/s) can be used for picking and sending it down the fulfillment sequence.

Allows users to pick inventory for one unique task zone movement path. Inventory for multiple destinations cannot be mixed in a single tote.

The following are the different screen parameters added to the new module:

determine-src-inv-by: This parameter controls how user can specify what is the current task zone, so that inventory in the associated drop locations can be searched. If customers can enter the task zone then specify the value as "Task-Zone". Option is also provided to determine the source task zone based on the scanned location. If user needs to specify the task zone by scanning the location mention the value as location. task-type: Destination Task zone to be replenished is determined from the task-type value provided in the screen parameter or user have to enter the value once. Once source task zone to search for inventory and also destination zone the person is working is determined system will look for inventory in the current location and if there is candidate inventory user will be shown the LPN/sku to be picked from the drop location.qty-uom: Provides options to pick in terms of units/packs or cases. If option selected is packs or cases, then movement of inventory will happen based on corresponding inventories case or pack quantity. Qty to be picked from the drop location will be in the UOM specified in the screen parameter.

18

1. 2.

dest-locn-filter-criteria: This parameter controls which destination locations are to be replenished. If the parameter value is set to

when inventory for destination locations whose current inventory level is Current<=Locn Minimum:less than or equal to location minimum it will be searched in the source zone. If a location to be replenished has an inventory greater than the location minimum (even though inventory is present in the source zone the user is working), the system will not consider that item for moving the fulfillment chain. If multiple locations are determined, the system will order the inventory to be picked in ascending order of the putaway sequence in the destination location.If value is none, then all destination locations which are determined to be replenished will become eligible as long as there is space. Destination Locations to be replenished will be ordered in descending order of available space (location max-location current_qty). With this setting, even if the destination location requires only a few units, you are prompted to pick that inventory.

pick-for-single-dest-locn: controls whether tote can have inventory for single or multiple destination locations. If customers do not want to mix inventory for multiple destination locations then set the value to N.assume-single-sku: assists you in picking single sku's only, even if there are eligible sku's to be picked system will pick single sku only.

NOTE: A wave might have created a full LPN replenishment task to be picked from an initial source location to the final destination location. In this case you need to drop the allocated LPN using wave generated task to move inventory to the initial drop location. From the drop location, you can use "rf.inbound.cwrfmultistepreplen" for systematic movement of inventory to the final destination locations.

STEPS TO ENABLE

To enable wave-based replenishment to replenish beyond location’s max

Navigate to Replenishment rule associated with the picking wave templateEnable the Ignore Capacity for Last Permanent Location flag(if the destination location has candidate permanent location for the sku and if order need is more than candidate location max then perform replenishment up to need.

WAVE GROUP

Prior to 18C, multiple wave templates could be chained together to be running one after the other using wave groups. Wave groups provide a mechanism to associate multiple wave templates. Each wave runs on its own and once the first wave is completed, Oracle WMS Cloud invokes the second wave as per the sequence configured on the wave group. Each wave creates tasks independently. As tasks are created independently, there could be chances of replenishment happening from similar source locations across different waves. If separate tasks are created, there could be chances of traffic in the pick areas. Update 18C addresses this issue and the following are some of the salient features added to enhance wave group functionality:

The Task Creation Template is now available in wave group configuration. You can now associate a task creation template at the wave group level. You can edit the Task Creation Template in the wave group screen. The Task Creation Template field is not exposed in the wave group run UI by default, so you need to add it to the screen.If a Task Creation Template is not provided, then tasks are created at the individual wave template level. By default, if customers are using the Task Creation Template, the existing wave groups field will be blank. If a Task Creation Template is provided at the wave group level, then you can create tasks by looking at allocations spanning across different waves pertaining to the wave group run. Task creation at the wave group level is handled once all the waves within a wave group have completed the process. If a Task Creation Template is provided at wave group level, Oracle WMS Cloud looks for any open allocations which do not have tasks created and will subject those for task creation. Existing tasks created based on the configuration for individual wave templates will remain as is. Only allocations which do not have tasks

19

1. 2.

associated will be subjected to task creation based on task template configuration at the wave group level. You can determine (based on use cases) what tasks need to be created at the individual level and what tasks need to be created across different wave templates. For example, one use case is picking tasks to be created at the individual wave template level and replenishment tasks to be created at the wave group level.Prior to 18C, if a wave group run was initiated, there was no separate user interface to view every instance of a wave group run. In 18C, you can view every wave group run through the new UI, Wave Group Run Inquiry (WaveGroupRunView module). Wave group logs which were present in the Wave Group UI will now be available from the wave group run. This provides visibility of wave group logs for every wave group run clearly. Wave group logs are available as an action button from Wave group run inquiry.For every instance of a wave group run, Oracle WMS Cloud creates a wave group run number based on the new sequence counter introduced. Just as a wave number is generated for every instance of a wave, wave group run will also generate a wave group run number. A new sequence counter code, WAVE_GROUP is now available in 18C. You will be able to see the status of a wave group run using wave group run inquiry. In cases where all the waves associated with the wave have not completed the run, the status will be In-Processing (started). If the wave group has a task template associated then the status of the wave group run, the status will be "task creation in progress" before going to completed status. There are checks in the application to prevent any undoing of waves associated with wave group run if the status of the wave group is "task creation in progress".As we are creating tasks across different waves, Task Inquiry has been enhanced to display the wave group run number. The option to search tasks based on the wave group run number is also added so you know which tasks are created at the wave group level. This filters tasks created at the wave group level. Wave Inquiry filter criteria has been enhanced to include a Wave group run number. This allows you to see individual waves associated with a particular instance of a wave group run.

STEPS TO ENABLE

To enable configuration of Task creation at wave group level.

Navigate to Wave group Inquiry Screen.Associate Task creation template in wave group screen.


CUSTOM REFERENCE TEXT IN TRAILER UI

A new Custom Reference Text field is introduced in the Trailer UI. This field gives you the flexibility to capture additional trailer information. This field is also made available in the Appointment UI.

Some of the characteristics of the custom field are:

By default, the custom field is masked from the data-grid view. However, this field can be manually added.This custom field is made available on Create pane, Edit pane, and in the Search criteria field for the Trailer/Appointment screen.

A new read-only Custom Reference Text field is added to the data-grid of the ObViewLoad UI. This custom field displays the value entered in the Custom Reference Text field of Trailer UI.

20

1.


IB LPN INQUIRY

In some cases you may want to prevent edit batch number in order to maintain data integrity. A new screen parameter is available in the IbContainerView screen that restricts all users from modifying the batch number for batch tracking inventory.

The UI parameter “allow_edit_batch_nbr” is configured in the IbContainerView with the following options:

When the “ ” is set to Yes/blank, the Batch Number in IBLPN screen allows you to allow_edit_batch_nbrupdate batch numbers and save the changes. This is an existing behavior and all the validation while updating the batch number remains the same.When the “ ” is set to No, Oracle WMS Cloud displays an error “ allow_edit_batch_nbr Cannot change

” message when you attempt to modify the Batch Number in the IBLPN.batch number

NOTE: This enhancement is applicable for inventory tracking batch. For a non-batch tracking inventory, Oracle WMS Cloud displays an error “Item does not track batch or expiry” when you attempt to modify the batch number in the IBLPN.

STEPS TO ENABLE

In the IbContainerView, set the “allows_edit_batch_nbr” parameter to .No

RELEASE 18C

REVISION HISTORY


Date Feature Notes

31 AUG 2018 Created initial document.

OVERVIEW


GIVE US FEEDBACK


STEPS TO ENABLE

http://mailto:[email protected]

http://mailto:[email protected]

21

FEATURE SUMMARY



Available

End User Action

Required


Required



RF Receiving

RF Print Item Label

Printer Selection

Return Facility on Inbound Shipment

Pack with Wave

Enable / Disable Company Flag

Priority Date Traceability

Additional Carrier Type Support

Inbound Shipment View

Lock Codes on Inbound Shipments

Reference LPN Number Display

Oracle Cloud Migration

Update Route Number for Multiple Orders

Oracle SCM Cloud Execution

Load Assignments for Orders Planned by OTM

Close Load

Reset External Planned Load Number from Order Header Browser UI

Integration Enhancements

Outbound LPN Shipping Info Triggered at Status Change

Generate Outbound LPN Info upon Manifest

Generate Order Export at Order Packed

XML Support for Additional Input Interfaces

Expanded Selection Criteria in Output Interface

FedEx International Shipment

22



Available

End User Action

Required


Required


Output File Target Selection

Item Master Protected Fields

Rearrangement of XLS File Format for Route Input Interface

Include Printer in Outbound LPN Shipping Info

Auto Process Inventory History Records

Oracle SCM Cloud Integration

Changes to Planned OB Load Interface

New logic for Loading API

REST API

Create LPN API

Update Custom Fields for Current lgfapi REST API

New API to Bulk Update Inventory Attributes


RF Screen Layout Realignment

Oracle WMS BI Cloud Reports

Improved Literal Localization

Improved Time Zone Localization

Yard Management Improvements

Oracle WMS BI Cloud Framework

Order Detail Level Permissions

Document Design and Printing

Price Label Support with Label Designer

Case and Pack Labels Using Label Designer

OBLPN Number Labeling and Printing


RF RECEIVING

The following screen parameters have been added to both “Receive by Load” and “Receive by Shipment” modules that provide additional flexibility during receiving:

23

1.

2.

3.

4. 5. 6.

LPN Prompt: Using this new screen parameter, the LPN Prompt is now made optional and blind LPNs can be received without explicitly scanning the LPN numbers. This parameter can be configured with the following Parameter choices None, Mandatory, Not mandatory, or Auto Generate. When the screen parameter is configured to None or Not mandatory, and you do not scan the LPN number, then Oracle WMS Cloud automatically generates LPN numbers during receiving. With this change, you do not need to print blind labels upfront. Your warehouse should ensure that all the users have operational controls on matching the labels printed with LPNs received, when multiple people are receiving and printing LPNs to the same printer.Prompt Location: This screen parameter can be configured to None, Do not prompt, Prompt if not known after receiving is complete. Support is added to locate inventory directly to an active location as long as the module is not configured for palletized receiving.Print Labels: This screen parameter provides an option to print None, Inbound LPN Label, UOM Case Label, UOM Pack Label, LPN Label and UOM Case Label after receiving is complete. When this parameter is configured, the RF option displays the key to capture printer information of the Ctrl Psession.

NOTE: Inbound LPN Labels/Case/Pack label print requests are routed to the printers using Ctrl P key. If not overridden, the request is routed to the default label printer attached to the user.

Prompt Dock Door: This screen parameter can be configured to None, Prompt or Do Not PromptPrompt Trailer: This screen parameter can be configured to None, Prompt, Do Not PromptConfirm-uom-qty: This screen parameter can be configured to None, Do Not Prompt or Prompt per Sku per LPN. If this parameter is configured to Prompt per Sku per LPN and the receiving UOM is configure to “ ”, users are prompted for Pack or Case quantity. You have an option to override the Packs or Casesitem’s standard pack or case quantity for each LPN Received. This mode is useful for items in which the vendor does not have a pattern to the case or pack quantity. If this parameter is configured as “Do Not Prompt”, you can use control Ctrl Q key to change the Case or Pack quantity.

STEPS TO ENABLE

Enable the following screen parameters:

LPN PromptLocation PromptPrint LPN and Case LabelsPrompt Dock DoorPrompt TrailerPrompt Case/Pack Qty

RF PRINT ITEM LABEL

A new transaction “RF Print Item Label” allows you to print item labels through an RF device. You have an option to scan the printer, item, and number of labels to be printed. If you want to print through a default printer, you can tab through the printer prompts and the system will automatically accept your defined default printer for printing the labels.

STEPS TO ENABLE


PRINTER SELECTION

In 18C, the following enhancements are added for label printing:

24

1. 2.

Ability to change default Label Printer through RF

New Control Key: “Ctrl P- Change default printer” is added in the launching screen of RF to change the default label printer.Default printer changed from RF is updated in the "Default label printer" field in the User screen.Ability to add default document printer through User screen or User Interface (UI)

In 18C, we have introduced a new field in User screen to add default document printer for the user.The field "Default document printer" is a free text field. User should make sure to enter correct printer name in the field of type DOCUMENT (as defined in Printer Configuration UI).

Enhancement in the RF screens to consider the default label/document printer defined for the user. Going forward, you will be able to use the default label printer if you tab out without scanning the printer. If you do not want to print through default printer/s, you can scan the required printer in the Printer Prompt. This enhancement is introduced in the following RF screens:

RF Print ASN LabelRF Print Invoice and LabelRF Print LabelRF Print Ship LabelRF RepackRF Combine OBLPNRF Pack NC ActiveRF Pack OBLPN from IBLPNRF WorkOrder Kit ProcessingRF Retail Price LabelRF Print LPN Packing Slip

STEPS TO ENABLE

Set the "Default document printer" in the User screen or User Interface

RETURN FACILITY ON INBOUND SHIPMENT

Oracle WMS Cloud provides an option to capture facility information for return shipments. An advanced look-up option is introduced in the Create/Edit pane of the Inbound Shipment UI. You can now look-up Inbound Shipments by selecting the Return From Facility Code and/or Return From Facility Type. This allows you to find faster return shipments.

To facilitate this feature, a new flag called Capture Returns Information is now available on Shipment Type. This flag needs to be set to Yes for Shipment Type used for return shipments.

The Inbound Shipment interface is enhanced to accommodate return facility information in the input file/message. Oracle WMS Cloud validates to ensure that the shipment type used on such shipments has the Capture Returns Information flag set to Yes.

Oracle WMS Cloud also includes return facility information on Transfer Shipments depending on the Shipment Type determined for a transfer shipment.

When a return shipment is verified, the return facility information is included in the Shipment Verification file.

STEPS TO ENABLE

Set Capture Returns Information flag to Yes on the Shipment Type used to returned shipments.Add returned_from_facility_code on the IB_Shipment Interface File

25

PACK WITH WAVE

Some warehouses need to pack large volumes of brochures and mail-out catalogs to be shipped out for customers without being too concerned about inventory accuracy or tracking inventory. In these cases, you could skip the picking process in Oracle WMS Cloud for such items and the picking is done outside of the WMS system.

In order to facilitate this requirement, "Pack with Wave" has been introduced for dummy sku items. The following enhancements have been added:

ITEM MASTER

The following enhancements provide item level support for "Pack with Wave" functionality:

Introduced a new flag to item which supports pack with wave functionality. This flag needs to be checked in order to be considered for the "Pack with Wave" logic during wave.The system does not enable ‘pack with wave flag' if dummy sku flag is not enabled.‘pack with wave flg’ is exposed to Item Interface.‘pack with wave flg’ has been added to the selection criteria of Wave's Dynamic Selection Criteria rules, Cubing Selection, Ordering rules and Task Selection.

WAVE TEMPLATE

’Pack with Wave' is added in the create/edit/copy pane of the Wave Template UI.

NOTE: Pack with Wave is not supported along with Replenishment with picking wave. Support for performing pack with wave will be done for items which are marked dummy and items which have 'pack_with_wave_flg' enabled at item level.

Pack with Wave is added if the wave template is set as the following:

'pack_with_wave_flg' set to yesUnderlying item of the order selected for the wave has pack_with_wave_flag set to yesItem has dummy sku flag set to yes

After that, the system creates outbound LPN’s which are in Packed status and the order status is calculated accordingly. Oracle WMS Cloud will perform load assignment or manifesting for the Outbound LPN’s created. The application can cube multiple sku's in same OBLPN. If any of the items in the determined outbound LPN are not marked dummy or if items are marked dummy but not eligible for pack with wave, then the corresponding outbound LPN will not be subjected to Packing Steps (All items on the cubed outbound LPN should have dummy_sku_flg set to yes and have 'pack_with_wave_flg' set to yes).

WAVE INQUIRY

Sometimes, you might want to perform pick and pack updates outside of a wave as you might need to watch the allocations as part of a wave run. The “Undo Wave” option will not undo/cancel pick and pack updates.

If you want to perform Pick and Pack updates after the wave is run, a new button ‘Autopack Wave OBLPNs' is added to the Wave Inquiry UI where you can select the wave and perform Pick and Pack (applicable for dummy sku items only).

NOTE: The ‘Auto-Pack Wave OBLPNs’ button will be enabled only if the selected wave's run status is Completed, Not Fully Allocated or Completed.

26

1.

2.

1. 2.

STEPS TO ENABLE

Set the Pack with wave flg to Yes for the “Dummy” Items. This could be done on the Item UI or Item Interface.Set the Pack with wave flg to Yes on the Wave Template.

ENABLE / DISABLE COMPANY FLAG

This new feature allows you to deactivate the company when it is no longer required or it is out of business.

In order to facilitate this requirement, the following enhancements are added:

New button is added in the Company Screen Module which allows you to “Activate/Deactivate”deactivate or activate a company.The new button is controlled by a permission and it is password protected.Whenever the company is deactivated/activated back, a corresponding log is written in the Framework/Common Logs.Upon deactivating the company;

Users whose default company is associated with the deactivated company will not be able to login.The deactivated company will not be visible in any Company drop-down in the browser UI. Also, you will not be able to switch to the deactivated company from the UI.Users will not be able to perform any transactions for the deactivated company from RF//UI/Interfaces and through WebService API”s. Oracle WMS Cloud throws an error when you scan an entity which belongs to the deactivated company.Scheduled jobs will not run for a company which is deactivated.Interface fails for a company which is deactivated.

All open transactions associated to the deactivated company will remain as it is.

NOTE: Parent company cannot be deactivated using the new button from the company UI.

STEPS TO ENABLE

Select the “Activate/Deactivate” button on the Company Screen.Add the permission "Deactivate/Activate Company."

PRIORITY DATE TRACEABILITY

During Receiving or LPN creation, the priority date on the inventory is updated with either the expiry date for expiry tracked items and the manufacturing date or the create time stamp. The Allocation Method for FEFO uses the Priority date for the inventory. When the inventory is transferred to another facility, the priority date from the outbound LPN is not copied to Inbound LPN’s, which potentially creates discrepancies in pushing inventory in a FIFO manner. In order to address this scenario, the following enhancements have been added:

Inbound LPNs created from a transfer shipment will receive an inventory Priority Date from their corresponding outbound inventory.The Inbound LPN screen is enhanced to show the Priority Date field.The Outbound LPN screen is enhanced to show the Priority Date field.

Upon performing RF Modify Cancel OBLPN, the Priority date is copied from an Outbound LPN to the Inbound LPN that was created. Prior to 18C, the Inbound LPN’s created from RF Modify LPN would have create_ts populated as the Priority date.

27

If an Inbound Shipment received has the Priority Date populated, this information is passed on to the corresponding priority date on the Inbound LPN Inventory. Even if items are tracking expiry date, priority_date from an Inbound Shipment detail is considered. Updates in 18C include the option to transfer the Priority Date from the shipped LPN to the received LPN. Customers can now adhere to FIFO without having to use Expiration Dates reducing spoilage and obsolescence in the Supply Chain. To adhere to FEFO, users should leave the Priority Date blank.

NOTE: Existing clients that track expiry dates should ensure that Inbound Shipment detail does not have Priority Date populated.

STEPS TO ENABLE


ADDITIONAL CARRIER TYPE SUPPORT

In update 18C, additional carrier types "AIR, "OCEAN", and "RAIL" are available.

If the carrier type is "AIR, "OCEAN", or "RAIL", Oracle WMS Cloud will accept the load assignment logic. When a load is assigned in Oracle WMS Cloud, the system considers the carrier types as "AIR, "OCEAN" and "RAIL" apart from LTL/TL.

STEPS TO ENABLE


INBOUND SHIPMENT VIEW

Oracle WMS Cloud users may often use the ref_nbr on IB Shipment to map their internal shipment reference numbers to the Inbound Shipments in Oracle WMS Cloud. In order to enable clients to view this field on Inbound Shipment, ref_nbr is exposed on Inbound Shipment View.

STEPS TO ENABLE


LOCK CODES ON INBOUND SHIPMENTS

Currently, Oracle WMS Cloud allows transfer of inventory between facilities as long as these facilities have the correct configuration. In18C, an option is provided to transfer Lock Codes from Outbound shipment to the destination facility. This enhancement allows customers using Lock Codes on inventory to share information across facilities. Sharing this Lock Code information allows traceability across facilities, which provides accuracy to the shipping process of the company. This functionality will only transfer lock codes that have the Copy to Transfer Shipment flag set to Yes on the Lock UI.

In 18C, a new button, “View IB Shipment Container Lock”, is added to the Inbound Shipment UI. A new UI allows you to view the Lock Codes available for LPNs from cartonized Inbound Shipments. You can also add Lock Codes to LPNs from cartonized Inbound Shipments.

28

Set the Copy to Transfer Shipment flag to Yes on the Lock Code Screen.

REFERENCE LPN NUMBER DISPLAY

The container record has the reference LPN number used to store the parent LPN from which the inbound LPN is created. The reference LPN number also has a corresponding Inbound LPN number when you perform full LPN allocations. In 18C, a reference LPN number column is exposed in Inbound LPN Inquiry and Outbound LPN Inquiry.

STEPS TO ENABLE

Add the reference_lpn_number from the Add/Remove column option if it is required to display on the datagrid.

ORACLE CLOUD MIGRATION

Update 18C introduces support for Oracle Cloud Infrastructure (OCI), the latest version of the Oracle Cloud. New customers are provisioned on OCI. Existing customer production environments will be migrated at a later point. In other words, the 18C update and OCI migration will be separate events. Some technical details such as URLs may change for existing customers. Details will be provided to customers once update dates are finalized.

STEPS TO ENABLE


UPDATE ROUTE NUMBER FOR MULTIPLE ORDERS

Oracle WMS Cloud allows you to update the Route of multiple orders from the Order Header UI.

The following enhancements have been added:

A new button in the Order Header UI, Set Route, allows you to update the Route of selected order(s).The new button is permission controlled and only those with permissions will be allowed to use this feature.The update of Route is applicable for Orders that are in a "Created", "Partly Allocated", or "Allocated" status.An Application Log is written whenever the update of the Route is performed using the Set Route action button.

STEPS TO ENABLE

Add the permission "Set Route."

ORACLE SCM CLOUD EXECUTION

LOAD ASSIGNMENTS FOR ORDERS PLANNED BY OTM

Oracle WMS Cloud can receive the planned load information for the order from OTM (or other transportation management systems) and receive it as an Outbound Load. In version 9.0.0, the externally planned load flag was exposed on the order input interface. This flag informs that the particular order is going to be planned by an external system. The external system can interface at a later stage, after the transportation management

STEPS TO ENABLE

29

system has planned the external planned load number. In update 18C, the following functionality enhancements have been added:

NEW LOAD ASSIGNMENT LOGIC

Oracle WMS Cloud has a new load assignment logic. It will prevent assigning an OBLPN if it has Orders that have the external planned load flag set to Yes, and if the external load number is blank. This new logic affects the following modules:

RF Assign Load – you are alerted when trying to assign OBLPN that are not planned for the selected load.RF Load - you are alerted when you try to assign OBLPNs that are not planned for the selected load.Wave - automatic load assignment logicPack – automatic load assignment logicClose Load

NOTE: By default, the alert will be a warning message. This message can be set as an Error/Warning or they can be turned off.

STEPS TO ENABLE

The externally planned load flag should be set to yes.

CLOSE LOAD

Prior to 18C, when users performed close load from the UI or the RF; Oracle WMS Cloud did not show any indication of remaining orders that were planned for the load which has an external planned load number populated. So, the user would close the load without knowing that there were pending orders for the OTM’s planned load.

In 18C, when you perform Close Load from the RF/UI, you will receive a warning if there are pending orders or OBLPNs planned for an external load associated with the load being closed or shipped.

Alerts in the RF are configurable as Error, Warning (default), or they can be turned off. However, an alert in the UI is always a warning.

NOTE: The message will be applicable only if the selected load has external planned load number populated and if there are any Orders/OBLPNs planned for the same external planned load and are not loaded yet.

STEPS TO ENABLE


TIPS AND CONSIDERATIONS

By default, alert messages are set as Warnings. Users can modify or change these alerts to an Error message.

RESET EXTERNAL PLANNED LOAD NUMBER FROM ORDER HEADER BROWSER UI

Earlier, an option to clear an external planned load number on Order detail from the UI was not available. In 18C, a new button “Reset Externally Planned Load Nbr” is available from the Order Header UI > Order Detail View. This action button is permission controlled; only those with permissions can perform resetting of an externally Planned Load Nbr. This button will help to clear external planned load number from order detail.

30

1. 2. 3.

To perform reset of externally planned load number, you can:

Select the Order and go to Order Detail.Select the required order detail and click Reset Externally Planned Load Nbr. The order details that are in the status "Created", "Partly Allocated", "Allocated", “In Picking”, “Picked”, “In Packing” and “Packed” are eligible for update.

The order details which are packed and assigned to the load, by nullifying the external planned load number will not unassign the OBLPN from the assigned load. Oracle WMS Cloud issues an error message when the selected order detail is fully loaded/shipped. Whenever a reset of the externally planned load nbr is performed using the Reset Externally Planned Load Nbr action button, a corresponding log is written in the Application Logs.

STEPS TO ENABLE

Add a new permission to Reset Externally Planned Load Nbr.

INTEGRATION ENHANCEMENTS

OUTBOUND LPN SHIPPING INFO TRIGGERED AT STATUS CHANGE

Prior to 18C, customers were only able to send the "container ship load file" (LLS) when an LPN went to Packed status. This was possible only if the company parameter "LLS_AT_LPN_PACKED" was set to Yes.

In 18C, the company parameter "LLS_AT_LPN_PACKED" is renamed to “FILES_TO_GENERATE_AT_LPN_PACKED”. This change gives customers the flexibility to generate the following files when an LPN goes to Packed status:

Container ship load file (LLS) and the OBLPN Shipping information file (OLO or OLI).The parameter values are LLS; OLO/OLI.If you would like to generate both files, the parameter should be configured with LLS; OLO.

The format of the OBLPN shipping information file will be based on the set up of the file in the output interface configuration UI.

NOTE: For customers having configuration LLS_AT_LPN_PACKED as ‘Y’ or ‘y’, the FILES_TO_GENERATE_AT_LPN_PACKED parameter will be configured as ‘LLS’, when they are migrated to 18C.

STEPS TO ENABLE

Change the value on the Company Parameter FILES_TO_GENERATE_AT_LPN_PACKED.

GENERATE OUTBOUND LPN INFO UPON MANIFEST

Prior to 18C, to successfully Manifest the OBLPN (Outbound LPN) in the UI, you needed to select the existing button "Send OBLPN Info". Update 18C allows both actions to be completed by clicking Manifest OBLPN. A new screen parameter has been added to the OBLPN Inquiry screen "gen_oblpn_shipping_info". A default set to No, and a parameter value of Yes will generate the OBLPN Info file after you click Manifest OBLPN. This enhancement improves the efficiency of this process, and it prevents mistakes.

31

STEPS TO ENABLE

Change the screen parameter value on OBLPN Inquiry Screen "gen_oblpn_shipping_info".

GENERATE ORDER EXPORT AT ORDER PACKED

A new company parameter, FILES_TO_GENERATE_AT_ORDER_PACKED is now available for the PLS file when an Order goes to Packed Status. You can configure this parameter with the values PLS, PBL, PBS, and PLP. When any of these values are set, an Order Outbound Load Export file is generated when an Order goes to packed status.

The format of the Order Outbound Load Export file is based on the output interface configuration set up. For example, if the FILES_TO_GENERATE_AT_ORDER_PACKED value is PLP, and your output interface configuration is set up to generate in XML, then the file that is generated at order packed will be Order Outbound Load Export in XML format.

STEPS TO ENABLE

Configure Company Parameter FILES_TO_GENERATE_AT_ORDER_PACKED to generate the Order Verification file with one of the following values:

PLS (If you want the file to be hierarchical)PBS (If you want the file to be Hdr & Dtl)PLP (If you want the file to be one line)

XML SUPPORT FOR ADDITIONAL INPUT INTERFACES

Update 18C enables Web Service support and XML support for the following input interfaces:

LOCATIONROUTESHIPTO_COMPANY

STEPS TO ENABLE


EXPANDED SELECTION CRITERIA IN OUTPUT INTERFACE

External order management systems that send orders to Oracle WMS Cloud typically keep track of order status by subscribing to IHT-20 (Order Status Change). Additional IHT records like IHT-10 (Container Detail Packed) and IHT-11 (Container Packed) provide detailed information during pick and pack. To ensure that only data specific to the Orders sent by such systems is filtered and sent back, a new filter for Order Type has been added to the Output Interface Configuration for Inventory History.

Other commonly used entities have also been added to the selection criteria (filter) for Inventory History in the Output Interface Configuration as listed below:

Order TypeRef Value 6 to Ref Value 20To LocationItem Description

32

TrailerShipment TypePO TypeBilling Location Type

STEPS TO ENABLE


FEDEX INTERNATIONAL SHIPMENT

In update 18C, the built-in integration to FedEx International Shipments now allows the support of Commercial Invoices. This new enhancement will send the required information to FedEx, so FedEx can generate the Commercial Invoice. Oracle WMS Cloud will make the direct web service call to FedEx if the destination country is other than the US, and if the standard carrier accessorial in the Ship Via detail is either FedEx Express or FedEx Freight. Paper Invoices are not supported in this enhancement. FedEx will be able to generate the electronic commercial invoice, and Oracle WMS Cloud will not hold any information about the generated Commercial Invoice.

STEPS TO ENABLE

Change the ship via accessorial to INTL_ELECTRONIC_COMMERICAL_INVOICE.

OUTPUT FILE TARGET SELECTION

CHANGE IN TIME ZONE CODE IN INTERFACE

Update 18C includes the time zone code for the facility where the load is shipped out from WMS in the following interfaces:

Shipped Loads (SLS)Container Outbound Load Export (LLS)Order Outbound Load Export (PLS)OB Load Parcel Header (OBL)OB Load Parcel HDR_DTL (OLP)

DISTRIBUTION MHE INTERFACE BACKWARD COMPATIBILITY

In update 18C, new facility and company parameters are added to the "TO_MHE_DISTRIBUTION_INFO" and "TO_MHE_IBLPN_INFO" output interfaces to support backward compatibility. These two interfaces expose additional inventory attributes.

A new parameter OUTPUT_LGF_FINFO_TO_MHE_DISTRIBUTION_INFO is available at the company and facility level for configuring whether to generate an interface with new fields for MHE Distribution information.A new parameter OUTPUT_LGF_FINFO_TO_MHE_IBLPN_INFO is available at the company and facility level for configuring whether to generate an interface with new fields for MHE IBLPN information.

If the value is configured as lgf or blank, then the latest version or current version is considered. Oracle WMS Cloud will look at the company parameter at the child company level first and then at the corresponding parent company level. If both parameters are not configured, then the facility parameter value determines the fields for the relevant version.

NOTE: This change is introduced in version 9.0.0 as well.

33

1. 2.

STEPS TO ENABLE

Change Company or Facility parameter OUTPUT_LGF_FINFO_TO_MHE_DISTRIBUTION_INFO.Change Company or Facility parameter OUTPUT_LGF_FINFO_TO_MHE_IBLPN_INFO.

ITEM MASTER PROTECTED FIELDS

Update 18C allows you to configure the following item fields in the Interface Protected Fields UI:

description_2description_3invn_attr_a_trackinginvn_attr_b_trackinginvn_attr_c_trackinginvn_attr_d_trackinginvn_attr_e_trackinginvn_attr_f_trackinginvn_attr_g_trackingpacking_tolerance_percentun_numberun_classun_descriptionpacking_groupproper_shipping_nameexcepted_qty_instrlimited_qty_flgfulldg_flghazard_statementshipping_temperature_instrcarrier_commodity_descriptionshipping_uomhazmat_packaging_descriptionhandle_decimal_qty_flgnmfc_codedummy_sku_flgpack_with_wave_flg

STEPS TO ENABLE

Select the desired fields to protect in the Interface Protected Fields UI


If a field is configured as protected, Oracle WMS Cloud will prevent the item from being updated from the Host/External System.

REARRANGEMENT OF XLS FILE FORMAT FOR ROUTE INPUT INTERFACE

The column positioning for the Route XLS file format is changed. Please refer to the latest Interface Specification documentation for the latest format.

34

STEPS TO ENABLE

Map the latest Route XLS from the Interface Specification documentation.

INCLUDE PRINTER IN OUTBOUND LPN SHIPPING INFO

Update 18C introduces the new columns "printer_type" and "printer_name" in the OBLPN_Shipping_Info and Pallet_Shipping_Info interfaces. Some customers use information from these two interfaces to be shared with an external printing systems for printing shipping labels or packing slips. If external systems are using these interfaces to print labels or packing slips, it will be useful to send the actual printer name in the OBLPN_Shipping_Info and Pallet_Shipping_Info where the documents need to be printed. The actual printer where the document needs to be printed will be selected by the end user who is generating the file.

In update 18C, when you click the Generate Shipping Info action button from Wave Inquiry or Outbound LPN Inquiry, Oracle WMS Cloud displays a pop-up screen with a drop-down list containing entries for the associated printer type and printer name. The selected printer type and printer name is shared in the OBLPN_Shipping Info file. You will have an option to select the printer name. Customers updating to 18C will see that Oracle WMS Cloud prompts for a pop-up screen where you are presented with an option to select a label or document printer.

In update 18C, from Pallet Inquiry, when you click the Generate Pallet Shipping Info action button, Oracle WMS Cloud displays a pop-up screen where you can select either a label or document printer. The selected printer type and printer name is shared in the Pallet Shipping Info file. You have an option to select a printer name. Those updating to 18C will see that Oracle WMS Cloud prompts for a pop-up screen where you are presented an option to select a label or document printer while you are generating pallet shipping Info.

STEPS TO ENABLE



Refer to the Interface specifications for update 18C to see the fields added to the OBLPN_Shipping_Info and Pallet_Shipping_Info interfaces.

AUTO PROCESS INVENTORY HISTORY RECORDS

Oracle WMS Cloud now provides the option to auto process inventory records for a particular activity type, which clients do not necessarily consume. This is so that they can become eligible for purges and can be cleaned up whenever the scheduled purge is executed.

In order to facilitate this requirement, the following enhancements have been added:

A new button in the Inventory History Activity Parameters UI allows you to configure which inventory history activity records will be tagged as auto processed.The new button is permission controlled and only those with permissions can deactivate or activate a company. In addition, this button is password protected.A new column in the Inventory History Activity Parameters grid to display the IHT that have Auto Process enabled.New search criteria in the Inventory History Activity Parameters UI to search the activity based on Auto Process flag.A Keyed Log is written whenever Auto Process is enabled/disabled.

35

For the activity types that are marked for Auto Process, the inventory history record is written as 'Processed'.

STEPS TO ENABLE

Add the permission "Change inventory history activity parm."

ORACLE SCM CLOUD INTEGRATION

CHANGES TO PLANNED OB LOAD INTERFACE

Update 18C includes new fields in the Planned OB Load interface and changes in logic for searching relevant order detail(s) based on the new fields in the Planned OB Load.

The following fields are available in the Planned OB Load interface:

erp_source_hdr_ref erp_source_line_ref erp_source_shipment_ref erp_fulfillment_line_ref erp_source_system_ref tms_order_hdr_reftms_order_dtl_ref

Prior to 18C, the following fields were mandatory in the Planned OB Load interface. As part of 18C, the following fields are now non-mandatory:

order_nbrorder_seq_nbr

New logic has been added for searching relevant order detail(s) based on the new fields in the Planned OB Load:

Prior to 18C in order to search relevant order detail that has been planned by OTM, you would use the WMS fields (Order_Nbr and Order_Seq_Nbr) that were sent in the planned load interface. In 18C, Oracle Cloud will rely on Order/Order Seq Nbr combination, erp_fulfillment_line_ref, or four part key for identifying the specific order details for which the load is planned by OTM.The precedence for identifying the particular order detail that is associated with the planned load is as follows:If OTM sends the Oracle WMS Cloud order fields (order_nbr and order_seq_nbr), the system uses the order_nbr and order_seq_nbr fields for determining the relevant order detail.If the order_nbr and order_seq_nbr are not populated, then Oracle WMS Cloud uses erp_fulfillment_line_ref for determining an order detail.If order_nbr, order_seq_nbr, and erp_fulfillment_line_ref is not populated, then a four part key (erp_source_hdr_ref; erp_source_line_ref; erp_source_shipment_ref; erp_source_system_ref) is used to determine the order detail.Once order details are identified for the planned load by OTM, Oracle WMS Cloud populates with OTM_RELEASE_GID and OTM_RELEASE_LINE_GID in the Order Header. The order may have multiple order detail and each order detail may be planned for a different planned load by OTM. So Release GID Reference will always have the last processed OTM_RELEASE_GID

36

While interfacing the planned OB load and the OBLPNs which are in the packed status associated with the order detail being planned, Oracle WMS Cloud performs load assignment for the underlying outbound LPN’s with the interfaced load (which is created with the OTM's planned load number).While interfacing the planned OB load and the OBLPNs are associated with the order (for an OTM-planned load that is already assigned to the load during waving or packing), the OBLPNs are automatically de-assigned from the existing load and get associated to the new planned load. (The new planned load is created with OTM's planned load number.)The planned OB Load will not associate the OBLPNs to the OTM's planned load if:

The OBLPN is packed for multiple orders and if the order detail has a conflicting externally planned load number, then Oracle WMS Cloud will not associate to the load through the planned load interface.The OBLPN is packed for multiple/same orders with multiple order details and if the order detail has a conflicting externally planned load number.The OBLPN is packed with multiple order and if one of the orders has an external planned flag set to Yes and the externally planned load number is not populated.

STEPS TO ENABLE


NEW LOGIC FOR LOADING API

For a better integration with OTM, a change to Load Assignment Logic using the Assign OBLPN to Load API has been added. This change prevents the assignment of loads for orders that are expected to be assigned by OTM. If the OBLPN contains an order that is marked for external load planning, Oracle WMS Cloud prevents updates on such OBLPNs. Oracle WMS Cloud also prevents updates, when you try to assign another load that it is different from the load expected by the external system.

STEPS TO ENABLE

The externally planned load flag should be set to Yes.

REST API

CREATE LPN API

Version 9.0.0 introduced a new set of APIs that follow REST standards to create entities. You can create an LPN using the new lgfapi REST API. With the Create LPN API, you can create an LPN by making a separate request for each entity as part of the LPNs such as iblpn, Inventory, batch, or attributes. In update 18C, a new lgfapi REST API, composite_create, is introduced to create an LPN. This new API optimizes the creation of an LPN by reducing the number of requests sent to the external system to just one request.

STEPS TO ENABLE


UPDATE CUSTOM FIELDS FOR CURRENT LGFAPI REST API

Update 18C allows you to update the Custom fields on the existing lgfapi entities. This is possible using the verb “PATCH”. Custom fields are informational fields and pass-through data is provided by the customers

In 18C, we have introduced the following changes to associate a planned OB Load:

37

without any associated business logic. You can update these fields with minimal restriction at your discretion using lgfapi. This update currently supports "cust" field(s) only on a single resource per request in "retrieve" mode.

STEPS TO ENABLE


NEW API TO BULK UPDATE INVENTORY ATTRIBUTES

In version 9.0.0, a new functionality is added to the IB Container screen to allow you to bulk update IBLPN inventory attributes. Update 18C has expanded this functionality by adding a new lgfapi REST API, bulk_update_inventory_attributes. This new API, which acts on the inventory entity, allows updating the inventory attributes for inventory in IBLPNs as well as active locations.

STEPS TO ENABLE



RF SCREEN LAYOUT REALIGNMENT

Currently, Oracle WMS Cloud supports decimal numbers in the application. You can enter decimals in the UI and in the RF. Update 18C includes enhanced RF screen layouts to display better information to the user. RF screens are realigned. This new display positioning will make it easier and faster for you to read and process the displayed information. This change allows you to scroll through the quantity entry field.

STEPS TO ENABLE


ORACLE WMS BI CLOUD REPORTS

Oracle WMS Cloud now allows you to launch and print additional custom report types designed using WebReports, directly from the UI. On the “Company Report Type” UI, choose the “WebReport” subreport type and provide the corresponding web report name and path to print custom webreports from the UI. This feature was already available for Order Packing List and Bill of Loading (BOL). As of 18C, this feature is enabled for the following additional reports:

OBLPN Packing Slip – Generated by clicking “Packing List” on the OBLPN UI.Task Report – Generated by clicking “Task Reports” on the Wave Inquiry UI.Inbound Receipt Report - Generated by clicking “Inbound Receipt” on the IB Shipment UI.Pallet Packing List - Generated by clicking “Pallet Packing List” on the Pallet View UI.Pick Travel Report - Generated by clicking “Pick Travel Report” on the Wave Inquiry UI.Receiving Variance Report - Generated by clicking the “Receiving Variance Report” button on the Appointment UI.Commercial Invoice - Generated by clicking “Commercial Invoice” on the OB Load UI.Export Shipment Packing List - Generated by clicking “Export Shipment Packing List” on the OB Load UI.Shipper’s Export Declaration - Generated by clicking “Shipper’s Export Declaration” on the OB Load UI.

38

NOTE: Custom reports design through WebReports cannot be invoked from the RF (This note is only applicable for reports that can be printed via RF).

STEPS TO ENABLE

OBLPN Packing Slip – “OBLPN_PACKING” in “Company Report Type” needs to configured with the sub report type “WebReports”.Task Report – “TASK” in “Company Report Type” needs to be configured with the sub report type “WebReports”.Inbound Receipt Report – “INBOUND_RECEIPT_REPORT” in “Company Report Type” needs to be configured with the sub report type “WebReports”.Pallet Packing List - “PALLET_PACKING” in “Company Report Type” needs to be configured with the sub report type “WebReports”.Pick Travel Report - PICK_TRAVEL” in “Company Report Type” needs to be configured with sub report type “WebReports”.Receiving Variance Report - “RCV” in “Company Report Type” needs to be configured with sub report type “WebReports”Commercial Invoice - “COMM INV” in “Company Report Type” needs to be configured with sub report type “WebReports”.Export Shipment Packing List - “EXPL” in “Company Report Type” needs to be configured with the sub report type “WebReports”.Shipper’s Export Declaration “SED” in “Company Report Type” needs to be configured with sub report type “WebReports

IMPROVED LITERAL LOCALIZATION

Earlier, you could personalize literals one by one through the browser UI. 18C introduces a new input interface entity: “Literals”. This interface helps you to change/modify the description for the literal in the required language in bulk. You can upload either through the Input Interface screen (UI) or through the Init Stage Interface (API).

The following formats are supported:

Formats for Input Interface screen (UI): XLS, PSV, XMLFormats for Init Stage Interface (API): XML

You can download all/multiple literals from the application in csv format, from the literals screen, modify the description of the required literal, save them in xls, and upload this file using the input interface UI. This feature allows you to update hundreds of records in bulk, through your uploaded files instead of doing so one by one through the browser. The Literals Screen Module data grid fields are now fixed relative to each other, and cannot be rearranged, so as to facilitate download and upload. You can download a literal as a CSV into excel, save as XLS format, and then upload it from the input interface screen.

UI/RF SCREEN MESSAGES

The UI Inbound screens and RF Messages screens now have literals, so that you can rename these messages to their wording or language of preference.

STEPS TO ENABLE


39

IMPROVED TIME ZONE LOCALIZATION

ADDITIONAL TIME ZONES

Update 18C now supports the following time zones:

LebanonTokyo (Japan Standard Time JST (UTC+9))MalaysiaAtlantic Time - America/HalifaxAlaska Time - America/AnchorageHawaii-Aleutian Time - Pacific/HonoluluSamoa Time - Pacific/Pago_PagoMauritius Time - Indian/MauritiusCentral European Time - CET

STEPS TO ENABLE


YARD MANAGEMENT IMPROVEMENTS

In 18C, the following enhancements have been added in Oracle WMS Cloud for yard management:

A new button, Locate Trailer, has been added to the Appointment, OB Load, IB Load, and Trailer screens.

The new button is permission-controlled and only those with permissions can perform locate trailer to yard.The Location drop-down in the pop up that opens up after clicking “Locate Trailer" displays only the yard location(s) of the logged-in facility that has enough capacity to locate the trailer i.e. location(s) where the number of trailers located is less than the max units of the yard location.Each trailer is considered as one unit.The current Yard Location field in the pop-up displays the current yard location if the selectedtrailer is already located to the yard.

NOTE: Prior to 18C, to locate trailers to yard locations or move trailers from one yard location to another, we used location drop down in edit/create option in UI. The “Location” field in the create/edit pane will be removed.

STEPS TO ENABLE

Add permission "trailer / Locate Trailer to Yard"

ORACLE WMS BI CLOUD FRAMEWORK

The mapped framework between Oracle WMS BI Cloud and Oracle WMS Cloud now supports additional objects and mappings, particularly those objects and mappings added in more recent releases such as Trailers and new fields for Orders.

40


ORDER DETAIL LEVEL PERMISSIONS

Prior to 18C, if you had order level permissions order_hdr/add order, order_hdr/change orders, or order_hdr/delete orders, you got access to modify the order header and also to add/edit/delete the order details. You had the permissions to add/modify/delete order details (navigated from order header screen). Update 18C includes additional permissions to add/edit/delete order details so that permissions for order header and detail are separated out. If you have permissions for order_hdr/add order, order_hdr/change orders, and order_hdr/delete orders, do not give permissions to add/modify/delete order details.

Upon updating to 18C, users with an employee role who have permissions for order_hdr/add order, or order_hdr/change orders will not be able to add/modify/delete order details. New Order detail level permissions need to be provided exclusively.

STEPS TO ENABLE

Add the new Order detail permission.

DOCUMENT DESIGN AND PRINTING

PRICE LABEL SUPPORT WITH LABEL DESIGNER

Update 18C allows you to create a Price Label using Label Designer. This new feature enhances the flexibility to personalize labels. Now, you can select a Price Label template from the Standard Templates drop-down, and design the Price Label by choosing the width from a selection of fields available in the Column Name. You can configure the created Price Label in the Label Template View UI, copying the user-defined Template name to the Template Name in the Label Template View UI. Update 18C also includes the locations where you can print the designed Price Label. The IB Shipment Screen and IB Shipment Detail Screen now have a Print Price Label button which will print the design Price Label. Also, the RF transaction "RF Retail Price Label" will print the design price label.

STEPS TO ENABLE

Configure the Price Label template on Label Designer

CASE AND PACK LABELS USING LABEL DESIGNER

Label Designer is enhanced to support the creation of Case and Pack Labels. A new button “Print UOM Label” is added to IBLPN UI to print Case and Pack Labels.

STEPS TO ENABLE

Configure the Case and Packs Label template on Label Designer with the following settings:

Set as inspectedEdit FeatureAdd CommentProperties

STEPS TO ENABLE

41

OBLPN NUMBER LABELING AND PRINTING

Some customer operations have specific requirements for LPN number labeling. Currently Oracle WMS Clouds creates a random LPN number for non-cubed OBLPNs which prevents the desired labeling for LPN. A new function "RENAME_OUT_BOUND_CONTAINER_NUMBER_ONCE" has been added to Label Designer. You can add this function on the Container Label by clicking Print OBLPN label on the OBLPN Screen. This function first checks to see if the field ref_oblpn is empty in the OBLPN, and if it will look up the sequence counter for that OBLPN's destination facility. It populates the LPN number according to the configuration on the sequence counter, and the old LPN number is moved to the ref_oblpn field.

STEPS TO ENABLE

Add the function RENAME_OUT_BOUND_CONTAINER_NUMBER_ONCE to the oblpn_content_label template.

---

42

Copyright © 2018, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

oracle warehouse management cloud · wms has the ability to store inventories with different...

Documents