4Inventory Management

WMS includes two inventory types: Allocatable (Available) and Unallocatable (Unavailable) Inventory.

Available/Allocatable inventory is any inventory that is located in a reserve or active location that has not been allocated against an outbound order.

Unavailable/Unallocatable inventory is any inventory that is either allocated for an outbound order, or is in a status that won’t allow for allocation. Below are the basic scenarios for unavailable inventory:

1. Received inventory that has not been putaway (configurable)
2. Inventory undergoing VAS processes
3. Inventory located in a Drop Zone
4. Inventory associated with outbound LPNs
5. Inventory in locations with lock codes (and the lock code is configured as Unallocatable)

The Item Master stores information for all the items that are used in the warehouse.

Oracle WMS Cloud supports four units of measure:

• CASE: Cases refer to physical boxes (must define “Standard Case Quantity”).
• PACK: Cases can be further broken down into Packs (must define “Standard Pack Quantity”).
• UNIT: The smallest unit of measure is Units, which represents an ‘each’.
• LPN: LPNs are the largest UOMs in the system, and can have multiple meanings.

If each box is labeled with an LPN, the LPN represents a physical box.

If an entire pallet is labeled with an LPN, the LPN represents a pallet.

The LPN has an attribute called “LPN is Pallet”, which systematically marks the LPN as a physical Pallet. The advantages of using this functionality is that pallets will only require one label (LPN) and can be allocated into Pallet, Cases, Packs or Units.

LPNs can only be set to “LPN is Pallet” during receiving. You must use a receiving RF module (either “Receive LPN Shipment” or “Receive LPN Load”) and configure its “pallet-handling” module parameter to “LPN as Physical Pallet”. With this setting, any LPN received with this Pallet will have the “LPN is Pallet” flag set to true.

Additionally, you must also define the standard pallet quantity in the Item master. To do so:

1. Go to the “Items” screen.
2. Select the item record and click on its details.
3. Click “Edit” to begin editing.
4. Populate the following fields:
   1. Standard Pack Quantity (optional)
   2. Standard Case Quantity
   3. LPNs per Tier
   4. Tiers per Pallet
5. Click Save.

Items can also be created through an Oracle WMS Cloud Excel template.

You must follow the rules below in order to correctly use the Oracle WMS Cloud interface:

• The filename must start with the letters “ITM”.
• The columns specified as ‘required’ in the interface specification document must be populated.

A third method to interface records into WMS is through a shared SFTP directory.

1. Host system drops the “ITM” file into the shared directory (typically an “input” folder).
2. When the file is dropped, ORACLE WMS CLOUD will automatically detect the file and process it into WMS.
   • If a file fails for some reason, it is automatically moved into the “error” folder.

The Alternate Item Barcodes screen sets up alternate barcodes for SKUs in the warehouse. This screen enables the ability to configure multiple barcodes for the same Item Code.

1. To add a new barcode to an existing item, from Item Barcodes, click “Create” () at the top right and input the Item Code and the new Barcode:
2. When you are populating the Item Code, you can either populate the field or use the magnifying glass to look for the code from the Item Master.
3. When you are using the magnifying glass, the system will pop up a new window. To display the records, press the “Search” button.
4. Once the Item record is found, double click the record to select it.
5. Click "Save".

You can also interface alternate barcodes into WMS using the “IXR” (or “IBR”) interface template.

Open the interface with Excel and populate the “item_barcode” with the original barcode and the “vendor_barcode” with the new alternate barcode:

Make sure that the correct company code is populated and that the “action_code” is set to “CREATE”. Save the interface.

You can also make certain Item fields required before it can be received into WMS. This is done through the Required Item Fields screen.

To add a new ‘required field’, click Create. This prompts a new window, where you can select a field from the drop-down:

If the required item field is not populated, the RF displays an error message during receipt:

To populate the required item fields, go to the Items screen, select the item record, and populate the appropriate item field. There are two places in which an Item field can be populated:

1. From the Items screen, click Edit:
2. From the Items screen, click Details (click Edit and then Save your changes when you are finished):

Once all of the required item fields are populated, you must retry receiving the LPN with the RF receiving option.

You can print item labels from handheld devices using the RF Print Item Label module.

1. Once you select Print Item Label from RF, you are presented with an option to enter the label printer.
   • If you tab out of this field without entering a printer, system will check if a default label printer has been configured for the logged in user. If a default label printer is not configured, the system displays a “Required Field” message forcing you to enter a printer.
   • If a default printer is configured for the logged in user, the system will ask if you would like to print the label to the default printer.
   • If this message is configured as a warning, you can either accept the message (using Ctrl+A) to print to default printer or hit Ctrl+W to go back to the printer field and enter a different label printer.
   • If this message is configured as an error, you are forced to go back (using Ctrl+W) and enter printer in the printer field.
     Note: If the message is not enabled, this message does not show up at all. The default printer is automatically populated in the printer field when you tab out of the printer field.
2. After printer validations, you are prompted to scan the item barcode or vendor barcode.
3. Finally you are prompted to enter the number of labels required to be printed for the scanned item. A quantity greater than 0 must be provided.
4. If a customized item label that has been designed through label designer is configured, then the customized label will be printed. Else item label(s) will be printed based on base label format.

