Produmex WMS Cycle count reporting (for Lost & Found config)

  • Updated

This article describes some additional reports/queries that can be used for doing analysis based on the Cycle Count processes with Produmex WMS.

 

This article is based on an example:

1. REAL LIFE Stock situation:

BIN

ITEM

QUANTITY

B001

ITEM A00001

60

B002

ITEM A00002

10

B002

ITEM A00001

10

 

2. SYSTEM Stock situation (before count):

BIN

ITEM

QUANTITY

B001

ITEM A00001

70

B002

ITEM A00002

12

 

So notice the differences :

  • ITEM A00001 is on 2 BINS in real life, but not in the system (however, no stock is missing)
  • ITEM A00002 is missing 2 pieces compared to real life

 

3. WMS Counting process:

 

A - Count BIN B001 = 60 PCS of ITEM A00001

CC_1.jpg

Aft this point 10 PCS of ITEM A00001 are MOVED to LOST AND FOUND.

Stock on B001 is corrected to 60 PCS.

 

B - Count BIN B002 = 10 PCS of ITEM A00001 + 10 PCS of ITEM A00002

 

Same process as above but for 10 PCS on B002, and then when on the before last screen, we don’t press STOP but we count then next item :

CC_2.jpg

 

At this point, the system will have ADDED 10 PCS of ITEM A00001 to B002.

To counter this, he needs to book -10 PCS of ITEM A00001 to LOST AND FOUND.

And from counting location B001, there were still 10 PCS there, so we now have not more stock in LOST AND FOUND for ITEM A00001.

 

For item A00002, the system will move the 2 PCS we did not count (from 12 to 10) to LOST AND FOUND.

 

4. Situation after stock counting – before processing

 

Correct stock on B001 and B002 location + 2 PCS in LOST AND FOUND for item A00002:

CC_3.jpg

At this point, we can PROCESS the Cycle count.

 

2. After processing, queries for statistics

 

Query 1: Statistics for the BIN counts: (all counts for today for example)

select * from PMX_CYCO where CreateDateTime > CONVERT(VARCHAR(10),GETDATE(),101)

Result from example:

CC_4.jpg

 

Info for line 1: Counted by user 1 at CreateDateTime – difference -10 on location B001

This is because the system had 70 PCS on the BIN, but we counted only 60 -> so -10 in total for this BIN

 

Info for line 2: Counted by user 1 at CreateDateTime – difference +8 on location B002

This is because the system only had 12 PCS (item A00002) on the BIN, and we counted 10 PCS for this item so we have -2 to start with.

But then we also counted 10 PCS (item A00001) on the BIN, which results in +10 in the difference.

So in total we come to a difference of 8 = -2 + 10

 

 

Query 2: Detailed counting statistics are also available based on the MOVES booked

select * from PMX_INVD where BaseType = 'PMX_CYCO' and DocDate = CONVERT(VARCHAR(10),GETDATE(),101)

Result from example:

CC_5.jpg

I have grouped the info in colour groups so you can easily see the COUNT action (LOST or FOUND) and then COUNTER-BOOKING on LAF location.

 

 

Query 3: Statistics for the ISSUES & RECEIPTS booked by processing:

select * from PMX_INVD where StorLocCode in (
select distinct StorLocLostAndFound from PMX_OSWH where StorLocLostAndFound is not null)
and TransType in ('59','60') and DocDate = CONVERT(VARCHAR(10),GETDATE(),101)

Result from example:

CC_6.jpg

So you can see its TransType 60 (= goods issue) and the quantity is NEGATIVE (= goods issue).

Receipts would also be listed in this query.

 

 

 

 

 

Was this article helpful?

1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.