Re-initialization

[Former Member]

Hey i have one q's

scenerio:

we are loading for two diff countries (US and europe).

The same LO-cockpit and CO-PA datasource is used by both the countries.

Now for europe we are having company code merger. So for this we require to delete all the contents for europe infoproviders and re-load all the stuff.

that will require to re-initialize all.That is to setup tables for LO-cockpit datasource and rest stuff.

Can we do this without affecting the US load where thy r using same data source and deltas already being thr in datatarget? i mean without re-initializing US stuff.

i have tried creating a dummy scenerio :

1.Create 2 diff ODS one for each US and europe.

2.Connect to R/3 system.

3.M using here both LO-cockpit and CO-PA extractors.

4.Created diff init with data transfer info packages with diff selections(specific to country) and uploaded the data.

5.Done delta for US country.

6.Deleted the contents for Europe.

7.Now i have to delete init req for europe n re-init for the same.

8.But as i delete the init, it wont further update my deltas for US country.(if the same datasource is used for both countries)

i can do this with downtime (Block users on R/3 side for particular duration n thn run setup tables). but this will consume much more time...

The minimum downtime can also be acquire using mirror image of my R/3 production system and run setup table from there and after that transferring the monitor entries to original R/3 system and then continuing with deltas.

But i do not want to re-initialize for my US datatragets that are using same datasources as Europe.

We are using both Lo-cockpit(SD,PP,MM) and CO-PA data source.

can anyone have help me slove this !!

Regards

Ankur

[Former Member · Accepted solution]

Hi Ankur,

No idea for CO-PA.

For LO when you need to init again and if DataTargets are different you can try to act as follow:

Delete set-up tables content.

Stop users.

Make job control run and upload in BW all Delta queues.

Start filling set-up tables.

Delete Init setting in InfoPachage (scheduler ...).

Upload Init in BW with selection for Europe with transfer of data (if you need to upload again all data for EU) and without data transfer for USA.

Start delta.

Make users start again.

Ciao.

Riccardo.

[Former Member · Accepted solution]

Hi

From one data source you can have only one init which will go to your data targets.

In your case :

1. Block users

2. Fill set up tables.

3. delete the init from data package , no need to delete data from ODS

4. Do a init without data transfer to both the targets.

5. run a full repair request with different selections for both the targets

6. now schedule the delta.

7. hope this helps !!

8. happy loading

Regards,

monika

[Former Member · Accepted solution]

Hi Monika,

great correction.

At step 3 you are referring to InfoPackage ?

At step 5 for full repair request with different selection you are referring to one with data transfer and one without data transfer ?

Let me know please.

Ciao.

Riccardo.

[Former Member · Accepted solution]

Hey

Riccardo,

"Stop Users" : it seems our Business users wont allow to stop R/3 transactions to halt. But i can do this by creating a mirror image and running up setup tables as mentioned in my earlier message.

i will test the scenerio provided by you and let you know.

Regards

Ankur Shah

[Former Member · Accepted solution]

hi riccardo

yes at step 3 delete init from infopackage.

new init without data transfer to both the data targets

at step 5 ful lrepair again for both with differet slections.

Am i missing something?

Regards

Monika

[Former Member · Accepted solution]

Hi Monika,

My question is about repair request, because as I have understood we need to delete and upload once again EU data, but not USA data. It is for this that I am asking you if repair request must have data also for USA. If I make a repair request for USA may I have doubled records for USA ?

LEt me know please, I have always problems in understanding repair request.

Ciao.

Riccardo.

[Former Member · Accepted solution]

HI

Riccardo,

Do i require to have downtime if i am using queued delta update mode for my extractors?

Hi

Monica,

repair full req in my infopackage is in display mode.

ne idea !!

Regards

Ankur

[Former Member · Accepted solution]

Hi Ankur,

You need all users stopped, because every transaction will produce a new item in LUW queue, and if you do not process this, with job control in LBWE, you will have double records in first delta after new Init.

Ciao.

Riccardo.

[Former Member · Accepted solution]

hi riccardo

here we dont have any logic of repair request , its ODS only. depending on keys data will be overwritten. Duplicate records issue comes in cube only.

one more suggestion , if there is no delta from ODS in any other target then you can do sleective deletion from ODS and run repair request.

[Former Member · Accepted solution]

Hi Monika,

I will not tell you that I am feeling a little stupid... only a little... Now I understand completely your suggestion, I was only thinking to cubes and not ODS.

If you are still connected and if you want (also becuase you are answering me but I can not assign you points...): how can I proceed in the same situation but with Cubes ?

Ciao.

Riccardo.

[Former Member · Accepted solution]

Hi,

Let me take a shot at answering that. For cubes you can do a selective delete of the data and then reload with a full infopackage but with selection conditions in the infopackage corresponding to the data you want loaded.

You can also run the full repair request for the cube, but before you do that, you need to delete the entire cube contents as you'll possibly get duplicate data.

Cheers,

Kedar

[Former Member · Accepted solution]

Hi

Kedar,

Am not able to figure out the repair full req option. It shows me in display mode..

Ne Idea!!

Regards

ankur

[Former Member · Accepted solution]

Hi Ankur,

Use the program RSSM_SET_REPAIR_FULL_FLAG to set the full repair flag.

Give your ODS object, Datasource and source system..

Regards

Manga

[Former Member · Accepted solution]

Hi

Riccardo,

If i create separate init info package for both the countries as susggested by you, will the <b>IDoc number</b> for both of them would be <b>same or different.</b>

--- Ankur

[Former Member · Accepted solution]

Hi

Riccardo,

I think it would have different IDoc number sent to R/3 system if i will have 2 init with different selection with same datasource.

If so, then how i can ensure that my deltas coming to 2 different targets would be fine..

---Ankur

[Former Member · Accepted solution]

Hi Ankur,

Sorry for the delay, but it was not a simple day.

Monika has correct me in one of the previous messages: you can not make two different Init for two different DataTarget. Best solution is to follow her steps: Init with zero data and then a full repair request with the different selection for the two different objects.

Another possible option can be to try to make a full upload and then an Init with zero data. Problem is with ODS that I never remember if they do not accept an Init after a full or vice-versa. Make a test.

If I do not answer Monday please write me also at riccardoventu@virgilio.it

Ciao.

Riccardo.

[Former Member · Accepted solution]

Hello

Riccardo,

thanks for the reply...

As suggested by monica, repair full request is always seen as in display mode...

and i m finding some alternate solution using Mirror image...m stuck up in the last step for the same...let me try n will let u know if it works...n provide you all guys with step by step solution.....

but ur inputs are most welcome here....

Regards

ankur