My Oracle Support Banner

E2B REPORT Fails-Messagedate Timezone Mismatch (Doc ID 1063292.1)

Last updated on MARCH 08, 2017

Applies to:

Adverse Event Reporting System - Version: 4.6.0 and later   [Release: 4.6 and later ]
Information in this document applies to any platform.

Symptoms


In AERS 4.6.1 , Global Maintenance->System parameters On changing E2B_DEST_TZ to " IST"  to get   E2B report  tag <messagedate> ,  aligned to the current user timezone (Indian Standard Time) the E2B report fails.
The same reports completes with value "CET" or "PST"

Expected Behaviour:
Message date tag data should be in-line with current users timezone data.
Timezone is Indian standard Time

Steps To Reproduce:


Configure users local timezone settings e.g. +5:30
Configure E2B_DEST_TZ to IST (Indian standard Time)
Run E2B Report in either Draft or Submission mode
 


Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
  Symptoms
  Cause
  Solution
  References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.