on 08-31-2013 4:44 PM
Hello All
I have an old BW legacy system 3.5 but technically upgrade
to 7.0 – and for some good reasons we have implement a completely new BW 7.3 landscape
- and I have to bring some critical data
flows into the new landscape from the legacy landscape – I have create a
transport in the legacy BW system and I would like to bring into the new 7.3
landscape , both the systems are not connected and separate landscape–
We are on Windows and SQL
Any help will be highly appreciates..
Anees Abbasi
Hello
Read these SAP notes
Note 556734 - FAQ Transport: Setup and further information
Note 1090842 - Composite note: Transports across several releases
Additionally read the related notes at the bottom of the note.
If you are looking for Data Flow migration then check these links:
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your quick response : But I think I have not explain my scenario correctly .
I have separate BW 3.5 landscape - it was technically upgraded but all the development still in 3.5 version -
Now I have another new BW 7.3 landscape - no connection between these two landscapes 3.5 and 7.3
I need to transport objects from 3.5 landscape to new BW 7.3 landscape - I was able to bring my transport into the new landscape trough COfiles but my transport fail with the error stating there is version conflict between the target landscape .
Question is how to I import my BW 3.5 object into this new environment? Do I have to convert my 3.5 development into 7.0 first to bring into the new 7.3 or is there is any other way of importing these 3.5 objects into the new 7.3 landscape.
I hope I have explain clearly ...
Thanks
Anees
Hello
I have provided you two SAP notes and you should read that.
Transporting between different released can cause inconsistencies but there are certain combinations which are supported.
If I were you I would import those transports into a sandbox system and will test them before importing them to the other systems.
Regarding the component version mismatch message you can check the box "ignore invalid component version" in the Options tab.
Regards
RB
User | Count |
---|---|
86 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.