Dimension Member Cross Validations

Hi,
Can we setup a combination validation between multiple Dimensions ? So that when users selects a member from one Dimension it automatically decide particular values only in another Dimension.
Example: Balance sheet Accounts members from Account Dimension should have combination with only one "0000" member of Cost centre Dimension, this is something like Cross Validation in Oracle Financials. So, user selects Balance sheet accounts from Account Dimension and then he finds only "0000" member in Cost centre Dimension list even though Cost Centre Dimension contains many children.
Thanks,
Ravi

There are usually two aspects of this question.
One is the "can I populate one drop-down based on a value selected in another dropdown". I saw this done at Cadbury in their IT planning application, but it involved a LOT of custom Java, and was very difficult to maintain. The cross-validation rules were maintained in separate custom text files and the planning app had to be recycled for any changes to take effect. They ended up walking away from this solution due to the maintenance issues.
The other aspect of this quesiton usually relates to security. "Can I have access to one account if I select a specific member, but then NOT have access to that account if I select another member?" This is similar to Oracle's cross-validation rules. Hyperion Planning doesn't support this type of security. Security for each dimension is maintained independent of other dimensions. Essbase itself doesn't have this limitation, however Planning does. Hopefully this will get addressed soon - it's usually in the top two or three complaints my clients have regarding Hyperion Planning.
Take Care,
- Jake

Similar Messages

Validation: more than one Other Source Dimension Member

Hi BPC Experts,
Is it possible to identify more than one Other Source Dimension Member in Validation Business Rules settings? For example, we need to use all DataSources that belong to IFRS roll up. If yes, what is the format?
Thanks.
Mila

Resolved. The format is DIMENSION=MEMBER OR DIMENSION=MEMBER.
For example,
C_DATASRC=MJ_MANJE OR C_DATASRC=GAAP_03 OR LOB_IFRS=TEST OR LOB_IFRS=IFRS_INSD.

Dimension 'Years' failed validation

Hi All,
I am getting this error while deploying the application.
Error : Dimension 'Years' failed validation 'YearMembersSequential' for the following reason(s): Year members must be sequential.
I am seeing my Year dimension is sequential only.
I am not able to figure out the reason for this error . Can anyone please help me understand this.

Not to open a new thread as I have an issue with dimension Year as well, I will post my problem here (hope the author won't mind).
I created a simple EPMA application in version 11.1.2.2 with all mandatory and 2 generic dimensions. One of mandatory dimension is, of course, Year (dimension type: Year) with following members: FY11, FY12, FY13. Initial deployment against both, Planning and Essbase went well. After that I wanted to extend dimension Year for member FY14 and to redeploy the application. Validation was successful, but deployment message was "Completed/With Errors" (100%). Deployment was done with selecting "Refresh outline" and "Full deploy". In deployment log file I have the following entry:
"Consolidation operators for years must be set to Ignore for all plan types."
"Rejecting Member FY14."
This message is clear enough, but the problem is that members that belong to dimension type Year don't even have consolidation operators in properties area.
What else comes to my mind is that (maybe) with version 11.1.2.2 it is not allowed to add new members for dimension Year once application is deployed for the very first time. But in that case, the above error message is quite misleading. Under version 11.1.1.3 it is possible to add new members to dimension Year and to redeploy it without errors.
Is this a bug or a feature?
Has anyone had such problem?
Thanks,
Damir

Performance issue:Show id and Description for same dimension member

Hi,
I am connecting a cube to another reporting system and i need to show the id of member resulting of a query.My first thought was to use this kind of code (bellow) however when i do the same thing with many dimension (many cross join ),it slow down a lot
my query.So how can i have in the same DImension member showing a description and id ? I also have a lot of statement,so i can't have just two columns in the dimension or i will need to duplication the mdx and i could drop down the performance.
So i am trying to get as a result
Dim1 | Dim2| Dim3| Measure
1 50
32 25.2
and also be able to get
Dim1 | Dim2 | Dim3
| Measure
NameElement1Dim1 NameElement50Dim2
NameElement32Dim3 25.2
Thanks in advance
with MEMBER [Measures].[IdElement] as
<element>.currentmember.properties("KEY")
select
CROSSJOIN({[Measures].[IdElement]},{[METRIC].[Description].[All]}),
CROSSJOIN({[Measures].[value]},{<listmetricmdx>})
} on columns,
<pointofview>
<element_and_function>
<TimeBreakdown>
} on rows
<list_filter_clause>
) as list
where ((ElementName is null AND IdElement=0) OR (ElementName is not null))
<list_condition_metric>
but i have multiple

