My Oracle Support Banner

Promotion Date Format Inconsistencies and Conversion Errors (Doc ID 2901872.1)

Last updated on OCTOBER 12, 2022

Applies to:

Oracle Retail Pricing Cloud Service - Version 19.1 and later
Information in this document applies to any platform.


On: RPCS 19.1 (RPM 19.1.005)

Actual Behavior
There are some inconsistencies in how the year portion of dates is rendered. Some issues are cosmetic, but others are functional.

Expected Behavior
The expectation is that all aspects of dates can be rendered and managed as "MM/DD/YYYY."


1. The Upload template requires date data in a DD-MON-RR format. This format does not match the UI, and it can lead to ambiguity about years (such as the year 2056, and does not appear to be configurable.
2. The required date format on the Promotion Add Offer screen is m/d/yy, which does not match the
Upload template or promotion results, and does not appear to be configurable.
3. The Promotion Add Offer screen UI will automatically convert dates entered in as m/d/yyyy, but it causes different results than the same date entered in m/d/yy format.
4. The Maintain Promotion (search screen) uses different formats for the search box (m/d/yy) and search results (m/d/yyyy).
5. The Maintain Promotion (results) incorrectly renders the year 2056 as 1956.
6. Maintaining (editing) a promotion with 2056 start and end dates results in unhandled errors while adding a second offer.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.