At present Transaction RSP is being saved at Sale Level but not for other transaction which makes it difficult for USER to know if for some reason the RSP of the product gets changed later on. In our case since the items are repetitive, the RSP of the products gets changed sometime and in that case if one or more store have those items in closing stock, then the closing stock value will not match with the books of account as the value to the extent of increase in the price remains unaccounted.
For e.g.
- RSP of item A is Rs.100/-, we send 50 pcs of item A to store X on 01.04.2015 so account of X debited with Rs. 5000/-.
- on 15.07.2015 the price of item A becomes 125/- and till then Store X have sold 10 pcs of item A n made pay of Rs.1000/-
- Since the price of item A in software has become 125 revised barcode send to store X for the stock in hand at the time of change of RSP.
- during 16.07.2015 to 31.03.2016 Store X sold another 30 pcs of item A at Rs. 125 and paid the Rs.3750/-
- stock in hand of item A with Store X 10 pcs @Rs. 125/- i.e. 1250/- so logically the balance of Store X should be Rs. 1250/- debit however it will be showing (5000-1000-3750) Rs. 250/- so a debit note of Rs. 1000/- (40*25) would be required to be passed in the books of X.
- for calculating this entire thing, user would need Transaction RSP Value and present RSP value for each transaction and it he/she gets it the calculation would be very simple.
So we should store Transaction level RSP for each of the transaction along with rate to facilitate preparation of the above required report in OLAP.
Sushil Agarwal
