Mapping Rule Effective Date Validation Missing After Upgrade to R12

(Doc ID 1265458.1)

Last updated on DECEMBER 10, 2010

Applies to:

Oracle Profitability Manager - Version: 12.0.6 and later   [Release: 12 and later ]
Information in this document applies to any platform.


In Profitability Manager 12.0.6, users can now give locked Mapping Rule versions an End Date that is before the time period for which the rules have been run.  In 11i, users would get a error if they tried to use a bad End Date.  For example, in 11i, a user runs a Mapping Rule for January 2009 and February 2009. For March 2009, they need to change the Mapping Rule so they set an End Date for the first version so they can create a second version.  If they give the first version an End Date of January 31, 2009, they receive the following error at the top the screen:

Effective date range does not include date range for which result data
exists. Result data exists for "v1" in the following date range: 31-JAN-2009
to 28-FEB-2009.

In R12, this error no longer occurs.  If the same scenario described above exists and the user sets an End Date of January 31, 2009, the Mapping Rule version is saved successfully with this date.  The error does not occur.  This can be an issue because, using the example above, it allows users to create a new version of a rule and run it against February 2009 a second time.

Steps to Reproduce:
  1. In 11i, go to the Profitability Manager responsibility
  2. Run a Mapping Rule against two consecutive months of data (ex. Jan & Feb) 
  3. Go to the Mapping Rule version and try to set an End Date that is the last day of the 1st month (ex. Jan 31st)
The error occurs.  You cannot use this date.

Repeat the same steps in R12. You do not get the error.


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