Skip to Content
Technical Articles

A few tips when using SPAU and SPDD in an upgrade

I’ve been doing quite a few upgrades recently. Here are a few tips.

1. Reset to original where possible.

Use version management to see if you can reset to original. This is should always be preferred over accepting the modification.  If a modif version exists, compare that to the last version before the upgrade. If there isn’t a modif version, compare the active.


Notes in the list with grey buttons should also be reset to original. Remember that any object that is not set to original will reappear in the SPAU/SPDD lists every time there is an upgrade or a support pack is applied.

2. Checking tables in SPDD

Usually, the first entry in SPDD is all you have to check for tables, since in version management, it will give access to all the other associated objects – indexes etc.

SPDD Version.png

table versionable.png

1.   3. Multiple selections

You can select entries using F9, and then reset to original in one go.

4. Current versions corresponds to proposal

4.  If clicking on yellow button tells you that the current version corresponds to proposal, then reset to original.


In later versions there is an EnjoySAP version of SPAU. Since (at least as of version 7.30) it lacks all the old functionality, I’ve found it better to use transaction SPAU_OLD.

6. Speeding up note download

1.       If during SPAU you are prompted to re-download a note (for a grey traffic light), click on cancel* and do it through SNOTE instead – it’s considerably quicker. For a yellow traffic light do the same, but you’ll need to implement the note through SNOTE as well.

* Depending on what level of ABAP you’re at, this may interrupt a “reset all” (point 3), but you can just reselect and continue once the note is downloaded.

You must be Logged on to comment or reply to a post.
  • Hi Matthex,

    Thanx for your blog! SPAU_OLD is much better than the new SPAU. I wonder why SAP designed the new SPAU? They want the admin to get a heart attack? The worst lack is: you can’t set multiple obsolete notes to “Reset to original”. In my ERP I have 80 to 130 obsolet notes after an upgrade? Quality is something the world don’t wants anymore:(

    Best regards

    Willi Eimler

    • It’s something I’ve observed in SAP many times. New tools arise, but the designer doesn’t understand that in the real world we don’t deal with a few objects – we deal with hundreds, if not thousands. (For example, transformations in BW look great – until you have 30 or more fields, and we have some infoproviders with over a hundred).

  • Hi Matthew!

    Long time no see.

    We are doing an upgrade and I’m trying to see what the damage will be 🙂

    I know there are quite a few objects modified, but when I run SPAU, I almost don’t get anything. Any idea why this might be?

    Also, SPAU_OLD doesn’t exist on my system 🙁




    • If SPAU_OLD doesn’t exist, maybe SAP have fixed things with the new SPAU? The program for SPAU_OLD is RSUMOD04.

      If you’re not getting any objects, that suggests there are no issues to deal with. Maybe the objects you changed aren’t affected by the upgrade.

  • My hints:

    • First go through the OSS note list, then check the other modifications.
    • With the OSS notes you have to check if it’s really included in your release. It can happen that SAP forgot to maintain the release validity and actually you still have to reimplement it, but ask SAP to maintain the OSS note atteributes first, so you can do it via SNOTE.