SPAU Corrections

Technical Approach in SPAU Corrections

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 SPAU and SPDD. These transactions allow customers to enter their modifications into the corresponding new objects being delivered at upgrade. The Modification Assistant supports this process of adopting customer modifications. 

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. 

SPAU

Some changes have been made by SAP in ECC 6.0, in the SAP Standard Programs, compared to 4.6C.

Using the 'SPAU' transaction code, that changes can be found between the two versions. SPAU Approach

Link to this Page Link Tiny Link Wiki Markup Close Move Page – ‘SPA

Set Page Location Move OK Cancel Click to select the Search

Recently View ed There w ere no re Know n Location The specified pag Brow se Error reading the

You could try relo HTTP Status You must make a Failed to retrieve There w ere no pa Show ing <b>{0}<

Move failed. Ther You cannot move SPAU Corrections ERP2005 Upgrade ERP6

ERP2005 Upgrade You cannot move Page Ordering Back Reorder Move

Unknow n user or Page Restrictions Editing restricted Cancel Close Save

43018

Go to SPAU transaction, select all check boxes on the selection screen & execute the transaction

Place the cursor on "MODIFICATION AND ENHANCEMENTS and expand all the nodes.

This will give you all the list of all standards SAP objects affected due to version upgrade.

Make an inventory of all objects in a tracker & start off with the analysis. Under node "NOTE CORRECTIONS" it will list all the notes which might or might not

be relevant for the upgraded system. Go to the individual notes and check if they is relevant for the upgraded version of the

system or not. If the note is not relevant IGNORE the note else IMPLEMENT the note in the system. If the note is implemented the background color of that note is automatically changed to GREEN as shown below.

  This should take care of all notes under NOTE CORRECTIONS node. For objects under "WITH MODIFICATION ASSISTANT" & "WITHOUT

MODIFICATION ASSISTANT" node analysis should be done as to what changes have

been done to the respective object. Below points explain various possibilities and action to be taken.

Changes could be done due to application of a note. If that is the case check if that note is relevant for the newer version. If yes then apply the oss note. If the note is not relevant for the newer version you can choose RESET TO ORIGINAL option for that particular object.

Changes could also be due to custom modification done by the customer to std. sap code. If that is the case check if custom changes can be easily extended to the new version. If it is then you can choose the option "ADOPT MODIFICATIONS" and apply the custom changes manually. Once the manual changes are done and the object activated you have to confirm the status so that the background color of those particular objects is changed to GREEN.

There is a possibility that some std. search helps does not exist in the newer version & the customer might be using these search helps or it's underlying database view. In that create a custom search help & database view & make changes to relevant objects which are referring to obsolete search help or database views. 

There is also a possibility that some std. table indexes are deleted in the newer version. Check with the customer if they need that particular index and create a custom secondary index as a replacement for the obsolete one.

Object with an RED LED light against it is mostly objects which do not exist in the newer version. You can simply ignore these objects.

For identifying what changes were done to the object version management can be very useful. You can safely assume that any object which has last active TR by one of the customer users has undergone change and probably those changes will have to be applied to the newer version of the code.

It is better practice that all objects changed under SPAU are locked under single transport request instead of individual transport request for each object. This will eliminate the dependency problem.

Objects which are reset to original will disappear from SPAU list. Objects for which custom changes are done and confirmed will appear with green

background color.

http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm