Inventory > ABC Codes > Update Item Assignments

The listsing of items in this form (MTL_ABC_ASSIGNMENTS_V) is arrived as:

select * from mtl_system_items_b

where organization_id = 84
--and cycle_count_enabled_flag = 'Y'
and inventory_item_flag = 'Y'
and STOCK_ENABLED_FLAG = 'Y'
and MTL_TRANSACTIONS_ENABLED_FLAG = 'Y'

Inventory > Counting > Cycle Counting > Cycle Counts (Open a cycle count and then click on items)

The listsing of items in this form (MTL_CYCLE_COUNT_ITEMS_V) is arrived as:

select * from mtl_system_items_b

where organization_id = 84
and cycle_count_enabled_flag = 'Y'
and inventory_item_flag = 'Y'
and STOCK_ENABLED_FLAG = 'Y'
and MTL_TRANSACTIONS_ENABLED_FLAG = 'Y'

The cycle counting process is outlined below:

1. The ABC compile is done to include all the eligible items for ABC classification; as per criteria. However
the items can be directly added with class/classification changed under ABC Assignment Groups.

2. The ABC Assignment Group is associated with Cycle Count which inherits the items classified into
classes like A, B, C.

3. The No. of Counts per Year for a particular class is specified at Cycle Count. (‘4 times per year' does
not necessarily mean that the items will be counted in even increments, such as quarterly., it just means
4 times throughout the year. The objective with Cycle Counting is to ensure that no one knows which
items are going to be counted, this is a near-random process that is generated by the system.)

4. The maximum number of items per class selected for cycle count are calculated as:

Maximum Items to schedule per class = ((Total Items in the class * Counts Per year * No. of working
days in count frequency duration)/(No. of working days in the year))+1

 No. of working days in count frequency duration is calculated as 1 if the Auto Schedule
frequency = Daily and 5 if Weekly (assuming the weekends are non-working days as per the
calendar attached to the cycle count)

5. The Auto Schedule is frequency is specified on Serial, LPN and Schedule tab on the Cycle Count.
The Auto Schedule does not mean that cycle counts will be generated automatically as per the
frequency unless the Perform Full Cycle Count request is scheduled to run with that matching that
frequency. So if the Perform Full Cycle Count request can be manually submitted and the items can be
counted as per the no. of counts per year within the ABC class.

e.g.

Auto Schedule Frequency = Daily

No. of Items in class B = 300

No. of counts per year for class B = 2

No. of working days in the year = 260

If the next date under the Auto Schedule = 2/17/2012, and the Perform Full Cycle Count is manually
submitted on 2/17/2012, then the cycle count is generated for 3 items in class B as:

(300*2*1)/260) + 1 = 3 (the first part of the equation is always rounded and that is why +1 is added)

When the Perform Full Cycle Count completes, it automatically updates the Next date as next calendar
date (2/20/2012) and last date as current date (2/17/2012).

Now since Perform Full Cycle Count is not scheduled to run, it has to be run manually on 2/20/2012. But
if it is not run because of some reasons and then run directly on 2/24/2012, then the cycle count is
generated for 12 items in class B as:

(300*2*5)/260) + 1 = 12
5. Thus system will ensure that each item in the class is scheduled to count at least as many times as no.
of counts per year.

6. Do not reinitialize the cycle count unless the cycle count definition itself is changed. Re-initialize
deletes all and re-loads. Update will update the items. Use update to add/remove items, change the
classification etc.