Error Free Transport

7/28/2019 Error Free Transport

1/39

Company Confidential


2/39

Error Free Transport

Rashmi Mangal


3/39


Contents

Overview of BI Transport Process

Common Pitfalls, Problems, Errors, and

Solutions

Tips and Tricks


4/39


System Landscape

A typical system landscape consists of a development, quality and productionsystem both on the R/3 and on the BW side.First objects are developed on development system. Unit testing is done on thissystem. After that the objects are moved to quality system. Here integration,user acceptance testing are done. After quality approval, the objects aretransported to production system.

BWSystems

DevelopmentSystem

DevelopmentSystem

QualitySystem

QualitySystem

ProductionSystem

ProductionSystem

R/3Systems

RFC RFC RFC

Sand Box

Sand Box


5/39


Object Dependencies: R/3 Objects

When transporting, object dependencies need to be taken into

Account In R/3, InfoSets must be transported, then DataSources,

then the User Exits/BAdIs If this sequence is not followed, the

transports will fail

InfoSet

Data Source

User Exits/ BAdIs


6/39


Object Dependencies: Info Objects

InfoObjects are usually transported first in SAP BW in the order

of dependency For example: Objects without master data, then text, attributes,

hierarchies, and key figures InfoAreas are transported afterwards and may need to be

transported several times in the final recipe to have all objects located in the correct

location Info area

Info Object Catalog

Info ObjectInfo Cube ODS

Update Rules

1

2

3


7/39Company Confidential

Object Dependencies: Info Source Objects

For Info Source Objects, the application component, source system, and data

source go first The Info Source should include the communication structure,

transfer rules and structure Info Packages are last

Communication Structure

Transfer Rules

Transfer Structure

InfoPackage

InfoSource

Application Component

Source System

Data Source

1

2

3

4

5



Object Dependencies: InfoProviders

Info Providers such as Info Cubes and ODSs are transported first

then their update rules Here the Info Area is transported again to

put the Info Providers in the correct place

Info Object Catalog

Info ObjectInfo Cube ODS

Info Area

Update Rules

1 1

2

3



Object Dependencies: Query Elements

All query elements that are used by several queries should be collected

together calculated and restricted key figures, structures, formulas, and

variable Queries should always be transported last

Calculated Key Figure

Restricted Key Figure

Structure Formula

InfoCube ODS

Query

Variables

Query Element



Transport Procedure

Grouping the objects

Create new transport request

Release the request

Check the status of request using STMS in target

system


11/39


Transport Procedure

Grouping the objects

Create new transport request

Release the request

Check the status of request using STMS in target

system


12/39


Grouping (Cont

In the menu Groupingyou can determine how many objectsshould be taken into consideration. The groupings summarizeall the objects of an area.


13/39


Grouping (Cont)

Setting Option MeaningOnly necessary

objects

Only those objects that are really necessary for action,

that is, the transport of the selected objects, are only

taken into the account (minimal selection).

In data flow before All objects are collected that submit data to a

collected object.

In data flow after All objects are collected that obtain data from a

collected object.

In data flow before

and after

All objects are collected that submit and collect data.


14/39


Collection Mode

Collection mode specifies that how the objects are collected for the

transport. There are two modes for transporting:

1. Collect Automatically

2. Start Manual Collection

With collect automatically the data is collected directly when selecting

objects

With start manual collection, the data is collected by first choosing

the pushbutton gather dependent objects


15/39


Transport Connection View

This screen shows the Transport Connection from theAdministrator WorkbenchFrom the Object Types, select the objects needed, drag them tothe right-side window and write the transport request1. Select one or several objects2. Drag and Drop objects or use context menu

3. Write to transport request New objects (development class $TMP) aremarkedautomatically

1. Select oneor severalObjects

2. Drag & DropObjects (or use

context menu)

3. Write totransport request

New Objects(Development class $TMare marked automaticall


16/39


Change the default Package

Change the

Package


17/39


Assign new Package to transport the objects


18/39


Creating new transport request

Create a newtransport request


19/39


Objects are written under the request

Check status of transport

Always check the status to ensureeverything is green after collecting

the objects


20/39


Releasing the request using transaction SE01

Transport Request Number


21/39


Syntax checking of Request


22/39


Request Details

Release the request


23/39


Released requests


24/39


Transport Organizer (SE09)

The Transport Organizer is used to display and organize all

transport requests SAP BW transports are saved as Workbench

Requests and are modifiable until they are released To restrict

the selection, include your User ID


25/39


Transport Organizer (SE09)(cont..)

Enter the User

Choose Workbenchrequests for SAP

BW transports

Select Modifiablefor Request statusand then Display


26/39


Transport Organizer (Transaction Code: SE09)


27/39


STMS: Import Queue List in target system


28/39


STMS (Cont)


29/39


STMS: Transport Request Log


30/39


Log Details


31/39


Detecting Problems by Reading Return Codes

TMS will provide the following return codes:

0000: Successful

0004: Successful with warnings

Means that the transport was successful but may still

need to be checked for errors

0008: Imported with errors

Transport was not successful, and object may be partially transported

Need to check what is cause of error


32/39


Detecting Problems by Reading Return Codes (cont.)

TMS will provide the following return codes (cont.):

0012: Transport terminated

Transport was not successful, and object not transported to

target

If the error is an import error, contact Basis

0013: Transport tool terminated by operating system

0016: Internal transport tool error


33/39


Common Errors Transporting

The transport gives the error that the target was repaired

Solution: Ensure transport selection overrides repaired

objects.

The RFC connection is missing

Solution: Do a source system check and repair RFC

connection.


34/39


Common Errors Interval Number Range is not Assigned

The numerical range is not assigned for the object

Solution: Go to transaction SNUM

Input the BIM number and create an interval


35/39


Error with Master Data Object

Master data object was changed

Solution: Delete all existing data in ODS and Info Cubes prior to

transporting changed objects

Error with activation of changed objects

Solution: Convert the master data table in the target system

Go to transaction SE14 and select the object table name /BIC/Pxxxxxxx


36/39


Common Errors Transporting

Error when activating update rule of ODS

Solution: it was because the Info Objects associated with the ODS

were not activated.


37/39


Tips

Be careful when adding objects as attributes for dependencies.

It would be better to activate an InfoObject without the attribute,

transport the attribute, then re-transport the changed InfoObject

with the attribute in it

Double-team the checking of transports

Have someone that didnt collect the transport check them and

vice versa

Check in the SE09 that all objects collected dont have

unwanted objects collected in them by accident


38/39


Tips

Dont put everything in one transport!

Dont send your entire recipe at once.

Send logical chunks of transports together and ensure they are

good before sending the next batch


39/39

THANKS

Error Free Transport

Documents

Transcript of Error Free Transport