I had a word with Rohit and he was of great help. We were able to successfully generate Initial Inventory for next bucket from Projected Inventory.
However, we are still looking for a work around for future period where all Kfs which are using Initial Inventory in there calculation are giving wrong results. That is beacause they are considering Initial Inventory as null. Initial Inventory is marked as stored in various Kfs calculation. If we mark it as not stored, we again get into a circular loop.
As of now we are using Copy Operator after every change in data. Can we have some other possible workaround using KF configuartion?
You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
Add a comment