Migrating Queries to BI

Hi All,
How do we migrate queries from 3.5 to version BI 7.....what steps are invovled? Any additional care to be taken?
Please suggest
Raj

There is no separate migration needed, you need to just open the Queries in Query Designer 2004s.
Also in background no new GUID or tables entires are created.
Also note the following:
Once you have edited with Query Designer 2004s you can no longer edit those queries in 3.x Query Designer.
Cheers,
Neel.

Similar Messages

  • Access 2003 to Oracle Migration Queries

    Hi Experts,
    I have taken up a project to migrate Access 2003 application to Oracle 9i.The Forms and Reports will continue to run in Access 2003 with Oracle 9i database. I decide to use Oracle Migration workbench for the migration purpose.What I think is the back-end i.e. database and queries will be automatically migrated to Oracle 9i but I'm not sure about the front end application.
    Do I need to change front end application to point to database in Oracle 9i or OMW will do that itself.I am also confused with lots of queries that reside in current Access database. I presume these queries will be converted to Oracle procedures/views without any manual intervention but will the front-end application also be modified automatically to point to those stored procedures/views. Otherwise an extensive code change will be required which may result in huge cost.
    Currently the Access application is not using any ODBC DSN as it gets connected to the database automatically. Should the database connection be changed to use DSN prior to Migration?
    One more thing, the application is using single-level linked table. Will the linked table get automatically converted and connected or I need to do anything?
    Could anyone help me in this issue by giving some ideas so I can manage the job efficiently and make proper planning before plunging into the real work.
    Thanks & Regards
    S C

    The Migration Workbench will modify the Access mdb file as part of the migration if you request it, to create the necessary link tables to oracle, it will use an ODBC DSN to do this. This is explained in our documentation. This should be transparent.
    However for complex application, you often have a tuning exercise, to ensure that the jet engine does the "right" thing, and there changes are required, e.g. a two way join, you would want that to happen on the server and not done on the client. This would be same tuning exercise, if the back end was SQL Server.
    In the latest release of the Access plugin, we did a better job migrating queries to views, but you need to plug this into your code.
    Yes, the exporter should extract the information about the linked table, assuming the link is valid at the time of extraction.
    Donal

  • Migrating queries from 3.5 to 7.0

    hi,
    we are in the process of migrating from BW 3.5 to BI 7.0. i would like to know, what are the steps to be executed to migrate queries from 3.5 to 7.0.

    There is no migration and there is no new GUID and there are no new objects in database tables. However, once you save the query with the NetWeaver 7.0 (2004s) Query Designer you cannot edit it anymore with the 3.5 Query Designer.
    In general the system logic allows you to still edit other 3.5 queries in the 3.5 Query Designer even if they are re-using elements of a query that has been edited with SAP NetWeaver 7.0 (2004s) BEx Query Designer as long as the reusable elements use no 7.0 (2004s) features (such as planning settings, new aggregation on formulas, variables with multiple default values).
    Please also check the NetWeaver 7.0 (2004s) BI release notes and check note 832713.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4754bc74-0901-0010-3e82-b761b4c74937
    Hope it Helps
    Chetan
    @CP..

  • Migration Queries GUID

    Gurus,
    Can any one pleasde share with how and what happens with query migration,does that change your GUIDS ? of the queries ..and whar tables do we need to look out for that in such cases ..
    thanks

    No. There is no migration and there is no new GUID and there are no new objects in database tables. However, once you save the query with the NetWeaver 7.0 (2004s) Query Designer you cannot edit it anymore with the 3.5 Query Designer.
    In general the system logic allows you to still edit other 3.5 queries in the 3.5 Query Designer even if they are re-using elements of a query that has been edited with SAP NetWeaver 7.0 (2004s) BEx Query Designer as long as the reusable elements use no 7.0 (2004s) features (such as planning settings, new aggregation on formulas, variables with multiple default values).
    Please also check the NetWeaver 7.0 (2004s) BI release notes and check note 832713.
    Hope it Helps
    Chetan
    @CP..

  • Migrating queries to new infoprovider

    Hi
    We have divided a large infocube into 5 smaller infocubes and built a multiprovider on top of those.
    How do I migrate the queries on the existing Infocube to the new multiprovider.
    Thanks

    Please try to search when you post a new question...you can find several posts here that mention transaction RSZC to do this.

  • Key Figure in Queries migrated to BI 7.0 front-end

    Hello Experts.  We are currently migrating queries from 3.5 front-end to 7,0 front-end.  Some queries that used to work in 3.5 withoug key figures no longer work after migrating to 7.0.  Can someone tell me if there is a way to resolve this?  Changing the query is out of the question.  Can someone point me to any forum document or Blog if there is any?  Thank you for your help.

    Hi Sree,
    I did encounter an error -  the error said that a key figure needs to be specifiied.  The other thing is, the query does have a formula which means it does have a key figure.  It migrates in spite of the error but does not execute and displays the same error message about a key figure needs to be added.
    We are on Pacth Level  13.
    On a side note, there is a way to restore the query from 7.0 back to 3.5   Abap program 'Component_Restroe' will do it.
    Thanks for your help.

  • BEx queries migration

    Hi Experts,
    Our Project is about BI Front end migration (queries, workbooks).
    What could be the common macro errors which might occur moving from BI 3.x to BI 7.0.
    or if you can share a BI 3.5 macro sample for converting it into BI 7 version.
    Best Regards,
    Neha
    Edited by: n.arya on Nov 2, 2010 11:49 AM

    Dear Neha,
    If you search on sdn and help.sap.com you will give a lot of issues which come in migration.
    Please check on service market place as well as there are couple of OSS notes as well answering to this issue.
    if you have any specific problem please open a new thread.
    Do post back if the issue is not solved.
    Please do close the thread if that answers your questions. Please help us keep the forums clean and open useful information only.
    Regards.
    Den

  • Migration of bex 3.x queries and workbooks to Bex 7.1 queries and workbooks

    Hi,
    Migration of bex 3.x queries and workbooks to Bex 7.1 queries and workbooks.
    For instance when you edit,open an 3.x query in 7.0 query designer it is automatically migrated.Would it be same if we open it in 7.1 query designer?Is it possible to migrate queries and workbooks without any fail or deletion or loss?
    Thank you.

    I will add to the already excellent suggestions made above that the migration from Bex 3.x to Bex 7.0 is VERY laborious. There are no automated tools.
    All queries and workbooks must be identified (use this as an opportunity to get rid of unused objects)
    Each query must be converted to BI 7 and repairs done as needed.
    Each Workbook must be converted to BI 7 and repairs done as well. The "Automated" conversion tool that SAP provides (it's behind the scenes Visual Basic) presents problems with at least 50% of the workbooks, and so they have to be manually fussed with.
    If you've used Visual Basic at all in your Workbooks, you'll have to change 'em all. The On Refresh event no longer exists.
    And of course, test... test.. test.. and test.
    And don't forget to retrain your users. The User interface is dramatically different.
    Good luck ! We're 3 months in to a five month conversion project.

  • Access 2003 to oracle 9i Migration(Oracle Migration Workbench)

    Hi Experts,
    I have taken up a project to migrate Access 2003 application to Oracle 9i.The Forms and Reports will continue to run in Access 2003 with Oracle 9i database. I decide to use Oracle Migration workbench for the migration purpose.What I think is the back-end i.e. database and queries will be automatically migrated to Oracle 9i but I'm not sure about the front end application.
    Do I need to change front end application to point to database in Oracle 9i or OMW will do that itself.I am also confused with lots of queries that reside in current Access database. I presume these queries will be converted to Oracle procedure without any manual intervention but will the front-end application also be modified automatically to point to those stored procedures.Otherwise an extensive code change will be required which may result in huge cost.
    So, could anyone help me in this issue by giving some ideas so I can manage the job efficiently.
    Thanks & Regards
    S C

    The Migration Workbench will modify the Access mdb file as part of the migration if you request it, to create the necessary link tables to oracle, it will use an ODBC DSN to do this. This is explained in our documentation. This should be transparent.
    However for complex application, you often have a tuning exercise, to ensure that the jet engine does the "right" thing, and there changes are required, e.g. a two way join, you would want that to happen on the server and not done on the client. This would be same tuning exercise, if the back end was SQL Server.
    In the latest release of the Access plugin, we did a better job migrating queries to views, but you need to plug this into your code.
    Yes, the exporter should extract the information about the linked table, assuming the link is valid at the time of extraction.
    Donal

  • Variants Migration 3.0 to 7.0

    Hi,
    We are migrating Queries, Work Books & Web temples to 3.0 to 7.0.
    I have gone through many links for Query or Work Book Variants Migration 3.0 to 7.0.
    I found some of the tables like RSRPARAMETRIZA - Parameterization for a query, workbook, and web application. RSRVARIANT -- Variant Values
    Is it possible to Migration existing variants 3.0 to 7.0 or same variants we need to create in DEV and transport to PRD?
    Pls share the steps.
    Any help is appreciated.
    Regards,
    Prakash

    Hi Phani,
    Many Thanks for your reply..!
    I checked the attached link.
    Once we run the report RSR_MIGRATE_VARIANTS migrates into 7x tables RSRPARAMETRIZA,RSRPARAMETRIZAT but this activity I can do across the land scape D.Q,P or we can transport tables pls correct me.
    same report report migrates all Global & Local saved Variants?
    Thanks
    Prakash

  • Query Migration from 3.5 to 7.0

    Hi All,
    We have a upgrade done from 3.5 to 7.0.
    We need to migrate queries which were developed in 3.5 to 7.0.
    As of now, we are migrating EACH query by opening it in 7.0 and Saving it.
    This works fine.
    But we have N number of queries of diffrent projects.
    Any pointers how to migrate ALL the queries at one time in 7.0.
    Thanks,
    Best regards,
    Prashant

    Hi Diwakar,
    For Query migration - u have to do one simple thing only...
    i.e just open the query in 3.x and save it ... then it will be automatically migrated to 7.0...
    Hope it helps..
    Regards,
    V. Vijay

  • Questions for Query Migration to 7.x

    Hi, I am sure lots of people have converted all of their Queries from 3.x to 7.x at this point in time so I'm hoping to leverage from the experienced knowledge base that is out there. 
    When Migrating the Queries did everyone...  (If you could add your detailed experience that would be appreciated! 
    1. Migrate in Dev and transport
    or ---
    2. Migrate Queries separately in each environment?
    Thanks

    Hi
    Before Migration , make sure system having BI 7 installation for query designer and other.
    As Per your thread , YES we need to migrate the queries in Development system , collect the transport and move it further system.
    Migration process like:
    1). Goto Query Designer open the 3.x in BI 7.
    2). If there were no warning and errors after query opened in query designer, Then Save query into BI7. With this step query migrated into BI 7.
    3).  If query wants to restore into 3.x , we are having program COMPONENT_RESTORE to get it back, This program will gets query back into older version as its same as old query.
    4). After migration of queries use transport connection to collect transports. With this help we can make sure all query elements also collected successfully.
    Hope this will clear all your concerns.
    M

  • Sequence of Migration activities

    Hi,
    Is there a sequence that must be followed while migrating BI objects. i.e. let us say if I Migrate queries before dataflow does it make a difference.
    Also kindly let me know the system requirement in terms of SP level, Java Stack or ABAP Stack requirements. I believe NetWeaver 2004s reporting tools are not compatible with Microsoft Office new version. Is that true?
    Thanks a lot for help.
    Regards
    Pooja

    Hi,
    Points to be kept, (not a version migration) Migrating from one system to other
    1. Review the objects in both the systems and ensure they dont clash or overlap.
    2. May be they had different source systems and you need to carefully look at all the source system dependent objects and re assign the source system.
    3. Performing transports will be the one of the options for the move; in that case collect the objects in logical order starting with the info objects, data targets, info sources, update rules finally queries, roles, workbooks.
    4. Review the master data and also the ODS to ensure the data dont overwrite; better to have a system identifier for the master data objects.
    5. For the transaction data, approach will be to go with the EDW approach
    6. For the same of reconciliation purposes, suggest to keep the Regional system, if exists, within the same region system separate and for reporting purposes, use infosets and multi cubes rather than loading data to the same data targets.
    For Version Migration ,Pls chk this links;
    Migration of BW 3.x Dataource to BI 7.0
    Migration of ECC BI Content to BW 2004s
    Transformations Migration
    Transformation Rules
    http://help.sap.com/saphelp_nw2004s/helpdata/en/43/f00e2696d24c5fe10000000a155369/content.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8d1a0a3a-0b01-0010-eb82-99c4584c6db3
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d163a7-0301-0010-d9b0-98f692ea3c60
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
    https://websmp102.sap-ag.de/upgrade-bw
    web blog ...
    Rolling out the New SAP NetWeaver 2004s BI Frontend Tools
    Hope this helps,
    Regards
    CSM Reddy

  • Automate the migration process from BW to BI

    I want to automate the process of migration from BW to BI. Currently as we know this is done manually. I studied the program that is generated at runtime. How is this program triggered?
    Is it possible to combine all the steps of migration into a single step where a user can input the details and then the migration takes place by itself?
    Thanks
    Kushagra

    not impossible?
    How are you going to let your program decide what to do about a corrupt table etc?
    The upgrade may stop at the active-table of a DSO for example.
    IMO the upgrade is already highly automated.
    An upgrade without human interaction is very risky.
    If you are talking about migrating queries and workbooks, that's a whole other issue.
    just my 2 cts

  • Migrate from sql server to oracle

    can anyone help me how to migrate from sqlserver to oracle

    Hi;
    i have been searching in google if anybody having live experience in migration pl help meOk than i am helping you,checked google search and found below links from search. They should help you friend. Please see:
    http://st-curriculum.oracle.com/obe/db/hol08/sqldev_migration/mssqlserver/migrate_microsoft_sqlserver_otn.htm
    http://www.oracle.com/technetwork/database/migration/sqlserver-095136.html
    Also see:
    SQL Server to Oracle migration queries
    SQL Server to Oracle migration queries
    If have still question than update thread.
    Regard
    Helios

Maybe you are looking for