How To Create Customizing Transport Request In Sap

Transport

You use this function to transport master data and/or Customizing data from the Customizing system to another system (for example, a live system).

Note Note

The transport system for consolidation has various special features that distinguish it from other SAP applications. For more information, see Transport: Additional Information.

End of the note.

Integration

You use this function to create customizing requests, which you release with the Transport Organizer.

Caution Caution

You should not delete or change any objects in the Transport Organizer when transporting master data or customizing data for consolidation. Otherwise, this can lead to inconsistencies after the import to the target system.

End of the caution.

Prerequisites

No further prerequisites apply for the collection of transport requests.

Your system administrator needs to define a valid transport path before the objects can be transported.

Features

You can decide whether you want to transport a selection of objects you defined (for example, all existing consolidation groups or consolidation groups CG1000 to CG2000 and CG9000) for a specific object (such as a consolidation group), or whether you want to specifically select individual objects for the transport.

In addition to objects that belong to the consolidation data model, you can also transport all other Customizing objects (such as methods, tasks, and task groups).

Depending on which type of object you transport, it can be useful to add other objects that are related to the leading transports objects (objects that you explicitly add to the transport) to the transport. Specify which additional objects are to be transported:

Transport Values

You define that the objects (for example, consolidation groups) specified in the selection are to be transported. You do not have to set this indicator. However, if you set it, the consolidation groups are not transported, but the hierarchies of the consolidation groups from the dimensions also selected are transported.
Transport Hierarchy

If you set this indicator, you transport the hierarchies assigned to the leading transport object (for example, consolidation group). Hierarchies are also assigned to the dimension in this case.

You can select a hierarchy version for the transport. This must be a special version of type H0 (Hierarchy Structure). The special version must be configured in Customizing for special versions and assigned to a version combination. The hierarchies must be activated and must be version dependent for the characteristics for which you want to transport only specific versions. For more information, see Customizing of Versions.
Transport Top Node

If you set this indicator, you also transport the top node of the entire hierarchy in addition to the hierarchy nodes to which instances of the leading transport object are assigned.
Transport Text Nodes

If you set this indicator, you also transport the text nodes contained in a hierarchy for structure purposes. These nodes are used to improve the clarity of a hierarchy. You cannot assign objects that can be posted to text nodes.

You choose from different strategies (update mode) for the transport; these affect which objects are included in the transport and how the system treats the values to be imported in the target system:

Update Mode	How values are selected for the transport (system activities)	How the system treats values that already exist in the target system
Delete Selected Values	If you create new objects within the selection after the transport request is created, the system transports these as well.	All objects within the selection specified for the transport are deleted. The objects exported from the source system are then written to the target system.
Delete Transported Values	The system only transports those objects that exist in the source system within the selection at the time the transport request is created.	Objects that were exported and exist in the target system are deleted in the target system. The objects exported from the source system are then written to the target system.
Overwrite	The system only transports those objects that exist in the source system within the selection at the time the transport request is created.	No objects are deleted in the target system. Objects contained in the transport overwrite the corresponding objects in the target system. If a transported object is not available in the target system, it is created.

Update Mode

How values are selected for the transport

(system activities)

How the system treats values that already exist in the target system

Delete Selected Values

If you create new objects within the selection after the transport request is created, the system transports these as well.

All objects within the selection specified for the transport are deleted.

The objects exported from the source system are then written to the target system.

Delete Transported Values

The system only transports those objects that exist in the source system within the selection at the time the transport request is created.

Objects that were exported and exist in the target system are deleted in the target system.

The objects exported from the source system are then written to the target system.

Overwrite

The system only transports those objects that exist in the source system within the selection at the time the transport request is created.

No objects are deleted in the target system. Objects contained in the transport overwrite the corresponding objects in the target system. If a transported object is not available in the target system, it is created.

Replication to the BW System

When transports are imported, the system synchronizes the master data and hierarchies in the BW system with the local data. In Customizing for replication to the BW system, you specify which fields are to be replicated.

To change these Customizing settings, you must be authorized for authorization object R_UGMD_CHA for field name UGMD_TR_SYNCH_BI and activity 02 (Change).

Activities

Activities in the Source System