Item labels can also be printed using the Print Label button from the Item UI:

When an item is selected on the Items UI, Print Label button is enabled. This button is not enabled when multiple items are selected. When you click the Print Label button, the following dialog pops up:

You can enter the number of labels required for this item and hit submit. Item labels will be printed to the default label printer configured for the logged in user. Since there is no option to change or enter a printer using this option, it is necessary that the default label printer is configured for the logged in user.

There is also an option to print item labels from the IB Shipment UI. In the IB Shipments view, click on the Nbr Items hyperlink for the desired IB Shipment.

This brings up a view that lists all items on the shipment. There are two buttons available from this view:

• Print Item Labels – This button is only enabled when a single item is selected on this view. Item labels will be printed only for the selected item.
• Print All Item Labels – This button is always enabled and can be used to print labels for all items on the shipment

When you click either button, the following pop-up is displayed. You have the option to print labels based on Shipped Qty OR Received Qty. After choosing that, you need to enter the number of item labels that need to be printed for each unit.

For example, if Shipped Qty is selected (which is 10 in this example) and the number of labels per unit is 5, then 50 item labels will be printed for this item.

Similar to the item UI, since this option does not prompt for printer, you must configure the default label printer for the logged in user.

Using the Oracle WMS Cloud “LOC” interface file, you can map the warehouse locations into WMS.

Step 1: Fill out the “LOC” excel file

Fill out all the necessary information into the location interface. Column A defines the location type. Refer to the table below:

Step 2: Setting up the parameter for location updates

WMS requires a special parameter to be set before creating location updates in the system (for locations that contain inventory).

1. Go to the “Facility Parameters” screen.
2. Set the LOCATION_UPDATES_WITH_INVENTORY parameter to “YES”.

Step 3: Uploading the Interface file into WMS

1. Go to the “Input Interface” screen.
2. Use the drop-down to select the appropriate interface to process:
3. Click on “Upload Files” and navigate to the file you wish to upload.
4. When the file displays, click “Run Interface”.
5. The system will return a message dialog notifying you that the file has been successfully processed.

The ReserveInventory screen provides detailed inventory information filtered by Location Area and Item Code. You can click on the linked LPN number in the “Curr lpns” column and see more information regarding the items in each LPN such as the Shipped Quantity, Current Quantity (by LPN), and Pallet Number.

The IBLPNs screen contains detailed information about all the IBLPNs currently stored in the warehouse. This includes individual LPN information broken down by SKU such as its Status, Quantity, Current Location, Expiry Date, Pack, and Case quantity.

Inventory history records various WMS transactions taking place in the facility for purposes of informing the

ERP or any other external system that may be interested.

For more information about the Iventory History UI fields, see the Interface Specifications document.

Note: For any inventory records where you have selected and clicked the AutoProcess flag, the associated inventory history record will display as Processed in the Inventory History UI.

To enable Auto-Send of Inventory History, do the following:

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

Steps:

1. Go to the Inventory History UI.
2. Select the IHT record. You can select one or more IHT records to process the request at the same time.
   Note: The system enables the button only if the selected IHT records is in status “Processed/Processing/Cancelled”.
3. Click the Mark Unprocessed button. The system prompts for password.
4. Enter your OCWMS password. Click Submit. To discard, click Cancel.
5. Upon success, the system displays a confirmation message “Updated 1 record”, and the IHT status for that particular record is changed to “Not Ready”.

Reason codes are used as identifiers for performing certain transactions, such as modifying the quantity of an LPN. Reason codes must be added at the Parent company level.

1. Go to the “Reason Codes” screen.
2. Click the Create button.
3. Populate the code and description.
4. Click “Save”.

Lock Codes must be added at the Parent company level.

1. Make sure your current company view is at the Parent company.
2. Go to the “Lock Codes” screen.
3. Click the Create button.
4. Populate the applicable fields/flags.
   1. Allocatable: If checked, LPNs with this lock code are still eligible for order allocation.
   2. Unlock on locate to Reserve: If checked, LPNs with this lock code will have this lock code removed whenever it is located to a Reserve location (a location that does not have a lock code).
5. Click “Save”.

You can add specific Lock Codes to an IBLPN by clicking the blue number value in the “Nbr Locks” column:

This will prompt a new window, where you can add multiple lock codes to the container:

The above figure shows all the Lock Codes currently added to the container. Click Create () and select one of the configured Lock Codes from the drop-down to add lock codes.

LPNs can be modified via the RF module Modify IBLPN. Here you can modify either the LPN’s SKU, Quantity, or Putaway Type.

1. Enter the RF module Modify IBLPN.
2. Scan the IBLPN to modify.
3. In the “Qty:” field, enter the new quantity (you must input the current quantity even if the current quantity remains the same).
4. To modify the Putaway Type, select option Ctrl-R: Putaway Type. This prompts a list of Putaway Types in the system – select the appropriate Putaway Type to modify.
5. Once all the modifications are done, the LPN’s attributes should be displayed in the RF screen. When done, select option Ctrl-N: End Modify.
6. In the “Reason Code:” prompt, input the appropriate Reason Code for that transaction.
   • A list of configured Reason Codes can be viewed in the Reason Code screen.

