Policies Screen Should Show 4 Character Format For Year

(Doc ID 2357585.1)

Last updated on FEBRUARY 05, 2018

Applies to:

Oracle Retail Allocation - Version 15.0.1 and later
Information in this document applies to any platform.

Symptoms

Problem Description
We are facing issues, when users are entering  incorrect year manually and allocation is accepting it and only displaying only last 2 for year.

Steps to Reproduce

1) Create a what if allocation
2) Add release date.
3) Enter locations
4) Click on edit policies.
5) enter data as 01/01/118 and click on apply.

It shows as 01/01/18 when you check the data now as tool is showing only last
2 for the year. But in the backend, alc_rule_date got inserted starting the
year 118.

Users are not aware when they enter invalid date as they can only see 2
digits after they click apply.

Moreover, there should be a limit on what date range, you can enter. It
should not blindly allow 2000 years of history. it should warn users when
clicking apply that you are entering history date range more than 1500 years
and have to re visit them.

The original issue was resolved by setting the Date format under the
Allocation Preferences, to M/d/yy (11/15/17).  

However, customer is suggesting an Enhancement Request to set a limit on what
date range, you can enter. It should not blindly allow 2000 years of history.
it should warn users when clicking apply that you are entering history date
range more than 1500 years.

Changes

 

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