How Late Counts are handled with Cycle Counting functionality

(Doc ID 2213189.1)

Last updated on MARCH 06, 2017

Applies to:

Oracle Inventory Management - Version 12.2.4 and later
Information in this document applies to any platform.

Goal

1. How does Oracle calculate which items to count?

Situation: 4 classes (A,B,C,D) with A classes setup for 4 counts per year, B classes twice, C classes once, and once over two years. You would expect that the counts would be spread out evenly over the year with the A classes counted once a quarter, but we currently do not appear to be on-pace for that. There are currently 9,731 items in this cycle count and counting is performed 5 days a week. Is there any method to determine the correct number of counts based on total items?

2. Count sequence numbers appear to jump. In the two months count sequence has increased from 1 to a sequence of 193178. Is this normal to have such jumps?

3. What affect do late counts have on the adjustments when performed. Situation: late days is set to 5. This appears to show up as the "due date" on the cycle count listing report which can be misleading which leads some end users to take their time with entering the counts. So our question is, how does Oracle account for delayed adjustments?
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms