Consolidation Logic causing overflow errors

[houtbyr]

What exactly is happening in the CONSOLIDATION method?

*SELECT(%IC_FLOW%,"[ID]","FLOW","[DIMLIST] = 'CLO'")

*RUN_PROGRAM CONSOLIDATION
CATEGORY=%CATEGORY_SET%
GROUP=G_2001C
OTHER=[FLOW=%IC_FLOW%]
TID_RA=%TIME_SET%
*ENDRUN_PROGRAM

When I clear all data for a period and then run this statement, I get values in our F_OPE flow for opening balance. I've created a test script where this is the only logic statement that's running... so our actual consolidation logic isn't running for our closing balance so I can isolate what this program is doing.

When I run the script again, the F_OPE values then double... and running it a third time will produce 3X the original value. Instead of correcting the value and writing a delta record (0 if the values were the same so the total doesn't change), it seems to just be creating a new data entry each time for the entire value so it compounds and forever gets bigger.

When we run our consolidation script several times throughout the month, we eventually start getting warnings about overflows (at around the 10 trillion mark).

Excerpt from the Package Formula Detailed Log:

RUN CONSOLIDATION
Keyfigure (Signeddata) 10,052,799,870,067.7700000- is invalid due to overflow
Keyfigure (Signeddata) 10,113,202,022,144.5500000 is invalid due to overflow
Keyfigure (Signeddata) 13,479,699,376,612.0500000- is invalid due to overflow
Keyfigure (Signeddata) 13,538,452,500,538.6100000 is invalid due to overflow
Keyfigure (Signeddata) 14,979,687,541,470.0800000 is invalid due to overflow
Keyfigure (Signeddata) 14,979,687,541,470.0800000- is invalid due to overflow
Keyfigure (Signeddata) 15,012,776,853,151.5200000 is invalid due to overflow
Keyfigure (Signeddata) 15,012,776,853,151.5200000- is invalid due to overflow
Keyfigure (Signeddata) 15,017,018,836,518.4000000 is invalid due to overflow
Keyfigure (Signeddata) 15,017,018,836,518.4000000- is invalid due to overflow
Keyfigure (Signeddata) 15,049,898,304,935.0000000 is invalid due to overflow
Keyfigure (Signeddata) 15,049,898,304,935.0000000- is invalid due to overflow
Keyfigure (Signeddata) 15,418,809,806,963.0500000- is invalid due to overflow
Keyfigure (Signeddata) 15,419,528,578,754.8200000 is invalid due to overflow
Keyfigure (Signeddata) 15,649,144,500,000.0000000- is invalid due to overflow
Keyfigure (Signeddata) 15,651,220,913,788.7600000 is invalid due to overflow
Keyfigure (Signeddata) 19,398,576,390,518.2600000 is invalid due to overflow
Keyfigure (Signeddata) 23,987,005,444,828.5200000 is invalid due to overflow
Keyfigure (Signeddata) 26,151,685,540,051.1000000 is invalid due to overflow
Keyfigure (Signeddata) 58,606,787,629,894.4000000- is invalid due to overflow
Keyfigure (Signeddata) 66,963,094,137,845.5800000- is invalid due to overflow
Keyfigure (Signeddata) 66,963,142,446,410.2800000 is invalid due to overflow
15835  SUBMITTED, 15638  SUCCESS, 197  FAIL.
MESSAGE FROM DOING CONSOLIDATION
Keyfigure (Signeddata) 10,052,799,870,067.7700000- is invalid due to overflow
Keyfigure (Signeddata) 10,113,202,022,144.5500000 is invalid due to overflow
Keyfigure (Signeddata) 13,479,699,376,612.0500000- is invalid due to overflow
Keyfigure (Signeddata) 13,538,452,500,538.6100000 is invalid due to overflow
Keyfigure (Signeddata) 14,979,687,541,470.0800000 is invalid due to overflow
Keyfigure (Signeddata) 14,979,687,541,470.0800000- is invalid due to overflow
Keyfigure (Signeddata) 15,012,776,853,151.5200000 is invalid due to overflow
Keyfigure (Signeddata) 15,012,776,853,151.5200000- is invalid due to overflow
Keyfigure (Signeddata) 15,017,018,836,518.4000000 is invalid due to overflow
Keyfigure (Signeddata) 15,017,018,836,518.4000000- is invalid due to overflow
Keyfigure (Signeddata) 15,049,898,304,935.0000000 is invalid due to overflow
Keyfigure (Signeddata) 15,049,898,304,935.0000000- is invalid due to overflow
Keyfigure (Signeddata) 15,418,809,806,963.0500000- is invalid due to overflow
Keyfigure (Signeddata) 15,419,528,578,754.8200000 is invalid due to overflow
Keyfigure (Signeddata) 15,649,144,500,000.0000000- is invalid due to overflow
Keyfigure (Signeddata) 15,651,220,913,788.7600000 is invalid due to overflow
Keyfigure (Signeddata) 19,398,576,390,518.2600000 is invalid due to overflow
Keyfigure (Signeddata) 23,987,005,444,828.5200000 is invalid due to overflow
Keyfigure (Signeddata) 26,151,685,540,051.1000000 is invalid due to overflow
Keyfigure (Signeddata) 58,606,787,629,894.4000000- is invalid due to overflow
Keyfigure (Signeddata) 66,963,094,137,845.5800000- is invalid due to overflow
Keyfigure (Signeddata) 66,963,142,446,410.2800000 is invalid due to overflow
[INFO] GET_DIM_LIST(): I_APPL_ID="Finance", #dimensions=12
ACCOUNT,BUSINESS,CATEGORY,CURRENCY,DATASRC,ENTITY,FLOW,FUNCAREA,GROUPS,INTCO,MEASURES,TIME
#dim_memberset=6
TIME:2018.JAN,1 in total.
ACCOUNT:11100001,11100002,11100003,11100010,11120020,...1986 in total.
CATEGORY:ACTUAL,1 in total.
CURRENCY:USD,1 in total.
DATASRC:CS_TEMP,1 in total.
FLOW:F_CLO,1 in total.
REC :%value%*(1)
CALCULATION BEGIN:
QUERY PROCESSING DATA
QUERY TIME : 0.00 ms. 171  RECORDS QUERIED OUT.
QUERY REFERENCE DATA
CALCULATION TIME IN TOTAL :1.00 ms.
87  RECORDS ARE GENERATED.
CALCULATION END.

If the issue is unresolved and this keeps running, we get actual overflow ERRORS at around positive or negative 100 trillion which prevents ALL BW functions from working (clears, deletes, even UJBR backups). We've had to use some special programs provided from SAP that are somehow able to forcefully delete the largest data records causing the issue.

I thought maybe there was a copy being done from the closing to opening balances in the CONSOLIDATION method, but I can't figure out where these starting figures are coming from.

I tried to restrict the scope of the data in that statement to just F_CLO (as shown with the %IC_FLOW% variable above) but that doesn't seem to impact the outcome. F_OPE is still getting populated with values that keep stacking until it errors.

F_CLO is our FLOW_TYPE="CLOSING" and F_OPE is our FLOW_TYPE="OPENING" members.

What is this CONSOLIDATION method trying to do, and is there any way I can control or restrict the data that it ends up generating?? Or at least make sure that it's generating DELTA records when the logic is re-run instead of just posting the totals over and over again?

[houtbyr]

So the values it determines is based on the previous year end open and closing values.

[former_member186338]

Please read this note: https://launchpad.support.sap.com/#/notes/1941497

Also you can create a fresh copy of ENVIRONMENTSHELL and test CONSOLIDATION with it. Then you can increase complexity...

[former_member186338]

Sorry, but consolidation setup include a lot of settings and a lot of places to make an error 🙂

Nothing to discuss about script text!

And it's better to provide detailed version/SP info about your BPC and BW!

[houtbyr]

You don't have to tell me the consolidation set-up is complicated... I know that first hand lol. This is just the most recent example of my confusion.

So, does the CONSOLIDATION method more read your BPC configuration and execute things based on how it's set-up i.e. the issue is likely something configured incorrectly with BPC Administration like Business Rules or something?

We're running BPC 10.0 NW

CPMBPC 801-0015, HANABPC 801-0013, SAP_BW 740-0015