In my previous blog post FDMEE Map Monitor Reports (Finally!), I demonstrated how to enable this new functionality included in FDMEE patch 11.1.2.4.100. The tutorial listed which Map Type and Action were logged and which were not logged concluding with Bug 22526857 - AIF_ARTIFACT_AUDIT TABLE NOT LOGGING ANY CHANGES FOR EXPLICIT AND MULTI DIMENSION, which was provided by Oracle Support based on an SR opened during the creation of the tutorial.
This tutorial below will review the implementation of Patch Set Exception (PSE) 22506614, which contains three code fixes.
Before we begin, warning: I am an application consultant. However, I do create and install the various EPM products on virtual machines for personal testing and development.
1. Proceed to Oracle Support and download PSE 22506614, which assumes FDMEE Patch Number 20648390 (also known as PSU 11.1.2.4.100) has been installed. (See instructions for installation of PSU 11.1.2.4.100).
2. Prior to starting the patch process, create a backup of the EPM system to which you are applying the patches. Then, to apply the patches on the Windows operating system, stop the FDMEE service and copy the file downloaded from PSE 22506614 to <EPM_ORACLE_HOME>\OPatch, which based on a default install is Oracle\Middleware\EPMSystem11R1, e.g. C:\Oracle\Middleware\EPMSystem11R1 when installed to the C drive.
3. After the file is copied, unzip the file to folder p22506614_111240_Generic.
4. Start a command prompt and then update the path to C:\Oracle\Middleware\EPMSystem11R1\OPatch.
5. At the command prompt, key “opatch.bat apply C:\Oracle\Middleware\EPMSystem11R1\OPatch\p22506614_111240_Generic\22506614 -oh C:\Oracle\Middleware\EPMSystem11R1 -jre c:\Oracle\Middleware\jdk160_35” and then hit enter.
6. After a couple of minutes, the patch should complete successfully, which is indicated by “OPatch succeeded” prior to the command prompt returning.
7. Start the FDMEE service and then proceed to Workspace and Data Management (FDMEE) to test the patches.
Table 1 summarizes the Map Type, the Action (Add or Change), what changed, and whether the change is logged.
TABLE 1
|
Map Type |
Action |
What Changed |
.200 Only |
PSE |
|
Explicit |
Add |
N/A |
Y |
Y |
|
Explicit |
Change |
Source Value |
N |
Y |
|
Explicit |
Change |
Target Value |
N |
Y |
|
Explicit |
Change |
Change Sign |
N |
Y |
|
Explicit |
Change |
Description |
N |
N |
|
Explicit |
Change |
Apply To Rule |
N |
N |
|
Explicit |
Delete |
N/A |
Y |
Y |
|
Between |
Add |
N/A |
Y |
Y |
|
Between |
Change |
Source Value |
Y |
Y |
|
Between |
Change |
Target Value |
Y |
Y |
|
Between |
Change |
Change Sign |
Y |
Y |
|
Between |
Change |
Description |
N |
N |
|
Between |
Change |
Rule Name |
Y |
Y |
|
Between |
Change |
Apply To Rule |
N |
N |
|
Between |
Change |
Script |
Y |
Y |
|
Between |
Delete |
N/A |
Y |
Y |
|
In |
Add |
N/A |
Y |
Y |
|
In |
Change |
Source Value |
Y |
Y |
|
In |
Change |
Target Value |
Y |
Y |
|
In |
Change |
Change Sign |
Y |
Y |
|
In |
Change |
Description |
N |
N |
|
In |
Change |
Rule Name |
Y |
Y |
|
In |
Change |
Apply To Rule |
N |
N |
|
In |
Change |
Script |
Y |
Y |
|
In |
Delete |
N/A |
Y |
Y |
|
Like |
Add |
N/A |
Y |
Y |
|
Like |
Change |
Source Value |
Y |
Y |
|
Like |
Change |
Target Value |
Y |
Y |
|
Like |
Change |
Change Sign |
Y |
Y |
|
Like |
Change |
Description |
N |
N |
|
Like |
Change |
Rule Name |
Y |
Y |
|
Like |
Change |
Apply To Rule |
N |
N |
|
Like |
Change |
Script |
Y |
Y |
|
Like |
Delete |
N/A |
Y |
Y |
|
MultiDimension |
Delete |
N/A |
Y |
Y |
|
MultiDimension |
Add |
N/A |
Y |
Y |
|
MultiDimension |
Change |
Source Value |
N |
N |
|
MultiDimension |
Change |
Target Value |
Y |
Y |
|
MultiDimension |
Change |
Change Sign |
Y |
Y |
|
MultiDimension |
Change |
Description |
N |
N |
|
MultiDimension |
Change |
Rule Name* |
Y |
Y |
|
MultiDimension |
Change |
Condition from Explicit to Between |
N |
N |
|
MultiDimension |
Change |
Source Value |
N |
N |
|
MultiDimension |
Change |
Target Value |
Y |
Y |
|
MultiDimension |
Change |
Change Sign |
Y |
Y |
|
MultiDimension |
Change |
Description |
N |
N |
|
MultiDimension |
Change |
Rule Name* |
Y |
Y |
|
MultiDimension |
Change |
Condition from Explicit to Like |
N |
N |
|
MultiDimension |
Change |
Source Value |
N |
N |
|
MultiDimension |
Change |
Target Value |
Y |
Y |
|
MultiDimension |
Change |
Change Sign |
Y |
Y |
|
MultiDimension |
Change |
Description |
N |
N |
|
MultiDimension |
Change |
Rule Name* |
Y |
Y |
|
MultiDimension |
Change |
Condition from Explicit to In |
N |
N |
|
MultiDimension |
Change |
Source Value |
N |
N |
|
MultiDimension |
Change |
Target Value |
Y |
Y |
|
MultiDimension |
Change |
Change Sign |
Y |
Y |
|
MultiDimension |
Change |
Description |
N |
N |
|
MultiDimension |
Change |
Rule Name* |
Y |
Y |
|
MultiDimension |
Delete |
N/A |
Y |
Y |
|
N/A |
Delete Mappings |
N/A |
Y |
Y |
|
N/A |
Delete All Mappings |
N/A |
Y |
Y** |
*To value is not captured with the From
**Listed as “All mappings deleted by user,” as the maps deleted are not listed on the report
In conclusion, the FDMEE Map Monitor Reports are comparable to FDM Classic for the same map types, with the exception of Description changes not being logged in FDMEE for equivalent map types (Explicit, In, Between, and Like). The new FDMEE map feature of Apply to Rules is not logged consistently for all map types, and the logging of MultiDimension map types does not capture changes to Source Values, Condition, and the previously mentioned Description and Apply to Rules. Also subject to change at Oracle’s discretion, i.e. Safe Harbor, additional Map Monitor functionality may be released in the .200 patch for 11.1.2.4.
