SAP Knowledge Base Article - Preview

1785586 - Variance in expected values when using offline distribution: BPC-MS and NW

Symptom

When using Offline distribution to distribute and collect data, the collection operation of the worksheet will send only those cells that are different from the initial value when the report was generated.  These values will then be compared to the current values in the database and only the delta values between what is sent from the worksheet and the database will be written.

This results in a limitation in multiple collections that reference the same underlying data as it is impossible to send the initial value in the report.

For instance, if the initial data in the database is zero at the time of the report distribution, it will be impossible to set a cell back to zero via the distributed report if it is changed to another value.

Likewise, if the report is re-distributed after the value in the database is changed to 100, it will be impossible to send 100 back to the database to reset the value if it is subsequently changed to zero or 200.

Since there is no method to query the current value in distributed reports, it is important that the source data does not change by  another process (such as a data load) or via other distributed reports that reference the same data values.

Note also that when collecting reports, the success / failure count in the distribution wizard is simply a count of the cells with values that differ from the initial report values. This is not necessarily the same as the count of new rows that are created in the database, as the new rows will be generated based on the delta between the report value and the existing value in the database. This means that if you collect a report with 4 cells that have changed from the initial report, the count will be 4 and the initial send to the database (assuming that all 4 cells are different) will also be 4. If you then collect the same report again, the count in the wizard will still show 4 but no rows will be generated in the database as the value will match what is now in the database.

See the table below for a more detailed example of how this can result in values other than what would be expected from the report.


 

Account1

Account2

Account3

Account4

Send Count in Wizard
Compared to DB rows

Initial value in report

0

0

0

0

 

Input

100

100

100

100

4

SentToDB

100

100

100

100

4

Expected

100

100

100

100

 

Database

100

100

100

100

 

Input

200

0

300

100

3

SentToDB

100

 

200

 

2

Expected

200

0

300

100

 

Database

200

100

300

100

 

Input

100

0

0

0

1

SentToDB

-100

 

 

 

1

Expected

100

0

0

0

 

Database

100

100

300

100

 

Input

100

100

300

100

4

SentToDB

 

 

 

 

0

Expected

100

100

300

100

 

Database

100

100

300

100

 

Input

100

0

300

-100

3

SentToDB

 

 

 

-200

1

Expected

100

0

300

-100

 

Database

100

100

300

-100

 

Input

100

0

100

100

3

SentToDB

 

 

-200

200

2

Expected

100

0

100

100

 

Database

100

100

100

100

 

New report generated

100

100

100

100

 

Input

200

0

200

100

3

SentToDB

100

-100

100

 

3

Expected

200

0

200

100

 

Database

200

0

200

100

 

Input

100

100

200

100

1

SentToDB

 

 

 

 

0

Expected

100

100

200

100

 

Database

200

0

200

100

 

  


Read more...

Environment

  • SAP Business Planning and Consolidation 7.0 for the Microsoft platform
  • SAP Business Planning and Consolidation 7.5 for the Microsoft platform
  • SAP Business Planning and Consolidation 7.5 for SAP Netweaver
  • SAP Business Planning and Consolidation 10.0 for the Microsoft platform
  • SAP Business Planning and Consolidation 10.0 for SAP Netweaver
  • SAP Business Planning and Consolidation 10.1 for the Microsoft platform
  • SAP Business Planning and Consolidation 10.1 for SAP Netweaver 

 

Product

SAP Business Planning and Consolidation 10.0, version for Microsoft ; SAP Business Planning and Consolidation 10.0, version for SAP NetWeaver ; SAP Business Planning and Consolidation 10.1, version for Microsoft ; SAP Business Planning and Consolidation 10.1, version for SAP NetWeaver ; SAP Business Planning and Consolidation 7.0, version for Microsoft ; SAP Business Planning and Consolidation 7.5, version for Microsoft ; SAP Business Planning and Consolidation 7.5, version for SAP NetWeaver

Keywords

Offline Distribution, Collection , KBA , EPM-BPC-MS , Microsoft Version , EPM-BPC-NW , NetWeaver Version , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.