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

Similar Messages

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.

Precalc NW2004s Workbooks

From this post BW PreCalc Server not working I undesratnd that to precalculate NW2004s workbooks we need the Precalc server that comes with GUI 640 .
When I download GUI 640 from service.sap.com/swdc and install it with BW addon ( 3.X ) & BI Addon ( 7.X ) and then install precalc ( this is the one that comes with GUI 640 and not the old 350 version) all is well but the Bex Analyzer of 7.X does not work and hence the NW2004S workbooks cannot even be opened on precalc server. Also with 3.X workbooks we are getting corrupted workbooks. We have applied all the latest notes on oue BI backend system.
On the precalc server we have the .Net 1.1 installed .
Has anyone tried this scenario i.e GUI 640 with the precalc that comes with it??
Is there a fix for the issue with BI addon ( Bex Analyzer not working) on GUI 640 ??
Regards
Sanjay

Hi Alex,
Yes we have information broadcasting and BI java . Within information broadcasting framework you can broadcast workbooks as well and precalc is required for this. So we are trying use precalc to broadcast workbooks.
Regards
Sanjay

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

Workbook migration BEx 3.5 to Analysis 1.4 SP3

Hi togther,
we are currently in the migration phase at customer site. And we have many performance issue when we start the migration of bex workbooks to analysis workbooks. And we would like to know how we could monitor the migration.
Is there any possibility to create a trace file for the migration where i can see the reason of the system crash?
And the second question is:
Is there a possibilitity to get an progress bar for the migration? I mean the user dont know is the application crashed or is the migration still in progress.
Thanks in advance and best regards
Christian

Hello Christian,
On the first question, are you seeing the log for the conversion? (shown in Figure 4 here SAP BusinessObjects Analysis Office 1.3 – BEx Workbook Conversion Details + Q&A )
Maybe the log will help with the crash?
I don't work for SAP so I can't answer your second question. Maybe enter this in Idea Place as an idea (ideas.sap.com)
Tammy

Report and workbook migration

Hi all,
what are the steps that need to be followed to migrate 3.X queries and workbooks to BI 7.0(2004s)? Or do they automatically get converted?
And is it possible to upgrade the frontend to BI 7.0 and use the new reporting (front end)functionalities, while the back end is still on 3.X?
Any insight or help would be appreciated and rewarded.
Thanks,
Mav

This question is a little ambiguous then as Heike and I have different interpretations. When you say "2004s backend", what do you mean? You need a 2004s spack to use the new functionalities (both backend and frontend).
Within this new stack, the old 3.x runtime exists and you can use it. Within the 2004s stack, you can use 3.x Infosource, transfer rules, update rules. I view this as a 3.x backend in a 2004s environment. So if your dataflow is using 3.x, that doesn't limit you to use only the 3.x tools. You can use the new tools.
I consider using transformations, DTP, etc as 2004s backend functionality.
So to clarify, what are you considering a 3.x backend? The technical requirement is to be on a 2004s stack, which I outlined in my original post... The delineation is the 3.x backend concept or 2004s backend concept in the new stack can both be used and that doesn't influence which frontend tools you can use.

Workbook Migration Issues

Hi Experts,
We are migrating 3.5 workbooks to 7.0 . Can anyone please let me know what could be the issues in the new workbooks due to migration.
Thanks,
AM

Hi,
There will be various issues like; Format issue( lost format, vba,macro codes etc.), design Issues etc.
To retain the fromat after migrating the workbook to 7.0: I did this, in following way:
-save it. At this stage the format is going to be exactly same as 3.x workbook. If you start refreshing, you loose format.
-Go to design mode and deselect 'apply format' option and save it again. Here you can see that you have lost the format.
-Format it again and save it.
-This will work now when you refresh. Refreshing takes.
Pls chk this links;
/people/prakash.darji/blog/2006/09/22/rolling-out-the-new-sap-netweaver-2004s-bi-frontend-tools
/message/3502939#3502939 [original link is broken]
/message/3693377#3693377 [original link is broken]
/message/3502939#3502939 [original link is broken]
http://www.techonthenet.com/excel/macros/refresh_pt2.htm
http://www.dicks-blog.com/archives/2004/09/27/ask-to-refresh/
Re: Where are the BEx variable stored
http://help.sap.com/saphelp_nw04/helpdata/en/f1/0a55f9e09411d2acb90000e829fbfe/frameset.htm
Hope it Helps
Regards
CSM Reddy

