Ansicht
Dokumentation
RNUTRLK0 - IS-H: Transport Service Master Data
BAL_S_LOG - Application Log: Log header data Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
Description
You can use this program to include tables from the service master environment in a change request, together with the dependent tables. You can select an existing request or create a new one.
Note
You should only run this program if you are fully aware of the requirements, operation, and consequences. If necessary, please contact your consulting partner or SAP Consulting first.
SAP does not accept any liability for damages that can result from using this program.
Selection
You can directly specify the name of a correction (task) on the selection screen. This must not be a directly transportable change request, but an assigned task of the type SYST. When you enter a name, the system does not display a dialog box prompting you to specify a transport request. This means that you can also run the program in background processing, if necessary.
You can select the services according to the institution, catalog, service code, service group, charge type, service category, creation date, and the date on which they were last changed. SAPscript long texts are included automatically.
You can specify on the selection screen which data you want to transport for the selected services:
- Services
- Service rule tables
- Planned values
- Assignments/groupings
- Default values/pre-approved insurance verification
- Additional data for service master Switzerland
- Additional data for service master Italy
Table entries that are flagged for deletion are included in the request so that the deletion flag is transferred to the target system.
When selecting the services, bear in mind that the selection conditions are logically linked with AND. This means if you enter a date interval for the creation date and the change date, the system includes services that were created AND changed during this interval. However, if you want to select all services that were created OR changed within a given period, you must run the program twice: once specifying the creation date and a second time specifying the change date. The request may then contain duplicate entries, but this is not a problem.
The objects are not actually added to the request in test mode. Instead, the system checks this internally to determine whether they would be added successfully in an update run. If you select 'Test Mode', you must still always select a request or create a new one. There is no test mode for creating a request.
Requirements
If you want to use the function for transporting services to a different client or system, you must ensure that no inconsistencies result, since consistency checks cannot be run during transport.
In particular, you must not transport entries you have just modified in the target system, for example the service price.
You should always make changes in one system and then transport them to the other. You should decide on one transport direction: either always from the text system to the productive system, or vice versa, but not one direction and then the other.
Make sure you transport services before transporting dependent tables (for example, planned values). It is possible to transport within a request.
Since master data is based on Customizing data, you should always transport the Customizing data first. You should therefore always use automatic recording of Customizing changes.
It is not possible to transport change documents.
The program is intended for transporting minor changes. You cannot use the program to transport deletions, since only existing entries are added to the transport request. There are similar programs with restricted validity periods, for example if you delimit the validity of a service at a given time. If you make extensive changes, delimit the validity of services or delete them, you may have to transport the entire tables by manually adding them to a transport request. Here too, it is vital that you ensure consistency. Contact your consulting partner if necessary.
Output
The program outputs the number of table entries written to the transport request for each selected service and each table.
When tables contain several services (for example, the service assignments table NTPZ), output does not support the formation of totals, since only one entry is written to the transport request for two services that are assigned to each other.
The full log at the end of the list contains the number of entries actually written to the transport request.
Example:
Service A, 1 NTPK record, 1 NTPZ record
Service B, 1 NTPK record, 1 NTPZ record
The total number of NTPK records is 2.
The total number of NTPZ records is not necessarily two, since there may, for example, be an NTPZ record in which service B is assigned to service A, so that only one table entry needs to be transported.
PERFORM Short Reference CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 5287 Date: 20240531 Time: 173332 sap01-206 ( 106 ms )
