EPMA Period Dimension - cannot move Base members

I am trying to move Periods out of Quarters and under YearTotal in an already deployed application in EPMA (Planning app).
I want to have YearTotal above Jan-Dec, and Q1-Q4 as Dynamic Calcs with months shared below.
This is all well and good in planning classic where you can just delete the quarters and the months fall under year total.
In EPMA, because this change was not made in advance of deployment, when I make it now I get a validation fail about
"Base Time Periods cannot be moved after an application has been deployed". Fair Enough - if that is the rule then fine but hopefully there is a workaround.
So I moved them back to the original structure, and now I am getting double the number of validation errors - one for moving, and another one for removing !!
Rolled back the EPMA database to resolve the above but my question is has anyone figured a way to move months post deployment ?
Thanks,
Dave

I had the same problem and I found a solution.
1/. You have to transform the EPMA application to classic following these instructions:
- Connect to the planning application, in the top menu click on "Administration > Application > Properties"
- Add the property "EDIT_DIM_ENABLED", and set the value to "true"
- Restart Planning Service
- Connect to the "Application Library", right click on your application and select "Diagnostics"
- Check the option “Deployed but classic application in product”, click on “run selected test”, then into the “Test Detail” part check the option “delete from EPMA only” and finally click on "apply".
2/. Connect to the Planning application you make your change into the period dimension. ("Administration > Manage > Dimensions")
3/. Finally you transform your Classic to EPMA application following these instructions:
- Connect to the workspace and use the wizard to convert your classic to epma application ("Navigate > Administer > Transform Classic to EPM Architect")
- Connect to the "Application Library", right click on your application and select "Diagnostics"
- Check the option "Deployed but not in product" click on “run selected test”, then into the “Test Detail” part check the option "Retrieve" and finally the option "Syncronize".
Hope it helps you.
Regards,
David MENDELE
EPM/BI Project Manager at Business & Decision, Lima, Peru.

Similar Messages

Error : Period dimension 'Period' is missing a Base Time Period member 'Jun' that has been deleted since the last deployment. Base Time Period members cannot be deleted once the dimension is deployed

HI,
I am using V11.1.2.2 Hyperion Planning. I am currently getting an error:
Error : Period dimension 'Period' is missing a Base Time Period member 'Jun' that has been deleted since the last deployment. Base Time Period members cannot be deleted once the dimension is deployed
This is what i got when i tried to add alternate hierarchy to my shared dimension. I tried to delete it and it messed up.
NOw it wont deploy my application.
Can any one suggest.
Thanks in advance
Cheers,
XXX

EPMA!!!!! EPMA!!!!
I'm playing around with it to write a blog post and it is crazy. Only possible workaround (till now i'm not able to figure out a solution to it) is to copy the application and deploy it as a new one. Take copy of all objects (forms, tasklist etc). Delete the corrupted application and rename the new one to old.
Regards
Celvin
http://www.orahyplabs.com

Period dimension error in EPMA

Hi,
We recently imported the ads file using "replace" option in the import profile and we get the below error when we try to deploy the planning application. Tried to reassign the Begbalance member. But still not resolving the problem.
Error : Period dimension 'Period' is missing a Base Time Period member 'BegBalance' that has been deleted since the last deployment. Base Time Period members cannot be deleted once the dimension is deployed.
Error : Period dimension 'Period' contains a Base Time Period member 'BegBalance' that has been added since the last deployment. Base Time Period members cannot be added once the dimension is deployed.
Regards,
Ragav.

Hello Mady,
We are using EPMA applications and Classic applications; unfortunately we haven't taken any backup's of these applications.
I heard from some one that by performing EPMA re-configuration there is a chance of loosing the applications. Only Classic applications can be restored.
Please let me know if my understanding is wrong and kindly suggest the next steps to restore the applications.
Currently we are able to login only to Shared Services only; we can login to Workspace/planning but unable to access the applications.
Thanks for your help in advance!
Thanks,
VA

Attribute Dimension and association with multi level base members

I am trying to associate attribute dimension members with base members that can be at different levels (level 0 or level 1 or level 2 ).
First question - Is that possible ? Second how do I do that.
I am building the dimensions(base and attribute) members first and then trying to associate.
I get the following error message :
Base member (xxxxxxx) association level does not match base dimension association level
The base dimension looks like
Supplier
|-----Supplier Group
|---------Supplier ID (Associate this member to an attrbiute dimension)
|---------------Invoice Number
Sometimes the Supplier ID may not have a Supplier Group or an Invoice Number (hence it can be a level 0 or directly under the dimension name - Gen2)
The Attrbute Dimension looks like
Supplier Value
|---High
|---Medium
|---Low
Edited by: 816875 on 30-Nov-2010 07:01