NW2004s template migration error

I tried migrating a simple web template with a table item from 3.X to 2004S,SP6. The steps are give below:
1 Created a template in WAD 3.X with a table item.
2 Assigned the dataprovider
3 Saved the template and executed in web-Works fine!
4 Opened WAD2004s
5 Selected the migration tool option.
6 Selected the template created in WAD3.X
7 Performed complete conversion, then close and edit
8 New template is opened in the XHTML view.
9 Saved the template and execute.
ERROR:
Exception in BI runtime
Initial cause
Message:
Cannot find mapping for type "item.MIME_ITEM"
Stack trace:
com.sap.ip.bi.base.exception.BIBaseRuntimeException: Cannot find mapping for type "item.MIME_ITEM"
        at com.sap.ip.bi.base.service.object.impl.DefaultObjectFactoryService.instantiateType(DefaultObjectFactoryService.java:227)
        at com.sap.ip.bi.base.service.object.impl.DefaultObjectFactoryService.instantiateType(DefaultObjectFactoryService.java:211)
        at com.sap.ip.bi.webapplications.runtime.impl.Page.createPageObject(Page.java:1892)

Yes.
See path below.
https://websmp208.sap-ag.de/patches
Entry by Application Group -->
Support Packages and Patches" --> SAP Frontend Components" --> BI ADDON FOR SAP GUI" --> BI 7.0 ADDON FOR SAP GUI 7.10

Error while migrating discoverer Workbook

Hi All,
I am migrating Business Area and Work book from one instance(QA) to another(Production) DB instance.
I have successfully did export of business area and import in production instance.
For workbook migration I have followed the below mentioned steps.
1) Open QA instance and open the required workbook.
2) Do "Save As" of the workbook to local machine as ".DIS".
3)Then Login to Prodcution Open the workbook from the local machine. But in that case it gives following error
" Cannot join tables.Item dependency "" not found in EUL. "
"Attempt to open workbook failed" Anyone can help me to solve this issue. Please.
Thanks
Alaka

Hi Janet
Here are some more notes from my private collection of tips and tricks:
Discoverer workbooks are very picky when it comes to opening up against an end user layer. Basically, here is what happens:
All EUL objects have an ID number and a name. When Discoverer saves a workbook it saves both the ID number and the name of every essential object (business area, folders, items and joins) that is used within the workbook. The next time Discoverer opens the workbook it looks at the ID numbers of the objects and tries to find them in the EUL. If it cannot find an object by its ID number it tries to locate it using the object's name. If an object cannot be located either by its ID number or by its name you will get the dreaded Item Dependency error.
OK, having got that out of the way, if you delete a folder from within the EUL and re-create it you will lose the ID number of the folder and all of its associated objects (items and joins). The only way Discoverer will be able to open this workbook now is if everything within the folder is named EXACTLY the same way (including underscores and casing of the name), otherwise the workbook will not open. Discoverer will report the error message that you are seeing.
So what can you do? Well, you need to have some way of finding out what the old folder name(s), item names and join names were. Also, you need to make sure that all items that were not hidden are not hidden now. There is no need to worry about the names of hierarchies or lists of values. These are not stored within a workbook and are only hooked in at runtime.
Seems like you have to somehow painstakingly determine what all of the item and join names were in your old folder(s) and re-create them 100% the same way in the new folder(s). By the way, when the workbook gives you the error message does it also give you an opportunity to assign al alternative item to the item that it can no longer find a value for? This may work but, in my experience, usually doesn't!! It only works if the missing dependency is an item, it won't work if the error is being caused because you have got a join name wrong. Unfortunately, joins MUST have the same name exactly otherwise there is just no way to open the workbook.
Best wishes
Michael

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.

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

How to export / import workbook by discoverer plus

Hi,
I am an new user of oracle discoverer. We have two database there DB_DEV and DB_PROD. After doing our development in DB_DEV we need to release this development to DB_PROD. But here i am not able to do this. I had tried Export facility of discoverer desktop, but it create export as excel/png file. Could you please guide me how can i resolve the problem.
Thanks
Soumen

