Migrate workbooks

If there are two EULs test and prod, is it possible to migrate just the business units from a test EUL to the prod EUL? How can I migrate workbook developed in the test EUL to the prod EUL. Just to clarify I am not looking to share the workbook between both EULs, rather I want a finished workbook (in PLUS) created in test to now use the prod EUL.

Hi
Use the command line options of the Disco Admin.
Use export and import with /WORKBOOK option.
See the documentation.
Ott Karesz
http://www.trendo-kft.hu

Similar Messages

  • How to open 7.0 migrated Workbooks in 3.5 analyzer

    Hi,
    We have migrated BEx 3.5 workbooks to 7.0 version.
    We now want to execute these migrated workbooks in 3.5 analyzer, but we are not able to. Does migration of WBs create a new version of the existing WB or does it overwrite the migrated WB over the old one?
    How can we run our migrated WBs on 3.5 analyzer while retaining the migrated ones?
    Thanks,
    Abhishek.

    Hi,
    Pls have a look at this post.
    Re: How to open 7.0 migrated Workbooks in 3.5 analyzer
    Technically if you upgrade your workbook it will create new 7.0 work book with same name..
    but thing is most of time it doesn't work for upgraded workbook..
    Check your support package level, still if you face issues, log oss message.
    Regards,
    Senthil.

  • Issues when migrating workbook from one EUL to another EUL

    Dear Members,
    We have two types of EUL. One is an standard EUL and another one is Apps based EUL. We have many reports created in standard eul and my task is to move these workbooks to an apps based eul.
    Standard EUL is nothing but a database based eul. Users who created these workbooks in this EUL are the database users. Now i exported these workbooks to an .eex file using the command line interface. But when i am trying to import these workbooks in an apps based eul i cannot see them after import. I know this might be an previlages issue.
    My question is these two eul's are completly different from one another. One is database based and another one is apps based and even the users in both eul's are different as they have different accounts in database and application.
    We have a lot of reports created using the database based eul. Our goal is to move these to apps based eul so that users can use there responsibilities and run the workbooks rather than using desktop by logging in as a database user.
    How should i proceed in migrating these reports. It would be great if any one guides me.
    Thanks
    Sandeep

    Hi,
    You should ensure that you take ownership of the workbooks when they are imported and that you log in as an apps user (not the EUL owner) when the workbooks are imported.
    Rod West

  • Issue after migrate  workbook from 3.1 to BI Netweaver 7.0

    Hy experts,
    We have a workbook in v.3.1 with several querys in only one sheet, one below the other.
    When we migrate this workbook to 7.0 and refresh it, the system shows this message:
    <i>"Some item(s) overlap with each other".</i>
    Then an unassigned navigation pane (no characteristic is asiggned to it), corresponding to the first query,  is put on the analysis Grid, corresponding to the second query, so some rows are not visible.
    How can we do to avoid that unassigned navigation pane?
    Regards.

    Hi,
    Issue may be due to the Excle formulae used in the workbook which do not get migrated.
    One way around it is to migrated the queries first and apply Excel validations on top of it in 7.0
    Hope this helps.
    Thx,
    SK

  • New ID for migrated Workbook

    Hi Experts,
    As per the Migration Stratagies that SAP has provided says that the Migatred workbook will save with Name/ ID. But, I Observed that It is saving with the OLD Name/ID only. If you have same experience with Workbook Migration Please share your ideas 
    Thanks
    DB

    That is for standard workbooks (business content).
    For user generated it does not.

  • Workbook Migration-System error in program CL_RSR_XLS_VIEW and from ASSIGN_

    Hi Experts,
    We are migrating workbooks from 3.x to BI 7. While opening the workboon from BI 7 Analyzer we are getting the following System Error  and Disconnecting from BW server.
    'Program Error in class SAPMSSY1 method UNCAUGHT_EXCEPTION. System error in program CL_RSR_XLS_VIEW and from ASSIGN_QUERY_2_DP03'."
    We are at support pack level 17 and GUI - 710 with patch level 8.
    If you have experienced with the above errors. Please respond.
    Thanks
    DB

    Hi Naveen,
    In migration you will get all these errors related to Front end. First save the Existing 3.x workbook   so that the old version of the workbook will be saved into new Excel version (2003). now try to migrate the workbook , this time you will not get this error.
    The root cause for this problem would be all your workbboks have been created erlier in very old version of  Excel.
    Thanks
    DB

  • 3.5 to NW2004s : Workbooks migration

    Hi ,
    Is there any program to migrate  workbooks from 3.5 to NW2004s version or do we need to this manually ( i.e opening every workbook in NW2004s and resaving it).
    Regards
    MB

    See the below link,
    http://gnanamax.com/Documents/BI%207.0%20Functional%20Upgrade%20-%20Migration%20points.pdf
    Hope this will help you..?
    MSR

  • Format is changing, once we migrate the 3.x Workbooks to 7.x

    Hi,
    We are migrating the Workbooks form 3.x to 7.x,once Refresh the migrated workbook.
    the existing workbooks lines and colors are not coming into 7.x workbooks.
    can you pls give me related sap notes are some advise to achieve the issue.
    Regards.
    Malli.

    Hi,
    There is a great Note on this: 1807522 - BEx 3.5 Objects Migration to BEx 7.0.
    Please check the cookbook and check if it can help.
    Regards,
    Michael

  • Workbook Migration Restore

    Hi All,
    I am working on migration of workbooks to BI 7 enviornment.
    I want to know the answer or pointers for the following questions,
    1. What is the best strategy to migrate -
         Open the workbook in each system in Bex 7 analyzer and 
         save it.
       or Save in new tool in development system and transport to production.
    2. How to restore the migrated workbook to old BW 3.5 version.
    3. What kind of common issues are faced in workbook migration.
    Regards,
    Niraj

    Hi Chetan.
    Thanks for the response.
    I have already read the blog sent by you. But it does not  answers the questions which I raised.
    I s there any way to restore workbook to 3.5. We can restore the queries using program COMPONENT_RESTORE.

  • Regarding Migration of Workbooks

    Hi All,
    I need to migrate workbooks from 3.x to 7.0 version.I have some queries related to it..
    1.What is the basic difference between single,multiple,complex and query view??
    2.How to check for the VB code??
    3.How to manage the pivot table during migration??
    It will be really helpful if anyone of you can give me a stepwise overview of migration of workbooks and how to check whether it has been migrated properly to 7.0 version..
    Points will be assigned to the helpful answers...
    Thanks in Advance,
    Regards,
    Rahul.

    Hi Rahul,
    To migrate the 3.5 workbook, open it in BEx Analyzer 7, refresh it so it populates with data. The macro SAPBEXONREFRESH no longer works so you will need to  replace it if it exists with the macro name CALLBACK. Remove the SAPBEXONREFRESH macro.
    you do this in the VB code.
    Sub callback (ParamArray Resultsarea())
    <code> optional (or copy code that exists in the sapbexonrefresh macro)
    End
    In the global settings in the EXIT tab replace the macro to invoke as the CALLBACK macro.
    If no macro code exists then select the radio button for no macros.
    Save the workbook (this will now be a V7 workbook). Close session and reopen the saved workbook, refresh and check that the results are displayed correctly. FEP 700 of BEx 710 seem sto be more reliable then it's previous FEP's.
    Daksha.

  • Question of workbook/query/variable deletions

    Hello,
    Needed opinion from the gurus on how deletion of front end objects is handled.
    For example, we have migrated workbooks(including query elements, variables etc) to quality. Some of them need to be deleted and no longer are required in production.
    Can we delete those objects in development and would it create a request similar to how backend obkjects are deleted? So that when the transport is sent out, it would delete the objects in the target systems.
    Or do we manually/programatically delete those objects in the development and in target systems?
    Thanks in advance for your thoughts
    Regards
    Prakash

    Hello,
    Thanks for your input.
    Does the front end deletion get recorded the same way as backend?
    For example, if I delete a query from RSZDELETE. I am not prompted for a transport or a request.

  • Migration of queries and work books to BI7

    Hi,
    I would like to Migrate all the existing 3.X queries and work books to BI7.0 in Development box.
    Is it possible to capture these changes into a transport request, if possible how do I capture.
    Please guide.
    Regards,
    Sharma. IVN

    Sharma,
    Its better to collect all queries of a Infoprovider in a single request as u can avoid locking of dependent objects in different requests..Migrating workbooks would be tricky if u have any macros.Have a look at below links on migrating front-end objects
    SAP NetWeaver 2004s BI - Define your Publishing Strategy Part 2
    SAP NetWeaver 2004s BI - Define your Publishing Strategy Part 1
    Migrating Advanced BEx Analyzer Workbooks - What VBA is Supported?
    Chandu

  • Upgrade Workbooks & Queries

    Hi!
    We are currently in the middle of upgrading to NW2004s from 3.5. So far, we have completed a test upgrade on the development system.
    When opening workbooks, we can see that the query and workbook objects being upgraded “on the fly”, which decrease performance. To avoid this we have to resave the workbook, in order to convert all objects.
    So my questions are:
    1) Does anyone know if it.s both the workbook and the query that has to be resaved?
    2) Which “upgrade strategy” has been used when it comes to migrating workbook and queries?
    To let the end-users access via the 3.5 add-ins to start with
    *To resave all the queries and/or workbooks after been upgraded
    To let the end-user resave when appropriate
    Or any other methods?
    Thanks in advance!
    Bjørn

    Hello,
      I thought I would share our experience with workbook conversion issues so far. We are upgrading the toolset after having done the technical upgrade, implemented new analysis authorizations, and implemented support packs up to 12. 
    In our area we have a set of reports (workbooks)that are formatted to a very high degree, using Excel more than the BEx (3.5) settings, although we have both. Some examples are 1) in general the column widths and texts have to remain static to retain the proportions of the report and for printing, and 2) we redid BEx Exception cell formatting with Excel Conditional cell formatting since the users wanted blue as a condition (this is what we did, maybe there is a better way...), 3) graphs, print settings etc. 
    In order to make some of these settings in 3.5 we had to turn off the query property "adjust format after refresh".  I believe the same setting in 7.0 is "Adjust formatting" checkbox on the Analysis Grid properties.  Another setting we used extesively in 3.5 was the query setting "adjust column width on refresh - set to "do not adjust".  In 7.0 the equivalent is also on the Analysis grid properties "Auto Fit". 
    My thought right now is that the "Adjust formatting" is not carrying over during the upgrade process, in other words turning off "adjust format after refresh" seems to convert to having the " Adjust formatting" checkbox checked, which wipes out everything after refresh, including the standard BEx format.  I have come up with a way to manually convert them, but ultimately involves a fair amount of rework.  Many of our other users create workbooks and queries in an adhoc process, so we are communicating to them that they will need to go through this process, and there may be rework.  We are finding the 3.5 vs. 7.0 workbook creation process to be significantly different which was unexpected for us at least. 
    Hope that experience might be helpful, we are still working on it ourselves.

  • Cannot join tables used in the workbook. Join "" not found in the EUL. Atte

    Trying to migrate workbooks from one instance to other using discoverer 10.1.2.48.18 i am getting the following error
    Unable to open the worksheet requested.
    - OracleBI Discoverer was unable to find the worksheet that was requested.
    - BIB-10310 An unknown exception occurred.
    - Cannot join tables used in the workbook. Join "" not found in the EUL. Attempt to open workbook failed.
    but its fine one instance , and in prod i am getting above weird error.
    does anybody know how to rectify this.

    Note:267476.1 - for those who can't get into metalink but still need to know the answer
    Subject: Discoverer Workbook Fails With 'Cannot join tables.Item dependency "" not found in EUL' After EUL Migration, Importing Or Cloning
    Doc ID:      Note:267476.1      Type:      PROBLEM
    Last Revision Date:      28-APR-2005      Status:      PUBLISHED
    The information in this document applies to:
    Oracle Discoverer - Version: 4.1 to 10.1
    This problem can occur on any platform.
    Symptoms
    Opening a workbook migrated from one instance to another results in the following errors:
    * Unable to load EUL item ...
    * Cannot join tables. Item dependency "" not found in EUL.
    * Illegal operation... DIS4USR OR DIS5USR caused an invalid page fault in module....
    If using the workbook dump utility, you may notice:
    * Found in EUL by id *** Name has changed to .. where the new name is really the wrong column
    It seems that items are matched by internal item identifiers (IDs) and not by developer keys and names.
    Changes
    Migrating from one environment to another. For example, you may have performed a database export / import of the EUL schema from DEV to TEST
    Cause
    The timestamp is the same for both EULs, what can be confirmed by the following SQL statement:
    * Discoverer 4:
    SQL> select ver_eul_timestamp from eul4_versions;
    * Discoverer 9.0.2 , 9.0.4, 10.1 the script is:
    SQL> select ver_eul_timestamp from eul5_versions;
    If the result of the sql output is the same in both EULs, it means that timestamp of both EULs are the same. Discoverer assumes that the EUL are exactly the same (e.g. this can happedn when one of them is created with export/import of the other EUL schema using database export/import utilities) and this is the reason it tries to match items by identifiers and not by developer keys or names.
    Solution
    Change the column ver_eul_timestamp in the eul4_versions (4.1) or eul5_versions(9.0.2 - 10.1)tables to be something different in the destination EUL. The format of this column is like year:month:day:seconds:milliseconds
    Example:
    * Discoverer 4.1:
    sql> update EUL4_VERSIONS set VER_EUL_TIMESTAMP =TO_CHAR(SYSDATE, 'YYYYMMDDHH24MISS');
    sql> commit;
    * Discoverer 9.0.2:
    SQL> update EUL5_VERSIONS set VER_EUL_TIMESTAMP = TO_CHAR(SYSDATE, 'YYYYMMDDHH24MISS');
    sql> commit;
    * Discoverer 9.0.4 -10.1:
    Run the script: EUL5_id.sql as the eulowner ID
    o For 9.0.4 -- This is found on a PC with the Discoverer Administrator installed in drive:\Oracle Home\discoverer\sql
    o For 10.1.0 -- This is found on a PC with the Discoverer Administrator installed in drive:\Oracle Home\discoverer\util
    This is documented in:
    Oracle® Business Intelligence Discoverer
    Administration Guide
    10g Release 2 (10.1.2.0.0)
    Part No. B13916-02
    http://download.oracle.com/docs/pdf/B13916_02.pdf
    Chapter 4 "About copying EULs and EUL objects by exporting and importing"
    Oracle® Discoverer Administrator
    Administration Guide
    10g (9.0.4)
    Part No. B10270-01
    http://download.oracle.com/docs/pdf/B10270_01.pdf
    Chapter 3 "About copying EULs and EUL objects by exporting and importing"
    References
    Bug 3202329 - Migrating Workbooks Between Instances Shows Incorrect Column

  • Migration of work books, queries and web report

    Hi,
    kindly give me the steps to migrate workbooks, queries and web reports from BW 3.5 TO BI 7.0
    Regards
    Asim

    Hi,
    Kindly check the below link:
    Migration of Queries and Work Books from BW 3.x to BI 7
    /people/teja.badugu/blog/2008/11/11/migration-of-queries-and-work-books-from-bw-3x-to-bi-7
    Hope it helps,
    Thanks,
    Amit

Maybe you are looking for