Enterprise Transformations, It's all About Performance Management

The member "" does not exist for the specified cube or you do not have access to it. Issue:  If you are running into a issue, where for a RTP member selection is throwing an error for a missing member, this regardless of the member you have selected in RTP or regardless of rule. You may be able to execute the rule from Calc Manager and not from Planning. Reason: You may run into this issue if: 1. You have added members in Planning and have not refreshed the cube 2. For the default value of a RTP in calc member you have a member which is not valid any more for planning application 3. For the default value of a RTP in calc member you have a member which is not valid any more for a plan type Solution: 1. Refresh cube 2. Update Default value of RTP which is causing issue to member which exists 3. Deploy the rule Rahul S.

We have witnessed an issue where application migration or sometimes service restart in PBCS/EPBCS activates multiple navigation flows.  If multiple navigation flows are active you wont be able make changes in any of them, because in order to make change in navigation flow you have to make it inactive. Typically you may end up in following situation:  Solution is pretty simple: 1. Create a copy of any of the existing navigation flow:  2. Give it any desired name:  3. Now, you will see one additional navigation flow, with inactive status: 4.  Make it active: 5.  At this point of time you will have one active navigation flow and two inactive  6. Select the additional navigation flow you have created and delete it  7. Now you are back in business: Rahul S.

If you are using On Prem FDMEE to connect with PBCS/EPBCS you may run into the issue where ASO cubes are not showing up in On Prem FDMEE. In order to solve this issue you have to go to PBCS Data Management and create a ASO Target Application. Once this application is created, ASO cube should show up in On Prem FDMEE. 1. Go to Data Management in PBCS 2. Click on Add, select Local  3. Select Essbase from the drop down 4. ASO Cubes will show up with "A" and "A_ "  prefix  5. Save the ASO Target Application, you should see it as essbase application 6. Now login to On Prem FDMEE , you should see ASO cube in the list now: Rahul S.  

We will talk a little about what we need to ensure for data spread to work. For the sake of this discussion, we are assuming our application is set for 445 Distribution. We have many time balance properties, Flow, First, Balance, Average, Weighted Average (Actual and 365), you can read about them in Planning guide. The account we have taken for this example is set to Flow. You need to select either Idecendants of YearTotal or any of the quarters for period selection. Ex:  @IDESC("YearTotal") or @IDESC(<Qtr Member>) . Here is one sample data form: Entered 300 at Q4, values are distributed in 445: However, if you just select yearTotal and months, spread will not work. YearTotal is readonly! Even if you take descendants of any Quarter your spread will work fine. Now, One of the issues we faced: Issue: Data spread was working for every user in planning web, however, when they were trying to spread data throu

On Prem, PBCS, EPBCS Here are some frequently asked questions: Q 1.  Can we create multiple applications? Ans:  In On Prem you can create as many applications as you want, but in case of PBCS/EPBCS, it's limited to One application per environment. If you want more you may have to buy a new pod, per app. Q 2: How many environments we will get? Ans: In On Prem, you can have any many environments as you want. Typically, Dev, Test/QA, Prod. However, Oracle provides two instances Dev and Prod. Q 3: Can I delete application in PBCS/EPBCS environment or we need to reach out to Oracle? Ans:  Yes, you can delete application and create a new one yourself. Q 4:  What options are available for metadata integrations? Ans: For On Prem: FDMEE, metadata integration offered for EBS, People soft etc., Outline Load, ODI Adapter for planning, EPMA, Smart View Admin Extension.        For PBCS/EPBCS: EPM Automate Utility, Smart View Admin Extension Q 5: What options are available for D

Background: We had a dynamic calc member with a member formula but it wasn't getting calculated automatically. We had to aggregate account dimension in order to calculate dynamic calc values. This defeats the purpose of having a dynamic calc member.  After researching further we got to know the reason of the issue and a solution.  Here is how we can replicate the issue: Create  a TestMember, which Never Share or Store property: If you will go  to the member formula tab, data storage for default cube and OEP_WFP cube will be Never Share:   Let's edit this member and change the storage property to Dynamic Calc: You will notice data storage will change for the Default Cube: But if you look further data storage will still be never share for OEP_WFP cube. For us, initially when we loaded some members, we had the storage property as Never Share, which we later changed to Dynamic Calc, but internally it was still Never Share at th

Smart View: EPBCS / PBCS Drill Through is not Working If you have enabled Drill though in FDMEE and its working from Planning Data forms and but it’s not working through Smart View, then this post will save some of your time. In my case when I was trying to drill down from Smart View it was taking me to Cloud Planning instead of Drill through landing page.   A little background: When you try to click on drill through in it uses drill down aif, in within GET request it passes the application and member combination against which you are drilling though. A sample query is: <WorkspaceURL>?aif.drilldown&attribute=system.ds.planning&attribute=app.ds.<AppName>&attribute=<Dim>.id.<MemberName>&… Example: http://MyServer:19000/workspace/index.jsp?module=aif.drilldown&attribute=system.ds.planning&attribute=app.ds.MyApp&attribute=cluster.ds.PLANNING_LWA&attribute=database.ds.OEP_WFP&attribute=Period.id.Jan&