Optimizer run did not delete Deployment: Release for stk transf. req

Question

Hi Gurus,
I would like to know if the "Deployment: Release for stk transf. req" is also the result of the SNP optimizer run? If not, should this be expected to disappear in the system once the optimizer run is finished because this "Deployment: Release for stk transf. req" still exist in the system even after the optimizer run. Is it normal to have this in the system? If not, what are the factors why this still exist in the system? What are the process on how to delete this?
Your expertise will be very much appreciated.
Thanks

Answer 1

Hi Ann,
              "Deployment: Release for stk transf. req(category EG/EF)" is a deployment order generated by a deployment run and has nothing to SNP optimizer run. SNP optimizer creates planned/purchaser requsitions but does not create/delete deployment orders.
You need to run deployment with a "delete" option to delete and make the system delete the existing deployments and recreate new ones.
Here is the flow.
Lets say you have 1 DC being sourced from 1Plant.
You have a demand of 100PCs.
1. When you run the SNP optimizer, the system looks at the transportation lane, costs etc. Since this is 1 DC 1 Plant, the system just creates a stock transfer order at the plant for 100 PCs.
2. Then you run SNP/PPDS planning run at the plant depending on the SNP planning horizon. Assuming the SNP planning horizon is 0 days (no PPDS run here), the system creates a planned order for the 100PCs (this can be more depending on the lot size).
3. Then you run deployment. The deployment looks at the plant and DC, there is a requirement of 100 PCs and a receipt of 100PCs at the plant.
The system deletes the stock transfer of 100 PCs at the plant and creates a deployment order of 100 PCs at the plant.
A deployment run replaces a stock transfer. But a SNP optimizer run simply creates a planned order at the plant but does not ever change the deployment order.
Hope this answers your question.