Dear community,
Consider the following landscape
- BW_A, BW_B, ECC_A and ECC_B systems
- A source system exists in BW_A connected to ECC_A
- A source system exists in BW_B connected to ECC_B
- Transport routes exist from ECC_A to ECC_B and from BW_A to BW_B
When I need to transport a new DataSource "X" and it's associated flow from a BW system A to system B, what I've always done is
Step 1: Transport X from ECC_A to ECC_B
Step 2: Replicate X's metadata in BW_B (from ECC_B)
Step 3: Transport X's flow's objects from BW_A to BW_B
I was wondering whether there is a better (the "best practice") method for transporting X. I concretely doubt of my current step 2. I believe it would be better to transport X's replicated metadata from BW_A to BW_B instead of replicating directly in BW_B from ECC_B, so I tested this transport, but when importing the change request on BW_B I got an 8 return code with the message
... which is of course understandable as source system ECC_A does not exist in BW_B.
My questions are:
1. Which is the best practice method? My "current" one? The "new" one? Another one?
2. If the new one is the best, how is it accomplished? Source Systems cannot be transported, and I haven't found how to instruct BW and/or the TMS that ECC_A's replicated datasources should be transported as ECC_B's replicated datasources. That's probably not even possible.
Expert advice will be much appreciated
Fernando