5Inventory Management

Inventory Types

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

Available/Allocatable 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

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)

Item Master

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

Unit of Measure in WMS

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.

LPN as a Pallet

There are two ways to treat the LPN as a Pallet:

1. Using “LPN is Pallet” flag: LPNs have an optional flag that mark the containers as pallets.
2. Without using the “LPN is Pallet” flag: LPNs do not use the flag, but physically the pallets are labeled with LPNs.

While option two is easier as it does not require special configuration (the user tricks WMS by systematically using LPNs but physically using pallets), it is has limited visibility.

The main difference is that you cannot define the ‘standard pallet quantity’ with option two while this is possible with option one.

Setting up the "LPN is Pallet" flag to true for LPNs

As stated above, using option one requires extra configuration. You can only set the LPN’s “LPN is Pallet” flag to “TRUE” during receiving via a receiving RF module with special parameters configured. To configure this:

1. Go to the “Screens Configuration” screen.
2. Create a new “Receiving LPN Shipment” or “Receiving LPN Load” RF module.
3. Select this record and click on its details.
4. Modify the “pallet-handling” flag and set it to “LPN as Physical Pallet”.
5. Now, every LPN that is received with this special RF module will have the “LPN is Pallet” flag enabled.

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.

Note: You can view the “LPN is Pallet” column in the “IBLPNs” screen.

Description of Item fields

• Style: Represents the Item Code.
• Parts A through F: Represents the breakdown of parts in a SKU, if applicable. Example: A small blue polo could be represented as:
  • part_a = ‘POLO’
  • part_b = ‘BLUE’
  • part_c = ‘SMALL’.
• Alternate Item Code: An alternate representation of the SKU, which concatenates parts A through F into a single record.
• Description: Description of the item.
• Barcode: The item’s barcode.
• Putaway Type: Refers to the value used to group similar SKUs together. For example, SKU “LAPTOP” could belong to Putaway Type “ELECTRONICS”. This is a functional field that defines the putaway logic in the “Putaway Priorities” screen.
• Unit cost: The item’s individual cost.
• Unit Length/Width/Height/Weight/Volume: Denotes the unit’s dimensions. This field does not store the values in a particular unit of measure. These fields are required for functional purpose such as cubed waving, putaway, and replenishment.
• Item Line: Not used in WMS.
• VAS Group Code: If there is a VAS Group Code defined in WMS, this field links the item to a particular set of VAS activities.
• Hazardous: Used to define an item as hazardous.
• Pre-Pack Code: For Prepack scenarios, the item also carrys a prepack code, which is a separate record that represents a group of child SKUs. For example, WMS could use a combination of different Polo’s that come in a prepack into a single ‘Prepack’ SKU record.
• Host Aware Item Flag: Used in Prepack scenarios in determining whether or not the Host is aware of the Prepack item.
• Is Parent: Used in Prepack scenarios to determine whether the item is a parent SKU. If it is a parent SKU, it will contain a prepack of multiple child SKUs.
• Dummy SKU Flag: This is a SKU that can be ordered and allocated, but will have unlimited inventory. The SKU will be prompted for during picking. For example, this could be used to grab gift cards to go along with an order
• Cubiscan Mod Timestamp: Updates the timestamp in which the Item was modified by a cubiscan interface.

Additional Fields (Item Details)

• Std Case Qty: Defines the standard Case Quantity of an item.
• Std Case Length/Width/Height/Weight/Volume: Defines the dimensions of a Case.
• Std Pack Qty: Defines the standard Pack Quantity of an item.
• Std Pack Length/Width/Height/Weight/Volume: Defines the dimensions of a Pack.
• Special Code 1 & 2: Informational fields.
• Product Life: The expected lifespan of an item in DAYS.
• % Acceptable: The percentage of remaining life required (according to the product life) at receiving.
• Require Batch Number: Requires an item to have a batch number during receiving.
• Require Serial Number: For future use only in release 6.3.
• Conveyable: Used when MHE systems are enabled. Defines whether or not an item is conveyable.
• Sortable: Used when MHE systems are enabled. Defines whether or not an item is sortable.
• LPNs per tier:
  • If the “LPN is Pallet” is FALSE, this field defines how many LPNs are in a tier for a given pallet.
  • If the “LPN is Pallet” is TRUE, this field defines how many CASES there are in a pallet tier.
• Tiers per Pallet: This field defines how many tiers there are in a pallet for this SKU.

Note: “LPNs per tier” and “Tiers per Pallet” fields are used to define the standard number of LPNs acceptable per pallet.

• If the “LPN is Pallet” is FALSE, the RF only displays a warning message to the you that the maximum number of LPNs has been reached for the pallet (you can override this message).
• If the “LPN is Pallet” is TRUE, these fields are define the standard pallet quantity of a SKU, given that the “Standard Case Quantity” field is also defined.

Creating Items Manually

1. Go to the “Items” screen and click the Create button.
2. Enter the following information to create a new item:
   1. Parts A
   2. Description
   3. Barcode
   4. Unit Cost
   5. Unit Length
   6. Unit Width
   7. Unit Height
   8. Unit Weight
   9. Unit Volume
3. Click “Save”.

Adding Items through Manual Interfaces

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

Step 1: Preparing the Input Interface file:

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.

Step 2: 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 is displayed in the screen, click “Run Interface”.
5. The system will return a message dialog notifying you that the file has been successfully processed.

Note: if you have any issue uploading your file, try uploading the file without the column headings.

Item Master Integration into WMS

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.

Alternate Barcodes

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.

Adding Alternate Barcodes from the UI

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".

Adding Alternate Barcodes via Interface

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.

1. Go to the “Input Interfaces” screen and select the “Item Barcode” from the drop-down menu:After selecting the Item Barcode from the drop-down, upload the file and click “Run Interface” to process the file.
2. If successful, the new barcodes should be displayed in the “Alternate Barcodes” screen.

Required Item Fields

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:

Note: for numeric value fields such as “unit_weight”, WMS will treat ‘0’ as an empty value. In other words, the system does not allow receipt of that item until it is changed to a non-zero value.

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.

Printing Item Labels

If items received into warehouse do not have item labels, users on the warehouse floor have the option to print item labels from WMS and stick on individual items. WMS provides the option to print item labels from the following three modules:

• RF Print Item Label
• Item UI
• IB Shipment UI

RF Print Label

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 UI

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.

IB Shipment UI

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.

Location Master

Locations in WMS represent storage locations in the warehouse. Below is a brief description of each Location field:

Location Type: Locations have different types depending on how they are used within the warehouse. The different Location Types are:

Location Type	Description
Active	Used for designating active locations. Active locations can only store units.
Consolidation	Used in PTS flow to assign Locations to Destination Stores.
Dock	Used to assign to loads during receiving/shipping.
Pack and Hold	Used for temporarily storing OBLPNs before shipping.
Yard	Used to locate trailer.
Packing Station	Used for packing LPNs with the ‘Packout’ RF option.
Drop	Used to hold both inbound and outbound LPNs while in between warehouse processes. You can configure the picking task to target a specific drop zone.
QC	Used to perform QC on LPNs during receiving.
Reserve	Used for designating reserve locations. Reserve locations store bulk inventory in all UOMs (LPN, Cases, Packs, and Units).
Staging Location	Used in the outbound process to consolidate OBLPNs based on a configured criteria.
Receiving Station	Used for inbound sorting functionality for LPNs.
VAS	Used to perform VAS on units during receiving/shipping.
Shipping Location	Used for shipping LPNs individually; if LPNs are located to a “Shipping Location”, its status is automatically updated to status “shipped”.

Additional warehouse Location Type identifiers are defined below:

Identifier	Description
Facility	Facility ID for location is part of.
Type	Add drop-down options
Dedicated Company	Used to assign a company to the location.
Location Size Type	Used in putaway for defining the Putaway Priorities.
Alloc zone	Refers to the Location’s allocation zone. This is a free-form field used to group locations that must be allocated separately. The ‘alloc zone’ field is used in “Allocation Mode” (Wave Template) and “Replenishment Rules” (Replenishment Template) for specific UOMs. By specifying an allocation zone, you can configure WMS to allocate inventory by zones.
Item	If Location applies to an item.
Area/Aisle/Bay/Level/Position/Bin:	Used to describe the specific warehouse location.
Pick Sequence	Numeric value used to determine the pick sequence between locations. NOTE: The picking sequence values for all locations must have the same number of digits; it is recommended that the user start this field with the value 10000.
Barcode	The location’s barcode.
Length/Width/Height	Refers to the location’s dimensions. These values are considered during two different processes: During Putaway logic if using the Putaway Search Mode “Most Empty by Volume” or “Least Empty by Volume”; As a trigger for Replenishment if using Replenishment Mode “Percentage of Max”.
Min/Max Units	Refers to the min/max units of inventory allowed in the location at a time.
Max LPNs	Maxinum LPNs the location can hold.
Mod Timestamp	When Location was last modified.
Mode User	User that last modified this location.
Allow Multi Sku	If checked, allows location to have multi-Sku.
To be counted flg	If checked, a cycle count has been created for this location.
To Be Counted Ts	A time stamp that gets set whenever the to_be_counted_flg gets set.
Lock Code	Used to lock a location. When a location is locked, all inventory stored in this location receives the specified lock code. Additionally, any other LPN that is located to this location will have that lock code added to it as well.
Last Counted At	When item was last counted.
Last Counted By	User that completed cycle count.
Allow reserve partial pick	This flag determines whether the location can be allocated for partial picking or not. If the flag is checked, the location is eligible for partial picking, and vice versa. If this flag is checked, you can add an extra restriction to prevent Full LPNs stored in this location from being broken by setting the Facility Parameter “RSV_PARTIAL_STRICT_FLG” to “YES”. Note: The system is not currently handling the Allow reserve partial pick flag during replenishments.
Lock_for_putaway_flg	If set to “YES”, the location is not considered when using “Directed Putaway.”
Putaway Seq	Refers to the putaway sequence of the location, similar to the Picking Sequence field. Putaway sequence values for all locations must have the same number of digits; it is recommended that the user start this field with the value 10000.
Replenishment Zone	Replenishment Zones define locations that are eligible for replenishment when a Replenishment wave is executed. Replenishment Zones must first be created in the “Replenishment Zones” screen.
Min/Max Volume	Refers to the min/max volume of inventory allowed in the location at a time. These values are used during the following: Putaway: If the location’s max volume is reached, WMS skips this location for putaway. Replenishment Mode “Percentage of Max”: If the location’s inventory drops below the ‘min volume’ value, WMS triggers this location to receive replenishment up to the defined ‘max volume’.
Restrict Batch	If the Restrict Batch flag value is set to yes, then the idea is to not have different batch numbers for the same sku present in a single location. If there are different batch numbers but each batch corresponds to different items, then the system should allow putaway to place the LPN. If a Pallet has two LPN's (LPN-1==>SKU-A batch-b1, LPN-2==>SKU-A, batch-2) then the location with restrict batch flag set to yes should not be picked even though capacity checks passes. If the flag value is set to no then the system allows mixing inventory with different batch numbers in same location for same sku. So If Pallet has two LPN's (LPN-1==>SKU-A batch-b1, LPN-2==>SKU-A, batch-2) then location with restrict batch flag set to no should be picked for putaway assuming other checks do pass.
Item Assignment Type/Item	These fields assign a permanent item to a location. If the Item Assignment Type is set to “Permanent” and the Item Code is specified in the Item field, other items may not be mixed in this location. These fields also set up locations for Replenishment.
Task Zone	Task Zones are used to group locations based on a functional configuration. Usually locations of type “Drop” are assigned Task Zones. Task Zones may be used to designate a “Destination Zone” in the Task Template. If this is defined, you are asked to drop the LPN to the “Destination Task Zone” at the end of a Task. Task Zones are also used as intermediary locations for Tasks that require multiple drop locations.
Mhe_system/Divert Lane	This field specifies whether or not this location will integrate with an mhe system for routing purposes. If an MHE system is defined, you must populate the specific Divert Lane code that the location will be used for during routing.
Pick zone	Configured / designated picking zone.
In Transit Units	Units that are en route to the location.
Cust Field 1-5	Used as custom fields for any custom operation. Example: Using cust_field_1 to populate a printer’s IP address to assign a printer to that location.
Display Text	A calculated field that is the concatenation of area, aisle, bay, level, position and bin. These are separated with a '-'.
Restrict Inventory Attribute	If checked, only allows one inventory attribute to be stored in the location.
Assembly Flag	If checked, flags a location where inventory is brought to to be assembled into a different SKU.
Billing Location Type	Specify billing location type.