Before you begin to assign an inbound load to an outbound, create an LPN as shown in the following steps:

Steps:

1. Login to the WMS RF through your credentials.
2. Create an LPN for the order. To do that, select the Create LPN transaction. After invoking, create a new LPN and enter the LPN number. For example: LPN: SKLPN1504M.

   

3. The RF screen takes you to the next screen where you need to enter following information:
   1. LPN: Enter the LPN Number.
   2. Items: Enter the items that you created through the items UI.
   3. Qty: Enter the quantity.
4. You can also check the LPN status in the IBLPN UI. Go to the IBLPN UI > Search for the LPN number > the status displays as “Received” when items are successfully consumed.
5. After consuming all the items, press Ctrl-X to exit from the current page.

The Inventory Summary shows the inventory movement of all items from available quantity to packed quantity. This report can be used as an overview/summary of available inventory and to view how many allocated units are still pending to picked or shipped.

A cycle count is an inventory auditing procedure, which falls under inventory management, where a small subset of inventory, in a specific location, is counted on a specified day.

In Oracle WMS Cloud, you can run Cycle Counts in three ways:

1. Manually execute a Cycle Count in a location (RF)
2. WMS automatically triggers a Task (UI)
3. Run a Task Template that generates group of Tasks (UI)

There are three ways to run Cycle Counts with the RF, each varied by level of detail:

