MDX logic issue (migrating from BPC 4 to 7)

[Former Member]

Hi Experts,

I'm trying to migrate this simple piece of logic from version 4 to version 7 of BPC (on SQL 2008). In version 4 (on SQL 2000) the code works perfectly while in version 7 does not post any figure. The only modification I've done to the original script was to specify the hierarchy number as the entity dimension (ENTITA) has two different hierarchies.

Does anybody know how I can fix this? Thanks

Simeone

*QUERY_TYPE = 2

*XDIM_MEMBERSET PROCESSO = QR_FASE6
*XDIM_MEMBERSET TEMPO = %SET%
*XDIM_MEMBERSET SCENARIO = %SET%
*XDIM_MEMBERSET DRIVER = NO_DRIVER
*XDIM_MEMBERSET CONTI = FILTER([CONTI].members, [CONTI].properties("FASE") = "FASE6")

*SELECT (%DEST6%, "[ID]", "ENTITA", "[FASE6] = 'X'")
*SELECT (%DRV6%, "[ID]", "DRIVER", "[FASE6] = 'X'")

*FOR %CDCDEST6% = %DEST6%

*BEGIN

[ENTITA].[H1].[#%CDCDEST6%] = ([CONTI].[C_TOT], [ENTITA].[H2].[FASE6], [PROCESSO].[TOT_DA_RIBALT]) * ([DRIVER].[%DRV6%],[CONTI].[DRV_PERC],[PROCESSO].[INPUT],[ENTITA].[H1].[%CDCDEST6%])

*END

*NEXT

*COMMIT

Edited by: Simeone Zanoli on Jul 5, 2011 3:00 PM

[Former Member · Accepted solution]

Hi,

I think a pretty easier approach would be to use the allocation engine with *ALLOCATION.

[Former Member · Accepted solution]

HI,

Thanks again for your input.

As I'm migrating an application which has already been developed and has been working for a few years with this logic (at the time we developed it, the standard allocation logic was not available in BPC..), I'd rather keep the things as they are and use again the same logic: I don't see a reason why such s simple piece of code should not work.

Any other hint? Thanks.

Simeone

[JohnL · Accepted solution]

Hi Simeone

Can you please attach the log file to this message or if it is too large can you create a google word document and share the link with us?

Thanks,

John

[Former Member]

Hi,

I noticed %set% for tempo and scenario dimensions. How are you getting the values in this variable. Usually, if you want to pass members from DM package to the script, then your syntax should be %CATEGORY_SET% (just an example).

Secondly, you dont require BEGIN and END statements (though it will not make any difference).

Coming to the main part, did it validate succesfully? How does your log look like? Is this in your default logic?

[Former Member]

Hi, thanks for your reply.

I'm running the logic from the debugger and it validates and runs with no errors. It's not my default logic.

I left the %SET% syntax as that's how it used to work in BPC 4 but haven't tried running the script from a DM package yet so I'll keep in mind the %CATEGORY_SET% syntax you suggested, in case I get an error message from the DM.

What information do you need from the log exactly? ("looks" fine to me but it's too big to post)

Please let me know, thanks.

Edited by: Simeone Zanoli on Jul 5, 2011 5:50 PM

[Former Member]

Hi,

The script looks fine to me.

Can you please explain how the script is not working, with some example. What is that you need and how is the script behaving.

[Former Member]

Hi,

The script is not producing any result in the sense that when I run it, I get no posting at all (but also no error messages).

The task it's supposed to complete is pretty simple as it has to:

allocate costs --->

[CONTI].[C_TOT], [ENTITA].[H2].[FASE6], [PROCESSO].[TOT_DA_RIBALT]

on business units --->

[PROCESSO].[INPUT],[ENTITA].[H1].[%CDCDEST6%]

based on the value of a driver --->

[DRIVER].[%DRV6%],[CONTI].[DRV_PERC]

Through further investigation, I found out that if I substitute [ENTITA].[H2].[FASE6] with a leaf member (a member from the first hierarchy), the logic works. Can you figure out a way to workaround this? Thanks again for your help.

Simeone