Creating Locations through the Interface (UI)

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:

Interface Code	Location Type
C	Consolidation
D	Dock
Q	QC
V	VAS
P	Drop
S	Staging Location
A	Active
H	Pack and Hold
Y	Shipping Location
R	Reserve
K	Packing Station
T	Receiving Station

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.

Inventory Screens

You can use the following screens to view the available inventory in the warehouse:

• Reserve Inventory
• IBLPNs
• Inventory Summary

Reserve Inventory

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.

IBLPNs

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.

Action Button	Description
Accept	If the LPN is Marked for quality control, you can accept it here.
Reject	If the LPN is Marked for quality control, you can reject it here.
Deallocate LPN	If the LPN is allocated, you can deallocate here.
Print Label	This button prints the LPN label according to the label template set up in Label Template View (label type IB Container)
Blind Labels	Allows you to print blind labels by selecting the number of labels, Label type (either IBLPN, OBLPN or Pallet), Destination company, and Destination facility.
Change Pack QTY	Allows you to change the pack quantity of the selected IBLPN.
Set LPN as Pallet	Allows you to Set LPN as Pallet.
Unset LPN as Pallet	Allows you to unset LPN as pallet.
Modify Qty	Allows you to modify the LPN quantity, and you must provide a reason code.
Locate LPN	Locates the LPN. If the flag capacity check is enable, the system will make sure that the LPN fits the location according to max volume, max units, and max weight.
Generate MHE Distribution Msg	It generates the TO_MHE_DISTRIBUTION_INFO message.
Generate MHE IB LPN Info Msg	It generates the TO_MHE_IBLPN_INFO message.
Mass Update Attributes	Allows you to do a mass update for Inventory attributes A-O and Putaway Type. Updates all the records shown in the page, so it’s a good idea to limit your search. It will first tell you the number of records that will be updated.
Print UOM Label	Allows you to print a UOM Casel label or UOM Pack label fo the LPN selected.
Update LPN Type	Allows you to update the LPN type of the selected LPN.

Editing Batch Numbers

Currently, Oracle WMS Cloud provides an option from the IB LPN Inquiry screen to update batch numbers for batch tracking items. Some warehouse managers may want the option to prevent batch number edits for certain users based on screen parameter settings.

The allow_edit_batch_nbr screen parameter in the IB LPN Inquiry screen allows you to prevent editing the batch number of an inventory.

Parameter Choice Behavior

• When the allow_edit_batch_nbr parameter is set to yes, the batch number field in the edit screen in the IBLPN inquiry will be editable and you can edit the batch number and save.
• When the parameter is set to no, you can edit the batch number field in the edit screen in IBLPN inquiry. However, when you Save the edited batch number, the system will throw the error "Cannot change batch number".

UI Screen Parameter Name	Options	Behavior
allow_edit_batch_nbr	yes	User can edit batch number and save.
	no	Batch number field is editable and once you save, the system throws error “Cannot change batch number.”

Inventory History

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

ERP or any other external system that may be interested.

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

Note: not all columns will be included in each IHT record.

Enable/Disable Auto Process

To help customize your view of inventory history records, from the Inventory History Activity Parameters UI you can click the Enable Auto Process or Disable Auto Process buttons.

Once you click the Enable or Disable Auto Process buttons, a dialogue box appears asking for your password. Enter your password and click Submit.

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.

Enable Auto Send of Inventory History

In the past the main way to extract WMS transaction records would be via scheduled jobs at pre-determined intervals. Scheduling too frequently may place unnecessary load on the system and scheduling too infrequently may caused delays in notifying the ERP or other systems of critical WMS updates. You can now automatically send inventory history records as and when they are created.

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

Note: the flag is No. Auto send is supported if the file format is XML and also if the interface type is RestWebServices.

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.

Set Inventory History Transactions to Not Ready (Un-Processed)

From the Inventory History UI, you can click the “Mark Unprocessed” button to change the IHT status of a record to Un-Processed (Not Ready).

The Mark Unprocessed button allows you to reprocess the IHT records and let the system to pick up inventory again.

Note: The “Inventory History/ Can mark Inventory History unprocessed” permission should be enabled at the group level for user role SUPERVISOR/EMPLOYEE/GUARD/MANAGEMENT to perform this action.

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”.

Note: You need to turn-off the Auto-Process parameter in the Inventory History Activity parameter screen in order for the system to change the status of the IHT record status. Otherwise, if the Auto-process is configured for the IHT, then the record continues to remain in Processed status and the activity will not be reset to “Not Ready”.

Configuring Reason Codes

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”.

Reason Code Parameters

You may also configure reason codes that are required for certain transactions. These parameters are located in the “Company Parameters” screen.

• CYCLE_COUNT_REASON_CODE: Defines the reason code for performing a cycle count.
• DFLT_BATCH_EXP_ADJ_REASON_CODE: Defines the reason code for modifying a container’s batch expiry date.
• SHORT_REASON_CODE: Defines the reason code for performing a short pick.

Lock Codes - Background

Lock Codes control whether material is considered available for allocation and whether certain transactions can be performed against it (e.g. putaway, loading, manifesting, shipping loads).

Note: the parameter to disallow Multiple Lock Codes is only enforced during Receiving.

• Lock Codes can be applied to Active Locations, and Inbound and Outbound LPNs. When Lock Codes are associated to a batch, the Lock Code gets applied to all of the LPNs that contain that batch, including all of the material contained in the LPN regardless of the batch.

• Fully available inventory typically has no Lock Code.

• Multiple Lock Codes can only be applied at the LPN level. You can only apply one Lock Code to an Active Location.
• Reserve locations can have a lock code. Any LPN located in that location will get that lock code applied upon putaway. Unlock/remove lock code on LPN must be used to remove the lock code from the location while the LPN is still located. Moving an LPN out of the location does not remove the lock code.

Configuring Lock Codes

Lock Codes must be added at the Parent company level.

1. Make sure your current company view is at the Parent company.
   Note: the system will display an error if you try to configure lock codes at the child company level.
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.

Adding a Lost Lock Code

Warehouses can have a lock code exclusively for lost items. WMS requires a separate configuration to differentiate a lost lock code from all other lock codes.

1. Go to the “Company Parameters” screen.
2. Edit the “LOST_LOCK_CODE” parameter. In the “Parameter Value” field, populate the lock code you wish to use as the lock code for lost LPNs.
3. Click “Save”.

Lock Code Priority

The Inventory Lock Codes screenallows you to associate an Inventory Bucket (ERP Bucket) and tag a lock code priority.

Fields on Inventory Lock Codes Screen

ERP Bucket is a free form field where ERP buckets against the lock code can be defined. By default, this field is blank. You can track ERP buckets on the inventory by defining values in this field.

Note: the ERP bucket name should be configured properly to correspond to an Inventory Summary Bucket in ERP.

Lock Code Priority is a numeric field where priority for the lock code can be defined. The default value in this field is blank. You should define a distinct lock code priority value. When Inbound or Outbound LPNs are associated with multiple lock codes, then the lock code with the highest priority is considered for the ERP bucket. Lower numeric values are considered as the highest priority value. You should prioritize the lock codes from most restrictive (Priority 1) to least restrictive.

Allocatable flag - This flag on the lock code specifies that inventory can be allocatable for an order.

Unlock on locate to reserve flag - The Unlock on locate to reserve flag specifies that if inventory is located to reserve or active, the lock code gets removed from the Inbound LPNs.

Treat as Attribute – If a Lock Code has the Treat As Attribute field set to an attribute (between a-o), the Lock Code is recorded to the corresponding attribute field set in the Lock Code configuration. During any transaction, if a Lock (with "Treat_As_Attribute" set to any value between a-o) is applied to the LPN/Inventory and the LPN/Inventory already has an inventory attributes (a-o) value, then the system will overwrite the inventory attribute value on the corresponding inventory record when the Lock Code is applied. Treat as Attribute functionality is only applicable for IBLPNs and Active inventory.

Note: You can use the “Treat as Attribute” feature if you plan to align WMS Cloud Lock Codes to ERP Inventory Summary buckets.

Prevent Putaway – When an LPN is scanned, if the LPN has at least one lock code that has the flag 'Prevent Putaway' set to yes, the system will prevent the user from LPN putaway.

Copy to Transfer Shipment flag – When set to yes, the system passes the lock code from shipped out LPN's to Auto Created ASN's during transfer shipment so that destination DC/Stores can handle the putaway of the inventory.

Prevent Direct Consume - If an LPN has a lock code, and the lock code has the flag Prevent direct consume set to Yes, the system will not allow the user to consume this LPN using the transaction RF Direct Consume.

Company Parameter – Honor Lock Code Priority

When inventory is subjected to multiple lock codes, users need to know from which ERP bucket lock codes need to be considered against the inventory. To overcome this scenario, WMS determines priority associated with the Lock Code and considers the ERP bucket from the highest priority lock code.

The company Parameter “HONOR_LOCK_CODE_PRIORITY” (when set to yes) allows you to enable Lock Code Priority values. The default value in this parameter is blank (No).

Note: If you are using the ERP bucket feature, it is recommended that you confirgure this value.

The following table describes the behavior for the Company Parameter honor_lock_code_priority:

Company Parameter honor_lock_code_priority set to:

Description

Yes

ERP buckets that correspond to the lock code with the highest priority are picked up while writing inventory history. Lock Code priority is used to determine the ERP bucket. If a new lock code is applied on the inventory, then the previous ERP bucket value is based on the highest priority lock code present on the inventory prior to the new lock being applied. The current ERP bucket value is based on the highest priority lock code present on the inventory after a lock is applied. If an existing lock code is removed from the inventory, then the previous ERP bucket value is based on the highest priority lock code present on the inventory prior to the lock being removed. The current ERP bucket value is based on the highest priority lock code present on the inventory after the lock is removed. The previous and current ERP bucket on the inventory can be the same when inventory has the highest priority lock code and a lock code added/removed is having lock code lower priority (higher value) than already existing locks on Inbound LPN’s or Outbound LPN’s. If inventory is adjusted, then the previous and current ERP bucket is determined by the existing lock codes on the inventory. Some IHT’s populate previous and current lock codes in reference fields. Ordering of lock codes is in descending order of lock code priority. If inventory has multiple lock codes with conflicting lock code priority, then the ERP bucket is picked up from the lock code that was applied last. Lock Codes are ordered based on the lock code priority value. Locks applied on the container that also have a batch lock are considered while determining the ERP bucket. The ERP bucket is determined by considering the locks present on the container/location and the batch lock. When using this parameter, you should not have lock codes without ERP buckets for the highest priority lock code value.

