Schedulijg dates not calulated correctly for a specific plant

[vikasmayekar]

Hi All,

We have CRM / GATP / ECC platform.

We have a issue as when we create a Sales Order through CRM or ECC for a particular plant , where the system is not properly calculating the Goods issue date, Loading date based on the Material availability date based on Route.

For e.g. even if the Route is LT01 i.e. one day & for LT05 i.e. five days, system keeps the same date for Goods issue date, Loading date, delivery date . And this is for a specific plant only, for other plants it is properly calculating based on Route i.e. for LT05, it is considering five days.

Please help me in this issue.

Thanks & Regards,

Vikas Mayekar

[former_member209769 · Accepted solution]

Hi Vikas,

Please check if you are using "Transportation and Shipment Scheduling" in GATP. In this case, your dates would get calculated in APO using data from APO and not in R/3.

Go to SPRO-> Advanced Planning and Optimization -> Global Available-to-Promise (Global ATP) -> Transportation and Shipment Scheduling -> Define Condition Table for Scheduling. Select "display condition table" in the pop-up.

See if you get some tables in F4 in the next screen. If yes, most likely, "Transportation and Shipment Scheduling" is active in your system. In this case, you would need to maintain values in /sapcnd/au11. You can display the maintained values using /sapcnd/au13.

Let me know the results of this check.

Hope this helps.

Thanks - Pawan

[vikasmayekar · Accepted solution]

Hi Pawan,

Thanks for the reply, I could see there 12 entries

900 /SAPCND/KOTU900 Del. Prio.

901 /SAPCND/KOTU901 Trans. Grp/Plant/Spd TZone

902 /SAPCND/KOTU902 Plant/Spd TZone

903 /SAPCND/KOTU903 Plant/Dest.Cntry

904 /SAPCND/KOTU904 Trans. Grp/Plant/Dest.Cntry/Spd TZone

905 /SAPCND/KOTU905 Plant/Dest.Cntry/Spd TZone

906 /SAPCND/KOTU906 Plant/Product

907 /SAPCND/KOTU907 Plant/Trans. Grp

908 /SAPCND/KOTU908 Plant

909 /SAPCND/KOTU909 Route

910 /SAPCND/KOTU910 Incoterms

911 /SAPCND/KOTU911 Plant/Dest.Cntry

But I could not access this transaction /sapcnd/au11 or /sapcnd/au13.

Moreover, this issue suddenly happened from 18th December onwards, prior to that it was working fine. That too, this issue is for only one plant, rest of the plants are working fine.

Any other check points we need to check ?

Thanks & Regards,

Vikas

[former_member209769 · Accepted solution]

Hi Vikas,

You would need to check what values are being maintained in /n/sapcnd/au13 (Hope you applied /n in the beginning, otherwise you are missing authorization, and try to get the same from your authorizations team).

In this transaction au13, values for conditions are maintained against the different conditions, e.g. for load, tran, pick, we would specify what values should be used to arrive at the dates. These values should ideally be matching with values in R/3 to avoid confusions.

My guess is that if this plant having issue is a new plant, then setting the values in conditions has been missed, or if it was an old plant, then somehow values are missing (got corrupted in some way, or deleted by someone).

Not able to think in another direction. May be some other expert could give more directions.

PS: I am assuming that you do not have enhancements in GATP. If that is the case, then you would need to check the logic in your enhancements as well to understand how the dates are being arrived at.

Thanks - Pawan