SAP APO optimizer SNP not functioning

[former_member1220769]

After running optimizer, the system gives the following warning:

Storage resource STORAGE_0030: Not available or has no available capacity (/SAPAPO/SNPOPT117)

Diagnosis

Storage resource STORAGE_0030 is not available or has no available capacity from bucket 20081020->20081026 to bucket 20101011->20101017.

System Response

The optimizer is forced to use shipments or other activities to empty the warehouse (storage location) until 20081020->20081026.

Resource STORAGE_D020: increase capacity overload is not taken into account (/SAPAPO/SNPOPT045)

Diagnosis

The increase capacity of resource STORAGE_D020 is being loaded with more than its available capacity between bucket 20081020->20081026 and bucket 20101011->20101017 through other infinite planning methods.

System Response

The increase capacity available for the current optimizer planning run is less than zero. The linear problem cannot be solved. Therefore, the optimizer increases the capacity available in these buckets to 0.

The capacity of the resource is set properly (according to us). We have defined capacity of the resource at 60.000 T and the load doesn't exeed this capacity. The resource/buckets have also been defined properly.

Does anybody have an idea what the problem might be? Regards, Peter Hageman

[Former Member]

Hi ,

Try running the report /SAPAPO/CRES_CAPACITY_LENGTHEN for the storage location resources STORAGE_0030.This error might be coming becasue of validity of resource with respect to creation time of the resource.

This report extends the validity of the resource from the day of execution of the report.

You have to schedule this report regularly as the available capacity that reaches into the future and that can be used for planning, gets shorter and shorter as time progresses.

Regards,

Nikhil Nalgirkar

[former_member1220769]

Hello Nikhil,

Thank you for your response. I have executed the report for all storage resources in the system, but still the warning pops-up in the optimizer log.

I have looked at the extended optimizer log (/sapapo/opresult) and also there, there is something strange going on:

for example:

Storage_0040:

planned consumption: 100,110

planned capcity increase: 100,110

costs for extending the resource capacity: 100.110.100,11

The problem here is that the costs for extending resource capacity should be only 100,11.

So it appears that the system multiplies the planned consumption with 1000 and sees that as additional costs for extending the resource capacity. As stated before, the capacity defined in the resource is more then enough, so the penalty system should not be triggered.

Does this make any sense to you? The other message indicates that there is no available capacity in Storage_0040 and then in the cost log it appears that a penalty is payed for the whole planned consumption.

We have already entered a oss call for this issue, but so far the issue has not been solved. I hope via the forum an answer can be found.

[Former Member]

Hi Peter ,

First of all sorry for replying so late because of festive season.

From your optimizer log analysis its not clear where the problem lies.

But to ascertain the storage capacity problem , you can try one thing.Remove the storage capacity as hard constraint in the optimizer profile and also remove the finite planning check box in the storage resource master.Then take the optimizer run with detail logging on.

I know this might sound illogical , but if optimizer is then planning everything properly as it is infinite storage capacity then we can be rest assured that your storage resource definitions are proper.

Then we will have to concentrate on the optimizer settings and the costs that are maintained for the optimizer.

Regards,

Nikhil

[former_member1220769]

solved

[Former Member]

Hello Peter,

Finally how did you solve this issue ?

Thx

MB