Transporting Multiple or All Values of an Object

In the navigation hierarchy of the workbench, select an object (for example, Consolidation Unit) and choose Transport in the context menu.
In the selection screen of the transport, proceed as follows:
1. Specify the selection condition for the objects to be transported.
2. Specify which additional objects are to be transported (for example, hierarchies).
3. Specify the strategy the system is to use to import the selected objects into the target system.
4. To create a Customizing request, choose (Execute).
In the Customizing Request dialog box, select a suitable transport request or create a new one. Confirm your entries.

The objects are added to the transport request you specified.

Note

You can specify in the Tools view whether the system is to prompt you to enter a transport request each time you call up the transport function, or whether a request already specified within the session is to be used again automatically. For recommendations on using this setting, see Transport: Additional Information.

End of the note.
To physically transport the objects, you need to release the transport request in the Transport Organizer.

Once you release the transport request, the objects of the request are ready to be imported into the target system.

Transporting Individual Objects

On the detail screen for Customizing objects in the lower left area of the workbench, select the required object or hierarchy, and choose Transport in the context menu.
Continue with the steps outlined in the section on transporting multiple objects, starting with step 3.

Note

When you transport single values, the transported values are deleted before the import into the target system and then reimported.

End of the note.

Activities in the Target System

Creating and Testing an RFC Connection in the Target System

You need to create an RFC connection in the target system before you can import values into the production client of the target system. To do this, follow these steps:

Log on to the target system (to any client). Call up the maintenance function for RFC destinations (transaction SM59).
Choose Create.

The RFC Destination screen appears.

Enter the required data. This includes the following:

Field/Tab Page	Entry
RFC Destination	Logical system name of the target system in capital letters (for example, PRDCLNT324).
Connection Type	3, which stands for R/3 connection
Description	Short description of the RFC destination
Logon/Security	Enter the appropriate user, and for the logon client, enter the client of the target system to which you want to import data.

Choose Save.
To ensure that the network connection between the two systems works properly, choose Test Connection.
To test the authorization of the communication user, choose Test Authorization .

Note

This only tests the communication user, the password, and a basic authorization. This does not test if all authorizations that are required for central user administration exist.

End of the note.
After you have created and tested the RFC destination, make it known to the system as the RFC destination intended for transport postprocessing within the respective target client. To do this, call transaction FINB_TR_DEST and create a new table entry with the required entries.

For more information, see System Users and RFC Destinations.

Importing Values

Prerequisite: In the target system, you have created the data basis and the consolidation area or you have already transported both of them. For more information about the sequence recommended when transporting, see Initial Transport.

To import the objects previously exported into the production client of the target system, send an appropriate request to your system administrator.

Reconciling Number Ranges

Upon posting, the system automatically creates document numbers, which are derived from the number ranges that are assigned to the document types. This means that the number ranges of the document types in the target system need to correspond to those in the source system. However, the transport function for consolidation does not record the number ranges of the document types.

To reconcile the number ranges in the target system with those in the source system, you have the following options:

You manually set up the number ranges of the document types in the target system so that they correspond to those provided in the source system. You make this assignment in document type maintenance on the Properties tab page in the Number Range group box.
You separately transport number range object UC_DOCNR.

To transport number range object UC_DOCNR, proceed as follows:

In the SAP menu, choose Tools ABAP Workbench Development Other Tools Number Ranges .

The Number Range Object Maintenance screen appears.
Enter UC_DOCNR as the object name.
Choose Goto Number Ranges .

The Number Range of Consolidation Document screen appears.
Choose Interval Transport .

A dialog box warns you about the consequences of executing the transport.
Confirm the dialog box.

The system prompts you to enter a transport request.
Enter the required values and confirm.

The system adds the number range object to the transport request.

Caution

Make sure that all necessary objects have been successfully transported to the target system before you start posting in the target system. Posting automatically creates document numbers in the designated number range. Therefore, any subsequent transport of number ranges can cause inconsistent document numbers or can even cause existing documents to be overwritten.

For this reason, after transporting number ranges, make sure that the current numbers in the target system (including the numbers in the buffer) are greater than the currently highest document number assigned in the number range.

End of the caution.