I am trying to use the periodic transfer of SNP orders. We need this set up, because we run our SNP optimization on demand and need to control the write back of the orders to ECC for multiple reasons.
When the on demand solve runs in the active version, it puts a change pointer in APO to go and delete the old SNP orders from ECC. It also creates a change pointer to go and create the new orders in ECC. The orders are deleted / created in APO immediately. In between the time that the orders are deleted from APO and that deletion is sent to ECC, MRP is run with planning mode = 2, which means re-explode the BOM. The APO planned materials are set up to run through MRP to only re-explode the BOM, to ensure that material requirements for components are passed down, but MRP does not plan the APO materials. When the BOM is re-exploded, a change is captured on the ECC side causing the old order that has not been deleted from ECC yet, to be sent back to APO as a PPDS order. How can I stop this from happening?
This seems like a very fundamental issue. Whenever you use a periodic transfer of SNP orders, your orders are going to be out of sync between APO and ECC. If any MRP run can cause the SNP orders to get recreated as PPDS orders in the SNP horizon, I do not see how you can use the periodic transfer.
Any help / insights is greatly appreciated.
Thanks,
Matthew Bruckner