How to do "early delta initialization" in ODP-enabled DTP

[Loed]

Hi guys,

This is for 2LIS extractors......Since we don't need a downtime of ECC for using "early delta initialization" in infopackage, can we also do the same in DTP which is ODP-enabled?

So these are the steps when doing the "early delta initiliazation" setup in INFOPACKAGE:

1) Run the Info Package with the option "early delta initialization".

2) Delete the data in setup tables for specific application component.

3) Fill the setup tables.

4) Load the setup tables data to BW using full repair INFOPACKAGE.

5) Run DELTA INFOPACKAGE for the next DELTA data.

Just want to clarify if we can also do the "early delta initialization setup" in ODP-enabled DTP?

Which of these are correct???

OPTION1

1) Run the DTP with DELTA option delta init without data.

2) Delete the data in setup tables for specific application component.

3) Fill the setup tables.

4) Load the setup tables data to BW using DELTA DTP.

5) Run DELTA DTP for the next DELTA data.

OPTION2

1) Run the DTP with DELTA option delta init without data.

2) Delete the data in setup tables for specific application component.

3) Fill the setup tables.

4) Load the setup tables data to BW using FULL DTP.

5) Run DELTA DTP for the next DELTA data.

OPTION3

1) Delete the data in setup tables for specific application component.

2) Fill the setup tables.

3) Load the setup tables data to BW using DELTA DTP.

4) Run DELTA DTP for the next DELTA data.

OR

What are the correct steps to do it? From what I read, if we will be using ODP-enabled DTP, we still need to have a downtime in ECC. Is that correct? Something like this:

1) Downtime in ECC.

2) Delete the data in setup tables for specific application component.

3) Fill the setup tables.

4) Load the setup tables data to BW using DELTA DTP.

5) Run DELTA DTP for the next DELTA data.

Thank you,

Loed

[ashuetrxsap]

striker_wbb Did you get a workaround to this ?
I dont think we have early delta initialization in ODP based on DTP

[Loed]

Sorry not sure if it also present for ODP.

Did you get some info?

[Loed]

Any help?

Thanks.

Loed

[former_member534639]

Hello,

Actually I have many ideas, but I need to understand what you mean by downtime in this scenario? As long as delta data is not created or requested by any user or application during this process of setting up the DataSource, I don`t see why would happen a downtime. What I would do automatically would be -

1. replicate datasource in BW

2. trigger delta init using ODP connection to respective Source System.

3. fill the setup table and do a full load.

this is not the only option though.. you can fill setup table and then do the delta init with data transfer. Feel free to elaborate so I can help further.

Cheers!

[Loed]

Hi Tania,

We lock users because we might miss records posted by them while filling the setup table.

Check this blog:

http://saptechbiw.blogspot.com/2013/09/early-delta-initialization.html

I based my question on the "early delta initialization" setup in infopackage if we can also do that in ODP-enabled DTP.

So using INFOPACKAGE, these are the steps to avoid locking of users:

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.

Can we also do the same in ODP-enable DTP? If yes, how to do it properly? Which is correct in the options I mentioned in my thread? Or what is the best practice to mimic the "early delta initialization" function of infopackage?

Thanks.

Loed

[Loed]

Hi taniadiasr

Any help?

Thanks.

Loed