Opportunity Effective Date Is Using Sysdate Instead Of Date Specified

(Doc ID 2330957.1)

Last updated on DECEMBER 01, 2017

Applies to:

Oracle Fusion Sales Cloud Service - Version 11.12.1.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.12.1.0.0 version, Opportunities

ACTUAL BEHAVIOR
---------------
Issue closing opportunies by webservice called from PLSQL

Closing opportunities through web service, or PL/SQL, the opportunity effective date is the day when the process run, instead of the date specified





EXPECTED BEHAVIOR
-----------------------
Updating Effective Date via web service or PL/SQL should use the date specified, not today's date.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. In PLSQL, close an opportunity using effectiveDate 2017-05-05
2. Opportunity closed successfully, but checking SUI and BI reporting, the Effective date shows todays date


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use PLSQL to add an accurate Effective Date to the closed opportunity

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