| Description |
In the event something was done on a stroage record that should not have been then by using "reverse" in the history part of the screen, the program should be able to undo the transaction that was done.
Note: this may require storing more information or a transaction key xref, if so let us discuss this so it can be done correctly.
There are 4 types of history reversals I can think of that would possibly be done.
1) internal change done on storage maintenance screen. any updates to inventory must be undone as well related to this.
2) transfers
a) if this was the transfer from, then we would remove the "created" new storage records and have to un do inventory changes also. Note: the target cannot have any history other than being created to allow this.
b) if this was the target side of a transfer, then undo of most lines would be just like type 1 above or other types in this page, but if they reverse the creation line, all other lines must be reversed as well and then the units put back on the original transfer record.
3) if reverse is the "creation" line from external systems (eg scale, inventory shipment or inventory receipt) we must undo the storage updates to inventory and open back up the proper other part. EG: scale ticket must be opened back up or receipt/shipment unposted.
4) for 15.3, storage charges will start to be allowed and calculated as well as discount payments. Those undos will not have "inventory" changes but would create opposing money transactions. This will likely be more like if we should update "in house" in that we should ask if we should create the credit memo or debit memo. We will need to discuss more later.
note: we may need external team tickets, so please help me determine on the items above which ones we need to create tickets for and who they should go to.
This process will cerate the reverse history as well
|