Hi Vincent,
In your query, you use CrossJoin in it. Crossjoin function will cause the performance issue if there are a lot of properties that need to be displayed. If you cross-join medium-sized or large-sized sets (e.g., sets that contain more than 100 items each),
you can end up with a result set that contains many thousands of items—enough to seriously impair performance. For the detail information, please see:
http://sqlmag.com/data-access/cross-join-performance
In your MDX query, ensure only retrieval the required data. Here are some useful links for your reference.
Configure memory setting:
http://social.msdn.microsoft.com/Forums/en/sqlanalysisservices/thread/bf70ca19-5845-403f-a85f-eac77c4495e6
Performance Tuning:
http://www.microsoft.com/downloads/details.aspx?FamilyID=3be0488d-e7aa-4078-a050-ae39912d2e43&displaylang=en
http://www.packtpub.com/article/query-performance-tuning-microsoft-analysis-services-part2
Regards,
Charlie Liao
TechNet Community Support

ORA-35563: Multiple values exist for an attribute of this dimension member

After following the tutorial Building OLAP Cubes I was trying to make a cube with aggregation down to the day instead of down to the month.
I created a times table pretty similar to the one used in the tutorial:
CREATE TABLE EVENT_TIMES (
        HOUR_KEY        DATE NOT NULL,
        DAY_ID          VARCHAR2(10),
        DAY_NAME        VARCHAR2(10),
        DAY_END_DATE    DATE,
        DAY_TIME_SPAN   NUMBER,
        MONTH_ID        VARCHAR2(30) NOT NULL,
        MONTH_NAME      VARCHAR2(40),
        MONTH_END_DATE DATE,
        MONTH_TIME_SPAN NUMBER,
        YEAR_ID         VARCHAR2(30) NOT NULL,
        YEAR_NAME       VARCHAR2(40),
        YEAR_END_DATE   DATE,
        YEAR_TIME_SPAN NUMBER
As you can see, instead of a DAY_KEY like in the tutorial, I now use an HOUR_KEY.
This is a sample of the data I inserted in this table:
select to_char(hour_key,'YYYYMMDDHH24MISS'),DAY_ID,DAY_NAME,DAY_END_DATE,DAY_TIME_SPAN,MONTH_ID,MONTH_NAME,MONTH_END_DATE,MONTH_TIME_SPAN,YEAR_ID,YEAR_NAME,YEAR_END_DATE,YEAR_TIME_SPAN from event_times;
TO_CHAR(HOUR_KEY,'YYYYMMDDHH24MISS') DAY_ID     DAY_NAME   DAY_END_DATE DAY_TIME_SPAN MONTH_ID                       MONTH_NAME                               MONTH_END_DATE MONTH_TIME_SPAN YEAR_ID                        YEAR_NAME                                YEAR_END_DATE YEAR_TIME_SPAN
20140104050000                       Y2014M1D4 Y2014M1D4 04-JAN-14                1 Y2014M1                        Y2014M1                                  31-JAN-14                   31 Y2014                          Y2014                                    31-DEC-14                365
20140104060000                       Y2014M1D4 Y2014M1D4 04-JAN-14                1 Y2014M1                        Y2014M1                                  31-JAN-14                   31 Y2014                          Y2014                                    31-DEC-14                365
I then created my TIME dimension with DAY as the lowest level.
When I try the maintain cube option it fails at the 'LOAD NO SYNCH' step with the rejected records having an error message that says:
ORA-35563: (XSRWLD17) Multiple values exist for an attribute of this dimension member.
To me, this is a very cryptic message and the only explanation I find online is:
Cause
Multiple source table rows containing different values for a dimension attribute were found. Only the first of the multiple rows has been loaded.
Action
Fix the mapping or remove the rows with conflicting attribute values..
This confuses me. In the tutorial the lowest level was day and the TIMES table contained 1 record for each day.
In my example, the lowest level is hour and the TIMES table contains 1 record for each hour.
Which attribute has multiple values? And which values?
The rejected records (101) are not very clear:
ALIAS_1 = 'MONTH_Y2014M1' AND ALIAS_3 = to_date('31JAN14') AND ALIAS_4 = 31 AND ALIAS_5 = 'Y2014M1' AND ALIAS_6 = 'Y2014M1' AND ALIAS_7 = 'YEAR_Y2014'
If anyone can help point me in the right direction, it would be greatly appreciated.

I have seen this recently. The issue is with the dimension load itself. You have a hour level record table but the rules relating to hierarchy/attribute values etc are checked/reinforced during the load and this error comes up sometimes.
I would guess that the issue seems to be with your month level information present in the higher level month columns. There are many records corresponding to a single month in ur case, month of Y2014M1. Information relating to Month level member Jan 2014 or member MONTH_Y2014M1 is present in these records: 31 (days) *24 (hours) = 744 records. The data in these 744 records for columns - MONTH_ID, MONTH_NAME, MONTH_END_DATE, MONTH_TIME_SPAN need to be exactly the same in order for the single member MONTH_Y2014M1 to have month attributes loaded with valid values.
For e.g: if records #1 to #743 contain month_timespan=31 but for some unknown reason record #744 contains month_timespan=30 then this error will come up. OLAP does not know which value to load (31 or 30), and only 1 value can be loaded onto the month level member corresponding to month Y2014M1.
A quick check of the data should give you the answer. Typically there may be some mistake/invalid assumptions made with the boundary records (in your case, check for values for records corresponding to hour=0 or hour=23/24) which is causing the issue.
HTH
Shankar

Processing dimension error :DUPLICATE DIMENSION MEMBER %1 IS DETECTED

When I try to process the Account Dimension, I get an error u201CDUPLICATE DIMENSION MEMBER %1 IS DETECTEDu201D.
However my dimension does not contain any duplicate members.
Appreciate if someone could interpret this error message and help me resolve the issue
Thanks,
Sowmya
Edited by: 281642 on Nov 10, 2011 11:34 AM

Hi Sowmya,
We had same error couple of times. The issue is you could have some blank rows inserted at the end of your master data. Try the following steps
1. Maintain master data
2. Go to the last row with valid master data
3. Select all rows below it and right click and delete
4. Save and process dimension
Hopefully this should resolve your issue.
Regards,
Kranthi

Error(1012016) Cannot calculate Dimension Member [CYG_BILAN] with restricted Member [CYG_BILAN].

Hello,Below is a validated script, with generate a run time error :Error(1012016) Cannot calculate Dimension Member [CYG_BILAN] with restricted Member [CYG_BILAN].See the script below (with the error message in comment).Why can't' I calculate a member which is fixed ? Where is it documented ? How should I modify this script to make it runable ? Thanks for help Philippe Cuisset SCRIPT======/* Basculement des comptes d'actif de solde négatif vers les comptes de dettes *//* Philippe Cuisset 31/05/03 */SET MSG INFO;FIX ( @DESCENDANTS(&organisation, 0), @LEVMBRS(dev,0), @DESCENDANTS(&annee, 0), ind_financier, @LEVMBRS(cra, 0), @LEVMBRS(geo, 0), @LEVMBRS(clifa, 0), @LEVMBRS(ana, 0), @LEVMBRS(nc, 0) ) /* Copie des données du cycle réel dans le cycle bilan */ FIX( flu_ouv, flu_mensu ) DATACOPY cyg_reel TO cyg_bilan; ENDFIX /* Pour le flux solde, et (chaque nature comptable (d'actif circulant) ayant un attribut bilan, ou chaque nature comptable de dettes financieres) */ FIX( cyg_bilan, flu_solde, @ATTRIBUTE( BILAN ), @DESCENDANTS( NC7_FINANCIERES, 0 ) ) /* Initialisation du solde mensuel du compte d'actif */ VAR var_solde_actif = 0; /* Initialisation du solde mensuel du compte de dettes */ VAR var_solde_dettes = 0;/***** ERROR ON FOLLOWING LINE *****//***** Local/buedmt2/buedmt2/Essadm/Error(1012016))Cannot calculate Dimension Member [CYG_BILAN] with restricted Member [CYG_BILAN] *****/ cyg_bilan ( /* Si nature comptable (d'actif) avec attribut bilan */ IF ( @ATTRIBUTESVAL( BILAN ) != "" ) /* Calcul du solde mensuel de la nature comptable d'actif */ var_solde_actif = flu_ouv + @ACCUM( flu_mensu ); /* Si le solde mensuel est < 0 */ IF ( var_solde_actif < 0 ) /* Raz du solde dans le compte d'actif */ cyg_bilan = 0; /* Ajouter la valeur du compte de bilan depuis l'actif vers les dettes */ var_solde_dettes = @MEMBER( @SUBSTRING( @ATTRIBUTESVAL( bilan ), 3) ) ; cyg_bilan = var_solde_dettes + var_solde_actif; ENDIF ENDIF ); ENDFIXENDFIX

Not sure where it is documented, but you can not calculate what you are fixing on. To me it seems a bit odd, but I believe the logic is, if it is sparese and you are fixing on it, how can you fix on what might not be there? If it is sparse, fix on all the other sparse dimensions thenFix (....) CYG_BILAN ( CYG_BILAN = ....; )EndFiX;Also, if it sparse, make sure the block exists (either datacopy data into it or set 'CREATE BLOCK ON EQUATION' on - I tend to copy data into it).If it is dense, you wouldn't want to fix on it anyway.Rich SullivanBeacon Analytics

How to get the ID of a dimension member in script logic?

Hi everybody,
I am working in some logic scripts and I wonder if exists any option to get the current member ID of a dimension in order to concatenate a string using the member referred and an additional set of caracters such as: MEMBER_ID&"_ccccc".
Moreover, I would like to use this ID dimension member in order to filter members of another dimension whose attribute is equal to the ID of the desired member. Is it feasible?
In conclusion, is it possible to get a variable which is referred to a member ID of a dimension, and using it in order to filtering other dimensions?
Many thanks in advance,
Antonio

Hi Antonio,
You ask if it is possible compare a dimension id with a property value.. yes it is posible , for doing that you will have to do something like this,
*FOR %ACC1%=ThisA,ThisB,ThisC
      *WHEN DIMENSION.PROPERTY=%ACC1%
              *REC(............)
       *ENDWHEN
*NEXT
if you want to concatenate using a filter theres a posibility, like this example using the time dimension.
*xdim_memberset time=%year%.jan -
>2011.jan
hope it helps

Error: Invalid dimension member with special character / in BPC NW 7.5 SP7

Hi experts,
We are encountering the following problem in our Financial Planning application.
We are migrating our existing BPC solution from one server to another through backup and restore. The existing solution was on BPC NW 7.5 SP 5. The profit_centre dimension in the existing solutions has several member ids with special character '/' (forward slash). The dimension never threw an error when processed in the existing solution and there is planning transactional data against these member ids.
While the entire configration , appset , files were successfully restored through UJBR on the new system (BPC 7.5 SP7) through UJBR (backup and restore), the masterdata could not be restored only for this Profit_centre (masterdata for other dimensions were processed successfullu). All the member ids with / are rejected for this dimension. The same error is thrown if processed through the admin client from the member sheet.
Error: Dimension member PC_FF/WS/NT is an invalid member ID
Error in Admin module
Is there any setting which need to be made to allow / character in member ids? Any suggestion to get around this problem would be much appreciated.
Thanks
Abhiman

Hi Abhiman,
Yes, you need to maintain the transformation file to correct all dimension member IDs. Can you please refer to the following link with a similar issue:
conversion file formula not working
Hope this helps.
Rgds,
Poonam

How to tag attribute member with standard dimension member in EIS

hi,
would any one please help me how to tag attribute member with standard dimension member in EIS
THANK U IN ADVANCE

In your OLAP model, view columns for the base dimension table. Go into the column properties and for the columns that have Attribute values highlight them and click the Attribute button.
Go into Metadata Model and those fields will be available to drag into your outline as attribute members.
Once in the outline, go into the properties of the attribute and assign the level of the base dimension they associate with.

Reading data from a text file into PAS - Dimension member names truncated

Hi,
I created a procedure to dump variables and data into a text file to load into another model. I used a semicolon as a field seperator.
The data, measures and dimension members are dumped properly into a text file and no dimension member names are truncated .
However when I read the data into a measure, and I issue a peek command, dimension meber names are read in truncated
and remain full names in the text file. Any reason for this? What do I need to do to prevent this from happening?
THanks.
Lungile

Hi Lungile,
The problem that you're likely having is that you haven't created a file description for the file from which you're reading. When loading data into Application Server from a text file, you would normally go through three steps:
1. Enter the ACCESS EXTERNAL subsystem
2. Specify the name of the file to be read
3. Specify the format of the file field names, types, widths, and positions.
If you go into the Application Server help, select "Application Server Help", then "Application Server at the command level", then "Variables and reading in data", and then "Reading an external file", you will have the process of the steps you need to follow outlined for you, including links to the help topic for each command you need to issue.
So what I think you need to do is use the DESCRIPTION command to specify the names of your fields, their type, and also their width, in order to ensure no truncation of data on the load.
The same DESCRIPTION statement is required if you want to use your text file as the source of a dimension.
Hope this helps,
Robert

Error selecting a dimension member in BPC EPM report - The given key was not present in the dictionary

Hi,
We are currently running SAP BPC 10.1 NW on Hana
Version:
CPMBPC 810 SP 4
SAP_BW 740 SP 9
HANABPC 810 SP 4
EPM Excel Add-in 10 SP 21 .NET 4 build 9094.
On my embedded model. I have a BEX query on a aggregation level which I access in a report using the EPM Add-in Excel .
When I edit my report in EPM Add-in Excel , and I try to select the dimension members for a selected dimension member, I get the following error.
"The given key was not present in the dictionary"
Any assistance to help resolve the problem will be appreciated.
Regards
Gavin

Hi Shrikant,
I had a look at MBR_SEQ , it is a attribute on the dimension member in BW , this relates to a past version of BPC 7.5. We are currently on BPC 10.1 Embedded model , and the MBR_SEQ does not exist on any of the characteristics I have in my info cube.
When I create a web report I am able to access the dimension members using the select dimensions options, the problem seems to be on the EPM Add-in Excel client only.
Thanks
Gavin

How to migrate dimension member text files from ODI to Hyperion Planning

Hi
We are having an issue with ODI that it was not connecting to planning.
Later with some instructions from oracle, we have tried to set some RMI path in websphere and we tested the RMI connectivity test.
It was successfully connecting to planning.
Then we want to test that ODI is connecting to planning or not.
For this I think if anyone can send the doc relating to dimension member upload thru ODI to hyperion planning using text files, it will be helpful.
Appreciate if anyone can help us on this.
Please communicate to [email protected] for doc sending.
Thanks
Rajesh Reddy

Go through His(John's) earlier blogs which very clearly explains how to get connected & keep the ball rolling.
If you're so scared to use the existing connections, you may want to-
i) Set up new Master & work repository;
ii) Do few quick configurations from Topology Manager;
iii) Create your project, models, Interface;
Let us know if something isn't still clear.
- Natesh

