PJM locator subinventory different from parent subinventory
We have a critical situation where customer shipments are blocked because when putting away, the dynamically created PJM locator was generated in a different parent subinventory. Now, we cannot pick the component as the subinventory and locator do not match. E.g. subinventory is "XXX" but locator is "YYY-235-102-Project-Task".
We have an SR on this with Oracle Support for a patch and a datafix but they are taking too much time to provide the fix. Meanwhile, more and more locators are being generated in this way. Updating the errant locators with the right subinventory in all transaction tables should be sufficient. Only wondering if you have faced a similar situation and have a ready-made datafix that we could test in a non-production instance.