Hello,

Just about to start using Cycle Counting and the following initial questions have cropped up.

1) If we have the parameter "Block Warehouse During Cycle Counting" set at what point are transactions blocked ? Are they blocked from the point that the Cycle Counting Orders are generated and then unblocked when either the orders are processed or deleted ?

2) The INV parameters help screen talks about "Turnover" presumably this relates to the value of individual items but how is this calculated ? Purchase Stats ?

3) In respect of the counting intervals being weekly how does this work if your planned count is delayed by a week. Presumably Cycle Counting orders will still be generated. Also if we wanted to bring a count forward by a day would the system not generate the orders ?

4 ) When a B count is due are orders generated for both A and B items and when a C count is due A,B, and C items ?

Any assistance appreciated.

Cheers
Neal

1) If we have the parameter "Block Warehouse During Cycle Counting" set at what point are transactions blocked ? Are they blocked from the point that the Cycle Counting Orders are generated and then unblocked when either the orders are processed or deleted ?
Exactly.


2) The INV parameters help screen talks about "Turnover" presumably this relates to the value of individual items but how is this calculated ? Purchase Stats ?
You're probably talking about the Slow Moving Analysis? The system takes the annual issue from the inventory history tables.


3) In respect of the counting intervals being weekly how does this work if your planned count is delayed by a week. Presumably Cycle Counting orders will still be generated. Also if we wanted to bring a count forward by a day would the system not generate the orders ?
Cycle counting orders are not generated automatically, unless you don't run a job for it. The system does not generate orders if the interval is shorter than a week. There is a simple check against the value in Maintain Items by Warehouse (Form3) for each item. We had this issue once, when somebody processed the orders accidentally.


4 ) When a B count is due are orders generated for both A and B items and when a C count is due A,B, and C items ?
The system generates orders according to your selection, regadless whether the date is due or not. The only restriction is the shortest possible interval.

Hope this helps. Oh, we don't have ILC implemented, but I think it's basicly the same thing.

Regards,

Martin

Hi Neal,

1) yes, inventory is blocked as from the moment the cycle counting orders are generated and unblocked when either processing or deleting them

2) the turnover is calculated by using the data in table tdinv750 (item issue by period) by applying either the cost price, the sales price or the quantity as the basis for ABC analysis (in tdinv6210m000). In other words, you'll also have to have the INV-parameter 'item issue history' set to 'yes' in order to be able to calculate the turnover

3) no cycle counting orders for item X will be generated if there's still an unprocessed cycle counting order pending for item X

4) when a B-count is due, cycle counting orders are only generated for B-items

Hope this helps.

Frank

Many thanks for the quality info. We'd totally missed the relevance of the analysis sessions.

My company after being live with Baan for 8 years is currently in the middle of a major drive to make more use of the system. So as the man whose been here since day one my head is spinning at the moment. So forgive me if I need to update this thread in the future.

Cheers
Neal

How can you generate cycle counts by ABC Code?

i.e
One Count for all A items every 3 weeks.
One count for all B items once every 3 months
One count for all C item every 6 months.

Anyone do this or simliar counting intervals by ABC class?

after cycle counting, there is difference between Inventory Data & Cycle counting Check report. both figure are different, what may be the reason ?

The inventory is showing in ALLOCATED UNIT , How we find where it is allocated. this is purchase item.