cancel
Showing results for 
Search instead for 
Did you mean: 

2LIS* extractors after client merge?

Former Member
0 Kudos

Hi friends,

Our BW instance is sourcing data from two R/3 clients existing on one box.

Now we are going to merge 2 R/3 clients 001 and 002(say existing client 001 will supercede). Some of 2LIS* extractors are being used by both.

I have some concerns:

1. what would happen with the tables like TMCEXACT and TMCLVBW after merge?

2. any impact for the delta process!

3. should I expect any inconsistencies after the client merge?

4. anything I have to prepare before merge?

Thanks in advance for your help!!!

Regards,

Lilly

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

You merge 001 + 002 into 001?

Before the merge, make sure that the delta queues in both systems are empty (by repeatedly running the V3 and extractors until (in RSA7) all counters are showing zero.

After the merge you simply schedule the V3 (RMxxx) jobs in TR:LBWE on system 001. Then you restart extraction of the delta's.

A complete re-init should not be needed.

Former Member
0 Kudos

Hi friend!

many thanks for the prompt response which helped a lot. It is great to know that the re-init is not necessary.

We are using 'queued delta' which might not be V3?

Another question came to my mind is:

how about the extractors which are only on client 002 which will go away? will they be inactive after merge on 001 and hence a re-init is needed?

any feedback is highly appreciated.

Regards,

Lilly

P.S. it seems there is a issue in the forum, I am not able to grant reward points?

Former Member
0 Kudos

For queued delta (and others) it works the same. Actually we are also using queued delta but for historical reasons I keep calling them V3 delta.

About the second part of your question: Just make sure that before the merge you extracted all data. After the merge the extractors that where only on 002 have an undefined state. Officially you can't be sure that underlying tables in 001 are empty.

I.e. Even if you didn't use Purchase Order extraction it doesn't mean that on 001 there are no Purchase Orders. So for these extractors, an init on 001 is recommended.

What you can do is the following: For all delta extractors that are enabled on 002 but not on 001...

Enable them on 001 too before the merger. Since this data in not extracted currently you can take your time for this. Next treat them the same as the extractors that are running on both systems.

Only if you are absolutely sure that the underlying tables are currently not used you could continue the delta with a dummy init.