1. Cycle Count Location (By # of LPNs in a location): Prompts you to input the number of LPNs in the scanned location.
2. Cycle Count LPN (By LPN count): Prompts you to scan each LPN in the Location. Any IBLPN not scanned in a CC session will be updated as “Lost”.
3. Cycle Count LPN Detail

By SKU quantity: Prompts you to scan the LPN, SKU, quantity and its Inventory Attributes (Batch Number, Expiry Date, Serial Number) in the location. Here you input the quantity for each LPN.

By SKU Scan: Prompts you to scan the LPN and SKU in the Location. For the quantity value, you have to scan once for every SKU in the LPN. This option does NOT validate inventory attributes in the LPN.

The following sections describe the steps you would take to execute each CC type.

In addition to manually Cycle Counting locations, you can also create Cycle Count Tasks and execute them later. There are two ways to create CC Tasks:

1. Through user-configured Triggers.
2. Through user-executed Task Template

The Cycle Count Adjustment Approval Rule screen allows you to configure a rule for cycle count approval and set tolerance levels for groups of items (using selection criteria.)

You can configure different Approval Settings based on your preferences for different items.

The following table shows what each of the Approval Rule options are and what they check:

If you wish to exit and cancel the Cycle Count process for a given location, you must press “Ctrl-W” until the RF returns to the main menu.

• When you scan an LPN in “Consumed” or “Shipped” status in the Cycle Count operation, the system gives you an error message that the LPN is in invalid status.
• Finding “Consumed” and “Shipped” status LPNs in the reserve reflects poor inventory management.
• For the “Consumed” and “Shipped” LPN inventory, you must create a new LPN, using Create LPN RF option for the physical inventory in the location. DO NOT FORGET TO PUTAWAY.

• When you scan an LPN in “Packed” status in the Cycle Count operation, the system gives you an error message that the LPN is in invalid status.

Oracle WMS Cloud allows you to approve/reject inventory adjustments before any real changes are made to warehouse inventory. This process, called the “Deferred Mode”, is enabled at both the Facility and Company levels.

Refer to the following diagram for a high-level process flow of the Deferred Mode:

To enable Deferred Mode for your facility, set the Facility and Company parameters “INVN_ADJUSTMENT_APPROVAL_REQUIRED” to “YES”. If this parameter is set to “NO” at either the facility or company level, the “Immediate Mode” (default) will be enabled – in this mode, Cycle Count inventory adjustments are applied immediately. Note that in 3PL environments, this parameter must be set to “YES” at the child company level. Below are the possible configurations:

In the Deferred Mode, WMS keeps track of all Cycle Counts in the Cycle Count Adjustment screen.

This UI screen displays detailed information about the Cycle Count record.

• Group Number (group_nbr): Must be equal to the ‘Inventory History’ group number. In Deferred Mode, inventory adjustments need to get posted with the same group number in the ‘Inventory History’ table. The group number must be the same for all adjustments done in a specific location (when CC is done at the location level) or to a specific LPN (when CC is done at the LPN level) in one transaction. Note: Transaction is defined here as:
  • For RF CC_Location modules: Time between Location scan until ‘Ctrl-E- End Location Count’ is entered.
  • For RF_CC LPN module: Time between LPN is scanned until ‘Ctrl-P’ is entered to finish the LPN count.
• Company (company_code): Company where the transaction is performed. Note that parent level users are able to cycle count inventory at the child level, so child company code should be displayed here for this scenario.
• Facility (facility_code): Facility where user performing the count has logged in.
• Status (status): Current status of the adjustment record.
• RF screen name: Name of the RF transaction used to perform the Cycle Count.
• Total Expected Qty: Sum of current_qty (in units) of all the inventory in the location (CC at the Location level) or LPN (CC at the LPN level) before cycle count is performed.
• Total Count Qty: Sum of counted quantity (in units) during the execution of cycle count transaction for the location (CC at the Location level) or LPN (CC at the LPN level).
• Total Adjusted Qty: Total Count Qty – Total Exp Qty
• Location (location): Location where the CC transaction was executed. For CC at the LPN level, this field should be equal to the Location where the LPN was located at the time the count was performed.

Action that trigged the creation of this inventory adjustment record. The same ‘Creation Type’ values needs to be added to the ‘Task’ screen with the exception of ‘Manual’ so both screens may reference the same table. Valid Creation types are:

• Recount Reference: Used to keep track of counts that are done to the same location by generating a recount (rejecting a particular inventory adjustment). The first time a user rejects a record in ‘Pending’ status, the system must set the Recount Reference number equal to the Group Nbr of that record. This rejection will automatically trigger a CC task for the same location. Once this CC task is executed, the corresponding inventory adjustment record must be created with the Recount Reference of the first rejection (first Group Number)’.
  • Task: TheTask number that was executed to create the corresponding inventory adjustment. Value should be blank if the count was performed manually with RF_CC Location or RF_CC LPN.
  • Task Type: The Task Type that was created to create the inventory adjustment. Value should be blank if the count was performed manually with RF_CC Location or RF_CC LPN.
  • Cost Adjustment: Sum of (item.unit_cost*adjusted_qty) for all the items in the location.
  • Loc Dtl Count: ‘Yes/No’ value that indicates whether or not a particular non-active location count was done at the detail level.
  • Warnings: Displays the number of warnings for a specific inventory adjustment record at the location (RF_CC Location) or LPN levels (RF_CC LPN) as a hyperlink. Click the hyperlink display a list of all the warnings for that specific inventory adjustment record.

• Reason Code: Display the value configured in Company Parameter ‘CYCLE_COUNT_REASON_CODE’.
• Create User: User who creates the inventory adjustment record.
• Create Timestamp: Time at which inventory adjustment was completed. For the CC_Location scenario, time at which ‘Ctrl-E: End Location count’ is entered to finish the count. For the CC_LPN scenario, time at which ‘Ctrl-P’ is entered to finish the LPN count.
• Mod User: User who modifies the record. Set equal to Create User when record is created. Set equal to user who Rejects, Accepts or Cancels the record.
• Mod Timestamp: Time at which the record is modified. Set equal to Create Timestamp when record is created. Update timestamp when user Rejects, Accepts or Cancels the record.

Lot (batch) information is captured in receiving and maintained up until shipping. The LPN’s Batch Number is set up during receipt. The item master maintains a flag (‘require batch number’) that will be used to determine if a lot (batch) number will be captured.

Each item is configured if it requires WMS to capture the lot (batch) number during receiving.

1. Navigate to the ‘Items’ UI screen.
2. Using the ‘Search’ button, search for the item that requires expiration date setup.
3. Select the item record, and click on the ‘Details’ button.
4. Click the ‘Edit’ button, and scroll down until you see ‘require batch number’.

   

5. Click the checkbox, and then click the 'Save' button to save the changes made.

Lot (batch) numbers are maintained at the LPN level therefore, LPN screens are used to view the lot (batch) number.

1. To view lot (batch) number associated with IB LPNs navigate to the ‘IB LPN’ UI screen.
2. Using the 'Search' button, you can filter by a specific lot (batch) number in order to find all IB LPNs that are associated to the lot (batch) number.
3. To view the lot (batch) number associated with the OB LPNs navigate to the ‘OB LPN’ UI screen.
4. Using the ‘Search’ button, you can filter by a specific lot (batch) number in order to find all OB LPNs that are associated to the lot (batch) number.

Expiration dates are defined during receiving, either via ASN interface or user input, and they are tracked from receiving to wave allocation. Expiration dates are defined at the item level:

1. Product Life: Is defined as the expected lifetime of the item.
2. % Acceptable: Percentage of remaining life required at receiving (defined in %).

Expiration dates are maintained at the item level. Each item needs to be defined with the ‘Product Life’ and ‘% Acceptable’. The two values are defined in the ‘Items’ UI screen.

1. Navigate to the Item UI screen.
2. Using the ‘Search’ button, search for the item that requires expiration date setup.
3. Select the item record, and click Details ().
4. Click Edit, and scroll down until you see ‘Product Life’, and ‘% acceptable’.
5. Update these two fields and click “Save” when complete.

In order to receive items with expiry dates, the receiving RF module must have the Expiry Date validation enabled.

1. Go to the “Screen Configurations” screen.
2. Select the receiving RF module that will have expiry date tracking enabled.
3. Click on Details to access its parameters.
4. Modify the “capture-date-type” parameter to “Prompt for expiry date.”

   

   Note: if using manufacture dates, and if the item has the product life field defined, WMS automatically calculates the expiry date as well).
5. You can also define two parameters related to expiry dates: “allow-inv-exp-override” and “allow-rem-exp-override”.

• allow-inv-exp-override: By default, the RF displays an exception message when the scanned expiry date is older (i.e. will expire sooner) than all the expiry dates in the current inventory. If this parameter is enabled, it allows you to override this message.
• allow-rem-exp-override: By default, the RF will display an exception message when the scanned expiry date is below the item’s acceptable % of remaining life. If this parameter is enabled, allows you to override this message.

