One of your ideas has been delivered from your suggestion.Trigger Item-Driven Cycle Count for Rejected Counts from CC Adjustment UI

When a cycle count (cc) trigger is configured and you “Reject/Recount” cycle count adjustments on the Cycle Count Adjustment Header View (CCAdjustmentHdrView) UI, the system triggers a cycle count task for an entire location. However, for item-driven cc adjustments, this may not be ideal to recount all the SKUs in a location where only a few SKUs are counted and rest are untouched. Therefore, for the locations where item-driven cycle counts are performed, inventory controller may need to manually identify the item-location combination to be counted.

Now, we have enhanced the Cycle Count Adjustment Header View UI, so that you can trigger item-driven cycle count tasks only for the rejected item-driven cc adjustments. When you “Reject/Recount” item-driven cc adjustment records, the system can trigger item-driven cycle count task(s) only for the SKUs associated with the rejected cc adjustment(s). This enhancement ensures that auditors count only relevant items instead of entire location, saving time and resources.

This helps you with the following advantages:

  • Focusing cycle counting efforts on necessary items after an adjustment is rejected, reducing unnecessary workload.
  • Enhancing control and flexibility in managing inventory operations.

NOTE:

This is applicable only for the following types of cc adjustments:

  • Item-driven cc adjustments
  • Location-driven cc adjustments with count mode of “Counted Items only” or “Counted Item Inventory Combination” (i.e., “update-locn-invn-mode” is set to one of these values)

To trigger item-driven cycle count when you “Reject/Recount” cc adjustments, we have added a selection type screen parameter “allow-item-driven-recount” to the module CCAdjustmentHdrView. The behavior of this screen parameter is outlined in the following table:

Screen Parameter Configuration

Behavior

allow-item-driven-recount = Yes

When you “Reject/Recount” cc adjustment(s) on the Cycle Count Adjustment Header View UI, the system prompts to select an item-driven cycle count task type and priority. After selecting the task type and priority, upon confirmation, the system creates item-driven cycle count task(s) for the rejected cc adjustment(s).

NOTE: Both Task type and Priority fields are mandatory.

This is applicable only for the following types of cc adjustment records:

  • Item-driven cc adjustments
  • Location-driven cc adjustments with count mode of “Counted Items only” or “Counted Item Inventory Combination” (i.e., “update-locn-invn-mode” is set to one of these values)

NOTE: On rejecting regular location-driven cc adjustment records, if reject/recount trigger is enabled, the system continues to create location level cycle count task.

allow-item-driven-recount = No or Blank

Default behavior: When you “Reject/Recount” cc adjustment(s) on the Cycle Count Adjustment Header View UI, the system creates a location-driven cycle count task for entire location.

NOTE:

  • The system avoids creating duplicate tasks if an item-driven task already exists for a rejected SKU at the same location.
  • The system creates a single item-driven task for all rejected SKUs under a group header. If multiple item-driven cc adjustment records are rejected together for the same location, the system creates a single item-driven task for all rejected SKUs from the records.

The following table outlines some scenarios of how the system handles rejected cc adjustments when the screen parameter “allow-item-driven-recount” is enabled:

Scenario System Behavior
Rejection of single or multiple item-driven cc adjustments Creates one item-driven cc task per location (as per cc adjustments) for all rejected SKUs
Rejection of location-driven and item-driven cc adjustments together Creates item-driven tasks for specific items and location-driven tasks for location-driven adjustments
Location already has a “CC-LOCN-LPN-CNT” task Cancels existing “CC-LOCN-LPN-CNT” task and triggers a new item-specific task

Steps to Enable

To trigger item-driven cycle count for the rejected cc adjustments, do the following:

  1. Enable the screen parameter “allow-item-driven-recount” on the module CCAdjustmentHdrView.
  2. On the Cycle Count Adjustment Header View UI, reject one or more cc adjustments.
  3. On the select a task type pop-up, select an item-driven cycle count task type and priority.
  4. Click Submit.

The system creates item-driven cycle count task(s) for the rejected cc adjustment(s).