Ansicht
Dokumentation
RSUMOD02 - Modification Adjustment: Dictionary (SPDD)
PERFORM Short Reference Addresses (Business Address Services)This documentation is copyright by SAP AG.
Overview
- Introduction
- Requirements
- Procedure
- Preparations for transaction SPDD
- Transaction SPDD
- Adjusting other systems
- Notes (trouble shooting)
Introduction
This documentation describes how ABAP Dictionary objects are adjusted during upgrading. Transaction SPDD is used for this. This transaction should be executed as soon as upgrade control program R3up calls for it to be started.
Only the following are processed:
- domains
- data elements
- tables (structures, transparent tables, pooled and cluster tables and their technical settings)
Other ABAP Dictionary objects such as lock objects, matchcodes, and views, for which modification would not result in data loss, are not processed during the upgrade with transaction SPDD, but only after the upgrade is complete with transaction SPAU.
If you have not made any changes to ABAP Dictionary objects of the SAP standard version, you do not need to read this documentation. If you have added only developments of your own to the system, that is, only new domains, data elements or table structures belonging to the customer name range, you can ignore this documentation, since only modifications to SAP standard objects require subsequent processing activities.
Requirements
This subsequent processing is based on a comparison of the ABAP Dictionary object before the upgrade (old status) with its status after the upgrade has been performed (new status). Transaction SPDD controls the adjustment and provides you with assistance. If you require information about the object, you will find this in version management.
The displayed ABAP Dictionary objects must now be adjusted to correspond to the new status, since otherwise
data could be lost. During subsequent processing, the ABAP Dictionary objects modified in this system
or by means of customer transport (e.g.
Modifications to ABAP Dictionary objects that you made in a system that was wrongly set to "All change options" are not logged as repairs in the system. As a result, they cannot be displayed. If you not sure that this is the case, read the section "Notes" for a description of the procedure to be followed.
Procedure
Unlike in earlier Releases, an analysis is made in 3.0A in a test phase that determines the precise phases in which adjustment is necessary. This means that, if you have made no or very few ABAP Dictionary changes, you will not be asked to perform ABAP Dictionary adjustment.
If you have made changes to objects that have also been changed by SAP in one of the upgrade sections just imported, you are now only called on to carry out an adjustment in the part of the upgrade that is affected. Even during the test phase, you can see if an adjustment is required. As a result, upgrade control program R3up can show you where adjustment is required as early as the test phase. From this point onwards, you can display the objects found using transaction SPDD (display possible only with source Release higher than 3.0A; when upgrading to Release 3.0A, look at the log file referred to by upgrade control program R3up at operating system level). A comparison of the old status with the new is impossible at this point, since only the object list and not the new objects has been imported at this point.
Preparations for transaction SPDD
Before starting the adjustment the SAP System must be given the status repair system:
- Call transaction STME as user DDIC: Scroll to the end and choose "All objects, with correction system"
- Next log on using your normal user name (user DDIC cannot carry out any repairs).
Please note the following points with respect to modification adjustment:
- Do not work under user DDIC, but under a regular user and ensure that a repair is entered in the correction system if you make a modification to SAP objects.
- Include only SAP ABAP Dictionary objects that are accessed via transaction SPDD in this repair and not any customer objects that you have developed.
- If you create new objects of your own (such as customer APPENDs to an SAP table), please use a separate correction.
- When carrying out ABAP Dictionary maintenance activities (SE11), always save without activating. Activation takes place automatically in the subsequent ACT_
phase.
To ensure support for adjustments in subsequent Release changes and to simplify adjustment in other systems (such as the production system, for example), create a separate transport each time you call transaction SPDD. You then release your repair and correction to this transport. Note the information given in the section 'Adjusting other systems'.
Transaction SPDD
Transaction SPDD uses the Release level just imported as the basis for its work, the import having been stopped by upgrade control program R3up. Transaction SPDD provides these functions, which are described below:
- Object filter
- Comparison of old and new status
- Maintenance
- Return to SAP standard
- Setting 'complete' flag
- Refreshing
- Mark for transport
Object filter
In the first screen you are shown a list of objects changed both by you and by SAP. The list is a hierarchical tree. It can be sorted either by development class or by correction. To switch to the other view, chhose Settings -> Switch.
Within the various development classes or corrections, the objects are displayed sorted by object class. To look at a modified object, select the object in question by double-clicking. If you then select an ABAP Dictionary object, a comparison between the old and new statuses is made automatically.
The objects displayed in the hierarchical tree list are shown in different colors indicating their status. For information on the significance of the different colors, refer to menu option Utilities -> Color key.
Comparison of the old and new statuses
If you select a single object, a comparison of the old and new statuses is displayed in edited form for adjustment purposes. The display corresponds to that displayed by the version management function. The information given always refers to the status of the object after activation. For example, if a table field is marked as deleted, this means that it will be deleted after activation if you do not change anything.
You can get more information on an object from the version management function. The old status of the object always corresponds to the penultimate version stored, while the last version stored corresponds to the status of the object supplied with this upgrade of the SAP System. The last version was generated by the user R3TRANS, while the penultimate version will have been generated by a developer whose name is entered into your system.
Maintenance
Transaction SPDD normally only supplies an analysis. The adjustment must be made using ABAP Dictionary maintenance transaction (SE11) in a second parallel window.
To compare domains and data elements, transaction SPDD provides a comparison of the most important attributes of the old (customer) version and the new (SAP) version. This comparison is intended to assist you in making decisions with respect to the remaining procedure.
When selecting tables, you are not only shown a comparison but also a proposal for the field sequence to be maintained. This proposal takes into account in particular the innovations in the ABAP Dictionary introduced in Release 3.0A (See Release Notes: customer includes/ APPENDs to transparent tables and structures). In the case of transparent tables and structures, you are advised in this proposal to include the fields that you have inserted into a table in a table APPEND in order that the additions you have made are not in future overwritten by SAP. The newly created table APPEND is located in the customer name range.
In the case of the tables, you must proceed within the various object types in the sequence proposed to process includes correctly. Existing includes are always displayed before tables. At this point, you must also adjust includes (structures), otherwise data may be lost.
Return to the SAP standard
If, after analyzing the results of the compare, you decide that you no longer wish to maintain the modifications you made, you should call the function "Return to SAP standard" for the object in question. You will require this function if you at some time manually inserted an SAP preliminary correction. Since the preliminary correction and possibly also additional corrections were supplied with the next SAP upgrade, you can close the preliminary correction.
With the function "Return to SAP standard" you identify the changes made to the object as closed and return to the SAP standard. An object that is identified as closed is no longer displayed in transaction SPDD despite being included in a repair. In the version management display, this status is indicated by the code "C" (closed).
Caution: If you created a customer APPEND for a table and then left the table unchanged, you should close the repair to this table in order that the table is not proposed for adjustment again in transaction SPDD in one of the future upgrades.
Warning: After returning to the SAP standard, the object is treated like any unmodified object and overwritten without saving the old status when an upgrade is carried out.
Setting the closed indicator
To facilitate processing the object list that is generated, you can set any object in the list to status 'closed'. If you select this function, the status of the object is changed, shown by a color change. Assigning an object the status 'closed' is intended to assist you in organizing your work and does not have any kind of internal function.
Refreshing
If you select this function, the information in the database is read in again and the display is updated. This does not affect the number of objects, but only the status of the objects, which is shown through the use of different colors.
Marking for transport
The function "Marking for transport" is helps you in adjusting other systems. For more information, refer to the section "Adjusting other systems".
Adujusting other systems
As well as a production system, you normally also have a test system. If this is the case, an update level is imported first into the test system and, after a quality test, into the production system (or other systems).
To adjust ABAP Dictionary objects in the production system, the same applies as described before. If you are sure that your test system has the same technical status as your production system, you can use a simplified adjustment procedure.
Technically identical means:
- Before the upgrade, the test system had the same Release level as your production system
- In your test system only ABAP Dictionary objects are modified that exist in the same form in the production system or are transferred to the production system.
If these conditions apply, you can copy the ABAP Dictionary modifications adjusted previously in the test system using a transport rather than a second manual adjustment. If you are able to copy a transport, the upgrade will not stop to let you execute transaction SPDD even if ABAP Dictionary objects have been changed. The time required for an upgrade is reduced, an important consideration for a production system.
To describe the procedure, look at both the upgrade of the test system and that of the production system.
Test system upgrade
Perform the adjustment in the test system in the usual way. Make sure that all repairs for a particular phase are collected together in a single transport.
Release the repair and create a transport request when releasing the repair.
Caution: Do not release the transport that is produced but flag the transport for transport to another system with the "Mark for transport" function.
Once transaction SPDD has run, the transport you have marked is exported by the upgrade control program R3up.
Production system upgrade
In the test phase of the upgrade upgrade control program R3up checks if transports exist that you have marked for transport from the test system to a production system. During subsequent analysis during the test phase, another check is made to see if an entry exists in the transport you specified for each modified object found in this system. If this is the case, the upgrade control program R3up suggests that you import the transport automatically rather than maintaining it manually using transaction SPDD. If you agree, you can still opt to stop the upgrade to execute transaction SPDD to check the changes that were copied automatically before activation again yourself.
Even if you do not find an entry corresponding to each modified object in the transport, it may still make sense to import the transport. For example, you may no longer wish to maintain a modification and have not, therefore, made a repair. In this case, the object will not be contained in the transport, and the upgrade control program R3up will indicate that the transport does not contain an entry for every object that is indicated as modified. To obtain more detailed information about the discrepancy, you can log on to the system and call transaction SPDD (display from start Release later than 3.0A possible, when upgrading to 3.0A, look at the log file specified by upgrade control program R3up at operating system level).
Notes (trouble shooting)
- You are not sure if all your modifications to SAP objects were made with system change option "All objects with correction system".
- Call transaction SE01 and use the information system to check if repair requests exist for the objects you have modified.
- The correction and transport system (SE01) does not show any corrections or customer transports, although you know that your system contains SAP standard objects that have been modified:
- If this is the case, you must identify the SAP standard objects that you have modified as modified objects. To do so, include the objects in a repair and release the repair.
CL_GUI_FRONTEND_SERVICES - Frontend Services General Material Data
This documentation is copyright by SAP AG.
Length: 16488 Date: 20240601 Time: 024931 sap01-206 ( 355 ms )
