How 2 Digit Year Values Can Be Correctly Interpreted With Algorithm ADHV-DTD-US In CCB, BI And ETM? (Doc ID 780586.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle Utilities Framework - Version: 2.1.0 and later   [Release: 2.1 and later ]
Oracle Utilities Customer Care and Billing - Version: 2.1.0 and later    [Release: 2.1 and later]
Oracle Utilities Business Intelligence - Version: 2.2.0 and later    [Release: 2.2 and later]
Oracle Enterprise Taxation Management - Version: 2.1.5 and later    [Release: 2.1 and later]
Information in this document applies to any platform.

Goal

How can we obtain a correct interpretation of 2 digit year values when using algorithm "ADHV-DTD-US"?

Example:
A Characteristic type is created for the Premise entity. Its allows Adhoc values with Validation
Rule algorithm "ADHV-DTD-US". In the Characteristics page of the Premise, if the input value for this characteristic type has the year entered as 2 digits, for example 02-14-09 (mm-dd-yy) and button Save is clicked, the year is reformatted to 4 digits incorrectly such as 0009-02-14 instead of 2009-02-14.

Solution

	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
Goal
Solution

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

How 2 Digit Year Values Can Be Correctly Interpreted With Algorithm ADHV-DTD-US In CCB, BI And ETM? (Doc ID 780586.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!