Tuple Expression in BPC NW

[nicky_hays]

Hi,

I am running BPC10.1 Engine Javascript

When I validate or execute the following code. I get the error: Unknown dimension in keyword "[CATEGORY].[FORECAST:

Can't I use tuples like this?

Sincerely,

Nicky

*SELECT(%YR%,"[YEAR]",CATEGORY,"[ID] = FORECAST")

*SELECT(%PYR%,"[YEAR_PRIOR]",CATEGORY,"[ID] = FORECAST")

*XDIM_MEMBERSET CUSTOMER AS %CUS% = BAS(SAME_VALUE)

*WHEN PROFIT_CENTER

*IS BAS(ALLPRODUCTS)

*FOR  %CNT% = .07,.08,.09,.10,.11,.12

*FOR %CUST% = %CUS%

*REC(EXPRESSION=(([TIME].[TMVL(0,%YR%%CNT%)],[CATEGORY].[FORECAST],[ACCOUNT].[INFLATION],[CUSTOMER].[C_NONE]) * (([TIME].[TMVL(0,%PYR%%CNT%)],[CATEGORY].[ACTUAL],[ACCOUNT].[BAS(SALES_ACC)],[CUSTOMER].[%CUST%]) + ([TIME].[TMVL(0,%YR%%CNT%)],[CATEGORY].[FORECAST],[ACCOUNT].[COGS],[CUSTOMER].[%CUST%]))), ACCOUNT=INFLATION, AUDITTRAIL=CALC_INPUT, CATEGORY=FORECAST, TIME=TMVL(0,%YR%%CNT%), CUSTOMER=%CUST%)

*NEXT

*NEXT

*ENDWHEN

[Former Member · Accepted solution]

Hi,

You definitely can't use BAS inside a tuple. If you need a total of all members under SALES_ACC just put that Node in the tuple.

What is the purpose of using TMVL (0,...)?

[damovand]

Hi Nick,

According to the logic primer (a few years old) the tuple expressions can be used only in MDX expressions and *REC statement is a statement used in SQL based commands.

Please see the following links for more information

http://scn.sap.com/thread/3618809

http://help.sap.com/saphelp_bpc10_nw/helpdata/en/7d/ac04e9e83340089ecaa4bdf32f7d84/content.htm?frame...

Regards,

Leila

[nicky_hays]

Hi Leila,

Thanks for replying.

If I go to the following link, I see the below example. They are using SAP "SQL" logic rather than MDX which I am also using in my code. But then why do I keep getting the error: Unknown dimension in keyword "[CATEGORY].[FORECAST:

FORECAST is a member id in the Category dimension.

*REC - SAP Business Planning and Consolidation, version for SAP NetWeaver - SAP Library

[damovand]

Hi Nick,

I think to debug this you should simplify the expression and remove expression in the TMVL, replace it with a hard coded values.  Reduce the size of the expression to just the first part and validate.  If it validates correctly then we know that the problem is not in [CATEGORY].[FORECAST]

Regards,

Leila

[nicky_hays]

A weird problem. Sometimes it works and sometimes it does not. I am opening a ticket with SAP.

Nicky

[nicky_hays]

Please help!!!

Nicky