Transport Organizational Units (SAP Library

Transport Organizational Units

Use

You can transport organizational units (OUs) with their dependent tables using the RNUTROE0 program. For this purpose, you can select an existing transport request or create a new one.

Caution

Do not run this program until you are familiar with the basic conditions governing its use, how it functions and its possible consequences.

Contact your consultant or SAP Consulting if necessary.

SAP does not accept liability for any damage resulting from the use of this program.

Prerequisites

Ensure that no inconsistencies arise when transporting OUs to another client or another system.

Caution

The system does not perform consistency checks during the transport operation.

Inconsistencies can arise for the following reasons:

Since master data is based on Customizing data, you should always transport the Customizing data first. Always use automatic recording of Customizing changes.

In the target system, you may have already maintained OUs which have the following characteristics:

The OUs do not exist in this form in the source system
The OUs have a different identification key in the source system
The OUs were created in a different order in the source system

The order in which the OUs are created can lead to inconsistencies since address management essentially works with internal assignment and as a result two OUs with identical attributes can have different address numbers in the database.

If you transport OUs without transporting the building units, the assignment of OUs to building units can differ.

The OUs are transported to the target system with the respective release status they have in the source system. In other words, if an OU is not released in the source system and is transported, it is also not released in the target system. Consequently, you should release the building units in the source system prior to executing the transport. You could then run the release program in test mode in the target system to check the result of the transport.

Features

Selection Criteria

You can further restrict the OUs data to be transported by using the following selection criteria on the program selection screen:

Institution
OU
Date created
Date changed
Include the assignments of OU to cost centers

If you wish to include the OU-to-cost center assignments in the transport operation, select With OU-to-Cost Center Asgt.

Note

The selection criteria are linked by an AND operator. Thus if you enter an interval for service creation and change, the transport will include those OUs that were created and changed within the specified time frame.

If, however you want to select all OUs that were created or changed within a given period, you must run the program twice: once specifying the creation interval and a second time specifying the change interval. This could lead to entries appearing more than once in the transport request, but this is of no consequence.

The following data is included in the transport request:

OUs flagged for deletion, to ensure that the flag is passed on to the target system
Long texts for the OUs selected
Entries for the organizational hierarchy
Inter-departmental assignments
Assignment to building units
Statistical beds
Generic entries (‘*’, for instance for the statistical beds) are included in the transport request if the identification key of an OU appears directly in one of the dependent tables.

Example

Example Entries for Statistical Beds

Entries	Transport Request
* - *	These entries for the statistical beds are never included.
* - SURG1	These entries would be included, if the OU SURG1 were selected.

Note

This program does not take doors into account. They are, however, taken into account by the program for transporting building units.

The identifier table is not taken into account either. You should set up the identifiers again in the target system.

Moreover, it is not possible to transport change documents.

Specifications for Program Execution

You can execute the program for transporting OUs in test mode or live mode.

If you run the program in test mode, the system selects the OUs to be transported and checks whether they would be successfully included in the transport request in live mode. However, the objects to be transported are not actually included in the transport request. To run the program in test mode, select Test mode. Even if you have selected Test Mode, you must select or create a transport request. There is no test mode for creating a transport request.
If you run the program in live mode, the system selects the OUs to be transported. To run the program in live mode, deselect Test Mode.

See also:

Transporting Organizational Units