cancel
Showing results for 
Search instead for 
Did you mean: 

Duplicate formula found: Processing Dimension

former_member221145
Participant
0 Kudos

Hi Experts,

I am getting the following error when processing the ACCOUNT dimension

Failed to expand K2 function for dimension ACCOUNT's member formulas

Duplicate formula found: "[ ACCOUNT ].[# K_COS_LTBOM_FTPRC_PK ] =[ACCOUNT].["

The member K_COS_LTBOM_FTPRC_PK has formula [K_GM_COS_MTH_PKG]. I have checked if the member K_GM_COS_MTH_PKG has any formula but there are no formula for the member K_GM_COS_MTH_PKG. I tried removing all the formulas from the Formula column and process the dimension and it was successful. I started adding the formulas one by one to know which one is causing the problem and found the problem with the member

K_COS_LTBOM_FTPRC_PK

Thanks for your help in advance,

Rohit

Accepted Solutions (1)

Accepted Solutions (1)

former_member221145
Participant
0 Kudos

Hi ,

Thank you Vadim for your help on this, I have recreated the dimension  and pasted the members. Now I am able to process the dimension with out any errors.

Regards,

Rohit

Answers (1)

Answers (1)

former_member186338
Active Contributor
0 Kudos

Hi,

Is K_COS_LTBOM_FTPRC_PK a base member with no parent? Delete this member and recreate it. Then add formula...

Vadim

former_member221145
Participant
0 Kudos

Hi Vadim,

No K_COS_LTBOM_FTPRC_PK is not base member, it has parent K_COS_LTBOM_FUTPRC. I tried removing the member K_COS_LTBOM_FTPRC_PK and processed and added the member again and processed the dimension and got the same error.

Thanks,
Rohit

former_member186338
Active Contributor
0 Kudos

Hi Rohit,

Ups, the absolute rule is: node (member that has children) can't have a dimension formula. Node will aggregate the values of children...

Also, base member with a formula can't be a children of some node.

Vadim

former_member186338
Active Contributor
0 Kudos

And if you want to change a member from node to the base member with a formula, sometimes it's better to delete the node and recreate a base member.

Vadim

former_member221145
Participant
0 Kudos

hi Vaidim,

I have found in the SAP note 1356081 that both Account and Category dimension should not have formulas.

In addition to the above here is the hierarchy I have

  K_ALL No Formula

     K_COS_GROUP No Formula

 

        K_COS_LTBOM_FUTPRC No Formula

  

          K_COS_LTBOM_FTPRC_PK ( Has formula)

Regards,

Rohit

former_member186338
Active Contributor
0 Kudos

Hi Rohit,

I haven't read this note (will do it on Monday), but the message is clear. About your hierarchy:

If K_COS_LTBOM_FTPRC_PK is a child of K_COS_LTBOM_FUTPRC, the it can't contain formula. And thinking theoretically what do you mean by formula on the children? The formula will be calculated only at the time you run a report with this member. The result of formula can't be aggregated in the parent node...

B.R. Vadim

former_member186338
Active Contributor
0 Kudos

Hi Rohit,

The statement "I have found in the SAP note 1356081 that both Account and Category dimension should not have formulas" is not 100% correct, the note do not recommend this because of performance issues:

"3) Try to avoid having dimension member formulas on multiple dimensions (for example, do not have formulas on say, the Account dimension and the Category dimension, at the same time)."

Anyway, it's better to have dimension formulas only in the account dimension due to performance reasons and compare categories on the report level (using Excel functions...)

B.R. Vadim

former_member221145
Participant
0 Kudos

Hi Vadim,

Thanks for your help,  The same dimension formulas worked in BPC 75 MS version, but I am facing the error in NW version.

Regards,
Rohit

former_member186338
Active Contributor
0 Kudos

There is a huge difference between MDX in MS and NW versions of BPC (especially in performance).

In general, as it's correctly stated in the mentioned note, the dimension formulas have to be used for KPI calculations only (like MEMBER1/MEMBER2), because it's the only solution to get correct results on nodes. For the rest - script logic and Excel formulas are preferred solution today. May be in future with HANA and new HANA MDX the things will change, but...

B.R. Vadim