Data is not getting Saved for a Member in Data form

Can't Save Data for a Member in Planning Data Form

With Essbase implied sharing, some members are shared even if you do not explicitly set them as shared. These members are implied shared members. When an implied share relationship is created, each implied member assumes the other member’s value. Essbase assumes (or implies) a shared member relationship in these two situations:

1. When a parent is having single child

2. When parent is having single child and it is consolidates to the parent

In a Planning form that contains members with an implied sharing relationship, when a value is added for the parent, the child assumes the same value after the form is saved. Likewise, if a value is added for the child, the parent usually assumes the same value after a form is saved.For example, when a calculation script or load rule populates an implied share member, the other implied share member assumes the value of the member populated by the calculation script or load rule. The last value calculated or imported takes precedence. The result is the same whether you refer to the parent or the child as a variable in a calculation script.

Now the issue which we are going to talk about is We loose data on save even when the parent is dynamic calc and has a single child.

A dynamic calc parent to a single child:

If we design the form with following selection shown in below screen shot:

In the planning data form we will find parent is below the member and this is by design whenever you make a selection using commands to select all member below parent

Lets enter the data in the data form

Save the data

Our data wiped out.

Now, we will change the selection of member while creating a data form

Here we go, data saved.

Now the question again why this behavior:

Data from Planning data form passes to Essbase row by row, because in data form the child member appears before the parent. First, data goes to Essbase for child (Single Store Child), then when Planning passes the data for parent there was #Missing or No data, Over writes the data to #missing.

Note : As we know that dynamic calc members are calculated on the fly they are not allocated with any memory in the Essbase, here the parent was dynamic calc and it was pointing to same memory as child in the background, when Planning was passing data to Essbase for second row it has updated the child with missing data.

For more information you can refer below link of Oracle Document regarding Implied Sharing.

http://docs.oracle.com/cd/E17236_01/epm.1112/hp_admin_11122/ch14s11.html

Hope this helps!

Greetings

SST!

Business Rule Migration from One Server to Another using Export Import in EAS.

Business rule  Migration from one Server to Another using Export Import in EAS

When we export the Business Rules (BR's), EAS exports the BR's in a xml file format, this xml files contains all the BR's, Security (if you are not exporting for Calc Manager), locations etc. Now if we are trying to migrate the BR's from say Production to Development environment, we have to update the location of the BR's in the xml file because when we export our xml file, it have the location of BR's of Production Server and here we are trying to migrate the rules to Development, so we need to update the xml and modify the location of these BR's.

Here are the steps to export and import rules from one server to another:

1. Log into EAS console of Source Environment using an admin id.
2. Right Click on Business Rules Node.
3. Click on Export.
4. In the right hand pane you will get all the BR's listed. Click on Select All.
5. Uncheck For Calc Manager.
6. Click on Dependents.
7. Export the rules.
8. This will ask to save the BR's in a XML format, save the xml file.
9. Save As the xml file with a different name.
10.Edit the xml file and replace all the Old locations of BR's with the new one, the location is case sensitive and there will be two location we need to replace small case with the small one and Upper case with the Upper one, 

Ex: A part of exported .xml

Source .xml:

<Location>
<property class="int" method="setLocID" value="41"/>
<property class="int" method="setLocationID" value="41"/>
<property class="java.lang.String" method="setLocation" value="ProdClusterMXYZ"/>
<property class="java.lang.String" method="setUpperLocation" value="PRODCLUSTERMXYZ"/>
<property class="int" method="setCluster" value="-1"/>
</Location>

Say if our Destination Location is: "Planning/WDEPMR0543/PLAN/XYZ"

In this case in your source file replace All:

ProdClusterMXYZ with Planning/WDEPMR0543/PLAN/XYZ

PRODCLUSTERMXYZ with PLANNING/WDEPMR0543/PLAN/XYZ

12. Save the file.
13. Login to the destination EAS console.
14. Right click on Business Rule node.
15. Import the BR's using the modified .xml file.

Hope this Helps.

Greetings

SST!