During receiving, if the item has a product life value populated, the RF prompts you to input the LPN’s expiry date. When populating the expiry date, note that the input must be in the MMDDYYYY format.

Example: December 11, 2014 becomes “12112014”.

WMS supports the ability to lock a lot (batch) number in the event that a recall has been initiated.

1. To apply a lock to a lot (batch) number, go to the ‘Batch Management’ screen.
2. Using the search button, filter for the lot (batch) that requires a lock.
3. Select the applicable record, and click the ‘Edit’ button.
4. Select the applicable lock code from the drop-down menu, and click the ‘Save’ button.

Oracle WMS Cloud users that manage costly electronic merchandise may need to track items individually through the use of Serial Numbers. In WMS, Serial Numbers are unique codes that identify a single unit.

Before enabling WMS to track Serial Numbers, here are some important caveats to be aware of:

• Serial Numbers are unique per item. In other words, you cannot have duplicate serial numbers within the same SKU and facility.
• The system allows duplicate serial numbers for different SKUs. In other words, Serial Number records are unique by Serial Number and SKU code combination.
• Oracle WMS Cloud supports up to 25 alphanumeric characters for Serial Numbers.
• If enabled, you will have to perform a scan for each Serial Number in a transaction[1].
• Clients need to be cautioned for changing the serial number tracking level configuration. If we change the serial number tracking levels then there can be situations where inventory in WMS and Serial Numbers will not be in sync.
• Enabling a SKU for Serial Number tracking enables it for all facilities that use that SKU.
• You cannot receive with Serial Numbers when the receiving mode is “receive LPN as Pallet” or if the receiving unit of measure is not Units.
• The system prompts for Serial Numbers when the OBLPN is packed using the Full Case or Cross Dock, given that Serial Numbers for the respective IBLPN are known.
• If the Serial Number tracking option is enabled from ”Packing Only” ordering for a Specific Serial Number is not possible.
• Serial number functionality is not applicable for Pre-Packs. It’s advised not to enable Serial Number tracking for Parent and Child item.
• The Sort and Receive transaction does not support the Serial Number prompt.
• The system assumes that you will scan every serial number in a pack or case.

Refer to Serial Number Transactions for a list of all transactions that have Serial Number validation.

To enable Serial Number tracking in WMS, you have to configure the following:

• Enable tracking for the SKU in the Item Master
• Enable tracking for the Company in the Company Parameters
• Create a Barcode Type record for Serial Numbers

This screen displays a ‘flattened’ view of Serial Numbers and their associated inventory records (ex. LPNs) in a single record.

Note: If a serial number does not have an associated inventory, the LPN Number/Status/Type columns are left blank. If a serial number is shipped and returned back to the same facility, this screen displays two records (shipped and received).

This screen displays all the “serial number – inventory” association changes in the system. For example, there can be a serial number record for an LPN of type “I” (Inbound) and another for LPN of type “O” (Outbound).

You can add Serial Number records in the system in two ways: through the UI and through interfaces.

Some objectives of integrating Replenishment into WMS include:

• You can replenish inventory for locations if the inventory goes below a defined level.
• Replenishment can be based on requirements such as satisfying orders for stores.
  • In this case, certain dedicated replenishment locations can be configured to consolidated orders for a store.
• Replenishment is performed in Active Locations and also allows you to perform Reserve to Reserve replenishment.

Oracle WMS Cloud supports four replenishment modes:

Each replenishment type has different criteria for when the replenishment wave is triggered:

• Minimum Capacity: Triggered when a location’s current quantity goes below the required minimum quantity.
• Percentage of Max: Triggered when the volume of items in the location goes below the location’s pre-configured percentage of maximum volume.
• Reactive: Triggered when you manually scan a location to be replenished.
• Order Based: Triggered when an order’s SKU needs to be replenished in the picking locations.

Configuring a Replenishment Wave requires the following steps:

1. Setting up locations for replenishment
2. Setting up replenishment rules
3. Setting up task templates
4. Creating a Replenishment Template

Configuring the Allocation Zone:

1. Go to the “Locations” screen.
2. Select the location that you will replenish from and click Edit.
3. Scroll down to the “Alloc zone” field and populate an allocation zone. This value is used in the replenishment template for defining which allocation zone will provide the replenishment.
4. Click “Save”.

From here, depending on the Replenishment Task Type, the order of RF screens is different. The following section outlines the different replenishment scenarios:

• Scenario 1: Cases replenishment, no distribution
• Scenario 2: Full LPN replenishment, no distribution
• Scenario 3: Cases replenishment, consolidate and distribute (reserve to active)
• Scenario 4: Units replenishment, consolidate and distribute (active to active)

Once you enter the task, the RF prompts you for pallet and LPN numbers. This pallet is the intermediate pallet that transports the merchandise into the final replenishment location.

If there is no more room for more LPNs in the pallet, you can “End” the pallet by pressing Ctrl-E. Ending a pallet with pending picks causes the system to create a new replenishment Task for the remaining picks.

1. Once all the LPNs from the picking location are moved to the pallet, the RF prompts the destination location (the location to replenish to). You must scan the location barcode when they arrive to the location:
2. Once the location barcode is scanned, the RF will ask you to scan the “To LPN” (the destination pallet). This is the LPN that is replenished. In the “Qty:” field, you must enter the amount of cases being moved.

   

   Note: for the “Qty: 10 (cs=10)”, the first 10 represents the number of cases to move, while the second “10” value (“cs=10”) represents the standard case quantity of the item.
3. Once the contents are moved, the remaining contents in the LPN must be returned to a reserve location. The following is an example of the reserve location field.
4. If there are no LPNs remaining, the task ends and the RF returns to the Task List.

1. Once you enter the task, the RF prompts for pallet and LPN numbers. This pallet is the intermediate pallet that transports the merchandise into the final replenishment location.
   Note: If there are multiple LPNs to be picked, the RF prompts for another LPN. If there is no more room for more LPNs in the pallet, you can “End” the pallet by pressing Ctrl-E. Ending a pallet with pending picks will cause the system to create a new replenishment Task for the remaining picks.
2. Once all the LPNs from the picking location are moved to the pallet, the RF prompts the destination location (the location to replenish to). You must scan the location barcode when the pallet arrives to the location.
3. Once the location barcode is scanned, the RF will ask you to scan the LPNs in the pallet to replenish with. The “Qty:” field denotes how many LPNs there are to replenish.
4. If there are no LPNs remaining, the RF displays a message saying “No more tasks”. Press Ctrl-A to proceed.

1. Upon entering the task, the RF prompts you to “open” an IBLPN. This is the ‘dummy’ LPN that is used to carry the picks.
   Note: at any point in time you may choose to close the current dummy LPN by pressing Ctrl-E. This will allows you to open another LPN (if the first LPN gets physically full) and continue with the pick. When you press Ctrl-E, the system will suppress the capacity check (units/weight/volume).
2. After scanning the dummy LPN, the RF directs you to the first picking location. Scan the location barcode to confirm that the user is at the location.
3. The RF will now ask you to begin picking cases from the first picking location, prompting you to scan the Item code and quantity.
4. If there are more cases to pick, the RF will direct you to the next pick location, and repeat the picking process. When you finish all the picks, the RF displays the message “Nothing left to pick”:
5. Once all the picks are complete, the RF then directs you to the replenishment location. Scan the location barcode to confirm that the user is at the location.
6. The RF then prompts you to move the picked units into the replenishment location. Since you are replenishing to an active location, you should only enter the quantity being replenished.
7. When all locations in the task have been replenished, the RF will return to the Task list.

1. Upon entering the task, the RF prompts you to “open” an IBLPN. This is the ‘dummy’ LPN that is used to carry the picks.
   Note: at any point in time you may choose to close the current dummy LPN by pressing Ctrl-E. This allows you to open another LPN (if the first LPN gets physically full) and continue with the pick.
2. After scanning the dummy LPN, the RF directs you to the first picking location. Scan the location barcode to confirm that the user is at the location.
3. The RF now asks you to begin picking units from the first picking location, prompting you to scan the Item code and quantity.
4. If there are more units to pick, the RF directs you to the next pick location, and repeat the picking process. When you finish all the picks the RF displays the message “Nothing left to pick”.
5. Once all the picks are complete, the RF directs you to the replenishment location. Scan the location barcode to confirm that the user is at the location.
6. The RF then prompts you to move the picked units into the replenishment location. Since you are replenishing to an active location, you should only enter the quantity being replenished.
7. When all locations in the task have been replenished, the RF will return to the Task list.

When replenishment of items happens in a location via RF reactive replenishment, Oracle WMS Cloud allows you to do a weight based capacity check along with the current volume and unit. This will help optimize replenishment for a targeted location.

To enable weight based capacity check, make sure that your Replenishment Rule has the Capacity Check Method set as "Weight, Fall Back to Units."

In the Capacity Check Method drop-down, you can also specify the capacity check as Units, Volume, Fall Back to Units, or Volume, Weight, Fall Back to Units.

The following table provides definitions for the Capacity Check Method drop-down options:

In emergency situations that require quick replenishment, you can use the reactive replenishment functionality to instantly allocate a location for replenishment. This scenario uses a stand-alone RF module called “Reactive Replenishment”. Here, you simply scan the location that needs to be replenished with the RF and WMS creates a replenishment task. Depending on the RF’s parameter setting, you may or may not execute that replenishment on the spot.

1. Go to the “Reactive Replenishment” RF module.
2. In the “Locn:” field, scan the location to replenish. The RF displays the message “Replenishment submitted for location [area]”. This basically runs a replenishment wave for the scanned location.
3. If a replenishment task is generated, depending on the RF’s parameters, you may execute the replenishment on the spot. To do so, press Ctrl-A to proceed.
4. Perform the replenishment as described in previous sections.

Multi-Level Replenishment allows users to keep destination locations (final destination location /pick face) constantly stocked with products, so that pickers can efficiently fulfil orders without waiting for the system to replenish inventory when available.

The following describes a high-level pictorial representation of the Multi-Level Replenishment workflow with a reserve location, drop location, and final destination (active location).

