Description
This program enables you to include organizational units and theirdependent tables in a change request. You can choose an existingrequest or create a new one.
You can select the organizational units according to the institution,identification key of the organizational unit, the date on which theorganizational unit was created, and the date on which theorganizational unit was last changed.

Important!
You should only use this program if you are fully aware of therequirements, operation, and consequences. If necessary, please contactyour consulting partner or SAP Consulting first.
SAP does not accept any liability for damages that can result fromusing this program.

Selection
Organizational units flagged for deletion are included in the requestto allow the flag to be copied to the target system.
SAPscript long texts for the comment field are taken into account. Theentries for the hierarchy, inter-departmental bed assignments,assignment to building units, and statistical beds are also taken intoaccount. Generic entries (*) are included in the request if the key ofan organizational unit occurs directly in one of the dependent tables.Consequently, generic entries that follow the pattern '*'-'*' are neverincluded for statistical beds, whereas a generic entry such as'*'-'SURG1' would be included if the organizational unit 'SURG1' wasselected.
Address data records stored in the central address management facilityare not included in the transport to prevent number range conflicts inthe target system. This does not pose a problem as long as theorganizational units are not changed in the target system.
Doors are not included, but are processed by program RNUTRBE0(Transport Building Units) instead. The identifier table is notincluded in the transport either. This means that the identifiers haveto be redefined in the target system. Change documents cannot betransported.
You also have the option of including the OU/cost center assignments.You do this by flagging the appropriate field on the selection screen.
When you select the organizational units, keep in mind that theselection conditions are logically linked with an AND operator. If youenter a date interval for both the creation date and change date, forexample, those organizational units that were created AND changed inthe specified interval are included. If you want to select all theorganizational units that were created OR changed in a given interval,you must execute the program once with the selected creation date andonce again with the selected change date. The request may then containduplicate entries. This, however, is not a problem.
The objects are not added to the request in test mode. Instead, thesystem checks internally whether they would be successful in an updaterun. If you have selected 'Test mode', you must still select a requestor create a new one. There is no test mode for creating a request.

Precondition
If you want to want to transport organizational units to a differentclient or system, you must make sure that no inconsistencies arise,since consistency checks are not carried out during the transport.
You should always make changes in one system and then transport them tothe other. You should also decide on one transport direction: eitherfrom the test to the production system or vice versa. Do not mix thetwo!
Since master data is based on Customizing data, you should alwaystransport the Customizing data first. For this reason, you shouldalways use the function for recording Customizing changesautomatically.
Inconsistencies can still arise if you have already maintainedorganizational units in the target system that are not defined in thesame manner in the source system, that is if they have a differentidentifier or were created in a different order. The order in which youcreate the units is important, since the address management facilityassigns numbers internally with the result that two identicalorganizational units in the database can have different addressnumbers.
Inconsistencies can also arise if you transport organizational unitswithout building units, since the assignments between theorganizational units and building units are incorrect as a result.
The organizational units are transported with their release status,that is, if an organizational unit that is not released is transported,it is also not released in the target system. You should thereforerelease the units in the source system before you transport them andpossibly again in test mode after they have been transported to thetarget system to check them.
You should use this program for transporting minor changes. You cannotuse this program to transport deleted data - only existing entries canbe included in the transport request. If you have made major changes,or deleted data, you might consider transporting the entire tables byincluding them manually in a transport request. Please be aware ofpotential inconsistencies, and, if you have any misgivings, contactyour consulting team.

Output
The number of the transport request, the number of the task and thetotal number of records added for each table are output.