Management of this kind of scenario

[amine_lamkaissi]

Hi experts,

I was wondering how I can manage this scenario in BW. I would like some advices regarding your experience to avoid complex developments (may be some of you already have this case).

I want to manage planned data in a particular way:

Let’s say in ECC, we are on February 2013, planned data for WBS A is like following:

February 2013	500
March 2013	500
Total	1000

In BW easy, I need to see the same 1000.

But, In March, they changed in ECC the planned data as following:

February 2013	700
March 2013	700
Total	1400

So here it becomes more complex . If we launch the report in February we should show 1000. But if I launch it in March I should display 1200.

So it’s like keeping a snapshot of the past.

I tought about copying data from a month to another.

What advices can you give me for my scenario?If you have any useful links or scn articles I will appreciate it.

Thanks.

Amine

[Former Member · Accepted solution]

Hi Amine,

Have a look at non-cumulative key figures.

However I suggest a simple solution to this. For each month you want to maintain the values that are coming from source. Hence add a char like 0calmonth to your target. In transformation set it to current month. This new field should be in the keys of your target dso. Now onwards each of your records will be maintained with an extra month value. Add this month to your cube and multiprovider as well. In query create the variable on this field.

This way the delta will also work. For a month if the planning values come two times, only latest value will be retained. If a delta comes next month then a new record will be created.

This solution will allow you to maintain a snapshot but will increase number of records.

Regards,

Sujit.

[amine_lamkaissi]

Thanks guys for your contributions.

Amine

[Former Member]

Hello ,

You may consider putting additional info object in data target lets say "ZCALMONTH". Value of this will be derived by extraction date and updated in data target. (Derived from Snapshot Date)

When we report on this information provider, instead of referring to calmonth from source, we would have to refer to calmonth of newly added info object and it should work fine.

Regards

Nimesh Kapadia

[Former Member]

Hi,

This scenario is pretty common and can get really more complex. But lets focus on your scenario only.

Possible data flow in BW :-

ECC --> BW (ODS) .

Keep a calday on your ODS. This will help us track on which specific day changes were made.

Also add one version field which will keep track of version changes. This version will be updated based on certain logic (ABAP Code). You can do this while loading data into ODS in End routine.

Now load data to ODS on a daily basis..

In report level you need to use restricted key figure to display the output accordingly with the help of customer exit variable to fetch latest data for month of march and old data for february(if report runs of march). Use System date to find out which month needs to be displayed.

let me know if this helps you.

Regards,

Anup