Skip to Content
Author's profile photo Former Member

BW Transport – Order of Object list

We can attach all objects in one Transport request, being separated under different tasks and transport it to target system. Provided that the release of the tasks are in the dependent order and then the parent transport is released.


Order of Object list


1 R/3 Objects
2 Development Class – for backend objects
3 Developer Security Roles
4 R/3 Application Component
5 Custom Tablespace /  Custom Data Class
6 InfoObject & InfoObject Catalogs
7 BW Data targets
8 BW Data Mart Data Sources – After Replication & Activation
9 BW InfoSource
10 BW Communication Structure
11 BW Transfer Structure
12 BW Transfer Rules
13 BW Update Rules
14 BW MultiCubes
15 Development Class – for frontend objects
16 BW Custom Tables & Contents
17 BW infoPackages & Groups
18 InfoSet Queries
19 End user security roles
20 BW Function Modules
21 BW “ABAP Reports”
22 BW Customer Exit Objects
23 Variables Customer Exit code
24 BW Reporting Objects
25 BW Queries – Structures / Calculated Key Figure / Restricted Key Figure
26 BW Queries
27 BW Query variants
29 BW APD variants
30 BW Workbooks
31 BW Workbook Folders
32 Jump Targets’ settings
33 Process Chains – start / process variants



Extra tips –


In addition to the Syntax check and the Request Consistency check, another important check is necessary at certain cases – Inactive Objects’ Check. We can use TCode – SE10, where this option is available – Request/Task Menu -> Complete Check -> Display Inactive Objects


In attaching the query elements, if any of the fields are having different ‘Package’ other that your current project works’


      1. For $tmp – mandatory to change it into your current package. You can even do this at one shot by selecting all        such objects, clicking on the change package button over the top screen and proceed.


       2. For other packages – Right click on the object; Select the object Attributes in the context – menu, See if there is a    tick mark in the ‘Repair Flag’ checkbox. If so the DO NOT collect this object in your current transport request, as it will      fail during target import. The reason is any object with ‘Repair flag’ will not take the “M” version from other (lower)   systems on transport write.


In attaching the query elements, if any of the fields are already attached to any other transport number, but not yet released, system will show a warning message about the order of transporting the dependent requests. For reusable components like Restricted key Figures, Calculated Key Figures, structures, user Exits, etc.., one best way is to unlock the other transport requests which is holding these objects and you can proceed with your current transport collection.


Use TCode – SE03, Select Unlock Objects (Expert Tool) below the Requests/Tasks folder.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member
      It is a good article but I'd like to comment on one point.

      In my experience and practical, "20 BW Function Modules" should be transported prior to "11 BW Transfer Structure" because it can be used by ABAP Exit at Transfer Rules or so on.

      Author's profile photo Former Member
      Former Member
      Blog Post Author
      I agree with your point, Ishisone. 🙂
      Yes, ofcourse it is required to consider if you are using any "include" in your routines (Transfer Rules / Update Rules/ SE38 programs). As I said, we can attach any object in ant time, provided that they are in different tasks, and being released in the dependent manner.