Company Parameter honor_lock_code_priority set to:

Description

No

If you don’t want to use the priority defined on the lock code for ERP bucket consideration, you can set the value to No (Default value) in this parameter. When the value is set to No, the ERP bucket is determined based on the order in which the lock code is applied. The ERP bucket corresponding to the last applied lock code is considered. Locks applied on the container and the batch lock are considered while determining the ERP bucket. If the inventory has a container/active location lock and batch lock, then the ERP bucket is determined by based on the last applied lock code. If a new lock code is applied on the inventory, then the previous ERP bucket value is based on the last applied lock code on the inventory prior to the new lock being applied. The current ERP bucket value is based on the new lock code applied. If an existing lock code is removed from the inventory, then the previous ERP bucket value is based on the last applied lock code present on the inventory prior to the lock getting removed. The current ERP bucket value is based on the last applied lock code present on the inventory after the lock is removed. If inventory is adjusted, then the previous and current ERP bucket is determined by considering the existing lock codes on the inventory. If Inventory history has old and new lock codes populated, then the lock codes are ordered based on the ascending order of the lock code applied timestamp.

Example

Scenario: the following example shows the inventory flow from one bucket to other bucket when an LPN is applied with multiple lock codes.

Configuration

• The Facility Parameter “DEFAULT_ERP_BUCKET_FOR_INBOUND_INVENTORY” is set to “AVAILABLE.”
• The Company Parameter “honor_lock_code_priority” is set to Yes.

The Lock Code are configured with the following priority:

ERP Bucket	Lock Code Priority
Damage	1
Receiving	2
Cycle Count	3
Quality Check	4

1. The LPN is received in the warehouse with a default Receiving Lock Code. Inventory is moved to the Receiving bucket:
2. Inventory is located to the reserve location in the warehouse. The Receiving lock code is removed and the inventory is moved to the default available bucket.
3. A Lock Code of Cycle Count is applied, and the inventory is moved to a Cycle Count bucket.
4. Again, the Lock Code Damage is applied. Now inventory is moved to the damage bucket as the Damage lock code has the highest priority.

   

Key Considerations for Lock Codes

If	Then
You do not want to track ERP buckets…	Then you should not configure the ERP bucket value on the Lock Codes and Default Facility/Company parameter for ERP buckets. Also, you should not configure Lock Code Priority/Honor Lock Code Priority.
You decide when inventory is subjected to multiple lock codes…	The ERP bucket should be considered based on lock code priority or the lock code applied sequence, and based on that Honor Lock Code Priority company parameter.
The company parameter Honor Lock Code Priority is enabled…	The lock code priority should be populated with the proper numeric value. A blank value on the lock code priority column will have lesser weightage compared to lock codes with a numeric value.
Lock Codes are not defined with an ERP Bucket…	The system considers the default ERP bucket from the Inbound Facility parameter for inbound inventory and the default ERP bucket from the Outbound Facility parameter for the outbound inventory.
If lock the code is not configured with an ERP bucket and the lock present on the LPN’s does not have ERP buckets…	the value is considered from the default facility /company parameters.
You change the ERP bucket and lock code priority once they are set…	This might cause issues in regard to integration set up. Newly reflected ERP bucket values are considered for future Inventory History records that are written and not for previously created records.
Multiple lock codes on the inventory have the same priority…	The ERP bucket is picked up from the lock code that was applied last. It’s suggested not to have conflicting priority for lock codes.
You populate ERP Buckets with names such as (Prevent Loading, Unavailable for Allocation)…	This will not prevent inventory for allocation or Loading. In addition, corresponding Lock code properties should be set for WMS to achieve these operations.
You are using lock codes that are not defined with an ERP bucket…	The previous/currentERP bucket will not be populated.

Note: Default ERP bucket is considered when there is no outstanding lock code on the inventory being dealt with. The consideration of Adjusted Quantity/ Original Quantity for ERP bucket is based on IHT’s.

The following are the list of transactions where ERP bucket value is considered from default Facility/Company parameters even though lock codes are populated on the IHT’s. During those transactions, the system writes Lock Inventory History Transactions, to avoid double dipping of the inventory in the ERP bucket this change is done.

Activity	Inventory History Transaction
Container Received with default lock code	Even though the receiving inventory is subjected to lock, and the current ERP bucket is populated from the facility parameter “DEFAULT_ERP_BUCKET_FOR_INBOUND_INVENTORY ", the system populates the lock codes on the IHT with respect to receiving (IHT- 1 and IHT- 72).
Container Creation with default lock code:	When you create a container with a default lock code, then the system writes IHT for the container creation (IHT 29 -Create Allocatable Container / IHT 30 -Create Unallocatable Container) by populating a default lock code on it, but the current ERP bucket value is populated from facility parameter " DEFAULT_ERP_BUCKET_FOR_INBOUND_INVENTORY "
Inventory Movement to Active Location	When inventory is moved to an active location with a lock code, then the system populates the lock code in the Inventory adjustment IHT (IHT- 4 / IHT- 17) for the active location, but the current ERP bucket value is populated from facility parameter " DEFAULT_ERP_BUCKET_FOR_INBOUND_INVENTORY."
Partial Putaway to Active / Create LPN from Active Locations with a Lock Code	Inventory History (IHT 63 - Lock Update Pre-verification and IHT 64 - Lock Update Post-verification). WMS populates ERP bucket on IHT 63/64 during lock update, ERP bucket populated on this IHT act’s like summary of bucket transfer with respect to subsequent adjustment IHT’s. It’s advised that: If IHT63 and 64 are considered for ERP bucket processing, then ignore subsequent inventory adjustment IHT’s for correct flow of inventory from one bucket to another bucket. If IHT63 and 64 are not considered for ERP bucket processing, then consider subsequent inventory adjustment IHT’s for correct flow of inventory from one bucket to another bucket. After considering IHT 63 and 64 along with subsequent inventory adjustment, IHT’s will result in improper movement of inventory from one bucket to another bucket.

Note: Additional reference fields are added on the IHT’s (Inbound inventory adjustment IHT’s) such as ERP Vendor ID, Vendor Site ID, Unlock on Locate etc… Refer to the IHT Trigger Point Document for details.

Facility and Company Parameters

