Quantcast
Channel: SCN: Message List - ABAP Connectivity
Viewing all articles
Browse latest Browse all 3125

Issue when the loading records are more than 40000 in SAP BPC

$
0
0

Hi All,

 

This question is related to BPC ABAP.

 

Let me explain the scenario first:
We are using the standard process chain(/CPMB/IMPORT) to load the records into the cubes. In one of the step(LOAD) of this process chain, we have set the package size as 40000.

So when the user tries to load more than 40000 records, system will take the records in chunks of size 40000. For example: if user tries to load 86000 records into the cube. system first take 40000 records first and then next 40000 and the remaining 6000 in the next.

 

So In our BADI, we need to show how many records the user is trying to load and the number of accepted records and the rejected records after the validations, like shown below:
***package summary****

----------------------------------

Number of Total Records : ***********

Number of accepted records : ************

Number of rejected records : **************

 

So In our case, the log should be as follows

***package summary****

----------------------------------

Number of Total Records : 86000

Number of accepted records : 86000

Number of rejected records : 0

 

But since system is taking this 86000 in 3 chunks, logs are showing only for the last chunk, for example

***package summary****

----------------------------------

Number of Total Records : 6000

Number of accepted records : 6000

Number of rejected records : 0

 

I tried to use a private variables(for total,accepted,rejcted)in the logic, so when each chunk runs, those variable will be updated and will show the correct details at the end. But those variables are getting initiazed before each chunk runs.

 

Please provide your thoughts on how to handle this scenario....

 

 

Thanks,

Amaresh K


Viewing all articles
Browse latest Browse all 3125

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>