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 adjustedduring upgrading. Transaction SPDD is used for this. This transactionshould be executed as soon as upgrade control program R3up calls for itto be started.
Only the following are processed:
domains
data elements
tables (structures, transparent tables, pooled and cluster tables andtheir technical settings)
Other ABAP Dictionary objects such as lock objects, matchcodes, andviews, for which modification would not result in data loss, are notprocessed during the upgrade with transaction SPDD, but only after theupgrade is complete with transaction SPAU.
If you have not made any changes to ABAP Dictionary objects of the SAPstandard version, you do not need to read this documentation. If youhave added only developments of your own to the system, that is, onlynew domains, data elements or table structures belonging to thecustomer name range, you can ignore this documentation, since onlymodifications to SAP standard objects require subsequent processingactivities.

Requirements
This subsequent processing is based on a comparison of the ABAPDictionary object before the upgrade (old status) with its status afterthe upgrade has been performed (new status). Transaction SPDD controlsthe adjustment and provides you with assistance. If you requireinformation about the object, you will find this in version management.
The displayed ABAP Dictionary objects must now be adjusted tocorrespond to the new status, since otherwise data could be lost.During subsequent processing, the ABAP Dictionary objects modified inthis system or by means of customer transport (e.g. K9*) fromanother system are displayed for you to adjust them. Versions arechanged of objects that you changed by transporting them into thesystem in the test phase prior to the upgrade to ensure that the oldstatus is not lost. Before you can make changes to the newly importedSAP object, the status of this object is also stored in the versionsdatabase.
Modifications to ABAP Dictionary objects that you made in a system thatwas wrongly set to "All change options" are not logged as repairs inthe system. As a result, they cannot be displayed. If you not sure thatthis is the case, read the section "Notes" for a description of theprocedure to be followed.

Procedure
Unlike in earlier Releases, an analysis is made in 3.0A in a test phasethat determines the precise phases in which adjustment is necessary.This means that, if you have made no or very few ABAP Dictionarychanges, you will not be asked to perform ABAP Dictionary adjustment.
If you have made changes to objects that have also been changed by SAPin one of the upgrade sections just imported, you are now only calledon to carry out an adjustment in the part of the upgrade that isaffected. Even during the test phase, you can see if an adjustment isrequired. As a result, upgrade control program R3up can show you whereadjustment is required as early as the test phase. From this pointonwards, you can display the objects found using transaction SPDD(display possible only with source Release higher than 3.0A; whenupgrading to Release 3.0A, look at the log file referred to by upgradecontrol program R3up at operating system level). A comparison of theold status with the new is impossible at this point, since only theobject 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 statusrepair 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 modificationadjustment:

• 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 modificationto SAP objects.

• Include only SAP ABAP Dictionary objects that are accessed via
transaction SPDD in this repair and not any customer objects that youhave 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 thesubsequent ACT_ phase.
To ensure support for adjustments in subsequent Release changes and tosimplify adjustment in other systems (such as the production system,for example), create a separate transport each time you calltransaction SPDD. You then release your repair and correction to thistransport. Note the information given in the section 'Adjusting othersystems'.

Transaction SPDD
Transaction SPDD uses the Release level just imported as the basis forits work, the import having been stopped by upgrade control programR3up. Transaction SPDD provides these functions, which are describedbelow:
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 youand by SAP. The list is a hierarchical tree. It can be sorted either bydevelopment class or by correction. To switch to the other view, chhoseSettings -> Switch.
Within the various development classes or corrections, the objects aredisplayed sorted by object class. To look at a modified object, selectthe object in question by double-clicking. If you then select an ABAPDictionary object, a comparison between the old and new statuses ismade automatically.
The objects displayed in the hierarchical tree list are shown indifferent colors indicating their status. For information on thesignificance of the different colors, refer to menu optionUtilities -> Color key.

Comparison of the old and new statuses
If you select a single object, a comparison of the old and new statusesis displayed in edited form for adjustment purposes. The displaycorresponds to that displayed by the version management function. Theinformation given always refers to the status of the object afteractivation. For example, if a table field is marked as deleted, thismeans that it will be deleted after activation if you do not changeanything.
You can get more information on an object from the version managementfunction. The old status of the object always corresponds to thepenultimate version stored, while the last version stored correspondsto the status of the object supplied with this upgrade of the SAPSystem. The last version was generated by the user R3TRANS, while thepenultimate version will have been generated by a developer whose nameis entered into your system.