Why to open Block only with Dense dimension Member ???

Hi All,
I want to understand the logic behind opening the block with dense member. Generally we open the block with member of dense dimension by fixing the sparse members
e.g. below considering C1, P1,Working,Actual are members of sparse dimension customer, product, Version, Scenario.
Fix(C1,P1,Working,Actual)
Jan
IF(Some condition)
Calculation on Account Member
ENDIF
Now if i change the code as below making Jan in FIX and opening the block with Actual. How it will affect the performance. The Number of iterations in total number of datacells will be same in bothe cases above and below then why to give priority to dense dimension member for opening the block.
Fix(C1,P1,Working,Jan)
Actual
IF(Some condition)
Calculation on Account Member
ENDIF
ENDFIX
I know the logic behind keeping sparse dimension member in FIX but here i think keeping 'Actual' member for opening the block is also a type of fix which will tell the code to do the calculation only for blocks of 'Actual'.
In 1st case i have fixed the number of blocks containing members C1,P1,Working,Actual and by keeping Jan for opening block means Jan is also fixed for the particular application means code will not run for feb march etc.
Means code will run for C1->P1->Working>Actual->Jan
In 2nd case also i have fixed C1,P1,Working,Jan and by keeping Actual for opening block means Actual is also fixed for the particular application means code will not run for other members of Scenarion dimension.
Means code will run for C1->P1->Working>Jan->Actual
Then what is the difference??? Why it will effect performance???

