How to load selective request from PSA to DSO in 3.5?

[Former Member]

Hi Gurus!

I am in BW 3.5 and loading daily DELTA loads from PSA to DSO and then to the Cube1 and Cube2.

Let's say we have 3 requests: #1 is the earliest and #3 is the latest.

PSA has request #1, and request #3 (it has no data and I am not sure that this is correct). Request #2 deleted.

DSO has only request #3 and it is not activated.

Cube1 and cube2 are not updated at all.

Should I first load request #1to DSO? and then update the Cubes? If yes, then how can I do this if i already have request #3 in PSA?

Next questions:

1. What should I do with request#2 ( not in PSA)?

2. If I delete request #3 from PSA (it has no data), will the next delta load (it will be #4) pick up #3 too?

Please advise

Thank you in advance!

Olga

[KamalMehta · Accepted solution]

Hi ,

I would suggest that you can keep the request which has been successfully updated in all the data targets.Delete all the other request from all the targets including the PSA .Then you can run the repair full to PSA and then update the same to all the above data targets .

In this way all the request would get successfully updated to all the data targets .

Also going forward delta is also managed .

Thanks

Kamal

[Former Member · Accepted solution]

Thanks, Kamal. I will try this.

So, the last good request in PSA is 1/6 and the last good request in DSO and Cubes is 1/5. So, i will delete 1/6 in PSA and then do the full repair load to PSA first.

Now, FULL repair..

I will change Processing in Infopackage to 'PSA only' and Update to 'Full Update'

Then in menu in Schedular I will check 'Repair Full Request' .

And the question is: will this FULL repai bring duplicated in PSA (i have good PSA up to 1/5 and need dta from 1/6 - 1/10)?

What changes should I make in DSO in order not to load duplicated to DSO too?

I understand that Cubes will NOT have any duplicates anyway.

Please advise.

And thank you!!

Olga

[Former Member · Accepted solution]

Hi,

definately full repair will bring in duplicate records.

full repair is nothing but a full load which does not disturbs the delta indicator.

what you should do if you think records will get duplicated is first do a selective deletion of records for a particular selection and then run full repair for that selection. selective deletion will delete all records remaining in DSO for that particular selection and full repair will reload all records again and there will be no duplicacy.

Regards,

Neeraj.

[KamalMehta · Accepted solution]

Hi Olga ,

Your ODS is overwrite right . Frist level ODS is normally overwrite ODS . You can check the rule type related to Key figures such as Quantity etc to validate the same .

In short you can update all the request from the PSA to ODS even if there are some request which are already updated as it is an overwrite ODS . Duplicate records would get overwritten automatically .

Also do check and make sure that your delta DTP from ODS to Cube is picking from Chnage log table .If it is from active table then you might get duplicate records in Cube as well because Delta DTP would run and check if there is any request in the source which is not updated to the target it will pull that to the cube .

Hope it helps .

Thanks .

Kamal

[Former Member · Accepted solution]

Hi Kamal,

How to check that 'delta DTP from ODS to Cube is picking from Change log table'?

I am in 3.5...

Thanks,

Olga

[former_member210615 · Accepted solution]

hi,

go in your DTP -> extraction tab, just check extraction mode is delta or not

if delta option is selected then below you will see option "change log" and

In 3.5 when delta is selected data is picked from changelog ehile when full then data picked from Active

hope it helps you

regards

laksh

[Former Member · Accepted solution]

Ok, thank you, Laksh

[Former Member]

Hi Olga,

Should I first load request #1to DSO? and then update the Cubes? If yes, then how can I do this if i already have request #3 in PSA?

: in BW 3.x you can load specific PSA request in target, there is not DTP, you have do using scheduler of PSA itself. So sure you can do it

Next questions:

1. What should I do with request#2 ( not in PSA)?

:- Nothing, keep request#2 till you want it there...

2. If I delete request #3 from PSA (it has no data), will the next delta load (it will be #4) pick up #3 too?

:- Deletion of data in BW does not impact the Delta functionality, Delta is totally managed in Source system. So there is no impact on delta, once request/data comes to BW it will not take that data in next delta load.

Regards

Ganesh

[Former Member]

Ganesh,

So, If I delete a request in PSA (and in targets), will the next load bring it (the deleted one) to PSA again? Or will it be lost? Still not clear on this..

Olga

[Former Member]

Hi,

once delta is loaded into BW , it will set the delta indicator in source system till where the data has been loaded into BW. if you delete data from BW ( PSA or any data target ) , it won't reset the delta indicator back to the previous position.

in short if you delete data from BW then data is lost if it is a delta load.

you will have to do a full repair ( with relevant selections ) to get the data back ( this will not disturb your DELTA )

Regards,

Neeraj.

[Former Member]

Ok, i undertand, thank you.

[former_member188080]

Hi,

Yes in 3.5 selective loading is possible..

You can update request by psa by psa request..you need to schedule it accordingly..

also if you delete the latest delta request which is yellow for eg.. you can delete that yellow request,for some reason it is not completed..that means say timeout occured..when you will fetch next delta say 4# it should bring previous delta as well in repeat delta method..

Thanks and regards

Kiran

[Former Member]

Request#3 is green (but has 'no data'). If I delete it, will the next request #4 bring request #3 to PSA in this case?

Thank you