Why Data Entered In A Different Timezone Is Time And Dated At The Apps Server Time And Date? (Doc ID 1089219.1)

Last updated on APRIL 02, 2014

Applies to:

Oracle Inventory Management - Version 11.5.10 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
Form:RCVRCERC.FMB - Enter Receipts GUI


Goal

Customer's offshore operation data is stored in the system at the North American date and time when the transaction was created.  When the inventory and Purchasing periods are closed on the last day of the month in their time zone, they can not enter PO receipts on the first day of their new month since the system is still dating those transactions as the last day of the old month as the Data entered in a different timezone is time and dated at the apps server time and date.  How can this be addressed so the first day of the month in the offshore manufacturing operation is not lost?


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