Skip to Content
0
Jan 29, 2020 at 10:30 AM

Runalloacation behavior change after upgrading to BW 7.5 (and BPC 10.1)

86 Views

Hello experts.

SAP_BW / 750 / 0016 / SAPK-75016INSAPBW / SAP Business Warehouse

Current K2 calculation engine is JAVASCRIPT.

After an upgrade of the BW component it looks like the runallocation behavior has changed.

Previous components versions was :

CPMBPC / 801 / 0018 / SAPK-80118INCPMBPC / CPM Business Planning and Consolidation

SAP_BW / 731/ 0013 / SAPKW73113 / SAP Business Warehouse

HANABPC / 801 / 0016 / SAPK-80116INHANABPC / SAP BusinessObjects BPC Accelerator for

For example this script ...

*XDIM_MEMBERSET ACCOUNT = R1210
*XDIM_MEMBERSET AUDITTRAIL = INPUT
*XDIM_MEMBERSET CURRENCY = %CURRENCYSET%
*XDIM_MEMBERSET ENTITY = E999
*XDIM_MEMBERSET FLOW = CLOSING
*XDIM_MEMBERSET MANAGERIAL = %MANAGERIAL_SET%
*XDIM_MEMBERSET METRICS = PERCENTAGE
*XDIM_MEMBERSET PHASE = $MYPHASE$
//*XDIM_MEMBERSET PRODUCT = %BRTYPESET%
*XDIM_MEMBERSET SOURCING = SOURCINGND
*XDIM_MEMBERSET TIME = %Y_ATTR%.12 // %Y_ATTR% value is 2019 here


*FOR %loop_BRT% =  %BRTYPESET%
*RUNALLOCATION
*FACTOR = 1
*DIM         PRODUCT     WHAT = %loop_BRT%_I ;   WHERE = BAS(%loop_BRT%)
*ENDALLOCATION
*NEXT

*COMMIT

... was working as expected before upgrade.

After upgrade, the script is posting records on other accounts than R1210. It looks like the ACCOUNT xdim_memberset is just ignored.

If I add this line in the runallocation ...

*DIM         ACCOUNT     WHAT = R1210 ;          WHERE = <<<  //test

The script behavior is back to what I need.

Is it a known side effect of BPC and/or BW upgrade ?

If yes, is there a parameter to be changed in background configuration somewhere ?

(if there is no way to come back to previous behavior, I'll have to update and retest lots of existing scripts)

Thanks in advance for your help.