PRs getting created illogically during heuristics

[Former Member]

Hi All,

We do heuristics for the 10+ products and 500+locations for the 1 month horizion on daily basis in production environment. The PRs gets created if there is any shortfall at that location.

We are doing the same procedure for last 2+ years.

But recently we are finding indifferent results of heuristics.

The brief details of the issue is as follows:

1. Even though there is no shortfall on a particular day, its creating the PR at that location.

2. But we observed the same combination again after the next days heuristics, the issue wont persists.

3. The same issue we found for another combination. We tested the same in development system, we are unable to replicate it.

But for the most of the combinations the results looks good where as only for random combinations the issue persists.

Note: Shortfall is based on target stock and available stock. Target stock is based on target days of supply.

Please let us know if anybody come acroos this type of issue, if yes, please share us with the solution. Please let us know the what may be the possible reason for this behaviour and let us know if you need any further information. We suspect that some of the master data setting may be causing this issue.

Awaiting for your positive reply.

Advance Thanks & Regards

KPN MUrthy

[former_member187488]

Hello, did you apply any new SP before the issue happens?

This may due to some coding change in SNP scheduling ... Did you notice that whether the created excessive receipts were to cover the shortage in future days?

[Former Member]

Hi Ada,

Thanks for the reply..

We didnt apply any service packs, but we applied few notes for IC groups related. We think that if its the affect of coding it should affect all the combinations,but its affecting only few that too very indifferently.

Yes, it may be it may not be covering the shortage in future days. As per logic it should only create PRs on where the shortfall exists. We maintained rounding profiles, if any shoratage of even 1 also, it leads to create the PRs based on the rounding profile quantity.

Regards

KPN Murthy

[Former Member]

Hi Ada,

Thanks for the reply..

We didnt apply any service packs, but we applied few notes for IC groups related. We think that if its the affect of coding it should affect all the combinations,but its affecting only few that too very indifferently.

Yes, it may be it may not be covering the shortage in future days. As per logic it should only create PRs on where the shortfall exists. We maintained rounding profiles, if any shoratage of even 1 also, it leads to create the PRs based on the rounding profile quantity.

Regards

KPN Murthy

[former_member187488]

Hello KPN,

I cannot be sure where the problem lies since we cannot check your system.

But maybe you can try to follow the below scheduling logic to see whether the system is working fine.

SNP heuristic first create the planned order according to supply shortage, as you already understand. In this process, the system only determine the order's date (according to period factor if you're not using daily bucket). The order's date should corresponds to the supply shortage. Then it goes to SNP scheduling.

1)Set the end time of the distribution receipt to 12:00:00.

   If you're not using daily bucket, the receipt end date is determined by period factor.

   The receipt time should be working time in the receiving calendar of the demand location.

   If the date/time is non-working date/time in the calendar, it re-determines receipt date/time backwards to the receiving calendar.

2)Backward scheduling, on the GI/GR time and transportation duration, to determine the start date/time. GI date/time = GR date/time - GR processing time - transportation duration - GI processing time.

   GR processing time calculation considers receiving calendar of the demand location.

   Transportation duration calculation considers transportation calendar of the transportation lane.

   GI processing time calculation considers shipping calendar of the supply location.

3)If start date/time is not working time, find the most recent date/time (backwards) to be the final start date/time, considering shipping calendar of the supply location.

4)After backward scheduling, if the start time is not at 12:00:00 of  a day, the start time is adjusted backward to 12:00:00. It means, if the start time is later than 12:00, it will be adjusted to 12:00 of that day, otherwise it will be adjusted to 12:00 of previous working day.

  The purpose of this is to make sure the follow-up deployment process could get the correct time for the deployment orders.

5)Forward scheduling from the final start date/time, calculating the final end date/time, following the similar logic like step 2). The result start date/time may be different than 1).

Maybe you can follow this logic by your own.

Just hope this helps.

Best Regards,

Ada

[Former Member]

Hi Ada,

Thanks for the response.

We do heuristics on daily buckets so period factor wont come into picture.

We do consider the planned delivery time, goods issue time, and GR time.

Even though the system creates the PR(Distributin receit planned) in wrong date even though there wont be any shortfall. Even we are unable to replicate this issue. Its happening random combinations and it wont repeat again next day.

Regards

KPN Murthy

[Former Member]

KPN

A few general pointers.

You may check if the system is planning for extra safety stocks because of different safety stock method for recent products calling for more safety stocks !  You can also check the safety stock planning book to verify this.

Also try running the heuristics in regenarative mode if you are running it in netchange now

Check that SNP LLC is complete before the heuristics if you are running Heuristics in dialog mode. LLC ensures that requirements are planned in correct sequence esp. if you are running a network heuristic.

Check that 'Add products in supersession chain' is checked in programs SNP01 and SNP02.

If you are also running deployment heuristics, check the settings wrt SNP stock transfers in SNP02.  i.e. if SNP stock transfers are reduced or not.

Guru.

[dev_shetty]

Hi,

        Please check your past demans like forecast, sales orders, open delivery etc. heurisitc is creating receipts past due in future based on capacity available.

Thanks

Dev

[Former Member]

Hi Dev,

Thanks for the reply. We used to delete the past forecast before heuristics and we used to clear all the open orders frequently. Any how heuristics is for infinite capactiy, right?

Regards

KPN Murthy

[dev_shetty]

Hi KPN,

               You are right if you are using SNP heurisitcs. In your explanation you didn't specifically mention and misread it.

Thanks

Dev