My guess would be a pre & post method tagged to the deletion. The change log gets deleted when the line does as we found out the hard way. LOL
I’ve explored this too and have heard, but not yet tried a technique of using a customization made on a UD table entry app (with its 5 Key fields), made specifically only for this purpose, that can then be used as a base for a query and code that initiates the Refresh Part Quantities and Allocations Process) and then have this parent app scheduled in lieu of the Refresh process that can’t be scheduled. As others have mentioned though, and as we’ve seen too, the system would really have to be completely quiet and without any activities touching inventory or allocations etc. In our environment nearly 7x24, we have no such regular and pristine maintenance window for that. We typically double check a few things on the parts being requested for this refreshing and then run it for just those parts, and even then it is in s risky situation. We’ve had no horror situations so far but the warnings are there for a reason. If we do secure a maintenance window and time permits, I have taken the opportunity to run it wide open, but only when I can be sure I’m the only user of the system - which is rare.
I’m curious, if others on newer versions 10.2.xxx and beyond are better at keeping inventory allocations and Available quantities in synch, as I’ve heard it was improved there. We are heading for a UAT in Dec. with Kinetic so we may get some firsthand experience then.
Just by way of an update. We upgraded to 10.2.700.25 to include the fix that we had identified. After the upgrade completed I ran the Refresh Part Quantities and Allocations process across the whole system to give us a clean slate and so far after three weeks on operating we have had only one part reported and this was an issue that we could explain because the UOM in the job was not correct.
1 Like
Are you referring specifically to issue ERPS-152286 and problem PRB0229878? If not, could you please provide a reference?
Hi Scott apologies I think I must have discussed in a different thread to this one, but the problem request is PRB0236114 included in 10.2.700.24