Ansicht
Dokumentation
RNUTRBE0 - IS-H: Transport Building Units
Fill RESBD Structure from EBP Component Structure PERFORM Short ReferenceThis documentation is copyright by SAP AG.
Description
You can use this program to include building units and the associated tables in a change request. In doing so, you can choose an existing request or create a new one.
You can select the building units by:
- Building unit identifier
- Creation date
- Date on which they were last changed
Note
You should only use this program if you are fully aware of the requirements, operation, and consequences. If necessary, contact your consulting partner or SAP Consulting first.
SAP does not accept any liability for damages that can result from using this program.
You cannot use this program if the business function SAP Patient Management Rearchitecture BP/OM (ISH_BP_OM) is active in your system.
Selection
Building units flagged for deletion are included in the request to allow the flag to be copied to the target system.
The hierarchy, planning and fittings characteristics, assigned organizational units, and the doors associated with the selected building units are also taken into account, i.e. the entry is added to the request if the building unit key occurs in one of the associated tables.
SAPscript long texts for the comment field are also taken into account.
Address data records stored in the central address management facility are not included in the transport to prevent number range conflicts in the target system. This does not pose a problem as long as the building units are not changed in the target system.
The identifier table is not included in the transport with the result that the identifiers must be redefined in the target system.
When you select the building units, keep in mind that the selection conditions are logically linked with AND. If you enter a date interval for both the creation date and change date, for example, those building units that were created AND changed in the specified interval are included. If you want to select all the building units that were created OR changed in a given interval, you must execute the program once with the selected creation date and once again with the selected change date. The request may then contain duplicate entries. This, however, is not a problem.
The objects are not added to the request in test mode. Instead, the system checks internally whether they would be successful in an update run. If you have selected Test mode, you must still select a request or create a new one. There is no test mode for creating a request.
Requirements
If you want to want to transport building units to a different client or system, you must make sure that no inconsistencies arise, since consistency checks are not carried out during the transport.
We recommend that you always make changes in one system and then transport them to the other. You should also decide on one transport direction: either from the test to the production system or vice versa. Do not mix the two.
Since master data is based on Customizing data, you should always transport the Customizing data first. For this reason, you should always use the function for recording Customizing changes automatically.
Inconsistencies can still arise if you have already maintained building units in the target system that are not defined in the same manner in the source system, that is if they have a different identifier or were created in a different order. The order in which you create the units is important, since the address management facility assigns numbers internally with the result that two identical building units in the database can have different address numbers.
Inconsistencies can also arise if you transport organizational units without building units, since the assignments between the organizational units and building units are incorrect as a result.
The building units are transported with their release status, that is, if a building unit that is not released is transported, it is also not released in the target system. You should therefore release the units in the source system before you transport them and possibly again in test mode after they have been transported to the target system to check them.
We recommend using this program to transport minor changes. You cannot use this program to transport deleted data - only existing entries can be included in the transport request. If you have made major changes, or deleted data, you might consider transporting the entire tables by including them manually in a transport request. Please be aware of potential inconsistencies, and, if you have any misgivings, contact your consulting team.
Output
The program outputs the following:
- The number of the transport request
- The number of the task
- The total number of records added for each table
TXBHW - Original Tax Base Amount in Local Currency General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 5268 Date: 20240531 Time: 233717 sap01-206 ( 103 ms )
