Re: [Web-erp-developers] Reverse GRNs of Serialised stock

[Phil D. <ph...@du...>]

> When a Serialised Item has a Reverse GRN processed, here are the options
I've come up with:
>
> Under both ways:
> + all existing code is executed.
> + Additional conditions must be met
> => can only reverse GRN for stock that has not been sold (ie, current
StockMove for item cannot be Invoice type).

Makes sense.

> => item must have been received against the PO we are reversing pieces of

Why do you need to have the PO specified - this is held against the GRN?

> => any conditions a specialised stock module checks
> + Delete records from Item-specific tables (only affects you if you have
specialised stock modules)

You got me here - cant keep up - is this some new functionality module??

>
> then, either:
>
> 1) Change/Invalidate SerialNo in StockItems Records.
> a) Change Serial in All affected StockItem records to something bogus like
'XXXXXXXX' or just ''
> b) Update StockItems w/ new StockMove No. for each.
> c) Create StockItemMove for tracking (StockItemNo, OldStockMoveNo, New/Eff
StockMoveNo)
>

> 2) Delete Item history
> a) Delete records from StockItems
> c) Delete StockItemMoves
>
>

What about
3) Hybrid record reversal and delete stock item
a)  Delete records from StockItems
b) Create StockItemMove of a GRN reversal type for tracking (StockItemNo,
OldStockMoveNo, New/Eff StockMoveNo)

For security purposes we need some record of what happened but there is no
point having the stockitem existing if its gone. Just 2c

> I'm keen on using the second method b/c it creates a lesser chance for
problems in the future if the Items being reversed are actually received
later on. I figure at face value most would balk since I'm deleting, but I
really don't see much point in maintaining these records.

I agree - as long as there is a record of it having existed in the stock
movements.


Phil