Two new Facility and Company parameters are available. These parameters allow you to define default ERP buckets for Inbound and Outbound Inventory, (when inventory is not subjected to any lock code or inventory has operational lock codes that are not defined with any ERP bucket.

Note: It is not mandatory for you to configure these facility and company parameters if you are not using them.

Facility parameters will take higher precedence over company parameters.

The default Facility and Company Parameters for Inbound Inventory is:

DEFAULT_ERP_BUCKET_FOR_INBOUND_INVENTORY

• Allows you to define the default ERP bucket for inbound inventory in the above parameter. When inbound inventory does not have a lock code or a lock code present is not defined with an ERP bucket, then the system populates the value from the inbound facility parameter.
• If the facility parameter is set to blank, then the value in the ERP bucket is considered from the Inbound company parameter.

The default Facility and Company Parameter for Outbound Inventory is: DEFAULT_ERP_BUCKET_FOR_OUTBOUND_INVENTORY

• Allows you to define the default ERP bucket for outbound inventory in the above parameter. When inventory associated with an outbound LPN does not have a lock code or lock code present is not defined with an ERP bucket, the system will populate the value from the outbound facility parameter.
• If the facility parameter is set to blank, then the value in the ERP bucket is considered from the Outbound company parameter.
• If you want to keep the same default ERP bucket for both Inbound and Outbound inventory, you can define the same value in the Inbound and Outbound Facility/Company parameters.

Inventory History

Inventory History is now enhanced to display Previous and Current ERP buckets for inventory.

Previous ERP Bucket: the Value in this field represents the previous ERP bucket associated with the inventory before the inventory is subjected for update (Lock, Unlock, Adjustments, Inventory transfer etc…).

Current ERP Bucket: the value in this field represents the current ERP bucket associated with the inventory after the inventory is updated (Lock, Unlock, Adjustments, Inventory transfer etc…).

The current ERP bucket field can be blank. The previous ERP bucket field is populated if the system is consuming or shipping out inventory..

Values in the previous and current ERP bucket are derived based on the lock code associated with the inventory. If lock codes are not present, then the default value from the Facility/Company parameter is considered.

All of the IHT’s are not subjected for ERP Bucket population. Only IHT’s that impact inventory changes are subjected for ERP Bucket value population. See Inventory History Transactions subjected for ERP Bucket for more information about which IHT’s are subjected for ERP bucket changes.

Note: Some transactions result in multiple IHT's.

• The Inventory History file that is generated will include the previous ERP bucket, the current ERP bucket, and the lock code priority fields.
• Lock Code Priority value on the IHT is populated only for Lock/ Unlock container IHT’s.

• ERP Systems can use previous and current ERP buckets for updating the summary inventory buckets in ERP.

Output Interface

Shipment Verification:

The shipment verification file includes the lock codes present on the LPN during shipment verification and the ERP bucket. If multiple lock codes are present on inbound LPN then corresponding lock codes are separated with a delimiter. The ERP bucket is determined by considering the lock code priority or based on the last lock code applied.

Ship Load (SLS):

The Ship Load (SLS) file includes the lock codes present on the OBLPN during Ship Load and the ERP bucket. If multiple lock codes are present on the outbound LPN, then the corresponding lock codes are separated with a delimiter. The ERP bucket is determined by considering the lock code priority or based on the last lock code applied.

Note: the new fields added to the Shipment Verification and SLS file are applicable to the 20D version of Oracle WMS Cloud and not prior versions.

Inventory History Transactions subject for ERP Bucket

For more details on previous and current ERP bucket population for the following list if IHT’s, refer to the interface specification (IHTTrigger Point Document).

Inventory History Transaction	Description
IHT 1	LPN Received
IHT 2	Container Consumed
IHT 3	Container Shipped
IHT 4	Inventory Adjusted pre verification
IHT 10	Container DetailPacked
IHT 11	Container Packed
IHT 14	Container Cancelled
IHT 16	Pre receive inventory Adjusted pre verification
IHT 17	Inventory Adjusted Post verification
IHT 19	Inventory Adjustment Cycle Count Active
IHT 22	Lock Container Before ASN Verification
IHT 23	Lock Container After ASN Verification
IHT 24	Unlock Container Before ASN Verification
IHT 25	Unlock Container After ASN Verification
IHT 29	Create AllocatableContainer
IHT 30	Create UnallocatableContainer
IHT 31	OB Container Modified
IHT 32	OB ContainerCancelled
IHT 34	Split Container Before ASN Verification
IHT 35	Split Container After ASN Verification
IHT 36	Split Container Lock Acquired
IHT 49	Lock Active
IHT 50	Unlock Active
IHT 52	Audit Adjustment
IHT 53	Cycle Count Reserve SKU Counted
IHT 54	Container DetailPicked
IHT 62	POS Interface
IHT 63	Lock Update Pre verification
IHT 64	Lock Update Post verification
IHT 65	Lock OBLPN
IHT 66	Unlock OBLPN
IHT 69	Kitting Complete
IHT 70	Kitting InventoryConsumed
IHT 72	Container Received Subject to QC

Lock Code Priority Configuration

To setup ERP buckets and lock code priority for inventory, you need to do the following:

1. Configure the ERP Bucket in the Lock Code Field.
2. Set the Lock Code priority in the Lock Code Field to prioritize lock codes based on lock code priority value. (Applicable when inventory has multiple lock codes.)
3. The default ERP Bucket should be configured in Facility and Company parameters.
4. The Company Parameter Honor Lock Code Priority should be set to Yes (Applicable when inventory has multiple lock codes) to prioritize lock codes based on the lock code priority value.

Adding Lock Codes to LPNs

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.

Modifying IBLPNs

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.

RF Create IBLPN

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.

Formatting Rules for Inventory Attributes

Because there can sometimes be a mismatch of inventory attributes in systems overall, WMS structures rules around open inventory attribute fields. This gives more control to end users for what they want to store in these fields.

In order to provide consistency for tracking inventory attributes in ERP and across other systems, you can create formatting rules for inventory attributes.

The following topics provide details about configuring formatting rules and applying rules in the RF, UI, and APIs. which will help prevent incorrect data entry:

Configuring Formatting Rules

From the Column Formatting Rule UI, you can create formatting rules for inventory attributes:

From the Column Formatting Rule UI, you can define numeric data types and set minimum to maximum values to associate with inventory attributes a to o. You can also define the decimal precision for numeric inventory attribute values.

Note: you can’t enter decimal values for Min/Max fields above the defined precision. Also, you can’t save multiple formatting rules for the same inventory attribute column. The system will throw an error message in this case.

To create a formatting rule:

1. From the Column Formatting Rule UI, click create.
2. Select the Facility or * to apply the rule to all Facilities.
3. Set the min/max value and precision.
4. Select the Active Flag to enable the rule and click Save.

The following table provides descriptions for each of the configurable fields in the Column Formatting Rule UI:

UI Column	Description
Facility Code	User can select the facility or make it *. This drop-down will show what the logged in user is eligible for. Selecting * allows you to apply formatting rules to all associated facilities.
Column	List of Inventory Attributes (Drop-down)
Data Type	Numeric or String
Min Value	Applicable if the data type is Numeric. (leaving the field blank means there is no minimum value stipulated)
Max Value	Applicable if the data type is Numeric. (leaving the field blank means there is no maximum value stipulated).
Precision	Applicable if the data type is Numeric. This field does not support negative values. This field depicts the maximum precision allowed. A precision of 0 means no decimal points are allowed.
Active flag	Enable the active flag to activate or deactivate the rule. If the rule is not activated, then formatting rules will not be triggered.

Note:

• the system will not validate formatting rules against existing data. However, any new data will validate against formatting rules that you setup.
• the system will not allow multiple rules activated for the same inventory attribute/facility/company code combination.
• When multiple attributes are provided for a SKU, rule validation will happen before the user captures the next attribute field.

Validating Formatting Rules

RF Screens

Once formatting rules are configured, Oracle WMS Cloud will validate and apply the formatting rule criteria. The decimal precision and the min/max range will be applied as configured on the formatting rule for all RF transactions that prompt for inventory attributes including:

• RF Receive by shipment
• RF Receive by Load
• RF Cycle Count Location
• RF Cycle Count LPN
• RF Create LPN
• RF Sort and Receive.
• RF Split IBLPN
• RF Modify LPN
• RF NC Active Picking

Note: If the formatting rule mandates precision, you won’t be allowed to enter more than the precision after the decimals. If the rule has the min and max range configured, the entered value has to be within the range.

IMPORTANT: If you need to enter values with decimals and negative values, you must configure the company parameter Allow Barcode lower characters to allow "." or "-" .

Note: "." and "-" will be applicable for all barcode entries.

UI Screens

Once formatting rules are configured, Oracle WMS Cloud will validate and apply the Column Formatting Rule criteria. The decimal precision and the min/max range will be applied as configured on the formatting rule for all UI transactions that display attributes for user entry:

• Purchase Order Inquiry
• Order Inquiry
• Work Order Inquiry
• Inbound Shipment Inquiry
• IBLPN Inquiry
• Mass Update Inventory attributes
• Bulk Update Order details

Inventory attribute formatting rules are triggered when you click Save after creating/editing the record.

Note:

Input Interfaces

The Column Formatting Rule is validated in the Input Interfaces because data could come from external systems. WMS triggers formatting rules for inventory attributes to prevent invalid data from entering the application. The system will error and prevent records from interfacing if the rule fails.

• IB Shipment
• Orders
• POS
• Work Order
• Purchase Order

In the Input interface Configuration UI, you can enable trigger formatting rules for Input Interface screens via the Trigger Formatting Rules flag. This flag defaults to no. Input Interface validation will be triggered only if the corresponding interface being run has the trigger_formatting_rules flag enabled.

To enable trigger formatting rules for Input Interface screens:

1. From the Input interface Configuration UI, select the interface type for which you want to enable trigger formatting rules.
2. Click Edit.
3. Select the Trigger Formatting Rules checkbox and click Save.

Note: Be aware that when you configure formatting rules for Input Interface screens, this can have an impact on processing time for associated records.

The new configuration added to the Input Interface Configuration UI is only applicable for Purchase Order, Inbound Shipment, Orders, POS, and Work Order interfaces. Even though the Input Interface Configuration UI configuration can be enabled for other interfaces like appointment, cubiscan etc, trigger formatting rules do not apply to them.

Note:

• Inventory attribute Column Formatting Rules will not be triggered during Input Interface processing for action code of "Delete".
• The DTLUPDATE action code in header is supported for Purchase Order, Inbound Shipment, and Order Interface interfaces. Column Formatting rules are triggered for the DTLUPDATE action code when the detail action code is "UPDATE" or "DELETE".

Formatting Rules and Treat as Attribute Flag

The Order Interface allows lock codes from the order detail to be populated onto the inventory attribute if the Treat as Attribute flag is set on the lock code.

Note:

• Inventory Attribute formatting rules will not be applied when treat as attribute functionality is triggered. Users should ensure that any lock codes intended to populate an attribute do not have formatting rules defined.
• If attributes are not captured in the RF, formatting rules are not triggered. If Receiving does not prompt for attributes and corresponding shipment details have attributes which are not honoring formatting rules, receiving process will not be stopped. Formatting rules are only triggered upon user entry.

APIs

Certain Oracle WMS Cloud REST APIs allow inventory attributes to be interfaced and create new inventory records in the system. Once column formatting rules are configured for a particular inventory attribute, Oracle WMS Cloud will validate and apply the rule criteria for the relevant inventory attribute. API operations will fail when formatting rules are not honored or met.

The system applies formatting rules using the following API trigger points:

API Operation	Description
Update Active Inventory	Operation to update active inventory. POST .../entity/location/{id}/update_active_inventory/
Composite Create	Used for Creating IBLPN with all details in a single request) POST ¿/wms/lgfapi/v10/entity/iblpn/composite_create/
Bulk Update Inventory Attributes	Operation to Bulk Update Inventory Attributes on Inventory POST ¿/wms/lgfapi/v10/entity/inventory/bulk_update_inventory_attributes/

Note:

• When the user performs one of the above operations, if any of the attributes fail the validations, the system will send a response that includes the attribute which failed the validation.
• There will be some additional processing required for validating the formatting rules, so customers using Bulk Update Inventory Attributes cannot expect same performance levels with formatting rules enabled.

Combining / Splitting IB LPNs

If two or more IB LPNs for the same item need to be combined into a single LPN, you can do this through the “Split Cntr” RF module. This module is used to either split or combine two IBLPNs into one IBLPN.

1. Go to the RF transaction “Split Cntr”.
2. Scan the LPN that needs to be moved into another LPN or from which part of the inventory it will be moved.
3. Scan the SKU Barcode of the item being moved to the other LPN.
4. Enter the quantity that will be moved from the old LPN to the new LPN.
5. If the LPN is being combined, enter the full quantity being moved.

• If the entire quantity of the original LPN is being moved, the original LPN will be cancelled. Press ‘CTRL-A’ to accept.

Inventory Summary

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.

Cycle Count

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.

Note: Multiple locations per item, work in process, and lags in paperwork processing can contribute to errors. You can mitigate these problems with correct cycle count procedures that specify not only the part number to be counted but also the location the part number should be in.

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)

How To Check for a flagged Cycle Count Location

The Active and Reserve Location screens include a “To be Counted flg” column – if the value is Yes, then it means that the location needs to be cycle counted.

The Tasks screen.

Every location flagged for Cycle Count has a Task tied to it. To view these Tasks, filter the results by setting the Task type to “CC Location Contents” or “CC Location LPN Scan” and the status to “HELD” or “Ready”.

Cycle Count Execution (RF)

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.

Cycle Count Location

1. Enter RF transaction “Cycle Count Location”.
2. Scan the location that will be cycle counted.
3. Input the number of LPNs in that location.
4. Press Ctrl-E to end the count.
   • If the LPN quantity inputted is incorrect, RF prompts you to use the detailed Cycle Count transaction (option 0 - Cycle Count LPN Detail).

Cycle Count LPN

1. Enter RF transaction “Cycle Count LPNs”.
2. Scan the location to be cycle counted.
3. Scan the LPNs in the location.
   Note: if you scan an LPN that does not exist in the location, the RF prompts the message “Rescan the same LPN”. When you rescan the same LPN, WMS makes the inventory adjustment to record the new LPN into the location.
4. Continue step 3 until all LPNs are scanned.
5. When you are done scanning all the LPNs, press Ctrl-E to close the count.
   1. If WMS thinks there are still LPNs left to be scanned, the RF prompts the message “Remove LPNs from Location?”, followed by a list of LPNs that have not been scanned. Press Ctrl-A to proceed with the inventory changes.
   2. If the Cycle Count was correct, RF will prompt the message “Count completed for location”.

Cycle Count LPN Detail

1. Enter RF transaction “Cycle Count LPN”.
2. Scan the location to be cycle counted.
3. Scan the first LPN in the location. Scan the SKU and quantity for the current LPN.
   • If the LPN has the “LPN is Pallet” flag set to “FALSE”:
   • If the LPN has the “LPN is Pallet” flag set to “TRUE”:
   • Cases per Tier refers to the “LPNs per Tier” field in the item’s detail in the Item Master.
   • Tiers per Plt refers to the “Tiers per Pallet” field in the item’s detail in the Item Master.
4. If the quantity is incorrect, the RF will prompt message “Reenter quantity for this item”.
   • If you reenter the same LPN, SKU and quantity, the adjustment is made.
   • If you are counting a multi-SKU LPN, the RF displays a warning message for SKUs that are not counted.
   • If the quantity is correct, the RF screen blinks and you can continue scanning the rest of the LPNs in the location.
5. When all the LPNs have been counted, press Ctrl-E to end the count.
   • If there are LPNs that have not been counted, the RF prompts a message “Remove LPNs from Location?” to ensure this change. When you accept with Ctrl-A, the uncounted LPNs are set to “Lost” status and the inventory adjustment is made.
   • If all the LPNs are counted, the RF prompts the message “Count completed for location.”
   Note: LPNs in “Allocated” status cannot be “Lost”.

Cycle Count Caveats

1. WMS always validates the LPN’s Inventory Attributes (Batch Number, Expiry Date and Serial Number), if the SKU requires it.
2. LPNs that are allocated to a wave cannot be “Lost” during a Cycle Count transaction.
3. LPNs in “allocated” or “partially allocated” statuses cannot be Cycle Counted.

Cycle Count Task Creation

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

Cycle Count Trigger Management

Oracle WMS Cloud contains a list of possible triggers for cycle counts that you can choose to enable. When enabled, the system automatically generates Cycle Count Tasks for its location.

The Cycle CountTrigger Management screen contains the following parameters:

• Facility/Company: Defines which Facility and Company this trigger applies to (an asterisk * means it applies to all facilities/companies – must be at PARENT company level).
• CC Trigger: A description of the trigger. This is the action that will trigger the CC Task.
• Enabled: “Yes” means the trigger is enabled.
• Priority: The priority given to the Task when created.
• Task Type:
  • CC Location LPN Scan: Creates a Cycle Count Task that prompts you to scan the LPNs in the location.

See Cycle Count Execution (RF) for details.

• CC Location Content: Creates a Cycle Count Task that prompts you to scan the LPNs, SKUs and quantities in the location.

See section Cycle Count Execution (RF) for details.

Description of Cycle Count Triggers

Trigger	Definition/Expected behavior
Alternate location for Putaway	- You scan a location different than the one directed by the system during directed putaway: - System generates a CC task for the location directed by the system. - Trigger module: ‘rf.inbound.cwrfputaway’ with mode = ‘Directed Putaway Pallet’ or ‘Directed Putaway LPN’.
Short pick	- You short pick an LPN or units from an LPN: - System generates a CC task for the location where the LPN was shorted. - Trigger modules are: ‘rf.outbound.cwrfpacklpn’,‘rf.inbound.cwrfmovelpn’, ‘rf.inbound.cwrfpickiblpnreplen’, ‘rf.outbound.cwrfpickcart’, ‘rf.outbound.cwrfpackncactiveorder’, ‘rf.outbound.cwrfpickiblpn’
Short pick active	- You short pick the remaining quantity of a SKU in an active location: - System generates a CC task for the location where the quantity was shorted. - Trigger modules are: ‘rf.inbound.cwrfpickiblpnreplen’, ‘rf.outbound.cwrfpickcart’, ‘rf.outbound.cwrfpackncactiveorder’, ‘‘rf.outbound.cwrfpickiblpn’
Cancel OBLPN in ‘OB Created’ status	- You cancel an OBLPN in ‘Outbound Created’ status from the UI: - System generates a CC task for the location(s) where the inventory in this OBLPN was allocated from. - Trigger module: ‘ObContainerView’ - Note that this trigger should only work when an OBLPN in ‘Outbound Created’ status is cancelled manually from the UI. If an OBLPN in ‘Outbound created’ status is cancelled by ‘Undo Wave’, the system should not create corresponding CC tasks even if this trigger is enabled.
De-allocate IBLPN from UI	- You de-allocate an IBLPN from UI: - System generates a CC task for the location where the IBLPN was de-allocated. - Trigger module: ‘IbContainerView’
De-allocate Active Inventory from UI	- You de-allocate a SKU from active inventory in the UI. - System generates a CC task for the location where the SKU was de-allocated. -Trigger module: ‘ActiveInventoryView’
Set Location ‘To be counted’ from Location screen	- You set the “To be counted” flag equal to ‘Yes’ in the UI. - System generates a CC task for the location where the flag was set to ‘Yes’. -Trigger module: ‘LocationViewFW’
Recount Location	- You reject an inventory adjustment record with ‘Loc Dtl Count’ = No and with ‘Creation Type’ = Manual (Recount triggers are only applicable for Cycle Counts done manually). - System generates a CC task for the location with rejected inventory adjustment record. -Trigger module: ‘Inventory Adjustment Management’
Recount Location Detail	- You reject an inventory adjustment record with ‘Loc Dtl Count’ = Yes and with ‘Creation Type’ = ‘Manual’ (Recount triggers are only applicable for Cycle Counts done manually). - System generates a CC task for the location with rejected inventory adjustment record. - Trigger module: ‘Inventory Adjustment Management’
Approve ‘Location Mismatch’ record	- You approve an inventory adjustment record that moves an LPN from another location to the cycle counted location (inventory adjustment record has warning ‘Location Mismatch’). - System generates a CC task for the location where the LPN was located BEFORE the cycle count adjustment (LPN’s ‘Expected Location’). Ex. If LPN was systematically in location A. However, during the cycle count that generated the inventory adjustment record, same LPN was counted in location B. Upon approval of this record, the CC task must be generated for location A. -Trigger module: ‘Inventory Adjustment Management’
Substitute LPN from different location	- You scan an LPN that is in a location different from the allocated LPN during Full-LPN or Reserve NC Picking (LPN substitution from different location). - System generates a CC task for the location where the LPN was allocatedoriginally. - Trigger modules are: ‘rf.inbound.cwrfmovelpn’, ‘rf.inbound.cwrfpickiblpnreplen’, ‘rf.outbound.cwrfpickcart’, ‘rf.outbound.cwrfpackncactiveorder’, ‘rf.outbound.cwrfpickiblpn’, ‘rf.outbound.cwrfrepackoblpn’
Alternate location for Split LPN into active	- You scan a location different than the one directed by the system during RF_Directed putaway with parameter ‘multi-sku-lpn-mode’ = ‘Split into active locations’. - System generates a CC task for the location directed by the system - Trigger module: ‘rf.inbound.cwrfputaway’ with mode = ‘Directed Putaway Pallet’ or ‘Directed Putaway LPN’ AND ‘multi-sku-lpn-mode’ = ‘Split into active locations’.

Configuring Cycle Count Triggers

1. Go to the Trigger Management screen - this displays a list of Cycle Count Triggers.
2. Select the record and click Edit () to customize the trigger.
   1. Tick the “Enabled” checkbox to enable/disable the trigger.
   2. Set a number for the priority. This is the priority of the Task generated from the trigger.
   3. Select the Task Type. This defines the task type for the task created under this trigger (CC Location LPN Scan or CC Location Detali Count).
3. Click "Save" to save the changes.

Creating Cycle Count Tasks with Task Creation Templates

Another way to create Cycle Count Tasks in WMS is through existing Task Templates.

Note:

Optional: Configuration for Task Rules

Ordering Criteria in CC Task Templates are used to configure the order in which CC Tasks are displayed in the RF task list.

Note: If the Ordering Criteria is not specified, CC Tasks in the RF Task List is displayed in order of Task status, priority, and pick sequence.

1. Go to the Task Creation Template screen, select the template and click on ‘Details’.
2. Select the Task Type record and click “Ordering Criteria”.
3. This takes you to a new window with all the ‘ordering’ rules for the task type. Click Create to add a new record.
4. Input the necessary info for the ordering criteria record:

   

   • Sequence Nbr: The sequence number for the ordering criteria record.

   • Order by column: The criteria used for ordering the tasks.

   • Break by count: Leave this field blank (only applicable for non-CC Tasks).

5. Press “Save” to create the record.

Executing Cycle Count Task Templates

Once the Cycle Count Task templates are set up, the next step is to run them.

1. Go to the Task Creation Template screen and select the template.
2. Click on ‘Run Template’. The message “Tasks created” displays. Press OK.
   Note: You must specify a rule selection for the Cycle Count Task Template, or your will receive the error "CC Template does not have a selection rule."
3. To view a list of all the CC Templates that were executed, go to the CC Run Inquiry screen. This is similar to the Wave Inquiry screen for running waves.

Configuring a Cycle Count Approval Rule

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.)

Let’s say you want to define your selection criteria as "Item Unit Cost" >= 50. For all the items that fall under the criteria, you want to set the tolerance % to 10%. In this case, if an item (whose unit cost is 60) is counted and a variance found is above/below 10%, then it will go for approval; otherwise it won't go for approval. (For example, if the expected count is 100, and the counted value is 101 or 99, then it will not go for approval.)

Permissions

From the Group Configuration UI, click Permissions to view the available permissions for Cycle Count Adjustment Rule and to set group permissions.

Cycle Count - Approval Settings

From the Cycle Count Adjustment Approval Rule detail screen, you can set "Approval Settings". Approval settings allow you to configure the mode for approval for each item(s)/ group of item(s) specified in the selection criteria.

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

Let’s say you want to set item(s) belonging to velocity V1 so that they always go for approval when there is a variance. You set item(s) belonging to velocity V2 so that they never go for approval when there is a variance, and item(s) belonging to velocity V3 should go for approval depending on a certain threshold in the variance.

Approval Rule Options

When your Approval rule is configured with Approval Settings = "Apply Tolerance Settings", and you are cycle counting the particular item that falls under this rule, the system will apply the tolerance settings. You can populate each rule detail with different tolerance settings.

From the Cycle Count Adjustment Approval Rule screen, you can click on a rule’s Details to further refine the items that the Approval rule checks.

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

Approval Rule Option	Description
Priority	Priority for the Approval Rule.
Approval choice	You can specify your rule for Manual Approval or to Auto Approve Based on Tolerance.
Approval based on	You can apply Tolerance Settings based on "Quantity" or "Total Adjusted Cost". When the UOM selected is Quantity, you can set the tolerance check in terms of Absolute value or percentage. When UOM selected is Cost, then the tolerance check will be based on Adjusted Cost. When UOM selected is Cost, you can set tolerance check in terms of Absolute value only. So when "Value" is selected, you can specify the tolerance value in the Tolerance Value field. The system then checks for the value set in the Tolerance check by field.
Value or percentage	You can specify your rule to check for either value or percentage for approval.
Min tolerance %	Minimum quantity tolerance percentage that is applied on the Total 'Current Qty'.
Max tolerance %	Maximum quantity tolerance percentage that is applied on the Total 'Current Qty'.
Tolerance value	Is Tolerance value always 0?
Tolerance check by	Tolerance Check By can be populated with Inventory or SKU. This allows you to configure whether the CC approval process should be triggered when there is a variance in the count in Inventory or in SKU. When Tolerance Check By = Inventory, if there is a variance for one of the inventory in the location/IBLPN that goes beyond the tolerance threshold, the system will trigger a manual approval flow. If Tolerance check by is populated as "SKU", then the tolerance check is at the SKU level in the Active/Reserve Location (if RF CC Location is selected). If you specify RF CC IBLPN, then the tolerance check will be at the SKU level in each IBLPN.

Selection Criteria Button

From the Cycle Count Adjustment Approval Rule screen, click Details (), and then click the Selection button to view and configure the Selection Criteria.

Note: From the Rule Detail screen, you can configure different selection criteria for each rule.

Cycle Count Exception Scenarios

Cancelling a Cycle Count Process

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.

LPN is in "Consumed or "Shipped Status

• 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.

LPN is in an Invalid Status

• 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.

Cycle Count Inventory Updates

Deferred vs Immediate Mode

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:

