SNP Optimizer issue - plans incorrectly, discrepency between the logs and planning book and reads incorrect master data

[Former Member]

Hi Experts

We are running into some serious optimizer issues:

a. The optimizer is planning huge planned orders and does not correlates with the demand. We are doing fixed lotsize and discrete optimization. Planning horizon is for 2 years. SAP recommended to upgrade the Optimizer version which we already did but the issue remains the same. The upgrade patch from 5.1  to 7.2  did not help at all. Currently we are on 7.02_REL SP00.

b. Optimizer not reading transportation lanes and PDS's - In the message log the transportation lanes are read as 0 and also the PDS's are not read correctly. For example, if we have only 2 PDS's in the system, the optimizer log reads as 4 PDS's. Checked all the master data and it looks fine. The transportation lanes do exist and the PDS's carry valid production data. Some of the items from the selection does not have PDS data in the system but optimizer is reading PDS data in the input log. ET_PROMAT contains PDS data for the products were PDS's are not been maintained. Reaching out to the SAP, received some notes such as 1575726 ,1352214, 1638592. Not sure if these notes are valid to resolve this issue.

c. Also the production Qty in the table IT_PROMO does not match the Qty from the planning book for the same weekly buckets. There is a descrepency between the logs and the planning book.

If anyone who had have experieced such strange issues. Please share your valuable inputs.

Thanks

Abdus

[Former Member]

Hi Abdus,

a) Please check the production storage cost at plant location , if it lower than anyother location in network optimizer keep high stock at plant location instead of push to lower location.

b) RUn the consistency chak for PDS and TL and run the optimizer ,and also check trace file if issue not get resloved in that case SAP can help you.

c) we have faced similar issue where SAP suggest optimzer patch for this.

Regards,

Mangesh

[Former Member]

Hi Mangesh

Appreciate your feedback!

The notes did help to read the PDS data correctly. Also one of the basic root cause for not planning correctly besides patch update and implementing notes was that the penalty cost, maximum delay and ND penalty global and location dependent was not maintained for some codes and for some it was maintained incorrectly. The production storage cost model is correct where plants carry highest cost, PDC's carry second high and SDC's do the lowest. Now the planning results make complete sense. I am in the process of testing chunk of items as selection and running in background and foreground to ensure there are no more other issues and implications.

Thanks

Abdus