Professional Documents
Culture Documents
Cycle Counting
Contents
Introduction to Cycle count
System Reference
User Responsibilities
Ownership
Prerequisites
Steps for ABC Analysis
1 Create a ABC compile
! "enerate ABC descendin# $alue report
% &efine ABC Classes
' &efine ABC Assi#nment "roups
( Associate Classes and Assi#nment "roups
) Assi#n Items to Classes
* Update Item Assi#nment (if required)
+ "enerate ABC Assi#nment Report
C,C-. COU/0I/"
Cycle Countin# &efinin#
1 Scope and Control 0ab
1 Serial and Schedule 0ab
1 Ad2ustment and ABC 0ab
Assi#n ABC Classes to Cycle Count
Cycle Count Items
Cycle Count Scheduler
Perform 3ull Cycle Count
"eneratin# Cycle Count -istin#
.nterin# Actual 4uantities
Appro$in# the ad2ustments
Introduction to Cycle count
Cycle Counting is:
Performed periodically to ensure accuracy of inventory quantities & values.
Frequency of counting item may be based on the classification of items.
1. Example:
o Class items shall be counted ! times a year
o Class " items shall be counted # times a year
o Class C items shall be counted once in a year
method of ta$ing inventory that does not require the inventory organi%ation to
shut do&n in order to count actual inventory items.
System Reference
'racle (nventory: "C Codes
"C Compiles.
"C Classes.
"C ssignment )roups.
(nventory* +ision 'perations ,-./: Counting 0 Cycle Counting > Cycle Counts
User Responsibilities
1he store2s in3charge is responsible for:
.etting up the cycle count parameters and scheduling.
1he store2s person is responsible for:
Printing cycle count requests.
Performing the item counting.
Entering actual item counts.
4esolving inventory discrepancies in the database &ith Finance department.
Ownership
1he 5ead of 6aterial2s 7epartment is responsible for ensuring that this document is
necessary* reflects actual practices and supports company policy.
Prerequisites
(tem classification shall be done ,by finance and material dept/
Frequency of counting shall be decides ,by 6aterial dept/
.ystem setup shall be done ,by 6aterial 8 (1/
Steps for ABC Analysis
1. Creating a "C compile.
2. )enerating "C descending value report.
3. 7efining "C Classes.
4. 7efining "C ssignment )roup.
5. ssociating classes and assignment group.
6. ssigning items to classes.
7. -pdating item assignment.
8. )enerating the "C assignment report.
1 Create a ABC compile
1he "C compile ran$s all the items in your inventory based upon compile criteria. 1his
ran$ing is used to assign classes to your items.
Compile Criterion:
"C analysis is done based on the value of consumptions. "ut initially till next 9 months
from the date of 'racle implementation it &ill be based on .toc$3in3hand value. 6oving
ahead it &ill be shifted to Consumption base.
Current on3hand
quantity
-se the current on3hand quantity of inventory. ssign the sequence number by
descending quantity.
Current on3hand
value
-se the current on3hand quantity of inventory times the cost for the cost type. ssign
the sequence number by descending value.
5istorical usage
value
-se the historical usage value ,transaction history/. 1his is the sum of the transaction
quantities times the unit cost of the transactions for the time period you specify. ssign
the sequence number by descending value.
5istorical usage
quantity
-se the historical usage quantity ,transaction history/ for the time period you specify.
ssign the sequence number by descending quantity.
5istorical number of
transactions
-se the historical number of transactions ,transaction history/ for the time period you
specify.
ssign the sequence number by descending number of transactions.
Forecasted usage
value
-se the forecasted usage value based on the forecast quantity calculated and the cost
type you specify. ssign the sequence number by descending value.
Forecasted usage
quantity
-se the forecasted usage quantity. ssign the sequence number by descending
quantity.
Previous cycle count
ad:ustment quantity
-se the previous cycle count ad:ustment quantity. 'racle (nventory sums the value of
all cycle count ad:ustments since the last "C compile date. ssign the sequence
number by descending quantity.
Previous cycle count
ad:ustment value
-se the previous cycle count ad:ustment transaction value. 'racle (nventory sums the
value of all cycle count ad:ustments since the last "C compile date. ssign the
sequence number by descending value.
64P demand usage
quantity
-se the 64P demand usage quantity. 'racle (nventory sums the 64P gross
requirements for the 64P plan you specify. ssign the sequence number by
descending quantity.
64P demand usage
value
-se the 64P demand usage value. 'racle (nventory sums the 64P gross
requirements for the 64P plan you specify. 1he value is derived from the item cost
type you choose in the "C compile form. ssign the sequence number by descending
value.
;ogin to 'racle.
.elect <(nventory* +ision 'perations ,-./=
.elect <"C C'6P(;E=.
.elect M1 organi%ation
.elect New button on the form.
Complete <7efine "C Compile= form.
Enter a -nique name for "C compile.
'ptionally* enter a description of the "C compile.
Content .cope
o (f you select <Organization= ran$ing &ill be done for all the items defined for your
current organi%ation even those &ith %ero cost and %ero quantity.
o (f you select <Subinventory < ran$ing &ill be done for all those items for &hich
you have defined an (tem8 .ubinventory relationship. (n this case you can also
select specific subinventory defined in system.
+aluation .cope
o 4an$ing must be done at the organi%ation level if you did not select a
.ubinventory in the Content .cope field. (f you only &ant to include items in a
subinventory but you &ant the ran$ing to be done based on the organi%ation &ide
ran$ing* select <'rgani%ation=.
o (f you select <.ubinventory= than only those quantities &hich are lying in specified
subinventory &ill be considered. >uantities lying in other then specified
subinventory &ill not be considered.
Compile Specification
Criterion
Cost ype defaulted as per setup* !orecast depends on criterion* i.e. if forecast*
must select forecast* "lan Name# !rom $ate and o $ate are required for some
specific criterion.
.ave your &or$
Execute the Compile
o Clic$ the compile button and then a concurrent program &ill get fired.
(f needed compile results can be printed
'pen output of ?Compile "C analysis2 to vie& Compile 4esult
+erify that compile "C analysis is completed &ith a status of @ormal.
@ote: s this is in test system &e got only AB! items in this compile but in actual &e &ould be
much more.
! "enerate ABC descendin# $alue report
.elect the "C descending value report.
Clic$ the vie& output button to vie& output.
1a$e Print if required.
% &e'ne ABC Classes
-se your o&n terminology to determine &hat are commonly used as "C classes.
7efine class names that suit your business environment.
@avigation: (nventory* +ision 'perations ,-./ 0 "C Codes 0 "C Classes
Enter Class @ames and description
.ave your &or$
( &e'ne ABC Assi#nment "roups
"C assignment groups associate "C classes &ith an "C compile. Cou assign item
to "C classes &ithin a particular group. 1his allo&s you to assign items to different "C
classes in different group.
For example* suppose you define "C groups <Cycle Counting= and <Planning=. Cou can
define different "C classes to these t&o groups. Cou can then assign an item to a
different "C class in each group. 1his allo&s you to prioriti%e item differently for Cycle
Counting and Planning.
@avigation:
(nventory* +ision 'perations ,-./: "C Codes 0 "C ssignment )roups
Complete the %&C %ssignment 'roups form. 'n a blan$ line fill the follo&ing
information.
Enter a unique "C group name.
ssociate Compile @ame and save
) Associate Classes and Assi#nment "roups
Choose classes to use &ith assignment group
ssign ran$ing to the classes &ithin an assignment group.
"C )roup Class ssignment
.elect your assignment group from the list. Clic$ the 'roup Class button.
%&C 'roup Class %ssignment &indo& &ill get open.
Complete the %&C 'roup Class %ssignment form.
Priority: Enter the sequence number in &hich classes are ordered. @umber <1= is
the most important* number <#= is second* and so for.
.elect the class names you defined.