Happy Friday -
Okay - Soliciting Feedback -
In GP Manufacturing........FIFO Perpetual Inventory Valuation
Create MO
Build Pick List
Issue Raw Materials (Component Transaction Entry) (decrease item quantities from stock by issuing to WIP)
-----GL and Inventory Transactions are created with the system date. everything is great. Go to item Stock Inquiry - transaction is last record, etc...........
Reverse Issue Raw Materials - This is the process of reversing the material issue process (Component Transaction Entry) (Take from WIP and put back into Stock)
----GL Transaction (created with the system date)
----Inventory Transaction is created - the document (high level) has a date - today's system date - but the individual items have different dates depending totally on where the 'stack' was dated that the original receipt quantity used.........go to item stock inquiry (expect to see the 'return to stock transaction as last record).....can't easily find the record...............
In other words -
Issue Materials on April 1st - everything says April 1st
Reverse Issue - the individual items will be put back into inventory based upon the date of the receipt in IV10200 table - not based on today's date........(April 1st) - some will be in March, others in February - maybe even prior year.......every item has a different date....
This can easily be seen by looking at the Item Stock Inquiry Screen - the end user (in my case) happens to use that screen to 'verify' something came out of inventory or was put properly back into inventory.......when the end user performs the reverse issue transaction the 'receipt' back in is not the last record in the screen - the end user will see the out transaction (material issue) and will not see the put back in (reverse issue transaction) in some cases the put back in is dated prior year....etc.
At first glance - I was very concerned about tying out Inventory to GL and the ramifications - about the system updating IV30300 table with something other than current date) but after reviewing the SEE30303 Table - everything is fine........the two SEE30303 records are dated today - thus if HITB is used - no worries.
My question is - Is this a 'bug' or in the community's opinion an acceptable functionality of GP Manufacturing?
Hope I described situation well enough to solicit feedback..........
*This post is locked for comments