R12.2: PO: Default Need-By Date Timestamp Defaulting Incorrectly When Manual Input in Core Requisition Form
Last updated on MAY 23, 2015
Applies to:Oracle Purchasing - Version 12.2.4 and later
Information in this document applies to any platform.
Requisition form does not honor the System Profile "PO: Default Need-By Time".
System Profile "PO: Default Need-By Time" is set to 23:00 at the site level, if the date is manually keyed, the time stamp defaults to 00:00.
This is working fine in 12.0.6 environment - the time stamp defaults to 23:00 whether selecting the date from the calendar or manually keying the date.
Also setting the profile at the user level, the behavior is unchanged.
Expecting the Timestamp for Need-By date while creating Requisitions to default in per the System Profile "PO: Default Need-By Time".
Steps to reproduce:
1. Responsibility: Purchasing Super User
2. Navigate to: Requisitions > Requisitions
3. Create a requisition and manually key the need-by date (01/31/2015 for example).
4. Check the timestamp, it was default as 00:00 instead of the defined value in profile "PO: Default Need-By Time".
Upgraded from Release 12.0.6 to 12.2.4.
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