PARAMETER CONFIGURATION		RESULTING BEHAVIOR
Facility Parameter ‘INVN_ADJUSTMENT_APPROVAL_REQUIRED’	Company Parameter‘INVN_ADJUSTMENT_APPROVAL_REQUIRED’	Write record in ‘Inventory Adjustments Management’ screen?	Inventory Adjustments Mode
NO	NO	NO	Immediate
NO	YES	NO	Immediate
YES	NO	NO	Immediate
YES	YES	YES	Deferred

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.

Creation Type

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:

Creation Type	Definition
Trigger	Adjustment was done while executing a task that was created with a trigger.
CC Rules	Adjustment was done while executing a task that was created by running a ‘CC Task Template’.
Recount	Adjustment was done while executing a task that was created by generating a recount (rejecting an inventory adjustment record in ‘Pending’ status)
Manual	Adjustment was done manually with RF_CC Location or RF_CC LPN (no task is executed).

• 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.

Warning	Scenario
Attribute Discrepancy	- You enter a different batch and/or expiration date or serial number during Cycle Count. - Warning should only be displayed for the detail record(s) for which different attribute was entered.
Inventory Expired	- You enter a passed expiration date during Cycle Count. - Warning should only be displayed for the detail record(s) for which an expired expiration date was entered.
Mixed batches in restricted Locn	- You scan multiple batches in a location with ‘Restrict Batch’ flag enabled during Cycle Count. - Warning should be displayed for ALL records in the location. - Inv. Adjustment records with this warning cannot be approved.
Mixed SKUs in Single-SKU Locn	- You scan multiple items in a location with ‘Allow Multi SKU’ flag disabled during Cycle Count. - Warning should be displayed for ALL detail records in the location. - Inv. Adjustment records with this warning cannot be approved.
Permanent SKU mismatch	- You scan an item different than the item assigned to a location with ‘Item Assignment Type’ = ‘Permanent’ during Cycle Count. - Warning should be displayed for ALL detail records in the location. - Inv. Adjustment records with this warning cannot be approved.
Location Mismatch	- You scan an LPN that is systematically in a different location, i.e. LPN’s Expected location <> Cycle counted location. - Warning should be displayed for all the details of the LPN that is scanned in a different location.

• 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.

Approving and Rejecting Adjustments in Deferred Mode

The Deferred Mode allows supervisors to approve/reject inventory adjustments made by users who have previously Cycle Counted locations.

To approve/reject records, make sure it is in “Pending” status and click the “Approve” or “Reject/Recount” buttons.

Approving a record applies the inventory adjustments by adding/subtracting inventory from the locations as well as posting records in the Inventory History screen (referenced by the Group Number).

Rejecting a record will cancel the inventory adjustment and trigger a new CC task so that the location is re-counted.

Deferred Approval Mode set up in RF Cycle Count Transactions

Previously, when performing a Cycle Count with RF Cycle Count Location or RF Cycle Count IBLPN, you would use the screen parameter “auto-approve-mode (update 18C).” This screen parameter is now called “deferred-approval-mode.”

The deferred_approval_mode parameter makes it easy for you to distinguish the approval modes available while you are performing cycle counting operations.

From Modules, select Cycle Count Location or Cycle Count IBLPN, then Screens, and Screen Parameters to view and select your module parameter choice.

Note: you still have the option to use Auto-Approve-Mode as old options in this screen parameter are still available.

The available settings for the Deferred-Approval-Mode screen parameter are defined in the following table:

Mode	Definition
Manual Approve	When "deferred-approval-mode" is set with Manual Approve, "RF Cycle Count Locn/IBLPN" writes the count information in the CC Deferred Adjustment UI and will leave the information for the supervisor to approve or cancel the count if supervisor is logged in with company and facility combination and mode is configured with deferred mode.
Auto Approve	When "deferred-approval-mode" is set with Auto Approve, RF Cycle Count Locn/IBLPN" writes the count information in the CC Deferred Adjustment UI and will get Auto Approved after passing through all the validations if user is logged in with a company and facility combination and mode is configured with deferred mode.
Skip CC Deferred Adjustment	When "deferred-approval-mode" is set with Skip CC Deferred Adjustment, then while executing "RF Cycle Count Locn/IBLPN"; the system does not write the count information in the CC Deferred Adjustment UI even though the user is logged in with company and facility combination and mode is configured for deferred mode. In this case adjustments will be posted as an immediate counting mode. If there are discrepancies found while counting, when the system is operating in this mode, the necessary inventory adjustments are posted when counting is performed for the location/IBLPN.
Approval by Rule	You can define the rules and set the tolerance % or value for an item or group of items. The system will check for rules before writing to the CC Deferred Adjustment UI and wait for approval. See Configuring a Cycle Count Approval Rule (Approval Rule Options) for more details.

Lot Management

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.

Defining Lot (batch) Number Requirement

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.

View Lot (batch) Numbers

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.

Batch Lock Codes

In the Batch Management UI when you apply a lock code to a batch, the Batch Lock Codes are considered for the following:

• inventory with batch tracking items
• relevant batches present on the inventory with a batch lock code
• batches with a lock code removed
• determining the lock code priority and corresponding ERP Buckets to be written in relevant Inventory History Records.

  See Company Parameter – Honor Lock Code Priority for more details.

Note: the system does not consider the batch lock code for non batch-tracked sku's when the inbound LPN or outbound LPN or active inventory is subjected for locking or unlocking.

The following IHT's are affected when inventory with a batch number has a batch lock added or removed:

Inventory History Transaction	Description
IHT 22	Lock Container Before ASN Verification
IHT 23	Lock Container After ASN Verification
IHT 24	Unlock Container Before ASN Verification
IHT 25	Unlock Container After ASN Verification
IHT 49	Lock Active
IHT 50	Unlock Active
IHT 65	Lock OBLPN
IHT 66	Unlock OBLPN

Shipment Verification File

When inventory with multiple lock codes has a batch lock, the shipment verification file has batch lock populated in the inventory_lock_code field and the ERP bucket is populated with the lock code with the highest priority when honor lock code priority parameter is set to Yes.

• When the honor lock code priority parameter is set to No, (inventory with multiple lock codes and batch lock is present), the shipment verification file has batch lock populated in the inventory_lock_code field and the ERP bucket is populated with the ERP Bucket for the Batch lock code.
• Inventory with a Batch lock will have Container Consumed (IHT - 2) and Container Cancelled (IHT-14) IHTs.
• During QC rejection, when the system writes IHT- 74 QC Rejected, if the container has inventory with a batch lock, the lock code field displays with Batch Lock.

Note: The Order Interface allows lock codes from the order detail to be populated onto the inventory attribute if the Treat as Attribute flag is set on the lock code.

Expiration Dates

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 %).

Defining Expiration Dates

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.

Product Life: 30 days

% Acceptable: 60%

This converts to 30 * 0.6 = 18 days acceptable. In this case, the item has to have at least 19 days left until it expires for it to be accepted into the facility.

So if today’s date was 11/24/2014, the system will only allow receipt if the item has an expiration date of at least 12/13/2014 (19 days later).

Configuration for Expiry Date Receiving

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.

Receiving Expiry Date Items in the RF

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”.

Recall Control

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.

Serial Number Tracking

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.

Important Caveats

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.

Enabling Serial Number Tracking

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

Item Master Configuration

The item can have two types of Serial Number configurations:

Item Master Serial Number Configuration
Selection	Description
Not Required.	Item does not track Serial Numbers.
Required, don’t validate.	The receiving RF transaction will NOT prompt for serial numbers when host has interfaced serial numbers to the system.
Required, validate and allow user override.	The receiving RF transaction will prompt for serial numbers regardless of whether or not the serial numbers are interfaced in the system.

To enable Serial Number tracking, complete the following steps:

1. Select the SKU and click Details.
2. In the window, click Edit to begin modifying the SKU’s properties.
3. Scroll down to the ‘require serial number’ field and select and option to enable Serial Number Tracking.
4. Click Save.

Company Parameter Configuration

All companies within the environment that plan on tracking serial numbers must have the company parameter set.

SERIAL_NUMBER_TRACKING_LEVEL
Value	Description
0	Company does not track serial numbers, even if items are configured to do so.
1	From packing: - Prompt Serial Numbers at packing - Track Serial Numbers that are shipped - Serial Number is tied to inventory from Packing
2	End to End: - Track Serial Numbers at all stages, from receiving to shipping - All inbound to outbound transactions prompt for Serial Numbers (if the item is tracking it)

Barcode Type Configuration

Once the item and company parameters are configured, the last step is to make sure that the barcode type for the Serial Number is created. This step configures the barcode length validation for Serial Numbers.

This step is important because without this configuration Serial Number records cannot be created in the company view.

1. Go to the Barcode Type screen.
2. Click Create. Select ‘Serial Number’ under the Barcode Type field.
3. Populate the remaining fields. Length refers to the barcode length required for Serial Numbers.
4. Click Save.

Serial Number Management (UI)

Serial Number Repository View

This screen displays all Serial Numbers for all items in the current facility.

You can also drill down to the serial number record’s details () to view the inventory associated to it:

If the serial number is associated to inventory, the detailed view indicates the LPN’s status (Located, Allocated, Packed, and so on).

Serial Number Inventory View

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).

Serial Number History View

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).

Creating Serial Number records in WMS

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

Through the UI

1. Go to the Serial Number Repository screen.
2. Click Create () and populate the Item and Serial Number.
3. Click “Save” to save your changes.

Through Interfaces

You can also interface Serial Numbers into Oracle WMS Cloud through the “ISN” interface. This is essentially an excel file with a set of columns that are populated to link LPNs with Serial Numbers.

Here is a list of things you need to check before attempting to interface an ISN file:

• The SKU in question must have the Serial Number activated.
• The Company Parameter SERIAL_NUMBER_TRACKING_LEVEL is set to either 1 or 2.
• The ASN (Shipment Number) must already be in the system.
• The ASN (Shipment Number) must have cartonized inventory (the ASN details must have the LPN populated).

Once you verify that all necessary information is in the system, follow these steps to upload your serial numbers:

1. Go to the Input Interfaces screen.
2. Select IB Shipment Serial Nbr from the drop-down, upload the interface file, and click “Run Interface”.

   

3. If everything was done correctly, the system prompts the message “Status: Interface Completed”. From the the Serial Number Repository screen, click OK and verify that the serial numbers were successfully uploaded.

Replenishment

Short description: Replenishment is the movement of inventory from reserve storage locations to picking storage locations. The purpose of replenishment is to maintain adequate inventory levels to meet customer demand.

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.

Repenishment Template Modes

When a location is allocated for replenishment, WMS considers several criteria, depending on the Replenishment Template’s configuration:

• The Locations Min/Max Units (mode = “minimum capacity”)
• The Location’s Min/Max Volume (mode = “percentage of max”)
• The Location’s Item assignment

Additional Configurations Required Based on Replenishment Mode

Minimum Capacity:

Mimimum Capacity mode is triggered when a location’s current quantity goes below the required minimum quantity. Additional configurations:

• Locations with Replenishment Zones require Min/Max Units and/or LPNs populated.
• Locations with Replenishment Zones need to be “Permanent” with an assigned Item.

Reactive:

Reactive Replenishment mode is triggered when you manually scan a location to be replenished. Additional configurations include:

• A “Reactive Replenishment” RF module must be added in the “Screens” tab and to the user’s Menu in the “Menus” screen.

