Description
This program lets you include tables from the service masterenvironment and their dependent tables in a change request. You canselect an existing request or create a new one.

Note
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
You can directly specify the name of a correction (task) on theselection screen. This must not be a directly transportable changerequest, but an assigned task of the type SYS. When you enter a name, adialog box does not prompt you to specify a transport request. Thismeans that, if needs be, you can also execute the program in thebackground.
You can select the services according to institution, catalog, servicecode, service group, charge type, service category, date of creationand date of last change. SAPscript long texts are includedautomatically.
Using checkboxes on the selection screen you can stipulate the data forthe selected services that you want to transport:
Services
Service rule tables
Planned values
Assignments/groupings
Default values/preapproved IV
Table entries flagged for deletion are included in the request to allowthe flag to be copied to the target system.
As regards the service selection, keep in mind that the selectionconditions are logically linked with AND. If you enter a date intervalfor both the creation date and change date, for example, those servicesthat were created AND changed in the specified interval are included.If, however, you want to select all of the services that were createdOR changed in a given interval, you must execute the program once withthe selected creation date and one again with the selected change date.a 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, 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 services to a different client orsystem, you must make sure that no inconsistencies arise, sinceconsistency checks are not carried out during the transport.
In particular, you must not transport entries you have previouslymodified directly in the target system, for example the service prices.
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!
Make sure you transport the services before transporting the dependenttables (planned values, for example). It is possible to transportobjects within a request.
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.
Change documents cannot be transported.
The program is intended for transporting smaller changes. Deletionscannot be transported on by this program, since only existing entriesare added to the transport request. There are similar problems withrestricted validity, for instance, if you delimit the validity of aservice at a given date/time. If you have made extensive changes, orcarried out deletions, you may have to transport the complete tables bymanually including them in a transport request. Note especiallyconsistency here, and contact your consultant, if necessary.

Output
The number of table entries that were written to the transport requestis output for each service and table selected.
When tables contain several services (NTPZ - service assignments, forexample), the output does not support the formation of totals, sinceonly one entry for two services assigned to one another is written tothe transport request.
The total log at the bottom of the list contains the number of entriesactually written to the transport request.
Example:
Service A, 1 NTPK record, 1 NTPZ record
Service B, 1 NTPK record, 1 NTPZ record
Total number of NTPK records is 2.
The total number of NTPZ records need not be two, since there may be anNTPZ record in which service A is assigned to service B, therebynecessitating the transport of only one table entry.