Detailed View On Transports and The Common Issues in BW 7.0: Applies To

Detailed View on Transports and the Common Issues in BW 7.
Applies to:
SAP Net Weaver BW 7.0. For more information, visit the EDW homepage
Summary
Detailed view about Transporting Objects & the common issues which we face while transporting and solution to fix those issues.
Author:
Adlin Sundararaj
Company: Accenture Services Pvt. Ltd. Created on: July 19, 2011
Author Bio
Adlin S is working as SAP-BI Consultant in Accenture Services Private Ltd and has 1+ year experience of working on end to end implementation as well as maintenance projects.
SAP COMMUNITY NETWORK 2011 SAP AG
SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1
Detailed View on Transports and the Common Issues in BW 7.0
Table of Contents
Introduction ......................................................................................................................................................... 3 Transport Landscape .......................................................................................................................................... 3 How to Transport - Procedure ............................................................................................................................ 4 Common Issues while Transporting ................................................................................................................... 5 Issues at the Backend - Modeling ...................................................................................................................... 5 Error 1 ............................................................................................................................................................. 5 Error 2 ............................................................................................................................................................. 6 Error 3 ............................................................................................................................................................. 7 Error 4 ............................................................................................................................................................. 7 Error 5 ............................................................................................................................................................. 7 Error 6 ............................................................................................................................................................. 8 Error 7 ............................................................................................................................................................. 8 Error 8 ............................................................................................................................................................. 8 Issues at the Front-end - Reporting .................................................................................................................... 9 Error 9 ............................................................................................................................................................. 9 Error 10 ........................................................................................................................................................... 9 Few More ...................................................................................................................................................... 10 Conclusion ........................................................................................................................................................ 11 Related Content ................................................................................................................................................ 12 Disclaimer and Liability Notice .......................................................................................................................... 13
Introduction
Development projects for Business Intelligence (BI) are generally not performed in a productive system. They are normally carried out in one or more development systems depending on their scope. If you carry out your development projects in a development system, you have to transport the development to a target system (a test or productive system). To do this, the standard transport system has been enhanced in BI to provide the BI transport connection. Using the transport connection in your BI development system, you can collect a consistent amount of new or changed BI objects and then transport them using the Change and Transport Organizer (CTO).
Transport Landscape
The graphic below outlines the transport process in a BI landscape:
A typical system landscape consists of a development system, a consolidation system, and a productive system. You can only transport either between source systems (O1, O2, and O3) or between BI systems (B1, B2, and B3). When we refer to source and BI systems in this documentation, we are referring to the systems in their specific roles. The communication between the source systems and the BI systems takes place when the metadata is replicated and the data is loaded using an RFC (Remote Function Call).
Extractor enhancements and metadata changes are automatically written to transport requests in the source systems. These have to be transported from the development source system to the consolidation source system and from here to the productive source system.
BI objects that are directly or indirectly dependent on the source system need to be handled differently. This ensures that the BI objects recognize the current source system names in the target system landscape.
The DataSource metadata has to be transported from the original source system to the specified target source system and is replicated during import post processing of the assigned BI objects. Make sure that the DataSource exists in the target source systems before you import the dependent BI objects. For example, if a transformation with a DataSource as the source is transported, the transformation can only be activated if the corresponding DataSource exists in the target system.
In the consolidation system, you can test how the transports affect system functions. BI objects are transported as logical objects (TLOGO objects) from an original system to a target system. You can choose from the following transport strategies: Standard Transport System When you create an object, you specify a package for the object and write it to a transport request. BI Transport System When you create an object, it is automatically assigned to a local package. You can subsequently use the BI transport connection to collect all the objects relevant for a scenario, assign them to a package, and write the objects to a request.
How to Transport - Procedure

1. In the Data Warehousing Workbench, choose the Transport Connection functional area (transaction RSOR) by choosing the pushbutton in the left navigation window Or by choosing the menu option Go to Transport Connection. You can display or hide the left navigation window in the Data Warehousing Workbench by choosing Navigation Window On/Off.
2. Collect objects that you want to transport and check the settings. 3. To transport the selected objects, choose Entry dialog box appears. Transport Objects. The Change Object Directory
4. Under Attributes, in the Package field, enter a transportable customer package (beginning with Y or Z). This prompt only appears once for all collected objects. If you want to transport objects in different packages, you must collect the objects more than once. You can change the package assignment subsequently. 5. Save your entries. A dialog box appears where you are prompted for a transport request. 6. In the Request field, enter a transportable request or create a new request first. 7. Choose 8. Choose appears. 9. Release the individual tasks first and then the complete request. Ensure that you release any requests with locked objects beforehand. In the Collected Objects screen area, the system displays the corresponding information for individual objects in the following columns: Last Changed by Last changed by Transport Request Transport Request Holder Package Continue. CTO Transport Organizer: Overview. The Workbench Organizer: Requests screen
10. In the log display in the lower screen area of Collected Objects, check the status of the transport.
Common Issues while Transporting Issues at the Backend - Modeling

