E1: BSFN: Business Function "N0800640 - Convert String to Date" Cannot Handle 2 Digit Year Format Set in User Profile
(Doc ID 2295054.1)
Last updated on FEBRUARY 06, 2019
Applies to:JD Edwards EnterpriseOne Human Resources Management - Version 9.0 and later
JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
The Named Event Rule (NER) business function N0800640 (Convert String to Date) cannot handle 2 digit year format. The business function N0800640 reads the date format from User Profile. If the user profile is set to a 2 digit year date format like DMY, the N0800640 is not able return the correct date. If the user profile is set to a 4 digit year format like DME, the correct date is returned. The input string passed into the called business function B0800208 (Convert String Date To Date Format) which is called within N0800640 is of a 4 digit year format. However, the Date Format Mask passed into B0800208 is according to the user profile date format and if the format is DMY and the separator is /, the date format mask is passed as ASOSR, but the input string is passed in as DD/MM/YYYY. This results in an incorrect year returned.
Steps to Duplicate:
- Create a custom application which calls N0800640.
- Make sure your testing user profile is set to DMY with date separator '/'
- Test with an input string like "16/03/2017"
- The returned date is incorrect. It returns "16/03/20"
Due to this issue, N0800640 cannot handle 2 digit year format which is set in user profile.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document