Create work status report in BPC embedded planning

[former_member187400]

Hi All,

I am working on BPC Embedded planning for BW 7.4 SP14, and Analysis Office (AO)  2.3.

I'd like to develop the Work status report in Analysis Office (we don't use standard work status report in the BPC Web client).

Work status generate Virtual Provider. I can create Composite Provider on top of Virtual provider.

The issue is the status info object is a key figure. Hence, if I extract the report, it shows status with the number - it's difficult to understand by user. I need to extract the text for this.

E.g.

Date	Cost Center	Status (key figure)
10 Jan	100101	1
10 Jan	100102	1
10 Jan	100103	2
10 Jan	100104	0

0: not started

1: in progress

2: completed

There is option: Extract virtual provider to DSO via APD, it works,  I can get the text for it, but it's not real time (need to trigger data extraction) .

We want to have a real time one.

1. Do you have any suggestions what the solution for this?

2. I am thinking to create analysis view.

But I don't know how I can get the hana work status table, and join it to the text for status.

If you have an experience to create analysis view by joining virtual provider, and master data table. Could you kindly please let me know step-by-step to do it?

Kindly please ask your advice, and very much appreciated

Many thanks

[gregor_dieckmann · Accepted solution]

Hi Daniel,

the BPC work status table is generated and building a HANA view on top you might have an issue with life cycle (i.e. transports and maybe with the technical name of the generated table).

It would have been the most flexible solution if work status table would have been a DataStore-Object, then any kind of reporting functionality would be not problem.

Using the work status table in a HANA view might also lead to issues since you would miss the BPC logic to compute the 'status'. Thus you can create another virtual provider on top of the BPC generated virtual provider for work status and in your implementation you move the 'status key figure' to a 'work status' characteristic. If you have not too many work status relevant dimensions the performance of this solution should be no issue.

Regards,

Gregor

[former_member187400 · Accepted solution]

Hello Gregor,

Many thanks for the feedback below

Gregor Dieckmann wrote:

Hi Daniel,

the BPC work status table is generated and building a HANA view on top you might have an issue with life cycle (i.e. transports and maybe with the technical name of the generated table).

It would have been the most flexible solution if work status table would have been a DataStore-Object, then any kind of reporting functionality would be not problem.

Using the work status table in a HANA view might also lead to issues since you would miss the BPC logic to compute the 'status'. Thus you can create another virtual provider on top of the BPC generated virtual provider for work status and in your implementation you move the 'status key figure' to a 'work status' characteristic. If you have not too many work status relevant dimensions the performance of this solution should be no issue.

Regards,
Gregor

I will try, and revert back to you .

Many thanks ,

Daniel

[former_member187400 · Accepted solution]

Hi Gregor - 

Many thanks for your help.  I tested,  and it worked. 

Btw,  I want to develop the report via Calculation View.  How can I build it?

1. I have the generated Work Status Virtual Provider, and

2. Info Object master data containing the text of status, 

If I created New Calculation View, 

a.  I will create project for both Work Status,  and Master Data Info Object -  but can project have data source for Virtual Provider?

b.  and,  I joined both Work status,  and Master Data, 

c.  and I created work status on top for Virtual Provider, 

d.  and I reported the Virtual Provider. 

Do you think these above plan works?

If not,  are you OK to share what it should be?

Many thanks, 

Appreciate much your help,

cheers,