First to clarify, base mambers by definition would all be level 0 members, but to your question, attributres can only be associated to a single level within a dimension. your problem is sometimes the supplier is level 0 and other times level 1. This can't be done.

Period Dimension members

Hi All,
I want to calculate Period Dimension members Jan to Dec only.
I have some more period dimension members at level 0.
If I use @LEVMBRS("Period",0), it will caluculate all the level 0 members in the period dimension. But I want to calculate only Jan to Dec.
May I use Jan:Dec in the FIX Statement?
Thanks & Regards,
Sravan Kumar.

Hi,
Yes you can use them in a fix
FIX(Jan:Dec)
ENDFIX
Cheers
John
http://john-goodwin.blogspot.com/

Deleting custom Period dimension members

Hi,
We are in Planning 11.1.2.1. and we created custom period dimension members (while creating application). Now we would like to delete one of those members (whcih is at level0). Obviously we don't see an option of delete in planning web interface. One option is to recreate the application but is there any way we can delete this member in oracle database. If yes, it would be great if you can provide us the table details.
Thanks,
Siva

As John suggested it is not advisible, however you can delete in Essbase using Planning:
1. Edit custom dimsion
2. un-select all plan type
3. cube referesh
Hope this will help.

Pipe in Expansion does not expand BAS members for all KeyRanges

Hi all,
I created a simple report to input some figures (in this case currency translation rates). I would like to add the different figures per period (BAS members of selected time period) and would like to have the different input currencies separated using the PIPE within the expansion parameters (rf. screenshot):
http://up.picr.de/4945568.png
I would expect the following result after expanding (rf. screenshot):
http://up.picr.de/4945586.jpg
What I get is the following; for the first KeyRange the BAS members are listed from JAN to DEC. the other KeyRanges only show the JAN 12 times (rf. screenshot ):
http://up.picr.de/4945604.jpg
Does anyone have an idea? I already tried to modify the expansion from BAS to BAS|BAS|BAS, but the result is the same.
Thanks in advance and best regards
DoubleM
Using: BPC 7.5 for Microsoft

Hi Karsten,
thank you for your answer, too. Yes, this is sth. I also thought about (just add the Dimension description in a new header able. I think now it's ok.
If I would adapt the report like this I would have the next issue. I like using the pipes as they give a little bit more overview to a report (from my point of view), but I guess the functionality is not always really sophisticated.
Example: Normaly the formula next to the first cells in the headers (like EVDES) is copied to the rest of the KeyRange. If you use pipes you have different KeyRanges and I would also expect, that the formula is also copied to this Ranges, but it will not. If I have static reports (like in the example of this thread), it's quite easy to copy the formulas, so the description is also named in the other ranges.
But if you have really dynamic reports (so you do not know, how many rows will be filled) you cannot copy the formulas easily. Maybe a solution with macros might be possible, but it's not the nicest way ...
cheers
DoubleM

How to customise the Period dimension in Hyperion planning

Hi Guru's
We are using Hyperion Planning 11.1.2.2
We have an requirement to customise the period dimension as follows,
   -Period
     -HalfYear1
       -Q1
       -Q2
     -HalfYear2
       -Q3
       -Q4
How to add HalfYear in the period Dimension..Please help me with this..
Thanks

While creating application what did you choose to have for Period Dimension , is it Periods by default or you did go for custom ?
Also check hp_admin guide page 104
Period Dimension Properties
Period, Parent, Alias: Default, Alias: T1, Data Storage, Two Pass
Calculation, Description, Formula, UDA, Smart List, Data Type,
Operation, Type, Start Period, End Period, Aggregation (Plan1),
Aggregation (Plan2), Aggregation (Plan3)
Notes:
. For Period, Parent should be specified for most update operations.
. Type (such as Base or Rollup) cannot be changed for existing members. You can add and
update Rollup and Alternate members. You can update BegBalance and Base time periods
(for example, to add an alias). You cannot add or modify YearTotal time period. The DTS
Period type is recognized, but is not supported by the Outline Load utility. If you try to load
DTS information, the utility displays an error in the log file.
. Start Period and End Period are valid for Rollup Period types.
Thanks
Amith

Value based hierarchies and Period dimension should only contain 2 monthl

Hi,
Can anyone tell me what is value based hierarchies. And also can anyone let me know to filter the records in AWm because in Period dimension should only contain 2 monthly values (Oct. 2008 ( 200810) and Sep. 2008 ( 200809)) it is urgent.
Thanks
vel

The following definition of a value hierarchy comes from the OLAP Developers guide
"A hierarchy defined only by the parent-child relationships among dimension members. The dimension members at a particular distance from the base level do not form a meaningful group for analysis, so the levels are not named. For example, an employee dimension might have a parent-child relation that identifies each employee's supervisor. However, levels that group together first-, second-, and third-level supervisors and so forth may not be meaningful for analysis."
Typically this means that the source table has two columns, VALUE and PARENT, where PARENT has a (logical) foreign key relationship to VALUE. An example may be EMPLOYEE, MANAGER, where MANAGERs are also EMPLOYEEs.
The simplest way to restrict the values loaded into the AW is to define a SQL view over the source table with an appropriate WHERE condition. You then use AWM to map the dimension to your new view. E.g.
CREATE OR REPLACE VIEW RESTRICTED_TIME AS
SELECT *
FROM TIME
WHERE MONTH IN (200810, 200809)

Sparse VS Dense and neglecting Period Dimension

Hi All,
I am working on a classic planning application, in which i have 3 custom dimensions apart from six standard dimension. As the application grows and we start developing business rule we feel the need for optimization of our application hence along with increasing Cache Size, Block Size etc. we also make changes in JVM registry and lastly we also convert our Custom dimension to Dense from Sparse. As we are always using these dimension at either row/columns. Now i have to different questions:
1) there are three custom attributes associated with one of my Custom dimension with 150descendants, so if i change it to Dense then i loss those three custom attributes. So is there any way to convert this from sparse to dense while having the attributes with it. Note: I am using this dimension on Row and i only want to convert it to dense in order to enhance performance. The motivation behind this change is that i piratically experiment that the business rules that take more then 20mins to executes just execute in less than a minute when i convert the other 2 custom dimensions from sparse to dense.
2) I am not using Period Dimension in my application, because my need are fulfiled by year dimension only, so is there any way to delete it or neglect it while processing business rules?

