Loading Zero-Value Data into EPM Applications

[former_member1094799]

Need to load zero-value records from BW source to EPM app, AND copy these zero-value records to another EPM app. After implementing Note 1874809 (setting Environment parameter DM_WRITE_ZERO_DATA to '1'), we successfully load zero-value data from BW source to EPM app #1. But, when trying to copy the same zero-value data to EPM app #2, the data is not copied.

We are executing /CPMB/DEFAULT_FORMULAS_LOGIC and using RUNLOGIC_PH to copy records between the two applications. We are using the logic script because we need to transform YTD data in app #1 to periodic data in app #2.

Is this (copying zero-value data from one EPM app to another) just not allowed ? Or, is the logic script causing the problem somehow.

Appreciate any feedback, advice.

[damovand]

Hello Joe,

We found note 1607231 - K2: script logic can not save ZERO data but it seems that the records with zero values are not sent from the source cube. Please add *WHEN_REF_DATA = MASTER_DATA to the script. This will slow down the process because it’s going to send zeroes for non-existing records as well.

Please let me know if either the note or including the additional statement resolves this issue. Thank you

Best Regards,

Leila Lappin

[former_member186338]

Sorry, but I still see no reason to store zero's. Just an example:

1. Load data to BPC for some period.

2. Found that load is incorrect (some values don't need to be loaded)

3. Clear loaded data - a lot of zero's generated

4. Reload data with some values missing

5. You will still have zero's for missing values

In this case Lite Optimization with zero elimination is used to remove all zero's.

In general - don't load zero's - useless!

About YTD->Periodic conversion - please read my blog: https://blogs.sap.com/2018/11/02/periodic-ytd-conversion-using-script-logic-in-bpc-nw/

[former_member1094799]

Thank you for your comments Vadim. I have worked with OLAP technology for years and optimizing cubes is a big part. But there is a valid business reason. We know it's not the best design (data in two places), but it's a temporary solution with a large, redesign project on the horizon.

Here's the data flow:

1.EPM cube #1 pulls YTD balances for Balance Sheet accounts from BW source #1
2.EPM cube #2 pulls periodic data for P&L accounts from BW source #2 (P&L also has cost center value, which B/S does not)
3.to get B/S data from EPM cube #1 to EPM cube #2 (done to bring all data together in periodic), we run a logic script using runlogic_ph that calculates the periodic value of the B/S data (current month minus previous month) and sends to the destination cube #2

Zero-value data from BW is being loaded into cubes #1 and #2. The zero-value calculated data is not being sent/stored in cube #2.

[former_member1094799]

It is a business requirement. Zero "balance" indicates transaction activity that nets to zero, as opposed to no entry.

[former_member186338]

Strange requirement! The general concept of BPC is that there is no difference between no record and zero record!

Can you explain the business case in details?

[former_member186338]

"Need to load zero-value records from BW source to EPM app" - sorry, but why do you need to load zero values? It's a bad idea in general!

P.S. There is something wrong with your logic... try to explain!