Maintenance
Transaction SPDD normally only supplies an analysis. The adjustmentmust be made using ABAP Dictionary maintenance transaction (SE11) in asecond parallel window.
To compare domains and data elements, transaction SPDD provides acomparison of the most important attributes of the old (customer)version and the new (SAP) version. This comparison is intended toassist you in making decisions with respect to the remaining procedure.
When selecting tables, you are not only shown a comparison but also aproposal for the field sequence to be maintained. This proposal takesinto account in particular the innovations in the ABAP Dictionaryintroduced in Release 3.0A (See Release Notes: customer includes/APPENDs to transparent tables and structures). In the case oftransparent tables and structures, you are advised in this proposal toinclude the fields that you have inserted into a table in a tableAPPEND in order that the additions you have made are not in futureoverwritten by SAP. The newly created table APPEND is located in thecustomer name range.
In the case of the tables, you must proceed within the various objecttypes in the sequence proposed to process includes correctly. Existingincludes are always displayed before tables. At this point, you mustalso 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 nolonger wish to maintain the modifications you made, you should call thefunction "Return to SAP standard" for the object in question. You willrequire this function if you at some time manually inserted an SAPpreliminary correction. Since the preliminary correction and possiblyalso 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 changesmade to the object as closed and return to the SAP standard. An objectthat is identified as closed is no longer displayed in transaction SPDDdespite 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 thenleft the table unchanged, you should close the repair to this table inorder that the table is not proposed for adjustment again intransaction SPDD in one of the future upgrades.
Warning: After returning to the SAP standard, the object istreated like any unmodified object and overwritten without saving theold status when an upgrade is carried out.

Setting the closed indicator
To facilitate processing the object list that is generated, you can setany object in the list to status 'closed'. If you select this function,the status of the object is changed, shown by a color change. Assigningan object the status 'closed' is intended to assist you in organizingyour work and does not have any kind of internal function.

Refreshing
If you select this function, the information in the database is read inagain and the display is updated. This does not affect the number ofobjects, but only the status of the objects, which is shown through theuse of different colors.

Marking for transport
The function "Marking for transport" is helps you in adjusting othersystems. For more information, refer to the section "Adjusting othersystems".

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 testsystem and, after a quality test, into the production system (or othersystems).
To adjust ABAP Dictionary objects in the production system, the sameapplies as described before. If you are sure that your test system hasthe same technical status as your production system, you can use asimplified 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 tothe production system.
If these conditions apply, you can copy the ABAP Dictionarymodifications adjusted previously in the test system using a transportrather than a second manual adjustment. If you are able to copy atransport, the upgrade will not stop to let you execute transactionSPDD even if ABAP Dictionary objects have been changed. The timerequired for an upgrade is reduced, an important consideration for aproduction system.
To describe the procedure, look at both the upgrade of the test systemand that of the production system.

Test system upgrade
Perform the adjustment in the test system in the usual way. Make surethat all repairs for a particular phase are collected together in asingle transport.
Release the repair and create a transport request when releasing therepair.
Caution: Do not release the transport that is produced but flagthe transport for transport to another system with the "Mark fortransport" function.
Once transaction SPDD has run, the transport you have marked isexported by the upgrade control program R3up.

Production system upgrade
In the test phase of the upgrade upgrade control program R3up checks iftransports exist that you have marked for transport from the testsystem to a production system. During subsequent analysis during thetest phase, another check is made to see if an entry exists in thetransport you specified for each modified object found in this system.If this is the case, the upgrade control program R3up suggests that youimport the transport automatically rather than maintaining it manuallyusing transaction SPDD. If you agree, you can still opt to stop theupgrade to execute transaction SPDD to check the changes that werecopied automatically before activation again yourself.
Even if you do not find an entry corresponding to each modified objectin the transport, it may still make sense to import the transport. Forexample, you may no longer wish to maintain a modification and havenot, therefore, made a repair. In this case, the object will not becontained in the transport, and the upgrade control program R3up willindicate that the transport does not contain an entry for every objectthat is indicated as modified. To obtain more detailed informationabout the discrepancy, you can log on to the system and calltransaction SPDD (display from start Release later than 3.0A possible,when upgrading to 3.0A, look at the log file specified by upgradecontrol 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 repairrequests 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 systemcontains SAP standard objects that have been modified:
If this is the case, you must identify the SAP standard objects thatyou have modified as modified objects. To do so, include the objects ina repair and release the repair.