Allow New or Cancelled LPNs through Cycle Count
Currently, the cycle count supports the detailed counting of LPNs for reserve locations. When conducting a detailed cycle count of a reserve location, you may come across LPNs that are new to the system or have a cancelled status and inventories may be present in the LPN physically. In these cases, you may want the flexibility to scan a new or cancelled LPN for that location.
To improve inventory management, we are expanding the Cycle Count feature to include the ability to scan and count new or cancelled LPNs. This enhancement provides efficient and accurate way to manage inventory, ensuring that all stock, is accurately reflected in the system.
To provide the compatibility to consider new or cancelled LPNs, we have introduced the following screen parameter to the module rf.inbound.cwrfcyclecountlocn.
| Parameter Name | Parameter Type | Module Parameter Choice | Behavior |
|---|---|---|---|
|
allow-new-lpn-scan |
Selection |
Yes |
If the parameter is set to Yes, the system allows auditors to scan a cancelled or a new LPN during cycle counting. |
| No |
If the parameter is set to blank or No, the system does not allow auditors to scan a cancelled or a new LPN during cycle counting. (default behavior) |
After enabling the screen parameter “allow-new-lpn-scan”, you can scan new or cancelled LPNs in both tasking and non-tasking mode (“CC-LOCATION” or “CC-LOCN-BY-ITEM” tasks) to perform cycle count.
After scanning a cancelled or new LPN and accepting the warning message, the system loops you through all the items present in the task detail. You can press CTRL-D End SKU count hotkey to ignore a SKU that is not relevant for the LPN. As you are scanning a new or cancelled item, post completion of cycle count, the system updates the expected quantity as “0”.
Points for Consideration
- For both cancelled and new LPNs, after entering the quantity for each SKU, the system prompts you to recount the inventories.
- The system allows you to scan a cancelled or new LPN when the content-count is on for a reserve location. If not, the system displays an error message while scanning a cancelled or new LPN in the LPN scan mode.
- The system records IHT-53 inventory history transaction for each SKU that you count from a cancelled or new LPN.
- After counting a cancelled or new LPN, the system updates that corresponding LPN to Located status and creates records in the Reserve Inventory (in immediate mode). In deferred counting mode, the LPN will be created only when the corresponding CC adjustment records are approved.
- If a cycle count location has a lock code, the system inherits the lock code to the counted cancelled or new LPNs and the system records the inventory history transaction “IHT-23 - Lock Container - After ASN Verification”.
- During cycle count, you can scan reusable totes associated with a cancelled or new LPNs.
- In the deferred mode, after counting a cancelled or new LPN, the system writes “Cancelled LPN counted” or “New LPN created” message respectively on the Cycle Count Adjustment Header (CCAdjustmentHdrView) and Cycle Count Adjustment Detail warning hyperlinks.
- For a “CC-LOCN-BY-ITEM” task, on scanning a new or cancelled LPN, the system displays a warning message “Scanned LPN is not present in task, proceed?”. You can update this warning message as a hard error to restrict unanticipated LPN scan. For more details on scanning a SKU in reserve location for a “CC-LOCN-BY-ITEM” task, refer Implement Item Driven Cycle Counting for Reserve Locations.
IMPROVEMENTS TO CYCLE COUNT ADJUSTMENT SCREEN
The Cycle Count Adjustment Header screen have options to perform both approval and rejection actions. However, in certain scenarios where you want to implement unique workflows for approval and reject, we are introducing separate group permissions for approval and rejection actions.
This modification provides the flexibility to designate specific individuals or teams responsible for approvals, ensuring that warehouse supervisors and other relevant parties have the appropriate access levels tailored to their roles and responsibilities.
We have modified the existing permission “location / Approve / Reject CC Adjustments” to “location / Approve CC Adjustments” to control the Approve action button only. Also, we have introduced a new group permission “location / Reject or Cancel CC Adjustments” to control Reject and Cancel action buttons. For groups that are already enabled with the previous group permission “location / Approve / Reject CC Adjustments”, the system automatically enables the group permission “location / Approve CC Adjustments”. To control the Reject and Cancel action buttons, you must manually enable the group permission “location / Reject or Cancel CC Adjustments”.
Additionally, users with the "Administrator" role can Approve and Reject Cycle Count adjustments by default. To grant the group permission “location / Reject or Cancel CC Adjustments” to users with other roles, such as "Management", it must be added to their respective groups.
Steps to Enable
The “location / Reject or Cancel CC Adjustments” group permission must be enabled separately from the "Approve/Reject CC Adjustments" permission. Additionally, to grant the group permission “location / Reject or Cancel CC Adjustments” to users with other roles, such as "Management", it must be added to their respective groups.