E2B XML Export is Showing incorrect Local Timestamps (Timezone) for Report Output and MESSAGEDATE tag (Doc ID 877203.1)

Last updated on AUGUST 08, 2011

Applies to:

Adverse Event Reporting System - Version: 4.6.0 to 4.6.2 - Release: 4.6 to 4.6
Information in this document applies to any platform.
=================================
***Checked for relevance on 08-AUG-2011***
=================================

Symptoms

AERS 4.6.1 :

issue related to the ICH E2B report.

The system generates an xml with the tag ,<messagedate> which is currently not aligned to the current user timezone and is also different from the system sysdate

Expected Behaviour:
Message date tag data should be in-line with current users timezone data.

Steps To Reproduce:

  1. Configure users local timezone settings e.g. +02:00 (CET - Central European Time)
  2. Run E2B Report in either Draft or Submission mode
  3. Confirm the Report PDF timezone parameters are correctly in users timezone
  4. Note that timezone in the <messagedate> tag is not the same as that for user timezone or the back-end server sysdate.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms