Initial Transport You need to take certain special aspects into account the first time you transport Customizing objects and settings of consolidation into a production system or another client. We recommend that you perform the initial transport according to the following information.
The recommended process flow for the initial transport is oriented especially towards transporting all the settings in SEM-BCS and in SAP NetWeaver Business Intelligence (BI), which were made during Customizing, into the target system or the target client.
Transport all the BI objects relevant for SEM-BCS to the target system. This includes InfoCubes, key figures, characteristics, queries, and so on. You may also want to transport the ODS objects created when you customized the data bases . This is not absolutely necessary as you can regenerate the ODS objects in the target system using the Consolidation Workbench. However, the advantage of transporting the ODS objects is that you can commence operation of consolidation more quickly in the target system. To transport BI objects, use the transport function of the DataWarehousingWorkbenchof BI. For more information, see Transport System .
Generate transport requests for all objects that you have created in the Consolidation Workbench. Choose
Transport
in the context menu of the appropriate
object type
(for example, data basis, view, consolidation frequency) and enter the selection. Choose
Overwrite
as the update mode for the initial transport. This ensures that a consistent status is imported into the target system.
Note
For the initial transport, be sure to use the transport function of the object type (in the upper left screen area of the workbench) and not the transport function of individual objects . Otherwise incomplete transports can occur for some selected objects (for example, items for which no hierarchy information is transported).
Recommendation
We recommend that you look at Transport to find out more about the system behavior and the effects of the different update modes.
In the target system, make sure that the transport requests for data bases , consolidation areas , and special versions are imported first . All other object types in consolidation are related to each other and can be traced back to these basic object types. As long as these object types do not yet exist in the target system, you cannot consistently import other object types into the target system due to the existing dependencies.
If possible, use separate transport requests for special versions (and for the remaining settings). A successful transport of special versions is the prerequisite that all hierarchy information, method assignments, and other information can be used correctly in the target system.
After you have imported a Customizing transport of consolidation into the target system, import postprocessing is necessary (see
Transport: Additional Information
). As the import normally takes place in a different client (not 000) but postprocessing takes place in client 000, you require an RFC destination that refers to the target client of the transport. If problems occur during import postprocessing due to missing or incorrect RFC destinations, the system displays the error message
FINB_TR 032
“No suitable RFC destination could be found“. The message long text contains more detailed information on the correct Customizing of the required RFC destination.
If after you have performed the initial transport in the Customizing system, you want to make changes to the data basis (add new fields, delete fields that already exist, make changes to the role assignment of fields), you should release these transport requests as early as possible and import them into the target system. Otherwise there can be conflicts with objects that are locked in a transport request that was not yet released due to the dynamic generation of internal technical objects of consolidation.
If you follow the recommendations described in the Process Flow section, you can implement consolidation in the target clients.