Error 1 Error: NOT CORRECT USAGE!
T code ST22 - Runtime Error
Reason: This error occurs when we change the structure of any cube which has BWA Indexes created for it. Change in structure could mean a change as simple as adding a navigational attribute. Fix: Delete the indexes (BWA Indexes), re-import the transport and then rebuild the indexes.
Error 2 Error: The view containing the transfer structure fields could not be imported in target system
Reason: This problem generally occurs due to lack of table space. Fix: Either increase the table space or manually activate the cube or MultiProvider using the programs RSDG_CUBE_ACTIVATE or RSDG_MPRO_ACTIVATE.
Error 3 Error: Info Object not available in active version
Reason: We generally get this error when we try to transport the Info Object Catalogs without transporting the info objects. Fix: As a prerequisite, please transport the info objects before transporting the Catalogs.
Error 4 Error: Password logon no longer possible
Reason: This error occurs when the user ID (DDIC) responsible for sending the transports is either locked or the password for the same has expired. Fix: Unlock the user ID or reset the password as applicable.
Error 5 Error: Dimension can only be manually activated in the target client
Reason: This error mostly occurs for the system configuration. Fix: Active the cube/MultiProvider/aggregate using the program RSDG_MPRO_ACTIVATE/RSDG_CUBE_ACTIVATE
Error 6 Error: Info object is not available in active version
Reason: This error occurs when we try to transport an object (ODS/Cube/Multiprovider) which has an info object which is not available in the target system. Fix: Transport the info object first and then re-import this transport.
Error 7 Error: Navigation attribute does not exist
Reason: If we mark an object in the cube as a navigational attribute and the navigation attribute exist as navigational in the target system we get this error. Fix: Transport the info object with the navigational attribute and then re-import this transport.
does not
Error 8 Error: Structure changed at field level. Table could not be activated.
Reason: This error occurs if we try to change the data type or length of an info object after data has been loaded to it in the target system. Fix: In such cases you need to delete the data first and then adjust the data base with the new data type and length. This can be done using TCODE SE14. Here we need to enter the table name and adjust the database.
Issues at the Front-end - Reporting
Error 9 Error: Element is missing in version M
Reason: This error occurs if all the related/associated objects of a query element are not captured. E.g. a Structure captured without related formulae and selections. Fix: Capture all the related objects and Re-transport.
Error 10 Error: Object has not been imported successfully.
Reason: All dependant/relevant objects are not captured. Fix: Capture all the related objects of the query (CKF/RKF/Variable etc) from transport connection and retransport.
Few More
Log for import post processing only displays the information Error occurred in object <xyz> Possible Cause The log displays the first object in the list that is processed when the after-import function module is called. This object need not necessarily be the object in which the error occurred. Procedure Expand the log. Navigate to the location where the error message occurred. The actual error is displayed here in its context. Where? In the target system
The log for import post processing contains messages that indicate that objects are missing Possible Cause The transport request is inconsistent. Procedure Look for the missing objects on transport requests using the tools of the Transport Organizer (transaction SE03). If the missing object is on another request, import it first. If the missing object is not on a request, collect it and the incorrect object on a request and transport it. Do not import the original request again. Create a merge transport for the consolidation if necessary. Change the package assignment. Then transport the missing object. First import the DataSource in the source system (object type OSOA) and replicate it to the BI system. You can then import the DataSource-dependent BI objects. If the replication of the DataSource is on the BI transport request, replication is not required. You must first import the OSOA objects separately, even for DataSources of the Myself system. The object was imported for the wrong source system. Define the correct target source systems by maintaining the view V_RSLOGSYSMAP. In the target system Where? In the original system
A different package is assigned to the missing object than to the dependent object. The DataSource is not active in the source system.
In the original system
In the target system
Objects are deleted during import post processing although they should have been imported Possible Cause The object was transported as a deletion. You can see this from the piece list of the request in that the objects to be deleted are marked with a deletion indicator. The request was included in a mass import and the object is in more than one request. Procedure Make sure that the object to be transported is active. When delivering BI Content, make sure that the delivery or shadow version exists. Import the requests individually or create a merge transport by merging the object lists of the requests. Where? In the original system
In the target or original system
Objects were not activated or not found (especially process chains and DataSources) Possible Cause The client-dependent parts could not be activated because the transport destination is incorrect or missing. Procedure Maintain the correct transport destination: Where? In the target system
Conclusion
The above said things have to be taken care while transporting.
Related Content
Transporting BI Objects For more information, visit the EDW homepage
Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

Detailed View On Transports and The Common Issues in BW 7.0: Applies To

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Detailed View On Transports and The Common Issues in BW 7.0: Applies To

Uploaded by

Copyright:

Available Formats

Detailed View on Transports and the Common Issues in BW 7.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1