Order Based:

Order Based Replenishment mode is triggered when anOrder’s SKU needs to be replenished in the picking locations. Additional configurations include:

• Requires a Wave Search Template. Create a new search template from the “Replenishment Template” screen.
• Select the desired search template in the replenishment template.

Required Configuration for Replenishment

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

Step 1: Setting up Replenishment and Allocation Zones

Replenishment requires two types of locations: replenishment and allocation zones. Replenishment zones are locations that you replenish to, while allocation zones are locations that you pick from for replenishment.

To Configure the Replenishment Zone:

1. Go to the “Replenishment Zone” screen.
2. Define the different replenishment zones for the warehouse using the Create button.
3. Once the replenishment zones are created, go to the “Locations” screen.
4. Choose a location to replenish to by assigning it a replenishment zone. To do this, select the location and click Edit.
5. Scroll down to the “Replenishment Zone” field and select the appropriate zone from the drop-down.
6. Locations with replenishment zones also require item assignments. Item assignments tell the system what item this location is replenished with. To do so, change the location’s “Item Assignment Type” to “Permanent” and populate the SKU code in the “Item” field.
7. Click “Save”.

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”.

Step 2: Create the Replenishment Template

Next, you need to create the Replenishment template and define the parameter:

1. Go to the “Replenishment Template” screen.
2. Click Create () to create a new template.
3. Fill in the desired parameters.
4. Click Save.

Description of Fields

• Area: Configures WMS to exclusively look at the populated area to replenish to.
• Template Name: Enter the template name.
• Replenishment Zone: Determines which replenishment zones the template searches for.
• Replenishment Rule: Allows you to select which rule to use for the current template.
• Task Creation Template: Allows you to select which task template to use for the current template.
• Replenishment Trigger Mode: Determines the trigger mode (see replenishment modes described in section 5.1).
• Wave Search - Wave Search Templates are used as filters for selecting specific Orders during a wave. Each search template has a set of fields that are configurable.
• Percentage of Max: Triggered when the volume of items in the location goes below the location’s pre-configured percentage of maximum volume. Additional configurations:
  • Locations with Replenishment Zones need the Length, Width, and Height fields populated.
    • Locations with Replenishment Zones require Min/Max Volumes populated.
    • You should populate the “Percentage of Max” field in the replenishment template. This percentage value is used as criteria for triggering a location based on the location’s maximum volume.
      • For example, say that Location A’s Max Volume = 100 and Percentage of Max = 20%. If the location’s total volume goes below 20 (100*0.2 = 20), the location is triggered for replenishment.
• Allow Expired Inventory: If the flag is enabled, the system allows you to replenish inventory that exceeds the expiry date.

Step 3: Setting up Task Templates

1. Go to the “Task Creation Template” screen.
2. Click “Create” () to create a new Task Template.
3. Select this template and click on Details () to view its details.
4. Click “Create” () to create the appropriate task types and their ordering/selection criteria.
   • For LPN replenishment, select “Full LPN Replenishment”.
   • For Cases replenishment, select “Cases Replenishment”.
   • For Units replenishment, select “Consolidate Replenish”.
5. Click Save

Step 4: Setting up Replenishment Rules

Much like the Wave Template’s “Allocation Mode”, the Replenishment Template uses Replenishment Rules to define the types of allocations that are used for replenishment.

1. Go to the “Replenishment Template” screen.
2. Click on the “Replenishment Rule” button to access the rules.
3. Click Create to create a new rule. To access its details, select it and click Details.
4. To create a new allocation UOM, from the Replenishment Rule Sequence screen click Create and populate the appropriate fields.
5. Click Save

Description of Fields

• Replenishment Rule: allows you to select which rule to use for the current template.
• Sequence Nbr: Sequence for creating task types, if there are more than one within the template.
• Location Type: Locations in WMS represent storage locations in the warehouse. Locations have different types depending on how they are used within the warehouse.
• Restrict area: populating this field tells WMS to exclusively look at the populated area to replenish from.
• Restrict alloc zone: populating this field tells WMS to exclusively look at the populated allocation zone (which was defined earlier) to replenish from.
• Allocation Method: defines the order in which LPNs are selected for replenishment.
• Replenishment UOM: defines the UOM that is allocated for replenishment.
  • Note: Units replenishment only works for Active locations.
• Consolidate and Distribute Replen: if this flag is checked, WMS allocates replenishment from multiple locations. This flag only works with Unit and Cases replenishment.
  • Note: Units replenishment only works for Active locations.
• Consolidate and Distribute Replen: if this flag is checked, WMS allocates replenishment from multiple locations. This flag only works with Unit and Cases replenishment.
• Round Up One Uom: The Round Up One UOM flag allows you to replenish beyond the need by one extra UOM (LPNs/cases/packs) for all of the eligible locations. When the Round Up One UOM flag is configured in the Replenishment Rule Header, the system replenishes by one extra UOM compared to the outstanding need of the location (see example below). When the Round Up one UOM flag is combined with the Ignore Capacity for Last Permanent Location Flag, the required need is replenished to the destination location when the replenishment UOM is LPNs/cases/packs. If the Ignore Capacity for Last Permanent Location Flag is set to no and the Round Up one UOM flag is enabled, then the destination location is replenished by one extra UOM when the need is not an integral multiple of the LPN/case/pack quantity.

Step 5: Wave Inquiry

The Wave Group Inquirty screen will show the status of the Wave run. Choose the Allocation View in this screen. Once Allocation completes, the wave will generate a Task. It will also create an internal order.

Executing Replenishment Waves

1. Go to the “Replenishment Template” screen.
2. Select a template and click “Run Template”.
3. WMS returns a message displaying the wave number. This creates a new replenishment Task.
4. Go to the “Execute Task” RF module and select/type in the desired replenishment task.
   • To search for pending Replenishment tasks in the “Tasks” UI screen, click the magnifying glass and filter by the replenishment task type.
     Note: You can also search via the Run Number on the Wave Inquiry screen.
   • To filter by replenishment tasks in the RF, press Ctrl-T and select the Task Type.
5. To verify if the replenish to the location is successful, go to the Active inventory Screen and check the current quantity.

Replenishment Scenarios

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)

Scenario 1: Cases Replenishment, no distribution

For this scenario, you must make sure that both the Task Template and the Replenishment Rule have cases configured.

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.

Note: here the user will be pulling the entire LPN, even if it isn’t fully allocated.

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.

Scenario 2: Full LPN Replenishment, No Distribution

For this scenario, you must make sure that both the Task Template and the Replenishment Rule have LPNs configured.

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.

Cases Replenishment, Consolidate and Distribute (reserve to active)

Consolidate and distribute is the type of replenishment where the user is prompted to batch pick from multiple locations. During this batch pick, the user is to create a ‘dummy’ IBLPN that is used to carry the picked cases. In this sense, the ‘dummy’ LPN is an intermediate LPN use for transporting cases from the picking to replenishment location.

For this scenario, the you must make sure that both the Task Template and the Replenishment Rule have cases configured.

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.

Scenario 4: Units Replenishment, Consolidate and Distribute

Consolidate and distribute is the type of replenishment where you are prompted to batch pick from multiple locations. During this batch pick, you are to create a ‘dummy’ IBLPN that carries the picked cases. In this sense, the ‘dummy’ LPN is an intermediate LPN that transports cases from the picking to the replenishment location.

For this scenario, you must make sure that both the Task Template and the Replenishment Rule have cases configured.

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.

Reactive Replenishment – Weight Capacity Check

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:

Capacity Check Method Option	Definition
Units	Replenishment rule will check capacity in terms units.
Volume, Fall Back to Units	Replenishment rule will first check capacity in terms of volume and if volume is 0, the system will check capacity in terms of units.
Weight, Fall Back to Units	Replenishment rule will first check capacity in terms of weight and if weight is 0, the system will check capacity in terms of units.
Volume, Weight, Fall Back to Units	Replenishment rule will first check capacity in terms of both volume and weight, and if volume or weight is 0, the system will check capacity in terms of units.

Executing Reactive (Emergency) Replenishment

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.

Replenishment with Picking Wave

Oracle WMS Cloud supports replenishment via Picking Waves. Upon performing replenishment, the system recognizes the location to allocate the inventory based on the Replenishment Rule Configured in the Wave Template.

This type of replenishment is called Order Based, as it is making sure that the Orders picked by the wave are getting fulfilled. So, if there is no sufficient inventory in the source location for users to pick and satisfy the order need, the system will replenish those locations. The system first tries to replenish permanent (Locations that have an Item Assignment type field as Permanent), and if there is no enough capacity, then the system will replenish to a dynamic active location.

Note: Replenishment with a picking wave is supported from Reserve to Active and Active to Active only.

Table Supported Location

Location	Lean Time Replenishment	Replenishment with Picking Wave
Permanent Active	Yes	Yes
Dynamic Active	No	Yes
Permanent Reserve	Yes	No
Dynamic Reserve	No	No

Configuration for Picking Wave-based Replenishment

To configure Replenishment to dynamic locations, you’ll need to do the following: :

1. Set up Replenishment Type
2. Set up Replenishment Type to Replenishment Zone
3. Configure the Allocation Location
4. Set up Replenishment Rule in Wave Template
5. Run the Replenishment Wave
6. Execute Allocation tasks to Replenish inventory to active locations.

Set Replenishment Type

The Replenishment Type (Replen-type) is used for finding locations. You should create a replenishment type on the item defined at the company level.

Note: There can be similar replenishment types created across companies. Based on the login context, the system will show the replenishment types by company code.

Before you configure the Replenishment Type on the item facility, you need to define the type.

Define the replenishment type from the Replenishment Type UI > Click Add and enter the details as below:

To configure the Replenishment type on the UI:

Note: You can also interface Item facility to associate replenishment type (replen_type).

1. Go to the Item UI > Click the Warehouse icon.
2. Select the item or Click Add to open the item configuration pane.
3. Select your Replenishment Type from the drop-down menu and click Save.

Replenishment Type to Replenishment Zone

As the system searches the Replenishment Type for the item. You need to establish an association between the replenishment type and the replenishment zone by defining the sequence number.

This configuration is helpful as items classified with similar replenishment type will be assigned to similar locations which do not have permanent items assigned.

Setup Replenishment Zone

Before you configure the replenishment zone in a location, you need to create a replenishment zone and associate it to the active location:

To create Replenishment Zone.

1. Go to the Replenishment Zone UI > Click Add .
2. Enter the Code and Description for the Replenishment Zone.
   
3. Click Save.

Associate Replenishment Zone to the Dynamic Location

1. Go to the Locations UI.
2. Create an active location and associate the Replenishment Zone.

Now, configure your replenishment zone and sequence number in your Item > Warehouse > Replenishment type UI, click Replenishment Type hyperlink and configure your Replenishment Zone.

Configuring Allocation Location

Allocation Modes are used to define how the inventory should be allocated in terms of the different allocation UOMs.

1. In the Wave Template screen > click on the Allocation Mode button. This will route you to the list of Allocation Modes available for the current company.
   Note: Make sure you are at the correct company view before proceeding.
2. Create a new Allocation Mode with the Create button.
3. Enter its details with the Details button .
4. Create the sequence of allocation UOMs desired for the Wave Template.
   

5. Click “Save”.

