4/3/2017 12:00:00 AM

Time discrepancy between EWM tables and frontend(UI). EWM Posting Date / Time Inbound Delivery different to ERP Posting Date and Time.

This blogs will gives you about Time discrepancy between EWM tables and frontend(UI) especially daylight savings time

"Most of the United States begins Daylight Saving Time at 2:00 a.m. on the second Sunday in March and reverts to standard time on the first Sunday in November. In the U.S., each time zone switches at a different time. In the European Union, Summer Time begins and ends at 1:00 a.m"

Currently I am working in Europe region and recently I have completed ERP and EWM 9.2 implementation. Recently daylight saving is started and we could see the time difference between ERP and EWM. Let say there is an inbound delivery created in ERP and got replicated in EWM, when we see the date and time in EWM foreground(/n/SCWM/PRDI) and ERP are matching but when I checked in database tables(/SCDL/DB_PROCH_I and /SCDL/DB_PROCI_I) in EWM there is an one hour time difference.

Still there wont be any issues unless until custom programs are using date and time stamp from the tables /SCDL/DB_PROCH_I and /SCDL/DB_PROCI_I.

Latter we could see our time zone in EWM is BST(British Summer Time). This is strange we would have changed to UTC "Coordinated Universal Time (UTC) is the basis for civil time today. This 24-hour time standard is kept using highly precise atomic clocks combined with the Earth's rotation. The Greenwich Meridian in London, England."

EWM stores all time stamp fields in UTC time zone. The time zone field you see in /SCDL/DB_DATE indicates the target time zone in which the date has been stored (in this case this is the information sent by ERP).


When a transaction runs in an ERP system, the following information is always available in the program:

SY-DATUM system date

SY-UZEIT system time

SY-DATLO local date in user's timezone

SY-TIMLO local time in user's timezone

SY-ZONLO user's timezone (e.g. CET)

When you post a material document, some of this information is written into the document header table MKPF:

SY-DATUM is written into MKPF-CPUDT (Document entry date)

SY-UZEIT is written into MKPF-CPUTM (Document entry time)


In addition the local date is written into the 'Posting date'. SY-DATLO is written to MKPF-BUDAT (if no BUDAT was entered manually).

This information refers to system time. For several applications within the standard program it is required to know the exact system date and time when a document has been posted.


There is no way to replace the information in MKPF-CPUTM with the user's time (SY-TIMLO). This would cause problems for other processes.

According to standard system design there is currently no requirement to store the local time (SY-TIMLO) in the document header. This logic can also not be modified via Customizing.

It is also, not possible to display the system date and time of Material Documents in the user's local time. Conversion of date and time into the time configured in the User's account settings is also not possible in SAP Standard. This information, the posting date, is required information in order to derive accounting data, such as the FI period, or the currency conversion rates.

Conclusion:

1) To change time zone BST to UTC - Yes, better option but still problem in past documents.

2) Leave BST as it is and do addiional code in our besboke programs. Below the simple code will help to bring back normal.

Read time zone from FM SCWM/LGNUM_TZONE_READ

and use CONVERT TIME STAMP iv_tst 

                                 TIME ZONE ev_tzone

                                 INTO DATE ev_date

                                 TIME           ev_time.

Below the system fields can used its depends up on our requirement.

SY-DATUM system date

SY-UZEIT system time

SY-DATLO local date in user's timezone

SY-TIMLO local time in user's timezone

SY-ZONLO user's timezone (e.g. CET)


If you like this blog, please share (Facebook/LinkedIn/Google+) to click below links so it will reach to others.


COMMENTS