FDMEE Error – Essbase Error(1003007): Data Value [X] Encountered Before All Dimensions Selected, [1] Records Completed


Dimension details in the Target Application screen do not look like what is in Planning.
When setting up a new Data Load Rule, all of the available Plan Types are not showing.
When trying to run a Data Load Rule, the following error occurs: “Essbase Error(1003007): Data Value [X] Encountered Before All Dimensions Selected, [1] Records Completed.”
Mappings are not being applied to all dimensions even though mappings exist.

There are situations where the metadata that FDMEE has stored for a Planning application within PBCS is different from the actual Planning metadata. If changes are made via LCM or simply through the Planning application, it may not be the same as when the application was registered within FDMEE.

Use the following steps to resolve the issue:

  • Before trying anything, you should go into the Target Application screen, choose the Planning application and click the “Refresh Metadata” button and see if the issue is resolved.
  • If there is still an issue, back up all of the artifacts for this target application using LCM so that you have a backup.
  • Go into the Data Load Mappings screen, into each location and export mappings for all dimensions so that you have a backup(s) of your mappings.
  • Go to the Target Application screen, highlight the target application and click the red X to delete the target application.
  • Navigate to another screen within FDMEE, then back to the Target Application screen.  The problem target application should not exist anymore.  Register the Planning application
  • Restore your artifacts in LCM
  • Restore your mappings for each location in the Data Load Mappings screen

Thanks,

~KKT~

Advertisements

Mass Import Security Access into PBCS or EPBCS


How to mass import Security Access in PBCS or EPBCS, for Dimensions, Forms, Form Folders, Business Rules and Task Lists

Overview:
1. Generate your LCM zip file
2. Download the LCM zip file
3. Edit the XML files
4. Re-zip the LCM zip file
5. Upload and import the amended LCM zip

Details:
1. Generate your LCM zip file
Application > Migration
Select Planning link in Categories tab
Select Security only, and export

2. Download the LCM zip file
Application > Migration > Snapshots
Download the snapshot made in step 1

3. Edit the XML files
Users.xml contains all entries for user specific access
Under Groups folder, each <groupname>.xml is specific to that group
Start tag: <acls>
End tag: </acls>
Only use the above start and end tag ONCE in the file. If you start with a blank file, it will ONLY have these two tags in it
Review tables below to add your required access to the .xml file

User Group
Dimension <acl>
<name>user@oracle.com</name>
<objectName>MemberName</objectName>
<objectType>SL_DIMENSION</objectType>
<accessMode>READ</accessMode>
<flag>MEMBER</flag>
<isUser>Y</isUser>
</acl>
<acl>
<name>GroupName</name>
<objectName>MemberName</objectName>
<objectType>SL_DIMENSION</objectType>
<accessMode>READ</accessMode>
<flag>MEMBER</flag>
<isUser>N</isUser>
</acl>
Rule <acl>
<name>user@oracle.com</name>
<objectName>RuleName</objectName>
<objectType>SL_CALCRULE</objectType>
<accessMode>LAUNCH</accessMode>
<flag>MEMBER</flag>
<isUser>Y</isUser>
</acl>
<acl>
<name>GroupName</name>
<objectName>RuleName</objectName>
<objectType>SL_CALCRULE</objectType>
<accessMode>LAUNCH</accessMode>
<flag>MEMBER</flag>
<isUser>N</isUser>
</acl>
Form <acl>
<name>user@oracle.com</name>
<objectName>FormName</objectName>
<objectType>SL_FORM</objectType>
<accessMode>READ</accessMode>
<flag>MEMBER</flag>
<isUser>Y</isUser>
</acl>
<acl>
<name>GroupName</name>
<objectName>FormName</objectName>
<objectType>SL_FORM</objectType>
<accessMode>READ</accessMode>
<flag>MEMBER</flag>
<isUser>N</isUser>
</acl>
Form Folder <acl>
<name>user@oracle.com</name>
<objectName>FolderName</objectName>
<objectType>SL_FORMFOLDER</objectType>
<accessMode>READ</accessMode>
<flag>MEMBER</flag>
<isUser>Y</isUser>
</acl>
<acl>
<name>GroupName</name>
<objectName>FolderName</objectName>
<objectType>SL_FORMFOLDER</objectType>
<accessMode>READ</accessMode>
<flag>MEMBER</flag>
<isUser>N</isUser>
</acl>
Task List <acl>
<name>user@oracle.com</name>
<objectName>TaskName</objectName>
<objectType>SL_TASKLIST</objectType>
<accessMode>READ</accessMode>
<flag>MEMBER</flag>
<isUser>Y</isUser>
</acl>
<acl>
<name>GroupName</name>
<objectName>TaskName</objectName>
<objectType>SL_TASKLIST</objectType>
<accessMode>READ</accessMode>
<flag>MEMBER</flag>
<isUser>N</isUser>
</acl>

Table2

accessMode flag
Dimension – READ
– READWRITE
– NONE
– MEMBER
– @DESCENDANTS
– @IDESCENDANTS
– @CHILDREN
– @ICHILDREN
Rule – LAUNCH
– NONE
MEMBER
Form – READ
– READWRITE
– NONE
MEMBER
Form Folder – READ
– READWRITE
– NONE
MEMBER
Task List – READ*
– WRITE
– READWRITE
– NONE
MEMBER

*Note:
Read=Assign
Write=Manage
ReadWrite=Manage and Assign
None=None

4. Re-zip the LCM zip file
Use 7-Zip or any other zip build tool to re-zip the LCM file after edits are made.
Rename it from the original, to distinct as edited version

5. Upload and import the amended LCM zip
Application > Migration > Snapshots
Select Upload and browse to your new .zip file
Select Gear Icon > Import to import the new .zip file

Thanks,

~KKT~

FDMEE – Unable To See Newly Created PBCS Plan Type When Creating Data Load Rule


After creating new Plan Type in PBCS, it cannot be used in Data Management as a Target a Plan Type. When creating Data Load Rule in Data Management (FDMEE), the Target Plan Type drop down will not show the newly created Plan Type.

Follow the below steps to see the newly created Plan Type under Target Plan Type in Data Management.

– Add a new Cube at Administration > Manage > Cubes
– Refresh Database as usual
– Check that the new cube appears at the Planning Application windows
– Refresh Metadata and Members at Data Management Target Application window
– Click on Save
– Check that the new cube is not shown in the Plans list at Data Load Rule creation

Thanks,

~KKT~

Hyperion Planning: Deploy Option is Disabled for EPMA Application


Deploy option is disabled for EPMA applications

In general, majority of EPMA deploy option grey out issues occurs only when previous deployment failed or diagnostics tests are failed.Issue should be resolved after doing below steps:

1. In EPMA Application Library, right-click on the application and select ‘Run Diagnostics’ – tick all the tests.

2. If that doesn’t work, we can adjust the AWBConfig.properties and reduce the deploy timeout. The default is 8 hours (480), you can change it to 10 minutes.

It’s here:
%MIDDLEWARE_HOME%\EPMSystem11R1\products\Foundation\BPMA\config\Webtier

Restart of EPMA Web is required.

Thanks,

~KKT~