Hello,
Your question gets into some advanced design topics fairly quickly and you may want to engage an experienced consultant to help you.
It sounds like your application is past the design stage and you are making what are design level changes which is a likely risk to your project delivery time frames.
Regarding the conversion of the dimension from sparse to dense -- there is no way to tag a dense dimension as an attribute.
Review Chapter 10 of the Database Admin Guide at http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/frameset.htm?dattrib.html#dattrib524566
Pay special attention to the "Understanding the Rules for Base and Attribute Dimensions and Members".
In addition to loosing the attribute dimension please be aware of the implication to block size. Switching a sparse to a dense has a multiplicative effect on your block size; you should make all upper level members dynamic calc and then the number of level 0 members time your old block size will be your new block size.
On the topic of your period dimension you may want to try renaming it and using it for one of your other dimension needs if you do not require month level data.
On the topic of calculation speed you can usually make re-write your calculations to make them dense. In your instance it may be a good idea to make your years dense to use that to facilitate creating dense calculations.
Good luck,
John A. Booth
http://www.metavero.com

Planning on non-base members.

Hi Experts
I have a situation where different accounts in the Balance Sheet is translated at different exchange rates. For example, my hierarchy on P_ACCT:
Cash and cash equivalents Z0031011000
    ...More nodes and accounts
Net Receivables                   Z0031012000
    ...More nodes and accounts
The customer wants to translate Z0031011000 at a rate e.g. 1.05 and Z0031012000 at a rate of 1.075.
I have 2 questions regarding this:
- Since you can only plan on base-members, I cannot store a rate against a hierarchy node, or is there a way or workaroud?
- Is it possible to translate all the accounts below the node at the stored rate and how would the MDX look like?
Any help would be appreciated.
Thanks
L.

Hi,
Maintain different RATE types undere account dimension. Maintain one rate type for all base members under Z0031011000
and maintain different rate type under Z0031012000.
In Rate application maintain these 2 exchange rates aginst R_ACCT which is maintained as RATE type under account.
After this when you run currency translation all accounts under Z0031011000 will get converted based on exchange rate maintianed in rate application.Similarly for Z0031012000 also.
Hope it helps..
regards,
Raju

Syntax Error Messages - cannot recognize "bas" etc.