1. An order is said to be satisfied when there is sufficient inventory available in the Active location. However, when there is not enough inventory available in the Active location to satisfy the order, the system runs a wave for an Order and checks for inventory in the Permanent Active location or Reserve location to meet the need. This is the phase where the Replenishment takes place.
2. During these transactions, there may be scenarios involved with multiple drop locations where you are required to pick inventory and drop to another location and then to the final destination. In such cases, inventory needs to hop through multiple drop locations to reach the final destination. That is, inventory needs to pass through multiple Task Zones to reach the final destination. This process of moving inventory from one task zone to another is accomplished using Multi-Level Replenishment.
3. Once you run the wave, the system creates a Replenishment task where required inventory is pushed from the Reserve location to the drop location for the next hop/Task Zone (drop location).
   Note: This is configured under the Task Zone Movement screen for that Task Type.
4. In order to move inventory from the first Task Zone to the next Task Zone, you need to configure the path under Task Zone Movement for the Task Type “CONSOL_DISTRIBUTE”.
5. Use the RF screen "Multistep Replenishment", to scan the Task Type (CONSOLIDATE and REPLENISH) along with the current location.
6. The system will determine which destination location needs to be replenished. After logical calculation, the system will prompt you to scan the relevant LPNs to replenish.
7. The system picks inventory based on the task type and when picking of inventory is complete (or when you manually end the LPN), the system will prompt you to scan a drop location for the next Hop/Task Zone.
8. Repeat the process for replenishing inventory from one drop to the next until the inventory reaches the final destination.
9. When the inventory arrives at the last drop location, the final replenishment module is invoked through the RF and inventory gets replenished to the final destination.

Before you begin, you should understand the following check-points and then start with the configuration setup:

• Replenishment beyond maximum location is applicable only for Permanent Active locations and is not applicable for dynamic location.
• This enhancement is applicable for wave-based replenishment only and not for stand-alone replenishment.

The Wave Template consists of many parameters to be set for a wave to run. In multi-level replenishment, you need to create wave templates to pick orders from a source location to a final destination location. Create a wave template from a Reserve Location (Bulk) to a common Drop Location and then to the next hop.

• Create a wave template from the source location to the first drop location and then to the final destination.
• Associate the replenishment rule for the order to be replenished from one location to another in the wave template.
  Note: If the location needs to be enabled beyond max capacity, you need to enable the “Ignore capacity for the last permanent location” check box.

Configuring a replenishment rule is one of the most important configurations. Replenishment Rule allows you to replenish beyond max capacity by enabling a new flag “Ignore Capacity for Last Permanent Location” check box.

• Source to Final Destination – one task zone movement is created with * baring the end zone.
• Drop zones to Final Destination – Distinct task zone movement should be created with the relevant path.

Wave group helps to distribute loads across different pick lanes. For example, suppose there are two pick lanes from one reserve location, then you can create a replenishment task from the wave group level.

Once you configure a task template at the wave group level, you can combine multiple tasks from different waves. To create a wave group, you need to define the Task Creation Template and Task Type.

A new RF module, "rf.inbound.cwrfmultistepreplen" allows you to move inventory from one drop location to another and then to a final destination location.

The following diagram describes how this new RF module is used:

The following are some of the characteristics of the new RF Module:

1. Scan the inventory from the source location and the system inferred the task zone.
2. Determine the final destination zone of the inventory by scanning the task type that defines the unique task zone.
   Note: Task type can be inferred from screen parameter or user can manually enter into the system.
3. On obtaining the source and destination zone, the system determines the following:
   • If the source location has inventory to satisfy the need/demand of supply in destination location.
   • Once inventory is available in the source destination location, the system prioritizes which location to replenish first based on the following filter:
   • If the filter criteria is set to current quantity <= minimum, then system considers inventory from the source location which are destined to pick locations having current inventory less than or equal to locations configured minimum. If multiple locations are found, the system will order the locations in ascending order of putaway sequence.
4. After determining the source and destination, the system prompts you to pick the relevant quantity of inventory in the temporary tote and deliver to intermediate drop locations and then to final destinations.

Kitting is the process of assembling child items to create a parent item or a kit. The ratio of child items required to create a parent item is called pre-pack ratio and pre-defined in WMS. De-Kitting is the process of dis-assembling parent items or kits into child items. In order to assemble or dis-assemble parent items, Work Orders are required. The assembly or dis-assembly of parent items takes place in assembly locations.

There are two types of kitting flows in WMS - Make To Stock and Make To Order.

Make to Stock – The main objective of Make to Stock flow is that, the parent items or kits are assembled beforehand and putaway to stock in anticipation of future Outbound Order for the parent items. In this flow, a Work Order is either interfaced into WMS or created from Work Order view. After parent items are assembled using this Work Order, WMS prompts you to pack the parent items into Inbound LPNs. The Inbound LPNs are then putaway to stock (reserve locations). These parent items can be picked later against outbound orders, packed, loaded and shipped out like any regular item.

Make to Order – The main objective of Make to Order flow is for the parent items or kits to be shipped out based on the Outbound Order sent to the facility. In this flow, a Work Order is automatically created in WMS when an Outbound Order with a specific Order Type is interfaced into WMS. The Work Order has a reference to the Outbound Order. So when the parent items are assembled using this Work Order, Oracle WMS Cloud prompts you to pack the assembled parent items directly into Outbound LPNs against the Outbound Order. The OBLPNs can then be loaded and shipped out like any other OBLPN.