Note: You need to set the Location type as Active because the Allocation happens only from active and items are picked from the active location.

Replenishment Rule in Wave Template

After defining your replenishment type, you need to define the replenishment rule in the Wave template. Before you configure the allocation location type, you need to the define the replenishment rules.

1. Go to the Replenishment template UI > Replenishment Rules button.
2. Click Add and define the Replenishment Rules.
3. Go to details and define the Allocation Location type, Allocation method, replenishment UOM type, and so on.
4. Click Save.

To perform replenishment with a picking wave, go to the Wave Template UI. Select the Wave Template where you’d like to assign a Replenishment Rule and edit the Replenishment Rule with the Rule of your choice.

Workflow of Replenishment with Picking Wave

When replenishment is run with a picking wave, the system first identifies the order need. After the order need is determined, the system checks if the locations have the inventory. If the selected SKUs are available to satisfy the order need, then the system does not proceed with the replenishment process. However, once the need for replenishment is determined, the system looks for the source location by giving priority to the permanent locations. If the permanent location’s capacity is fulfilled, then the system finds a dynamic location to replenish.

1. You need to configure the Replenishment Type on the item facility and a search sequence by Replenishment type to Replenishment Zone configuration. This provides flexibility to set similar items together while assigning them to dynamic locations.
   1. Define capacity checks to assess how much can be replenished.
   2. On assessing the capacity, the system performs the capacity check based on the configuration you select. You can choose to perform capacity check based on any of the following methods:
   3. Upon assessing the capacity for reserve locations to perform replenishment, the system performs max volume and weight check, max units, and max LPN's check.
2. The Replenishment Rule associated to a wave template indicates the system to search for any replenishment opportunities.
3. On running the wave via a Wave Template, the system creates the replenishment allocation first based on the replenishment rule and then proceeds with the allocation phase.
4. Typically, replenishment with a picking wave will always replenish to locations defined in allocation mode sequences for the wave template. Therefore, its crucial to configure the Allocation Mode in the Wave and define the picking locations. This provides flexibility for users to replenish locations where the picking takes place.
5. After completing the Order selection phase, the system determines the total need required for each distinct SKU based on the Wave Search criteria in the Wave template. Then system calculates the required quantity needed to be replenished after considering the available inventory for each SKU in the locations. The system calculates the available inventory for the location as (In-transit + Current – Allocated).
6. If there is a need to replenish, the system first searches for permanent active locations for the SKU. The source locations of the SKU are fetched based on the replenishment rule and the destination permanent locations will be picked from the allocation mode sequence.
7. If Permanent Active Locations are full, then the system will search for Dynamic Active Locations for the SKU with inventory. Based on the location pick sequence, the available locations will be identified
8. After replenishing SKUs to permanent location is complete and if there are no further outstanding needs, the replenishment for dynamic active locations will be invoked. Replenishment of dynamic active locations will be done until the order need is satisfied.
9. On completing the replenishment phase, as part of the allocation phase, the system will provide the facility to allocate SKUs from In-Transit Inventory to the location. This allocated quantity is from the source location and apart from current quantity.
10. As part of the task creation phase, the system will create replenishment tasks, along with the picking tasks. There will be a single task creation rule for the wave template.

Replenishment via Picking Wave Examples

Scenario 1

• Orders need =150
• Replenishment UOM is units
• Locations have the following capacity

  Table Config-1

  Location	Type	Min	Max	Current Qty	Capacity
  A001	Permanent	20	200	20	180
  A002	Dynamic	20	200	0	200

The system first looks at the Permanent location. Replenishment with Picking Waves is based on order need, so the system will replenish until it meets the order need requirement. In the above case, the max capacity is 200,the Current Qty =20, and the available capacity is 180, and UOM is units

Therefore, after replenishment phase is complete, the system allocates 130 (in-transit) units where the order need of 150 is satisfied (Current + In-transit).

Table Output

Location	Type	Min	Max	Current Qty	In-Transit	Capacity
A001	Permanent	20	200	20	130	50
A002	Dynamic	20	200	0	0	200

Note: When replenishing via a Picking wave, the system only replenishes up to order need and NOT up to the maximum capacity.

Scenario 2

• Orders need =150
• UOM is units
• Locations have the following capacity

  Table Config-2

  Location	Type	Min	Max	Current Qty	Capacity
  A001	Permanent	20	200	120	80
  A002	Dynamic	20	200	0	200

Here, the permanent location has a capacity of 80, and to fulfill the order you only need 30 more units Therefore, the system will replenish up to 30 in location - A001. The system does not consider the Dynamic location as everything can be assigned from the Permanent Location.

Table Output

Location	Type	Min	Max	Current Qty	In-Transit	Capacity
A001	Permanent	20	200	120	30	0
A002	Dynamic	20	200	0	0	200

Scenario 3

• Orders need sums up to be 150
• UOM is units
• Locations have the following capacity

  Table Config-3

  Location	Type	Min	Max	Current Qty	Capacity
  A001	Permanent	20	100	100	0
  A002	Permanent	20	100	100	0
  A003	Dynamic	20	120	50	70
  A004	Dynamic	20	120	80	40
  A005	Dynamic	20	120	80	40

Here, the permanent locations (A001, A002) do not have any capacity in them. Therefore, the system replenishes items to dynamic locations – A003, A004, and A005.

Table Output

Location	Type	Min	Max	Current Qty	In-Transit	Capacity
A001	Permanent	20	100	100	0	0
A002	Permanent	20	100	100	0	0
A003	Dynamic	20	120	50	70	0
A004	Dynamic	20	120	80	40	0
A005	Dynamic	20	120	80	40	0

Multi-Level Replenishment

Formerly in WMS, inventories were replenished to an active location was done based on the location maximum capacity. That is, even when there were inventories available in permanent locations, the system could replenish only up to maximum capacity of units to the active/reserve location. This required the creation of replenishment tasks each time to satisfy order needs which in turn needed manual intervention. In an environment like fast paced seasonal warehouses, there is a demand to introduce a constant flow of replenishment to meet the order supply.

In order to improve efficiency and increase productivity, WMS has introduced a new functionality called Multi-Level Replenishment (MLR) that addresses the following:

• Replenish Inventory beyond configured location max (Supported only through wave-based replenishment).
• Ability to supply inventory in the fulfilment sequence when inventories are depleted in the destination location.
• Capability to combine allocations from different waves templates into a common task.

Workflow of MLR

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).

Note: The workflow contains the following elements:

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.

Configuration Process

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.

Setup

• Location (permanent active location) should be defined. The destination location can be active.
  • Task zones are created for each location. (i.e., locations that are created in the replenishment path (source, drop, and final destination locations) should have Task zone values populated.
    Note: You must create a task zone for this functionality to perform as expected.
• You must first create a Wave Template. These wave templates should have a Replenishment Rule defined.
• Configure the relevant Task Type for replenishment
• Configure the Task Zone Movement and define the movement of inventory from one location to another. Define the Task Zone Movement Rule.
• A new RF Screen Module must be configured to invoke the multi-level replenishment from drop locations.
• Wave Group configuration is required to be configured only if there are multiple orders required for different pick lanes. When you create a wave group, you can combine multiple tasks using the Task Creation Template.

Wave Template

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.

Replenishment Rule

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.

Task Zone Movement

In a multi-level replenishment flow, creating a task zone movement is important because every unique path must have a task zone defined.

Note: For example, you may want to create a task zone movement for the following:

• 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.

Task Zone Movement Rule

Define the task zone rule for every task zone movement by entering the mandatory information in the field as shown in the screen below:

Wave Group

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.

Task Creation Template

Task Templates are used to determine the Task Types that will be used for the wave. Task Types are records that create Tasks based on the UOMs defined in the Allocation Mode.

Note: The Wave Template configuration is said to be successful when the selected Allocation Mode’s UOMs match the Task Template’s Task Types.

Task Creation Template is a set of instructions given to the user to perform tasks to satisfy the need. The task creation template is defined by configuring the following parameter:

1. Create a Task Creation template. Define template. For example, Type > Select Regular.
2. Define the Sequence Number.
3. Define the Task Type in the Task Creation template.

Task Type

When you configure the system for multi-level replenishment, you need to create task types based on the Consolidated Replenishment. This Consolidated Replenishment is required to be created to move inventories from across one drop location to another drop location.

Note: A task type for Full LPN Replenishment is created to pick inventories from a source location to the first drop location.

RF Screen Module

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.

RF Configuration Setup

The following are the set of RF configurations that you need to configure before executing the Multi-Level Replenishment flow:

• Go to the RF Screen UI.
• Set the following RF screen parameters:

Parameters	Description
determine-src-inv-by	Determines the source inventory by Location or task Zone. By Default, the value is set to location.
task-type-description	Enter description that corresponding to valid task type:CONSOL-REPLEN. By default, the field is set to blank.
qty-uom	Set the quantity of inventory in unit of measure of units, packs, and cases. By default, the value is set to Units.
pick-for-single-destination-locn	System prompts only one destination location for which the inventory should be picked from the source location. By default, the value is set to no.
dest-locn-inclusion-criteria	System to determine via the destination location to replenish through the filter criteria. When the flag is set, system considers only locations whose current inventory is <=configured locations minimum when the value is "current<=locn minimum".

Kitting

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.

Note:

• Parent Items are also called Kit Items
• Child Items are also called Component Items
• Ratio of child items required to create a parent item is called pre-pack ratio

Configure Kitting Process

The following steps describe the configuration that needs to be in place for the kitting process. These steps are common for Make To Stock and Make to Order.

1. From the Replenishment Type UI, create a Replenishment Type for kitting.
2. Create a Replenishment Zone for kitting.
3. Tie the Replenishment Type with the Replenishment Zone.

   

4. Parent and child items need to be pre-defined along with the pre-pack ratio.

   

5. Parent items need to have a Replenishment Type defined in the item facility. On the Item UI, select the parent item that needs to be assembled and hit the facility button.

   In Item Facility view for the parent item, add a new record and select the Replenishment Type that was created in step 1.

6. Create an assembly location where the parent items will be assembled. This location needs to be a dynamic active location with the assembly flag checked and with the Replenishment Zone the same as the one created in step 2.
   Note: Since this replenishment zone ( KIT_ZONE) has been tied to the replenishment type ( KIT) and the replenishment type is configured on parent item P1, this would mean that whenever parent item P1 needs to be built, the child items for P1 will always be replenished to assembly location AS111. Similarly, different parent items can be configured to be assembled in different assembly locations.
7. Create a Work Order Type with the Activity Type “Assembly”. This Work Order Type needs to be on Work Orders that are used to assemble parent items.
   Note: Steps 1 through 7 are pre-requisites for both Make to Stock and Make to Order Flow.

Make to Stock Flow

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.

Work Order Creation

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.

Work Order Wave Template

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.

Inventory

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

Wave Run

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.

Task Execution

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:

Kit Assembly

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.

Make to Order Flow

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.

Work Order Creation

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.

Interfaced Order Header and Detail

Interfaced Work Order Detail

The Work Order Type on the Work Order is set based on the Work Order Type which is on the Order Type of the Outbound Order.

The Work Order Kit has a reference to the original Outbound Order Nbr.

Wave Run and Task Execution

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 Assembly

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

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.

Work Order Creation

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.

Wave Run and Task Execution

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.

Task Execution

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.

Dis-Assembling the Kit

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.