Time Zone Mismatch Causing Requisition Import To Fail (Doc ID 2193135.1)

Last updated on MARCH 21, 2017

Applies to:

Oracle Fusion Self Service Procurement Cloud Service - Version 11.1.10.0.0 to 11.12.1.0.0 [Release 1.0]
Oracle Fusion Self Service Procurement - Version 11.1.11.1.0 to 11.12.1.0.0 [Release 1.0]
Information in this document applies to any platform.

Symptoms

Oracle Cloud Database is set to the GMT Time Zone causing Requisitions Imported in EST Time to Fail when Interfacing Requisitions
from Oracle WAM (external system) to Oracle Cloud.

Requisition with Need By Date as 6/9/16 in the external system. The sysdate is also 6/9/16.
This Requisition gets approved at 11:00 PM EST on 6/9/16 in the external system.
Immediately upon approval, this Requisitions is picked up by the Interface, and imported
into Oracle Cloud.

However the Requisitions fails to get imported with error.

Run the query:


Steps To Reproduce
1. Create a Requisition with Need By Date as 6/9/16 in the external system.
-- The sysdate is also 6/9/16.
2. This Requisition gets approved at 11:00 PM EST on 6/9/16 in the external system.
3. Immediately upon approval, this Requisitions is picked up by Interface, and imported into Oracle Cloud.
4. Requisition fails to get imported with the reported error.

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