Details Description Of SPAU & SPDD
Describe SPAU and SPDD.
When you apply a package, a large number of objects are changed.If you have applied any OSS notes to objects in your system, the hot package mayoverwrite these objects.SPDD is used to identify dictionary objectsandSPAU (repository objects), will identify any objects where the hot package is overwritingchanges you have made through OSS notes.You must check all objects identified in SPAU and decide whether you need to reapplythe OSS note or reset the code to the original SAP Code.If, for instance, you are applying hot package 34, SPAU identifies an object where youhave applied an OSS note. You must check the OSSs note and see if SAP have fixed thatnote in a hot package.If the OSS note has been fixed in hot package 34, then you should reset the object to itsoriginal source code. This means that there is no repair flag set against this object againand it is now SAP standard code.If, however, the object is not fixed until hot package 38, or there is no fix available youhave to reapply the OSS note, otherwise users will encounter the problems they had before the note was applied.You must transport all reapplied notes and Reset to SAP Standard objects after you applyyour hot package to your QAS and PRD systems.
What objects will come in SPAU and SPDD?
All the objects which are modified, after tansporting to the current system, will be listedin SPAU and SPDD. SPDD contains the list of all modified Data Dictionary objects, liketables, dataelements, domains,view...etc. The rest of all the modified repository objectswill be listed in SPAU.
What happens to the modifications done in the older version when we upgrade theversion? (with Modification assistant and w/o)
After the initial upgrade happens, we have to do adjustments from SPAU/SPDD tomaintain or reset the changes. That is, from the list of objects in SPAU/SPDD, you have