SPAU

Enter the transaction code SPAU.
Provide the selection criteria if required and select the necessary check boxes.
Click on Execute (F8).
Following screen will be shown.
Expand the hierarchy and select your component.

Open the hierarchy and click on yellow traffic signal.
Then following popup will be shown.
Just click on tick mark of following pop up.
Following split screen editor will be shown.

Left hand side code belongs to original version before the upgradation or modifications changes
carried out to the SAP system, example like EHP applying and technical upgradation.
Right hand side code belongs to modified version before the upgradation or modifications carried
out to the SAP system.
Comparing the both versions, left hand side code is the one which is existing current system. Right hand
side code is the one which is in old modified version, now we need to compare LHS with RHS and make it
equal to RHS side.
Use delete button in order to comment any code.
Insert button for inserting new lines of code.
Then click on save, it will raise a popup stating

Click on Yes.
Program copied to the buffer will be shown on status bar as successful message.
Following popup will be shown for general feedback information.
Click on tick mark.
Yellow Traffic signal light will change into Green color automatically.
If not, just click on refresh button on application tool bar, it will change to green.
Once you get it done. Now place the cursor on the object name. click on the Process/status
button on application tool bar.
Following popup will be shown,
Select the complete check box and enter necessary comments then select the row and click on Copy
button.
You will be getting a status message
And hierarchy will be extended to one more step with date, user, role, transport request details.
Once you done with this, entire modification adjustment completed successfully.
To make sure, just see the hierarchy, if you don't find single object or single hierarchical step as green,
then corresponding adjustment not yet done completely.
ABORT CASE - Corresponding Error handling.
If any of the object having problem, it goes to abort type and an abort symbol will be shown just left to the
object, in this case, refer its upgrade log.
General causes for abort signal.
1. If developed object have syntax error.

2. If package assignment failed.
3. Subroutine calls failure. etc.
Click on Abort symbol . It will take you to the following screen, where it will illustrate the reason.
Now double click on the object name and do necessary changes and correct the respective problem.
Activate the object and come back to the modification assistant screen by pressing back button. (F3).
Now click on refresh button. The abort symbol will vanish and green color will acquire to the object with a
green color-tick mark.
If observed at main hierarchy level, all are in green color. It means modification adjustment successfully
carried out.
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
 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

SPAU

Uploaded by

Copyright:

Available Formats

SPAU

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SPAU

Uploaded by

Copyright:

Available Formats

Enter the transaction code SPAU.

Click on Execute (F8).

Following screen will be shown.

Expand the hierarchy and select your component.

Then following popup will be shown.

Just click on tick mark of following pop up.

Following split screen editor will be shown.

Use delete button in order to comment any code.

Insert button for inserting new lines of code.

Then click on save, it will raise a popup stating

Following popup will be shown for general feedback information.

Click on tick mark.

button on application tool bar.

Following popup will be shown,

ABORT CASE - Corresponding Error handling.

General causes for abort signal.

1. If developed object have syntax error.

3. Subroutine calls failure. etc.

During an upgrade or the import of a Support Package, existing objects

 Place the cursor on "MODIFICATION AND ENHANCEMENTS and expand

You might also like