Locking users and Early delta initialization - any experience ?

[bhat_vaidya2]

Hi,

I am under immense pressure from business to reload selected sales orders that have been deleted from Cube and DSO in BW via selective deletion. The business is 24X7 and they don't want to lock users out of the system.

I came across below blog which says that I don't have to lock users if I do early delta initialization and repair full load.

Does anyone have the experience of early delta initialization without locking users.

Explore to SAP Business Warehouse/Analytics: Setup Tables filling without Locking Users in SAP BI

Early Delta Initialization:

In this one we do the initialization before filling setup tables. So that users can post the records when we are performing setup tables filling. we will get the posted records in next delta run.

In this method we need to do the below steps.

i) Run the Info Package with option " early delta initialization". This will enable the delta queue and setup the timestamp for delta in system

ii) Delete the data in setup tables for specific application component

iii) Fill the setup tables.

iv) Load the setup tables data to BI using full repair IP.

How to check whether Data source supports for Early Delta Initialization?

We can check this in table ROOSOURCE.

i) Go to SE16 --> table name and enter

ii) In the next screen give the data source name and execute.

iii) If field ZDD_ABLE in the result has value X, then data supports for early delta initialization.

iv) If it has space, then it doesn't support.

My extractor supports early delta initialization

[bhavinvyas · Accepted solution]

Hi,

Check this one, same scenario as yours

Fill setup tables without locking users | SCN

Thanks,

Bhavin Vyas

[bhat_vaidya2 · Accepted solution]

Hi,

Thanks for your response. I tried to do Early delta iniitialization and it is asking me to "Delete init. request before running init. again with same selection".

This is something that I am trying to avoid inorder not to mess up the delta load.

what are the steps to prevent this ?

- Bhat

[Former Member · Accepted solution]

Why would you re-init if you have a correct running Delta.

Just fill the setup table with the missing (deleted) sales docs and do a full load of those to BW.

[bhat_vaidya2 · Accepted solution]

Hi,

When I try to change the infopackage, it is saying data delta already loaded for request.

thanks,

Bhat

[bhavinvyas · Accepted solution]

Please make new info package for full load with repair full option.

Thanks,

Bhavin Vyas

[bhat_vaidya2 · Accepted solution]

Hi Tom, but it will require downtime to do delete and fill setup table and do a full load. But business doesn't want to have downtime now hence why I am considering using early delta INIT which I haven't done before.

[Former Member · Accepted solution]

Why do you think you need downtime for such a repair action? You cna do it without locking users or forcing downtime:

• You don't touch your delta process, so all changes are still being captured and can be pulled to BW in the daily delta load.
• For filling the set-up table, no down time is needed technically (and in this scenario also not functionally)

[bhat_vaidya2 · Accepted solution]

Hi,

I am getting confuse. Must blog that I read it says that users should be locked out to avoid missed documents during the filling of setup tables. Technically,I can fill setup table and load full load and the delta process will continue as normal. but as rule of thumb, it is recommended to lock users out and avoid missed documents.

The only way to avoid locking the users out is if early delta INIT is used as per below blog.

http://explore-sapbw.blogspot.in/2012/01/setup-tables-filling-without-locking.html

Are you saying that it is safe to fill setup table, not lock the users and do full load without loss of data ?

thanks,

Bhat

[Former Member · Accepted solution]

I think your confusion comes from the difference in scenario:

* when you do a fresh init of your application in BW, you will indeed be worried about missing docs etc, end decide on locking users for a specific period of your process

* however, in your scenario, you already have a working delta flow, so no need to worry about 'missing documents'. Your delta is active, any change or creation will be captured in the queue, regardless of what you do with a repair load.

What you will do is actually supplying a little additional delta to BW that you create yourself: you decide which documents you want the latest status to go to BW by putting them in the setup table and then loading them to BW with a full package. Once in the PSA you will treat it as a delta, meaning pushing it throiugh your model and letitng the system decide wether this is a new or changed or unchange document (in your scenario he will interpret it as new ofc).

I hope now it is clear why it is safe to do this without locking or downtime.

[bhat_vaidya2 · Accepted solution]

Hi, Just one more thing. I am filling the setup table via dialog and would like to cancel it because I got the selections wrong. How do I do it ? thanks, Bhat

[Former Member · Accepted solution]

Top left of your screen : left click on the little icon and choose 'Stop Transaction'.

Don't forget to delete your setup table agian before restarting the filling

[q_raith · Accepted solution]

This message was moderated.