Transaction Date Issue Caused By Time Difference

(Doc ID 2271218.1)

Last updated on AUGUST 23, 2017

Applies to:

Oracle Fusion Cost Management - Version 11.1.11.1.0 and later
Oracle Fusion Cost Management Cloud Service - Version 11.1.11.1.0 and later
Information in this document applies to any platform.

Goal

Transaction date issue caused by time difference with period end reconciliation due to time difference between server and client location.

Example:
Transaction entered on 31st March 2017 the server will record the transaction in UTC which is 7 hours ahead.  Because of the time difference transactions are getting posted on April 1st 2017 instead of March 31st 2017.
This transaction will be considered only for April costing period.  Inventory manufacturing and costing transactions are time stamped with reference to server time which is UTC. 
 

Solution

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