In the Make to Stock Flow, Work Orders are either directly interfaced into WMS OR or they can be created manually using Work Order view.

The Work Order Type described in Configure Kitting Process is used on the Work Order. This automatically sets the Activity Type to Assembly on the Work Order. The Work Order is initially in a Created status.

This Work Order has been interfaced (or created) to assemble three units for parent item P1.

Create a Work Order Wave Template. This template will define rules to pull child items from reserve/active locations and replenish to an assembly location.

The Work Order Template Search needs to have the right criteria to select the required Work Order.

WMS offers multiple replenishment options. In this example, the rule is defined to pull full LPNs (with child items) from reserve locations.

…and a corresponding Task Template to create Full LPN Replenishment tasks.

Ensure that there are LPNs in reserve locations with enough child units.

Run the wave from the Work Order Wave Template View screen.

From the Work Order Inquiry View screen, the Work Order displays in Allocated status.

Tasks are created to replenish child items from a reserve location to an assembly location.

Execute the tasks in order to replenish the assembly location with child units from reserve locations.

1. Pick IBLPNs containing child items from reserve locations and place on a pallet.
2. Move and Replenish contents of the LPNs to the assembly location

   

   The assembly location now has enough units of child items (C1 and C2) to build 3 units of parent item (P1). From the Work Order Inquiry View UI, the Work Order is now in Picked status:

Now that the child items are in the assembly location, assembly of parent items can start using RF Work Order Kit Processing. All units of the assembled parent items can be placed in one IBLPN or multiple IBLPNs. In this example, all three units have been placed in one IBLPN.

RF Work Order Kit Process offers other Ctrl options for processing Work Orders. For example you can use Ctrl-V to view extra instructions if there are any available for the kit being handled. You can use Ctrl-T to view the ratio of the child items that are required to assemble the parent items.

From the IBLPN screen, the Inbound LPN with the assembled parent items displays in Received status, and can be putaway to a reserve location. You will see in the Work Order Inquiry View, that the work order is completed.

From the Inventory History screen, you can see the Inventory History for the work order.

In the Make to Order Flow, a Work Order is automatically created in WMS when an Outbound Order with a specific Order Type is interfaced into WMS.

Create an Order Type for the Outbound Order. This Order Type needs to have the Work Order Type populated which is described in step 7 in the Configure Kitting Process section.

When an Outbound Order with such an Order Type is interfaced into WMS, a Work Order is automatically created behind the scenes.

The same Wave Template that was described under Make to Stock flow can be used, ensuring that the Wave Search criteria is modified to pull the new Work Order. The wave is run and tasks executed as shown under Make to Stock flow. Executing the tasks will replenish child items to the assembly location.

Kit processing is similar to Make to Stock flow, however in the Make to Order flow, the system prompts for an Outbound LPN to place the assembled units. This Outbound LPN is tied to the Outbound Order that is on the Work Order Detail.

All units of the parent item can be placed in a single OBLPN or multiple OBLPN. In this example, all four units have been placed in one OBLPN.

From the Work Order Inquiry View, the Work Order is completed.

Next, the Outbound Order is packed. The Outbound LPN with parent items is packed and can later be loaded and shipped out of the facility.

The following screen shows you the inventory history for the Work Order:

De-Kitting is performed to dis-assemble parent items into individual child items and put away child items into reserve/active locations. The child items can be later picked, packed, and shipped individually against outbound orders. This flow is typically performed if there is a need to ship individual child items from the facility and there are not enough child items to fulfil the need immediately.

Create a Work Order Type with Activity Type as Dis-Assembly.

Interface a Work Order into WMS with the above Work Order Type on the Work Order. You can also create the Work Order from Work Order Inquiry view.

This Work Order has been interfaced to dis-assemble three units of parent item P1.

Since the pre-pack ratio for P1 is defined as two units of C1 and two units of C2 for one unit of P1, dis-assembling three units of P1 will result in six units of child item C1 and six units of child item C2.

Ensure that there is enough inventory for parent P1 in the facility. In this example, there is one LPN in a reserve location with three units of P1.

The same Wave Template that was described under Make to Stock flow can be used, ensuring that the Wave Search criteria is modified to pull the new Work Order. When the wave is run, it allocates one LPN from reserve which has three units of P1.

A task is created to move the LPN from a reserve location to an assembly location.

Execute the task to replenish the assembly location with parent units from the reserve location.

1. Pick IBLPN containing parent items from reserve location and place on a pallet.
2. Move and Replenish contents of the IBLPN to the assembly location.

The assembly location now has three units of parent item P1.

From the Work Order Inquiry View screen, you will see that the Work Order is in Picked status.

Now that the parent items are in the assembly location, dis-assembly of parent items can start using RF Work Order Kit Processing. After dis-assembling, child units for all parent items can be placed in a single IBLPN or placed separately in different IBLPNs. In this example, all three units of C1 and all three units of C2 have been placed in a single IBLPN.

The Inbound LPNs with child items C1 and C2 are in Received status and can later be putaway to a reserve location or items replenished to an active location.