Wip job exploding the BOM when they are released
We have a customization in WIP which check the wip components quantities and if the quantities of the components are available the request will change the WIP status from Unreleased to Released.
This customizations inserts the records in WIP_job_schedule_interface table from where they are picked up by WIP Mass Load request.
However in some cases when the jobs are in unreleased status users sometimes makes changes in the WIP material requirements for some components. so in this case when we run this custom request it will insert the record in WIP_job_schedule_interface table and this calls WIP Mass load program which releases the WIP job but while doing so it expoldes the BOM and the changes made by the users in the WIP material requirements are no longer there. It then considers the orignal requirements of the components from the BOM rather than the considering the changes made by the user in