cancel
Showing results for 
Search instead for 
Did you mean: 

Sales order confirmed before supply of components arrive

Former Member
0 Kudos

Hi,

I have an issue to consult on how can I can troubleshoot for the below issue.

1. SO confirmed 4/30

2. But PurReq to purchase part for the build only due 5/3

What factors could caused this? How I can troubleshoot?

Appreciate any advice, thanks.

Accepted Solutions (0)

Answers (3)

Answers (3)

dev_shetty
Active Participant
0 Kudos

Hi Hock,

             Based on your explanation it looks like your sales order has confirmed the availability. I am assuming you confirm all the orders within few days.

The purchase requisition is planned based on the procurement lead times. The purchase requisition due 5/3 is based on the procurement lead times you have defined. Please check your lead times.

Thanks

Dev

babu_kilari4
Active Contributor
0 Kudos

This is something to do with the bucket strategy that has been defined for your ATP group.

Basically - in the ATP tab, if the Scope of check is saying that you are considering the above mentioned reciept element as available supply - then try to see the Bucket. Is it Progressive / Conservative / something else which is making it to be available before it is actually available.

Also, you should check one more thing. What is the setting of Checking Horizon ? Is it configured in a such a way that the Material availability date that falls on or beyond the checking horizon is getting confirmed completely ? If yes, that explains the situation.

Please let us know if it has resolved the problem or give more details to trouble shoot. How about attaching the screenshots while explaining the problem ??

Former Member
0 Kudos

Hi Babu,

Today we have few cases where sales order confirmed before supply arrives. I think it must be something wrong with the setting. Here I attach screenshot of scope of check for your reference.

As for confirmation bucket, it is "progressive".

Appreciate your help, thanks.

babu_kilari4
Active Contributor
0 Kudos

Hi Hock,

Thank you for the screenshot. I see that the configuration looks Ok. However, it looks difficult for me to analyse the issue without the availability view and the MBDAT that has been calculated in the Sales document.


I see that in your scope of check, you have configured the requirements to be confirmed at the end of checking horizon. Could you specify the reason for that ?  Did you know the implications of that. May be you should change it to "E" to be able to confirm the stocks as of today and to the maximum extent of the delay parameter that you'd have defined in your system.

Thank you

Babu Kilari

claire_yang
Contributor
0 Kudos

Hi,

I can see you are using setting "confirm at checking horizon". With this setting, all requirements can be confirmed at the end of the checking horizon. To aviod overconfirmation, you may change to use setting "no checking horizon" or " End check without confirming in the checking horizon"and recheck ATP for the sales order.

Also, changing to use "Conservative" logic can make the order be confirmed at the end of ATP bucket.

Claire

claire_yang
Contributor
0 Kudos

Hi,

You can check ATP for this sales order. 

If ATP is off for this sales order, then any quantity can be confirmed.

If ATP is on, then verify ATP situation (Go into transaction VA02/VA03, click on "Environment" in the meau bar, then click on "availablity"). Also, please check ATP checking scope to verify whether other receipts elements has been involved to confirm the sales order.

Claire

Former Member
0 Kudos

Hi Claire,

Thanks for providing the info. I am SAP newbie, I did based on your suggestion above.

There are 3 tab in scope of check. As in "Receipt' tab, I can see "SNP: PReq" is there but the checkbox beside it is not being checked. What does it implies?

Appreciate your advice if you can provide more tips!

Thanks.

claire_yang
Contributor
0 Kudos

Hi,

That meands  "SNP: PReq" is considered in ATP check.  the checkbox specifies whether the category is relevant for an ATP check on both location and sublocation levels. You can refer F1 help document. You can change your checking scope in transaction /SAPAPO/ATPC04_05.

Claire