Issue with days of supply

[Former Member]

Hi folks

We are facing an issue with day's of supply.

In our scenario we have a plant 'P' and destination location 'D'.

After the weekly batch Heuristics run the days of supply generated was very high in destination location 'D'.

The problem was resolved when a Heuristic run was performed for issue products.

We checked the product master settings but everything looks fine.

If any one faced similar issue please share with us.

Thank you.

Regards

Jith James

[former_member215376]

Hi, may I know how this issue was resolved?

I think we have the same scenario. Thanks.

Regards,

AA

[former_member189901]

Hii Jith,

Just check which deployment you are using in Source location ( production Plant) .

If it is Push deployment then it may happen that you are  getting Deployed Pur req the way ahead of safety days supply maintained at destination location.

In fact it does not respect the days of supply maintained at destination location, it only checks the ATD quantity available at Plant and then deployed all ATD quantity in the Push deployment horizon.

Regards

Debashis

[former_member187488]

Hello,

It is not easy to explain the result ...

SNP heuristic works to procurement to target stock level. So you can check whether you have any improper supply shortage/safety stock/reorder point calculated at the destination location.

And the problem in batch heuristic run may also come from incorrect low level codes. So you can also check whether LLCs are calculated correctly.

Best Regards,

Ada

[Former Member]

Hi Ada

Thanks for reply.

The issue seems to be with Low level code,but not sure.

We are running temporary low level code with the following selection before Heuristics run.

product = *

location = 'all locations in our system'.

The low level code results for the above selection and when we tried to run low level code with selection as 'whole model' gave different result.

Is it necessary that we should run low level code with selection as 'whole model'??

When I checked SAP help I came to know that SAP recommends to run low level code with whole model before Heuristics run.

Regards

Jith James

[former_member187488]

Hello Jith,

Just for making sure, from where did you see the different result? Temproray LLCs could be seen directly in transaction /sapapo/snpllc, while permanent LLCs (only for whole model) could be seen in transaction /sapapo/rrp_netch.

It is suggested to run LLC determination for the whole model before heuristic run, but you also have other options. In /sapapo/snp01, you can choose from below 3 options:

1) Do not use temporary LLCs - by using this option, you'll need to run permanent LLC determination for the whole model before heuristic run.

2) Process chain propagation - by using this option, you can use the temporary LLCs, which are determined in a previous step in the process chain.

3) Calculate for current selection before planning - LLC calculation will be included in the heuristic planning run, before heuristic starts. This may cause low performance.

Best Regards,

Ada