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 may overwrite these objects.
SPDD is used to identify dictionary objects
and
SPAU (repository objects), will identify any objects where the hot package is overwriting changes you have made through OSS notes.
You must check all objects identified in SPAU and decide whether you need to reapply the 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 you have applied an OSS note. You must check the OSSs note and see if SAP have fixed that note in a hot package.
If the OSS note has been fixed in hot package 34, then you 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.
If, however, the object is not fixed until hot package 38, or there is no fix available you have 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 apply your hot package to your QAS and PRD systems.
Comments
good overview of SPAU & SPDD
SUDHIR
Hi,
Please, could you tell me what is the difference between the Dictionary objects and repository objects ?
Do you have some examples ?
Thanks.
Basically in t-code SE11, you can see what type of dictionary object there (tables, structure, data-element, domain, etc).
Difference is, during the upgrade, if you mess around with data dictionary object, then there is a possibility of \'data loss\', where for the other repository object (reports, FMs), the data will not directly affected. (data loss might occur due to program misbehavour, but not because you are applying the standard object).
