EPM Cloud Data management / FDMEE / Troubleshooting steps

 

Required Roles for Loading Data

If you have an issue with loading data to Oracle Enterprise Performance Management Cloud using Data Integration, Data Management, EPM Automate or REST APIs, make sure that the user loading the data has one of the following roles:

• Service Administrator predefined role
• Power User predefined role and Run Integration application role

How to trace issues  using ERROR log

• The process details log in data management is the key log to trace any issues
• Ensure the Log level is set to 5 under System Settings tab > select Profile type to ALL
• Open the process details log in Notepad / Notepad++
• Find (Ctrl+F) for the key word "error"

How to determine the load status from DATA LOAD  WORKBENCH

In the Workflow tab > Data load workbench > there are four icons (fish icon) > Import , Validate , Export , Check

If the Import fish is grey, then the import step is failed the source system level 

• Ensure the source system connection is setup correctly 
• Ensure the file name is defined correctly in the data load rule 
• Ensure the data is available in the source combination in which it is extracting 
• Ensure the source filters are defined properly 

If the Import fish is Orange and Validate fish is Grey

• Go the Data load workbench > click on Validation errors 
• You will find the details of the missing mapping members 
• Ensure the mappings are defined correctly for those members and re-run the validate step

If the Import fish is Green, Validate fish is Green but the Export fish is Grey

• Ensure the connection is available and the properties of the target system is defined properly for the target system
• In the error log you will find an error code "Error: 3303", "Error: 3335" - it describes that the member is not available in the target 
• In those scenarios we need to manually create the members in the target system if it valid

Known error codes and solution

3303 Member not found in database.

3304 Insufficient access to store data.

3333 Bad data value supplied.

3335 Record rejected because of duplicate member names.

3336 Member/Data unknown.

3337 Record rejected because of dimension conflicts with Header Name

How to restrict users from viewing load files from other locations in FDMEE

Create two locations in the names (example) "ForlocationA" and "ForlocationB"
Created two new users "USER A" and "USER B"
In Data Management enable "Location security" under Setup > Security settings
Click on "Maintain User groups" with prefix A and suffix K (anything)

Now new groups "A_ForlocationA_K" and A_ForlocationB_K" will be created

Assign those two groups with either Create Integration, Run Integration or any Intermediate roles.

Then in Shared services, assign USER A as a member of Group "A_ForlocationA_K"
Then in Shared services, assign user B as a member of Group "A_ForlocationB_K"

Then grant both the users USERA and USERB with the roles Create Integration, Run Integration roles

Then login to the workspace with userA - navigate to select Inbox and you will be able to see the folder ForlocationA alone
Then login in to the workspace with userB - navigate to select Inbox and you will be able to see the folder ForlocationB alone

You will not be able to see other locations created by other users when that respective user is logged in,