Skip to Content
avatar image
Former Member

ProductionDateService PAPI confusion on Timestamps/Timezones


we are currently trying to utilize the ProductionDateService: findProductionShiftsForDate PAPI to fetch the current Shift,

however there is some confusion with the Timestamps we get back as a result.

We have a Production Shift configured which starts 06:00 in the morning and ends 16:30 in the afternoon.

System and Site Timezone is set to Los Angeles.

Now if we call the PAPI with the Parameter 6:00:00 AM and America/Los_Angeles,

it returns the correct shift, but the Timestamps returned are the following:



The Time Offset of -7 between GMT and PDT is correct, however the timestamps are off by 3hours.

Could somebody elaborate where this behavior comes from?

For me it looks like a problem when actually storing the Production Shifts.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    May 29, 2015 at 10:13 AM

    Hello Christian,

    What are your values in the database in production_shift and production_date tables?



    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 03, 2015 at 01:00 PM

    Well the note states it is applicable for ME 5.2, we are utilizing ME 15.

    In the meantime we found out that everything we looked at in the Database is stored as GMT time, the only item which seems to differ are the entries in Production_Date table which seem to be stored in the system timezone (in our case currently EDT).

    So is it still a necessity to set the System time on the Database-Server to GMT? Seems a bit off, as apparently the rest of the system is handling it quite happily.



    Add comment
    10|10000 characters needed characters exceeded

    • Database setup is the same since 5.2. So, GMT is recommended for ME 15.0 too.

      As to the date/time for PRODUCTION_DATE table, it seems to be created by Production Calendar JSP - so it looks as if the offset is taken from the client's system where IE is accessing SAP ME. Actually, it seems quite logical because Production Shift Maintenance display shift's Start and End time for the local site - so it needs to be offset to GMT when written to the database where it is expected to be stored in GMT.