when using an IF statement in a calc script you have to specify a member to associate it with for the calc member block. This is like temporarily assigning it to that member as a formula in the outline. In most cases calculations on dense dimensions can work faster as the block is in memory. Remember that a block statement can have multiple calculation statements in it. When this occurs, having the calculations on a dense member can speed it up as it may not have to swap blocks to do the calculation.
Also consider that if a sparse combination of members does not exist, the block will not exist and there will be no attempt to do the calculations. If a sparse member is on the calc member block, it will cycle through all of the sparse members looking to do the calculation.

How to export data from Elimination Value dimension member by HAL HFM adapter?

Good day! Is it possible to export HFM 4.0.5 data with HAL from the <Elimination> Value dimension member? In 3.* versions it wasn't and there is Known Issue in the "HFM 3.* Adapter Read Me" file: "The Hyperion Financial Management Adapter exports data using the <entity currency> Value dimension member. The documentation erroneously states that there is a port available for the Value dimension" But there is not such point in the same file for HFM 4.0.5 AND there is Value port in the HFM 4.0.5. Adapter. Thanks! Regards, Georgy 

In the first approch, try to change the exporting parameter type REF TO DATA.
Try like:
CLASS lcl_test DEFINITION.
PUBLIC SECTION.
 DATA: t_mara TYPE HASHED TABLE OF mara WITH UNIQUE KEY matnr.
 METHODS:
 constructor,
 get
 IMPORTING
 if_matnr TYPE matnr
 EXPORTING
 ea_mara TYPE REF TO data.