Hello
I have a free document on my downloads page at: http://ascbi.com/downloads.htm called Workbook Migration Guidelines. It is a PDF and while it specifically talks about migrating from Discoverer 4i to 10g you could easily use the information inside to export from one EUL to another EUL at the same level using different users. I think you might find this a useful document.
Rather than export using the command line, in 10g you can use Administrator and export workbooks using selected objects from the database.
Best wishes
Michael

OBIEE 10g/11g RPD as a Data Source - Driver Name for metadata imports

Hi,
I'm trying to use OBIEE's RPD as a relational source in Informatica 9.5.1 PowerCenter Designer. I have the ODBC connection to the OBIEE's BI Server and can connect to it. I'm using OBIEE 10.1.3.4.1 (I also need to do something similar with OBIEE 11g). I've posted this question to the Informatica forum as well.
In order to use OBIEE as a third-party relational data source, Informatica needs OBIEE's DLL for metadata imports.
I've tried, with no luck, NQSODBC.DLL & NQSDRIVER.DLL.
Does anyone know what DLL it might be? It could be an issue on Informatica's end as well.
Thanks.

Hi,
For some more details, you can refer to the following document;
http://www.oracle.com/technetwork/developer-tools/discoverer/discoverer-metadata-conversion-assi-128504.pdf
My personal expreriences:
The Metadata Conversion Utility is an accellerator / assistant. It does not provide you with an end product. There is some additional handwork requiered. It could be a risk when you copy an old Oracle Discoverer environment. Shit in is shit out. Last but not least; There is not yet a workbook migration utility.
Cheers,
Daan Bakboord
http://obibb.wordpress.com

Oracle EBS Discoverer as a data source for OBIEE 11g

We are a heavy user of Discoverer workbooks with Oracle EBS. We're moving to OBIEE 11g(11.1.1.3) and have an RPD with both 3rd party and custom content.
I wanted to ask the experts here how I can leverage my Discoverer investment with out a lot of re-work in OBIEE. I briefly looked at the MigrateEUL.exe and it says it can move an EUL to an RPD, but talks about some limitations for complex EULs such as an EBS Apps EUL. Even if it created an RPD, I'm not sure how I can merge my current RPD and this newly gen'd RPD.
I also heard from someone that there is a way to setup Discoverer EUL as a standard data source in OBIEE 11g and consume it directly. I'm looking for a document or blog that explains these steps. Any pointers or experiences with the above is appreciated!!
Thanks.

Hi,
For some more details, you can refer to the following document;
http://www.oracle.com/technetwork/developer-tools/discoverer/discoverer-metadata-conversion-assi-128504.pdf
My personal expreriences:
The Metadata Conversion Utility is an accellerator / assistant. It does not provide you with an end product. There is some additional handwork requiered. It could be a risk when you copy an old Oracle Discoverer environment. Shit in is shit out. Last but not least; There is not yet a workbook migration utility.
Cheers,
Daan Bakboord
http://obibb.wordpress.com

Bex Mihration Issue while comparing the results of Bex analyzer

Dear Experts,
Currenlty i am working on a Bex migration project and we are still in the research and analysis phase. We have been migrating some queries and workbooks in sandbox for analysing the final approach we would be following eventually. For migration we first make a copy of the query and then migrate the copy to the 7.0 version. So after migration the formats in the report generated by Bex analyzer 7.0 of the migrated query and the one generated by Bex analyzer 3.x of the orignal query are quite different.
Can you help me figure out the reason behind this difference in the formats and how to go about it.
regards,
Anupam

Hi Anupam,
Go through the below link
[Migration of 3.x BEx Queries to BI7.0 - Useful Tips |http://wiki.sdn.sap.com/wiki/display/BI/Migrationof3.xBExQueriestoBI7.0-Useful+Tips]
[Queries or Workbooks Migration - Errors and Fixes|https://wiki.sdn.sap.com/wiki/display/BI/QueriesorWorkbooksMigration-ErrorsandFixes]
Regards
KP

3.5 to NW2004s : Workbooks migration

Similar Messages

Maybe you are looking for