Backward Scheduling is not working during ATP

[kumararmugam]

Hello

During ATP check the backward scheduling is not confirming the sales order on requested delivery date.

Ex:

There is enough inventory at location to cover the requirement.

Lets assume current date when order is being created as 9/11

If order is created with requested delivery date as 9/11 i.e. current date, system proposes confirmed delivery date 9/15 as below.

MAD = 9/11

PICK/PACK = 1 day = 9/12

LOAD = 1 day = 9/13

TRAN = 2 day = 9/15

So, the latest the order can be confirmed is by 9/15, So if I ask requested delivery date as 9/15 then it should be confirmed on that date. But the system is considering the MAD as 9/15 during backward scheduling and then adding lead time of 4 days in forward scheduling to confirm the order for 9/19.

If requested delivery date is changed to 9/14, then MAD is considered as 9/14 during backward scheduling and then add 4 days lead time in forward scheduling to proposed 9/18 as confirmed delivery date.

goods receiving hours at ship to location are 24/7 so no impact due to it.

We using GATP for transportation and shipment scheduling for sales order.

Regards

Kumar

[kumararmugam]

Seems like its a program bug in FM /SAPAPO/APO_SCHEDULING_CALC

got fixed after implementing the OSS note - 2777002

Thank you All..!

[kumararmugam]

Hello,

Scheduling is done in APO and not in ECC in this scenario.

Condition records are maintained in APO for PICK/LOAD/UNLD. TRAN is determined through T lane between customer Tran zone and Delivery location. screen shot below.

In OLVY dlvry and trans scheduling are activated in ECC even though the scheduling is done in APO. its a production issues and have we have not made any changes to config.

APO_SCHEDULING function module is called and not SD_SCHEDULING to calculate dates based on requested delivery date.

You can see that these condition records are read and used to calculate confirmed delivery date in forward scheduling, but not during backward scheduling. system considered the sequestered delivery date as MAD date and then same MAD date is passed on for forward scheduling.

Looks like system is ignoring the current date and time ( when stock are only receipt elements) as MAD during backward /forward scheduling...! but the system is reading current date and time as MAD when requested delivery date is current date that is correct behavior as we have enough inventory to cover the requirement.

[kumararmugam]

Hello Brahmankar,

Thanks for response.!

Condition records are maintained. No shipping calendar maintained in APO side. Calendar on shipping point on ECC doesn't have any holidays and they work 24/7.

Enclosed Screen shots of schedule lines and scheduling overview.

[rupesh_brahmankar3]

Hello,

Look like route scheduling is not working in gATP.

To determine the other duration (transport planning, picking, loading, unloading), you can use the condition technique. To do this you have to create a condition table for scheduling and an access for the scheduling

In SCM customizing (IMG - SPRO): -> Advanced Planner and Optimizer (APO) -> Global Available-to-Promise (Global ATP Check) -> Transportation and Shipment Scheduling -> Define Condition Table for Scheduling -> Maintain Access for Scheduling and Maintain Control for Scheduling

Check that, delivery and transportation scheduling is activated in transaction OVLY in ECC for your sales order type

Please refer SAP KBA 2221849 - Customizing and process flow of ERP SD scheduling

Best Regards,

R.Brahmankar

[rupesh_brahmankar3]

Hello,

Check Condition technique Transaction code: /SAPCND/AU12 for PICK. TRAN duration.

Does shipping location has a shipping calendar assigned (location master data transaction /SAPAPO/LOC3? Check calendar working days.

Also share the scheduling dates screen shot which appear after gATP check in sales order.

Best Regards,

R.Brahmankar