Dual Landscape. Overwriting 3.5 queries with 7.0 version

[Former Member]

We have a dual landscape. The production path uses the 3.5 version of BEX analyzer and hence any queries that need to be moved to production have to be developed in 3.5. On the alternate path, we manually dual sync them in 7.0 version. What happens when the 7.0 queries eventually come into production. Will they overwrite the existing 3.5 queries successfully. Anybody who has experience with this, please post your reply

[former_member207028 · Accepted solution]

Hi srilatha,

after the system Upgrade from 3.x to BI 7.0. Queries and work books still be in 3.X version.

when Query / workbook opens with SAP GUI 7 patch, then 3.X Query / workbook will migrate to BI 7.0 version.

hope this helps

Regards

Daya Sagar

[Former Member · Accepted solution]

Thanks for your reply. Let me explain the process in steps to make it more clear

Step 1 - A new query Zxxx was developed in the Dev_server_1 as a 3.5 Query and transported to Production server

Step 2 - A similar query with the same technical name Zxxx was developed in the Dev_server_2 (dual sync path) in version 7.0

Step 3 - Zxxx to be moved from Dev_server_2 to Production server

Will step 3 above work without problems? Is this the right way to do it? Are there better ways to handle this issue?

Thanks in advance for any reply posts

[Former Member · Accepted solution]

Since the Technical Name of the Queries are same the 7.0 Query Should over write your old Query. Can you tell us why you guys are doing this.

Because an easy thing to do would be when you are ready to Transport in 7.0 open the Query in in new ( 7.0 ) Query Designer and Save it back the system will save it in new version and transport.

I would suggest a transport with one dummy query if that works you should be good to go.

HTH

Datta.