ENDCLASS. "lcl_test DEFINITION
START-OF-SELECTION.
DATA: lo_test TYPE REF TO lcl_test,
 lr_data TYPE REF TO data.
FIELD-SYMBOLS: <fa_mara> TYPE ANY,
 <f_field> TYPE ANY.
CREATE OBJECT lo_test.
lo_test->get(
 EXPORTING
 if_matnr = '000000000077000000' " << Replace Your Material
 IMPORTING
 ea_mara = lr_data ).
ASSIGN lr_data->* TO <fa_mara>.
ASSIGN COMPONENT 'ERSDA' OF STRUCTURE <fa_mara> TO <f_field>.
<f_field> = space.
WRITE: 'Done'.
CLASS lcl_test IMPLEMENTATION.
METHOD constructor.
 SELECT * INTO TABLE t_mara
 FROM mara
 UP TO 10 ROWS.
ENDMETHOD. "constructor
METHOD get.
 FIELD-SYMBOLS: <lfs_mara> LIKE LINE OF me->t_mara.
 READ TABLE me->t_mara ASSIGNING <lfs_mara> WITH KEY matnr = if_matnr.
 GET REFERENCE OF <lfs_mara> INTO ea_mara.
ENDMETHOD. "get
ENDCLASS. "lcl_test IMPLEMENTATION
Regards,
Naimesh Patel

Dimension Member Cross Validations

Similar Messages

Maybe you are looking for