TIME ZONE Scheduling Summary
When orders are placed in R/3 for GATP-relevant materials, scheduling dates are calculated incorrectly from a user standpoint and is standard SAP APO/ECC behavior. During backward scheduling, the Goods Issue Date and MAD are scheduled one day earlier than they should be. During forward scheduling, the Requested Delivery Date (confirmed date) is scheduled one day later (or earlier, depending on the time zones involved).
This is caused during the time zone conversion that occurs when R/3 sends schedule dates to APO and receives schedule dates back from APO. R/3 design does not pay attention to time, only dates. The R/3 interface recognizes that APO uses time, and sends time to APO.
The problem occurs when the customer and plant are in different time zones. Depending on the time zones involved, the date will be shifted one day.
The following scenarios describe the specific problems that occur during backward and forward scheduling in different time zone situations.
Note: Order entry time = system time (GMT)
Scenarios
A. Customer Time & Plant Time are behind UTC ----- US
A.1 Customer Time ( ex: MST) is ahead of Plant Time(ex: PST)
Always occurs for Goods Issue Date and MAD.
Dates are shifted 1 day backward (earlier).
EXAMPLE:
Customer in MST (GMT –6)
Plant in PST (GMT –7)
Intransit Time – 2 days
Pick/ Pack Time – 1 days
2. Forward Scheduling +1 day
Only occurs when Order Entry Time is towards end of day, ex: 23:00.
The time of day when this occurs depends on the amount of time difference between customer and plant.
Requested delivery date is pushed 1 day forward.
At other times of day, there is no shift in days.
A2. Customer time (ex: PST) is behind Plant time (ex: EST)
1. Backward Scheduling 0 days
No change in the Scheduling dates.
2. Forward Scheduling -1 day
Only occurs when Order Entry Time is early in the day, ex:01:00.
The time of day when this occurs depends on the amount of time difference between customer and plant.
The requested delivery date is shifted 1 day earlier.
At other times of day, there is no shift in days.
B. Customer Time & Plant Time are ahead of UTC ----- EAMER
B.1 Customer Time (ex: EET) is ahead of Plant Time (ex: CET)
1. Backward Scheduling -1 day
Always occurs for Goods Issue Date and MAD.
Dates are shifted 1 day backward (earlier).
2. Forward Scheduling +1 day
Only occurs when the order entry time is late in the day, ex: 23:00.
The time of day when this occurs depends on the amount of time difference between customer and plant.
The requested delivery date is pushed 1 day forward.
At other times of day, there is no shift in days.
B.2 Customer Time (CET) is behind Plant Time (EET)
1. Backward Scheduling 0 days
No change in Scheduling dates.
2. Forward Scheduling -1 day
Only occurs when the order entry time is early in the day, ex: 01:00.
The time of day when this occurs depends on the amount of time difference between customer and plant.
The requested delivery date is moved 1 day backward.
At other times of day, there is no shift in days.
Examples for each scenario:
DISCLAIMER: Below are some suggested options which WORK FOR THE MOST NUMBER OF SCENARIOS depending on the time zones of your Shipping Point and Customer. There might be few scenarios in which the below suggested options will not work.Thorough testing is required before implementing any solution.
Suggested Options:
OPTION 1: Set time = 12:00 against the customer requested date/time in FM-SD_DELIVERY_DATE_CHECK
OPTION 2: Set Customer Unloading Point-Goods Receiving Hour to make sure that the date does not shift
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |