cancel
Showing results for 
Search instead for 
Did you mean: 

Batch expiry date consideration in aATP

Jayne
Explorer
0 Kudos
564

We are implementing public cloud 2402 with aATP the client wants to be able to consider the expiry date in the determination of the promise date. For example customer A requires at least 300 days remaining life but customer B will take 200 days remaining life. If I have stock with 250 days remaining life I can confirm order for customer B but not customer A. Is there a way of doing this without doing batch determination and assigning a batch in the sales order line (which the customer is not keen on)?

Accepted Solutions (0)

Answers (1)

Answers (1)

Andreas_Krause
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Jayne,

thanks for raising the question and add the small example which makes the requirement understandable. There is no possibility to achieve the behavior without assigning a batch. The ATP check on batch level is supported.

Regards,
Andreas 

Jayne
Explorer
0 Kudos
Thanks for confirming this Andreas, is there anything expected in future releases to make a more flexible solution as only one batch can be assigned to a sales order line
Andreas_Krause
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Jayne,

as of now there is no plan to add a shelf life capability. Feel free to use customer influence portal to create a request and trigger a discussion.

Regards,
Andreas