Importing Date Only Attribute Does Not Consider User Time Zone Difference (Doc ID 2035985.1)

Last updated on JANUARY 24, 2016

Applies to:

Oracle Agile Product Collaboration - Version 9.3.3.0 to 9.3.4.0 [Release 9.3]
Information in this document applies to any platform.

Symptoms

Actual Behavior
Importing Date attribute will be converted to GMT time zone automatically and does not consider user time zone preference. Even when the user time zone is set to (GMT+09:00) Japan Standard Time (Osaka, Sapporo, Tokyo), import results shows that the date is converted to -9 hours and the imported date is being set to date before.

Expected Behavior
Importing Date attribute will consider user time zone preference

Steps

  1. On Java Client, set a Part subclass with Page Three Date attribute to active. Date Time Format is set to Date only.
  2. Login to Web Client on the user with the following preference:

    Time Zone:(GMT+09:00) Japan Standard Time (Osaka, Sapporo, Tokyo)

  3. Import excel file with the following date attribute.

    Number | Date
    --------------------------------------------
    P00116 | 2015/06/01

  4. Go the Part and check the Date attribute.

    Date is set to 2015/05/31

 

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