Restrict RUNALLOCATION to WHAT account

[former_member341535]

BPC 10.1 SP09, BW SP14, HANAREV 102.6

Dear experts,

I have an issue with a RUNALLOCATION and was wondering if this was working "as design" and how I could overcome this (still using RUNALLOCATION)

I have reproduced my issue on ENVIRONMENTSHELL.

At first here is the data I have:

Quantity (VVQ03) Price (PMV_S) Turnover (VV010)

ProductA 10 5 50

ProductB 20 6 120

ProductC 30 7 210

In another input screen user can force an other price (another account is used there: long story on why, we are disagregating data on CLIENT dimension therefore could not use the same account)

Price 2 (PMV_S2)

ProductA 8

ProductB

ProductC

A RUNALLOCATION then calculates the new Turnover.

Script is launched for all 3 products.

*XDIM_MEMBERSET ACCOUNT=PMV_S2

*XDIM_MEMBERSET AUDITTRAIL=Input

*XDIM_MEMBERSET CATEGORY=Actual

*XDIM_MEMBERSET INTERCO=ThirdParty

*XDIM_MEMBERSET PRODUCT=BAS(TotalProduct)

*XDIM_MEMBERSET RPTCURRENCY=LC

*XDIM_MEMBERSET TIME=%TIME_SET%

*RUNALLOCATION

*FACTOR=USING

*DIM ACCOUNT WHAT=PMV_S2; WHERE=VV010; USING=VVQ03

*ENDALLOCATION

However, even though there is data only for ProductA in the WHAT, the RUNALLOCATION finds data for all three products in the USING and therefore calculates 0 in VV010 for ProductB and ProductC.

I do not want to use syntax WHEN/ENDWHEN for performance problems.

Any idea ?

Thanks

Camille

[former_member341535]

I need to keep the turnover previously calculated for the product where no new price was entered.

[Former Member]

So the user will not just enter the old price again, if its not changed in the other input form????

[former_member186338]

But how it was previously calculated???

Using the same multiplication?

Then you will get the same result... No issues!

[former_member341535]

Thanks Vadim,

This is what I thought. We will write a custom mogic with HANA procedure then.

WHEN/ENDWHEN is a performance killer (this allocation takes 9s written in RUNALLOCATION versus 4 mins written in WHEN/ENDWHEN ...

Anyway thanks again.

Camille

[former_member186338]

But I am unable to understand the required logic - what is wrong with zero written by RUNALLOCATION??

P.S. Please delete duplicate answer!

[former_member186338]

"However, even though there is data only for ProductA in the WHAT, the RUNALLOCATION finds data for all three products in the USING and therefore calculates 0 in VV010 for ProductB and ProductC." - this is a correct behavior by design of RUNALLOCATION. Nothing can be done. Use WHEN/ENDWHEN.