ODSM Create Like Option in OID 11g Returns Attribute orclactivestartdate with UTC Midnight Time (orclactivestartdate=YYYYMMDD000000Z). EBS Provisioning Fails with FND Log Error: OrclActive start date, greater than sysdate / Return false, user is disabled
Last updated on MARCH 08, 2017
Applies to:Oracle Internet Directory - Version 11.1.1 and later
Oracle Applications Technology Stack - Version 11.0.1 and later
Information in this document applies to any platform.
Oracle Directory Services Manager (ODSM) for Oracle Internet Directory (OID) 11g.
All servers and integrated application servers (EBusiness Suite / EBS) have the same hardware and OS, and are in the same timezone and have date and time synchronized correctly.
In OID (ODSM), all users show with correct local time stamp for creation date/time and matching the OS time.
After creating a user in OID with ODSM, it shows the following attributes and values, for example:
orclactivestartdate=20161109000000Z (2016-11-09 00hrs)
createtimestamp=20161109015905Z ( 2016-11-09 01:59)
modifytimestamp=20161109015905Z ( 2016-11-09 01:59)
An ldapsearch output also shows orclActiveStartDate (orclactivestartdate) as 20161109000000Z.
This value is affecting EBS provisioning for the user where, if the start date is greater than sysdate, or end date is less or equal sysdate, it means the user is disabled. So this user record fails with following FND log error:
fnd.plsql.oid.fnd_oid_util.isUserEnabled: Start date in Ebiz time zone:: 2016-11-09 05:30:00 AM
fnd.plsql.oid.fnd_oid_util.isUserEnabled: OrclActive start date, greater than sysdate
fnd.plsql.oid.fnd_oid_util.isUserEnabled: Return false, user is disabled
As EBS checks for current system time and this time is compared with orclactivestartdate, if this condition matches for records created between 00:00 hrs to 05:30hrs, it fails for this user record as above.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms