Skip to Content

Summary:

This document provides the directives needed to collect & reorganize transport requests from an ECC system to a BW system.

Introduction:

The transport procedures from an ECC system to a BW system are covered in this document.

Assumption taken into account is the Transport flow process from a Dev – > Qual -> Prod environment finally.

We will not go into the basics of “What is a Request/ Package?”, as most BI persons will be familiar with the terms.

In the below sections we will look into a scenario of a dataflow, ranging from a Datasource with enhancement of fields to the transformation, DTP, DSO’s, Info provider’s & the corresponding reports associated with it.

Transport collection and sequencing in ECC:

Collect your changes related to table, views, datasources, append structure, CMOD in a single request. Collecting in a single request will not take much time while transporting to target system. Make sure you have properly commented in the description of the transport request mentioning in short what the transport request contains.

E.g.: If it is a CR which involves changes in CMOD and changes in the Datasource, I would mention as

CRXXXX – Chng in CMOD, Enhancement for 2LIS_02_ITM

A look at the description will give me in instance what this request contains.

Transport collection and sequencing in BI:

Collect in the following order and make sure you collect them in separate requests.

1.Info Area

2.Info Object Catalog

3.Info Objects

E.g.: Consider for a CR/Module I’m collecting the request, the description would be

CRXXXX – Info Area & Info Object Catalog

CRXXXX – InfoObjects

          OR

You can combine them both.

Info Providers:

4.Info Cubes

5.Multi Providers

6.Info Sets

7.Data Store Objects

8.Info Cube Aggregate

E.g.: Consider for a CR/Module I’m collecting the request, the description would be

CRXXXX – InfoCubes

CRXXXX –DSO’s

CRXXXX –Multi Providers

Note: Make sure you transport Info Cube Aggregates, Multiproviders and Infosets after transport of corresponding InfoCubes & DSO’s.

Datasources:

9.Application Components

10.Data Source replica

11.Data sources (Active version)

E.g.: Consider for a CR/Module I’m collecting the request, the description would be

CRXXXX –Datasources

Note: Application Components can be placed within this same request.

Rules: This contains of:

12.Communication Structure

13.Transformations

14.Info Source Transaction data

15.Transfer Structure

16.Transfer Rules

17.Routines & BW Formulas used in the Transfer routines

18.Extract Structures

19.Update Rules, which may have:

20.Routines associated with them.

E.g.: Consider for a CR/Module I’m collecting the request, the description would be

CRXXXX –Transformations

CRXXXX –Update Rules & Transfer Rules

CRXXXX –Infosource

Note: If you need to collect before & after image of the transformation, collect in a same transport request.

Info Packages & DTPs:

21.Info Packages

22.DTPs

E.g.: Consider for a CR/Module I’m collecting the request, the description would be

CRXXXX –Infopackages & DTP’s

Note: This can be collected the same request or broken into Infopackages / DTP’s transport requests.

Process Chains:

23.Process Chains

24.Process Chain Starter

25.Process Variants

26.Events

E.g.: Consider for a CR/Module I’m collecting the request, the description would be

CRXXXX –Process Chain ‘NAME OF PROCES CHAIN’

Note: Recommended to collect all objects of process chain in the same requestPre-requisite – Make sure the DTP’s and Infopackages are transported to the target & are active.

Reports/Queries:

27.Variables

28.Calculated Key Figures/Formula

29.Restricted Key Figures

30.Structures

31.Query

32.Work Books

33.Web Templates

E.g.: Consider for a CR/Module I’m collecting the request, the description would be

CRXXXX –Query Name description

Note:

1) Include in the description technical name if desired.

2) Workbooks could be collected in the same or different request.

3) All the query objects are automatically store in BEx request. Make sure you remove only the contents of the query from the BEx request and then align the objects to the assigned transport request.

Transport Import Sequence:


1.Collect objects from ECC side and make sure it is transported successfully.

2.Collect BI Objects in the below sequence

    1. Info Area/Info Object Catalog/Info Objects.
    2. Info Cubes/Data Store Objects.
    3. Info Cube Aggregate/Multi Providers/Info Sets.
    4. Data sources/Application Components/Data Source replica.
    5. Transformations/Update Rules – Routines associated with them /Infosource.
    6. Info Packages & DTPs.
    7. Process Chains
    8. Reports/Queries.

Important points:


  • Transport Collection Timing – Do not start transporting until the development is stable. When new objects are created (e.g. InfoObjects, DSOs) these are by default created as local objects ($TMP). Leave all new objects as $TMP until they are absolutely ready for transport.
  • Transport Request Deletion – Do not delete any transport Requests in the DEV system. If you do not require a transport request to be transported, rename and append “DO NOT TRANSPORT” in the name. 
  • Make sure that the ECC transports that are required by the BW transports are successfully imported before the BW transports – Make sure that ECC DataSources are replicated prior to initiating the BW transports.
  • Maintain a Transport Status Log – A transport log should be maintained in order to track the status of transports.

Related Content:


Transport Connection and using objects.

Transport Sequence in SAP BW

Transport specific infoobject in BW

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply