Solution : https://service.sap.com/sap/support/notes/538040 (SAP Service marketplace login required)
Summary :
The SAP Note addresses inconsistencies in time zone determination between customers and plants within SAP systems, impacting scheduling functions. Previously, separate modules such, as SD_TZONE_CUSTOBJECT and SD_TZONE_PLANT, were used respective to customers and plants. The note introduces a unified approach using a new module, SD_TZONE ADDRESS, ensuring more consistent time zone application across these entities, using data from address master records prioritized by ZIP code, region, and country details. This change requires updates in Release 4.6B or 4.6C by adjusting the respective program lines as per the instructions provided in the note.
Key words :
sd_tzone_address sd_tzone_plant sd_tzone_custobject tz_location_timezone tzon_location_timezone reason, short text 'determine time zone, exception short text no_timezone, typing reference type if_addrnumber, typing reference type ef_timezone, standardize time zone determination, time zone determinationfunction modules, central function module 'sd_tzone_address', default time zone, time zone defined
Related Notes :
| 1375438 | Globalization Collection Note |
| 892116 | /sapapo/sdrqcr21: Inconsistent edatu in scheduling |
| 814213 | Time zone not taken into account at sales order transfer |
| 729130 | BOP: Performance during update to R/3 |
| 639624 | EXPORT_BUFFER_NO_MEMORY in TZON_CUSTOMIZING_ADDRESS_GET |
| 594334 | R/3 -> APO: Goods issue date not always transferred |
| 578434 | Goods issue date is not transferred to APO |
| 577990 | Performance: SD_TZONE_ADDRESS function module (Part 2) |
| 565258 | Performance: Function module SD_TZONE_ADDRESS |
| 561824 | Converting schedule line dates for R/3 adequately |
| 443500 | R/3 versus APO: Dates in sales orders and deliveries |
| 382746 | Collective note: Delivery+transportation scheduling with APO |