what's the problem with this syntax ? we read this at the sap online helpdesk.
1. the default logic
2. the system constants file
*INCLUDE SYSTEM_CONSTANTS.LGF
*XDIM_MEMBERSET ACCDETAILDIM=BAS(FLOW_CLOSING_CALC)
// Scope of what logic will be applied to for read or write, aka 'filter' in Int.Planning, if use 'bas' cannot select any others
*XDIM_ADDMEMBERSET ACCDETAILDIM=FLOW_CLOSING,FLOW_ERROR
// 'Closing' is not in 'Closing Calc' above so we 'add' it in here
*XDIM_MEMBERSET INTCODIM=BAS(IC_TOT)
*XDIM_ADDMEMBERSET INTCODIM=IC_ALL
// Copies P&L Profit to Balance Sheet
*WHEN ACCOUNTDIM.GROUP
    *IS "PL"
       *WHEN ACCDETAILDIM
       *IS "FLOW_CLOSING"
          *WHEN INTCODIM
          *IS "IC_ALL"
              *REC(ACCOUNTDIM="ACC_PROFIT_BS",ACCDETAILDIM="FLOW_RESULT",INTCODIM="IC_ALL")
              *REC(ACCOUNTDIM="ACC_PROFIT_BS",ACCDETAILDIM="FLOW_CLOSING",INTCODIM="IC_ALL")
           *ENDWHEN
        *ENDWHEN
