Using FCM/ARM? Find out about managing "Completeness" of ARM Data Loads

(In via Mel)

Have you ever run into issues when doing DRM Data Loads? Are you getting any completeness errors?

You are not alone, Oracle Support is seeing several Service Requests related to the 3 types of completeness errors which are:

  • Missing Profiles
  • Unmapped Accounts
  • Invalid Profiles

MISSING PROFILES

The profile exists with a frequency that matches the frequency of the period (indicating it is supposed to be reconciled this period), and a balance is mapped to the profile, but the Administrator either forgot to copy the profile to the period, or they copied it and then subsequently deleted the reconciliation. We refer to this error as a "Missing Profile" - meaning, the profile is missing from the period. This verification is accessed from the Manage Periods dialog, by selecting the period and clicking the Identify Missing Profiles button:

UNMAPPED ACCOUNTS

Balances exist in the source system, but ERPI/FDMEE does not map these balances to a profile in ARM. These accounts are visible in the FDMEE Data Load Workbench by viewing "Invalid" records. You will also receive a warning for these errors in your Data Load Results dialog,which is accessed from the Manage Periods dialog by selecting the period and clicking the Load Data button:

Once on the Data Load Results dialog, check the contents of the Results column. If you see an "Unmapped Accounts" warning in the results column, that means you have balances in your source system that did not make their way into a reconciliation in ARM, because a mapping rule is missing. You can click the Unmapped Accounts link to see the list, or you can view it from the ERPI/FDMEE Data Load Workbench as noted above.

INVALID PROFILES

Balances exist in the source system, and a mapping rule exists in FDMEE, but the mapping rule is mapping the balance to a profile that doesn't exist in ARM. These accounts will not show up within the FDMEE Data Load Workbench under the Invalid filter, because from FDMEE's perspective, these accounts are properly mapped. The problem is, they are mapped to a profile in ARM that may have existed at one time, but does not exist now. Therefore, you have to look for these errors within ARM. Like the Unmapped Accounts error, the Invalid Profiles error appears on the ARM Data Load Results dialog. Click the link to see the list of accounts affected by the error.  To correct these errors, locate the mapping rule in FDMEE and fix the rule such that it maps the balances to a valid profile in ARM.

If you have any questions on this matter, please reply to the discussion that has been started in the FCM Subspace:

My Oracle Support Community:
Managing "Completeness" of ARM Data

For other FCM questions please start a new discussion in:

My Oracle Support Community
Hyperion Financial Close Management


Comments:

Post a Comment:
Comments are closed for this entry.
About


This blog talks about the latest news and upcoming events initiated by the EPM/BI Proactive Support Team.

Authors:

italia.nowodworska(€)oracle.com
torben.hein(€)oracle.com
paul.anderson(€)oracle.com
julie.foster(€)oracle.com





Search

Archives
« August 2015
SunMonTueWedThuFriSat
      
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
     
Today