How to identify the data source of the request in BPC cube

[Former Member]

Hi:

I have to write a code to delete some specific requests in BPC cube. But there are too many requests in the cube and those requests have no data source that I cannot tell which one should be deleted.

Could anyone tell me is there any table to store the relevance of these requests and data source or is there any other good ways to identify the date source of these requests? Thank you!

[former_member200327]

Can you please clarify what did you mean?

How data got into that cube: using BW data load or using BPC tools?

If you use BPC tools then records from many datasources can be in one request and load from one datasource can go into multiple requests.

If you just need to delete records that have a particular datasource you have 2 options:

1. BPC option - run Clear package and then Light Optimization with zero elimination.

2. BW option - run Selective Deletion.

[Former Member]

Hi Gersh:

Thanks for your reply. We use the BPC tools to load staging cube data into BPC cube.

Is there any chance to know the request ID in BPC cube from which staging cube? Thanks a lot~

[former_member186338]

I Think the answer is No!

[manohar_pappireddy]

Hi Chen,

One more point to consider,if you had run LO job all the data from F Fact table moved to E table.

Though you see request numbers in the cube,the data is not available request ID wise any more.

The request ID would be blank for compressed data.

Regards,

Manohar

[former_member200327]

Still not clear in which cube you want to know request ID: in BPC cube or in staging cube? But really request ID doesn't have any meaning in rel-time (BPC) cubes. In basic cubes it plays a role of some unit of work, like a single load. In BPC cube records are grouped in a request just based on number of records processed. Hence knowing request number of something doesn't provide you any information.

If you want some process to put records in a separate request you should close open request, run your process and close open request again. Then if nobody else is posting anything at same time you have a chance to know request IDs of your records.

Otherwise - no way.