cancel
Showing results for 
Search instead for 
Did you mean: 

ATP as background job?

Former Member
0 Kudos

Hi everyone,

ATP is being a real struggle for us and we are for a required balance of not missing out on deadlines and improving the service levels if possible within the constraints. For a product not in stock it or available at a later date, the MAD comes in perfectly on the basis of the RLT or in house production time set up. It gives it's correct dates and are communicated - the system proposes the MAD, loading date etc on the basis of which the shipping personnel run the VL10C.

However, if, in a day or two (before the proposed delivery creation date), for any reason, we re-schedule a batch earlier or get returns for non quality reasons, the dates remain as they were (which of course, is the way it should be considering they were promised that way) but now, we are in a position to ship the goods out earlier. However, the shippers won't see it in VL10C as they would run it for their usual parameters.

How can we get around this? Assuming a big range of products and hundreds of orders a day, it isn't feasible to do a CO06 individually. Is there any way to re-run the ATP in the background or something and it's report gives us the changes the system made, the new proposed dates etc?

Or any other suggestions to handle these situations?

Appreciate any help or guidance for any more research or answers...

Many thanks.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

You can write a BDC program to open that order with the transaction VA02 and click the avaialbility check button once again. Based on that the availability check program will fire once again. You can run this BDC program as a background job!!!!!!!

If it helps give me points na!!!!!!!!!!!!!!

Chandra

Answers (0)