15-05-2012, 01:38 PM
SPDD and SPAU Adjustments Handbook
SPAU.pdf (Size: 366.37 KB / Downloads: 681)
Introduction
This document was created with a basic premise of providing a user manual for the ABAP developers involved with the SAP Upgrade projects, and help them out in executing the SPDD and SPAU transactions more smoothly and efficiently.
During an upgrade or the import of a Support Package, existing objects of the SAP standard are overwritten with the objects redelivered. To help the customer retain the objects modified in a previous release, SAP provides all modified objects which are redelivered (in an upgrade or Support Package) in the upgrade adjustment of transactions SPDD and SPAU. These transactions allow customers to enter their modifications into the corresponding new objects being delivered at the time of upgrade. The Modification Assistant supports this process of adopting customer modifications.
SPDD Adjustments for Data Dictionary
SPDD activities will be carried out during the upgrade phase when it prompts for, otherwise whatever customizations that we have done will be lost. Using SPDD, we can adjust Domains, Data elements, Tables, Structures, Transparent tables, indexes of transparent tables, pooled and customer tables including their technical settings. After the SPDD adjustment, system may display the Dictionary objects in transaction SPAU in the sub tree ‘Without Modification Assistant’. The objects themselves are not modified during this process. The system only deletes the log entry.
Go to transaction SPDD and execute it after checking the relevant checkboxes. You will get the screen more or less similar to the below one depending upon the objects that are available in your system for adjustment. As you could see from the below screen shot, you will get objects with traffic light icon on its side.
SPAU Adjustments for Repository Objects
SPAU transaction will identify any objects (repository objects), where the hot package is overwriting changes that we have made through OSS notes. We must check all objects identified in SPAU and decide whether we need to reapply the OSS note or reset the code to the original SAP Code. If, for instance, we are applying hot package ‘XX’ SPAU identifies an object where you have applied an OSS note. We must check the OSS notes and see if SAP has fixed that note in this hot package. If the OSS note has been fixed in hot package ‘XX’, then we should reset the object to its original source code. This means that there is no repair flag set against this object again and it is now SAP standard code.