*ENDWHEN
// For accounts with the L1_E property, if Closing is not equal to opening plus the changes, write it to the error flow
[ACCDETAILDIM].[#F_ERR] =IIF([ACCOUNTDIM].CURRENTMEMBER.PROPERTIES("DIMLIST1")="L1_E", [ACCDETAILDIM].[F_999] - [ACCDETAILDIM].[F_100] - [ACCDETAILDIM].[F_120] + [ACCDETAILDIM].[F_140],0)
// For accounts with the L1_V property, if Closing is not equal to opening plus the changes, write it to the variation flow
[ACCDETAILDIM].[#F_900] =IIF([ACCOUNTDIM].CURRENTMEMBER.PROPERTIES("DIMLIST1")="L1_V", [ACCDETAILDIM].[F_999] - [ACCDETAILDIM].[F_100]- [ACCDETAILDIM].[F_120] + [ACCDETAILDIM].[F_140],0)
*COMMIT
System Constants syntax:
// application constants
*FUNCTION CATEGORYDIM=C_CATEGORY
*FUNCTION TIMEDIM=TIME
*FUNCTION CURRENCYDIM=RPTCURRENCY
*FUNCTION ENTITYDIM=ENTITY
*FUNCTION ACCOUNTDIM=C_ACCT
*FUNCTION INTCODIM=INTCO
*FUNCTION ACCDETAILDIM=FLOW
*FUNCTION DATASRCDIM=C_DATASRC
*FUNCTION GROUPDIM=CONSGROUP
// For default logic
*FUNCTION ACC_PROFIT_BS=25712000
*FUNCTION IC_TOT=INP_INTERCO
*FUNCTION IC_ALL=ALL_INTERCO
*FUNCTION FLOW_CLOSING=F_999
*FUNCTION FLOW_CLOSING_CALC=F_TOT
*FUNCTION FLOW_VAR=F_900
*FUNCTION FLOW_ERROR=F_ERR
*FUNCTION FLOW_RESULT=F_RES
*FUNCTION VALID_RUN_FLAG=VALRUN
// This part is needed when a RATE cube
// is associated to the application
// (FX = single or multi currency)
*FUNCTION THISAPP=LEGALAPP
*FUNCTION RATEAPP=RATE
*FUNCTION RATEENTITYDIM=R_ENTITY
*FUNCTION RATEACCOUNTDIM=R_ACCT
*FUNCTION INPUTCURRENCYDIM=INPUTCURRENCY
*FUNCTION RATEENTITYMBR=GLOBAL
*FUNCTION RATESRCCALCMBR=GLOBAL
*FUNCTION AVGRATEID=AVG
*FUNCTION ENDRATEID=END

As far as my knowledge goes,
You can't use this *XDIM_MEMBERSET ACCDETAILDIM=BAS(FLOW_CLOSING_CALC)
To make this work, i did the folowing
I modfied the dimension, and created and extra collumn, and assigned it the value of "FLOW_CLOSING_CALC" to all of it's base members.
Now you can use the folowing code
*SELECT(%VARIABLE%,[ID], ACCDETAILDIM,"COLUMN_CREATED='FLOW_CLOSING_CALC'")
*XDIM_MEMBERSET ACCDETAILDIM= %VARIABLE%
i HOPE THIS HELPS

BPC Logic Script: Copy from calculated members (non-base) to base members

Hi experts,
I want to copy some values from some calculated members to base members in the same dimension. It appears I have a hard time scoping the calculated members.
This is my C_ACCOUNT dimension:
And this is the COPYCALC.LGF script I am running:
LGX:
*XDIM_MEMBERSET C_ACCOUNT = 450
*WHEN C_ACCOUNT
*IS 450
*REC( EXPRESSION = %VALUE%, C_ACCOUNT = 50)
*ENDWHEN
LOG:
LOG BEGIN TIME:2014-02-26 17:21:12
FILE:\ROOT\WEBFOLDERS\STEP_UNIT_TEST \ADMINAPP\BUDGET_CASH\TEST.LGF
USER:KAROLISB
APPSET:STEP_UNIT_TEST
APPLICATION:BUDGET_CASH
[INFO] GET_DIM_LIST(): I_APPL_ID="BUDGET_CASH", #dimensions=16
AA_NUMBER,AUDITTRAIL,BUDGET_OBJECT,BUDGET_TYPE,CATEGORY,COFOG,CURRENCY,C_ACCOUNT,C_ACCOUNT_DT,ENTITY,FLOW,GRANTS,MEASURES,TIME,TIME_DT,VERSION
#dim_memberset=4
CATEGORY:RES,1 in total.
CURRENCY:LC,1 in total.
TIME:2012,1 in total.
C_ACCOUNT:450,1 in total.
SCRIPT RUNNING TIME IN TOTAL:1.00 s.
LOG END TIME:2014-02-26 17:21:12
My model structure:
So as you can see I am trying to copy from account 450 (which is non base) to account 50 ( which is base member). Also you can see that in the previous example no record was generated.
Whereas, if I replace the account 450 with 4500 I get record generated in order:
LGX:
*XDIM_MEMBERSET C_ACCOUNT = 4500
*WHEN C_ACCOUNT
*IS 4500
*REC( EXPRESSION = %VALUE%, C_ACCOUNT = 50)
*ENDWHEN
LOG:
LOG BEGIN TIME:2014-02-26 18:26:26
FILE:\ROOT\WEBFOLDERS\STEP_UNIT_TEST \ADMINAPP\BUDGET_CASH\TEST.LGF
USER:KAROLISB
APPSET:STEP_UNIT_TEST
APPLICATION:BUDGET_CASH
[INFO] GET_DIM_LIST(): I_APPL_ID="BUDGET_CASH", #dimensions=16
AA_NUMBER,AUDITTRAIL,BUDGET_OBJECT,BUDGET_TYPE,CATEGORY,COFOG,CURRENCY,C_ACCOUNT,C_ACCOUNT_DT,ENTITY,FLOW,GRANTS,MEASURES,TIME,TIME_DT,VERSION
#dim_memberset=4
CATEGORY:RES,1 in total.
CURRENCY:LC,1 in total.
TIME:2012,1 in total.
C_ACCOUNT:4500,1 in total.
REC :%VALUE%
CALCULATION BEGIN:
QUERY PROCESSING DATA
QUERY TIME : 0.00 ms. 1 RECORDS QUERIED OUT.
QUERY REFERENCE DATA
CALCULATION TIME IN TOTAL :0.00 ms.
1 RECORDS ARE GENERATED.
CALCULATION END.
ENDWHEN ACCUMULATION: 1 RECORDS ARE GENERATED.
DATA TO WRITE BACK:
AA_NUMBER AUDITTRAIL BUDGET_OBJECT BUDGET_TYPE CATEGORY COFOG CURRENCY C_ACCOUNT C_ACCOUNT_DT ENTITY FLOW GRANTS TIME TIME_DT VERSION SIGNEDDATA
AA_NONE LIM NONE 10 RES FA_NONE LC 50 CAD_NONE A00 F99_1 NONE 2012 TD_NONE CURRENT 222.00
1 RECORDS HAVE BEEN WRITTEN BACK.
WRITING TIME :1.00 ms
Why can I not copy value from 450 ? How do I solve this problem ?
PS: currently I am testing this as a DM package run script but in the future I would like to make it a Default.lgf functionality.
I am working on:
BPC 10 SP5 for NW, calculation engine ABAP, BW 7.4

Sorry to keep you in darkness. My code has developed since I have started this thread:
*SELECT(%ADMISSIBLE%, "[ID]", C_ACCOUNT, " [THIERARCHY]<>'' AND [ACCTYPE]<>INC ")         // DEFINE THE SET OF REAL(ACTUALY EXISTING), NON-REVENUE AND NOT ANCIENT CASH ACCOUNTS HERE.
*SELECT(%INADMISSIBLE%, "[ID]", C_ACCOUNT, " [ID] <> %ADMISSIBLE% ")
*SELECT(%L1%, [ID], C_ACCOUNT, "[ID] = %C_ACCOUNT_SET%")       // DEFINE BASE LEVEL ACCOUNTS
*SELECT(%L2%, "[THIERARCHY]",C_ACCOUNT, "[ID] = %L1% ")       // DEFINE FIRST(COUNTING FROM BASE) LEVEL PARENTS
*SELECT(%L3%, "[THIERARCHY]",C_ACCOUNT, "[ID] = %L2% ")       // DEFINE SECOND(COUNTING FROM BASE) LEVEL PARENTS
*SELECT(%L4%, "[THIERARCHY]",C_ACCOUNT, "[ID] = %L3% ")
*SELECT(%L5%, "[THIERARCHY]",C_ACCOUNT, "[ID] = %L4% ")
*SELECT(%L6%, "[THIERARCHY]",C_ACCOUNT, "[ID] = %L5% ")
*SELECT(%LALL%, "[ID]", C_ACCOUNT, "[ID] = %L1%,%L2%,%L3%,%L4%,%L5%,%L6%") //UNION OF ALL LEVELS
*XDIM_MEMBERSET AUDITTRAIL = INPUT
*XDIM_MEMBERSET VERSION = CURRENT
*XDIM_MEMBERSET AA_NUMBER = AA_NONE
*XDIM_MEMBERSET TIME_DT = TD_NONE
*XDIM_MEMBERSET C_ACCOUNT_DT = CAD_NONE
*XDIM_MEMBERSET C_ACCOUNT = %INADMISSIBLE%     //SCOPE LEAVES ALL POTENTIAL DESTINATIONS FOR MEMBERS IN %PARS%
*FOR %A% = %PARS%    //LOOP OVER ALL ADMISSIBLE PARENTS
*WHEN C_ACCOUNT
*IS L_C_%A%
*REC( EXPRESSION = [C_ACCOUNT].[%A%], C_ACCOUNT = L_C_%A%)         //SUM UP THE VALUES OF LEAVES AND WRITE THE SUM TO DESTINATION ACCOUNT
*ENDWHEN
*NEXT
screen shot of part of member table for C_ACCOUNT:
continuation in next reply (I have problems with my text editor)

Error while loading period dimension in planning through DIM

Hi,
I am trying to load the metadata extracted from DRM into Period dimension in Hyperion Planning through Informatica using DIM. But I am getting the following error:
Record [[YearTotal, Period, Total Year, Dynamic Calc, 0, null, null, null, null, Unspecified, null, null, null, null, ~, ~, ~]] was rejected by the Planning Server.
Error occurred during load process. Error message is: Cannot load dimension member, error message is: java.lang.RuntimeException: Year operations not handled through this entry point.
Record [[1stHalf, YearTotal, null, Dynamic Calc, 0, null, null, null, null, Unspecified, null, null, null, null, +, +, +]] was rejected by the Planning Server.
Error occurred during load process. Error message is: Cannot load dimension member, error message is: java.lang.RuntimeException: Invalid First Child Id
Appreciate your help.
Thanks.

The .otn file is created when essbase is restructuring and once completed renamed to otl, if it does not complete it can leave the .otn file.
You should be able to delete the otn (maybe stop the application first) and open the outline.
I would also check the logs generated from ODI and also the essbase app logs to troubleshoot the issue.
Cheers
John
http://john-goodwin.blogspot.com/

EPM Context filter - select base members of a node

Hello Experts,
Is it possible to select the base members of a node in epmcontext filter?
Thanks,
Nadine

Hi Nadine,
Its not possible to get base members of a particular parent.
The suggestion provided by Nagarjuna will fetch you all the base level members in your dimension.
The suggestion provided by Biswajit will not work at all. Consider the Time dimension as an example. You will have certain properties for the months. However, if you want to fetch the base level of a year, and you put a condition as PARENTH1=2010.TOTAL; BASE_MEMBER=X, it will not give you anything; since PARENTH1 of the months will not be equal to the year. Instead, it will be the quarter.
Hope this helps.

EPMA Period Dimension - cannot move Base members

Similar Messages

Maybe you are looking for