This application is meant to provide a mechanism for backflushing materials. When a higher-level (parent) part is put on hand into inventory the components from the bill of material are removed from inventory at the specified location. This application works with previously established Tulip table structures and is meant to expand upon the functionality that can be utilized for managing inventory within Tulip.
How it works
This application relies on two standard Tulip tables: *BOM and *Inventory. The BOM table must be populated with a list of parent components (ex: Assembly 001) and child components (ex: Child 002). You could upload a CSV with your own bill of material if you'd like. The application will store inventory information into the Inventory table (take a look a the inventory management app for more detail).
When a parent part is created, the application will use the Tulip table API to pull a list of components from the Bill of Material. It will then loop through each item of the list and make the necessary inventory transactions.
In order for this application to function you must set up your Tulip Table API.