spau

[Former Member]

Hi,

please any one tell me in real time how to use spau tcode in upgradation.

[Former Member]

Hi Anitha,

Check http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/61ec66e33611d1954b0000e82de14a/frameset.htm

http://help.sap.com/saphelp_webas620/helpdata/en/83/7a18ecde6e11d195460000e82de14a/content.htm

<b>Reward points if this helps.

Manish</b>

[Former Member]

hi

good

check this link,

http://help.sap.com/saphelp_nw70/helpdata/en/83/7a18ecde6e11d195460000e82de14a/content.htm

thanks

mrutyun^

[Former Member]

Tcode SPAU is for adjusting programs and Function Modules.

http://help.sap.com/saphelp_nw04/helpdata/en/2e/6d66617d9011d396b60000e82de14a/frameset.htm

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

SPAU - for repository Objects Changes

see the doc

SPAU

http://www.sap-img.com/bc018.htm

http://help.sap.com/saphelp_nw04/helpdata/en/c6/068d380be34e6ce10000009b38f842/content.htm

http://help.sap.com/saphelp_46c/helpdata/EN/60/d6ba7bceda11d1953a0000e82de14a/content.htm

Please find below, answers to your questions:

1.What objects will come in SPAU and SPDD?

Ans: All the objects which are modified, after tansporting to the current system,

will be listed in SPAU and SPDD. SPDD contains the list of all modified Data Dictionary objects, like tables, dataelements, domains,view...etc. The rest of all the modified repository objects will be listed in SPAU.

What happens to the modifications done in the older version when we upgrade the version? (with Modification assistant and w/o)

Ans: After the initial upgrade happens, we have to do adjustments from SPAU/SPDD to maintain or reset the changes. That is, from the list of objects in SPAU/SPDD, you have to either carry forward the changes to the new version, by choosing the option ADOPT CHANGES (available on right click) or RESET TO ORIGINAL (available on right click).

Will they come in these transactions?

Ans: yes, they will be listed in these transactions, after the BASIS updgrade activity.

And what if we apply some patches(Notes) to the system? What is the impact of these patches to the SPAU transaction?

Ans: Patches will be supported by the version upgrade. In case of notes, we have to verify whether these notes are supported by the new version (you can go into http://www.service.sap.com/notes to verify this. Also, we have to analyze whther the code in the note is already incorporated in the new version. In this case you can ignore the chanes choosing RESET TO ORIGINAL option

http://help.sap.com/saphelp_erp2005vp/helpdata/en/2e/6d66587d9011d396b60000e82de14a/frameset.htm

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.

Also once the changes have been done you would see a green traffic light.

If you double click on the modified object it will show you a split window where on the left you will have the original version and on right the modified version. So you can choose which to keep and which to reject. You may keep the modified version incases where you know that the notes will only be pakages in the next version.

http://help.sap.com/saphelp_47x200/helpdata/en/2e/6d66647d9011d396b60000e82de14a/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/2e/6d66647d9011d396b60000e82de14a/frameset.htm

http://www.sap-img.com/bc018.htm

http://help.sap.com/saphelp_nw04/helpdata/en/c6/068d380be34e6ce10000009b38f842/content.htm

http://help.sap.com/saphelp_46c/helpdata/EN/60/d6ba7bceda11d1953a0000e82de14a/content.htm

http://www.sap-img.com/bc018.htm

http://www.sappoint.com/oss/spamspau.html

http://help.sap.com/saphelp_nw04/helpdata/en/fe/4b284837bf11d5b3bf0050dae02d7c/content.htm

http://help.sap.com/saphelp_webas620/helpdata/en/83/7a18ecde6e11d195460000e82de14a/content.htm

http://64.233.167.104/custom?q=cache:nJasGnXhh4sJ:www.asug.com/client_files/Calendar/Upload/SAP%2520...

Also the following link is very good

http://www.sapgenie.com/basis/starter.htm

Rewards if useful

[Former Member]

Hi Anitha,

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.

Refer to the following links .... You will get more info

ABAP Dictionary Objects --> All Data Dictiaory Objects like tables, Structures etc.,

http://help.sap.com/saphelp_nw70/helpdata/en/2e/6d66587d9011d396b60000e82de14a/frameset.htm

ABAP Repository Objects - Program Includes, Function groups, Function modules etc.,

http://help.sap.com/saphelp_nw70/helpdata/en/2e/6d66587d9011d396b60000e82de14a/frameset.htm

Also Check:

http://www.sap-img.com/bc018.htm

http://help.sap.com/saphelp_nw04/helpdata/en/c6/068d380be34e6ce10000009b38f842/content.htm

http://help

During an upgrade or the import of an 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.

In the past, all objects modified by a customer and delivered again by SAP, an IBU or an SAP partner, had to be manually re-modified during an upgrade. Now, modifications are either automatically adopted or the system provides you with an assistant for adjusting your modifications to the newly upgraded configuration.

In general, objects altered using the Modification Assistant can now be automatically accepted into the upgraded system if the modifications undertaken in the original version do not directly overlap those made in the customer version. If collisions occur between the two versions at upgrade (naming collisions, or if SAP has deleted an object modified by a customer), the system offers support during the upgrade, which means that a semi-automatic adjustment is made. In some cases, however, you may still have to manually adjust objects using ABAP Workbench tools.

Objects modified according to the old system used prior to the advent of the Modification Assistant must be manually maintained after an upgrade has been run.

Use transactions SPDD and SPAU during an upgrade to select these objects and modify them manually.

Transaction SPDD allows you to adjust modifications to ABAP Dictionary objects during an upgrade.

Transaction SPAU allows you to adjust programs, function modules, screens, interfaces, documentation, and text elements after an upgrade.

Reward if usefull.

Thanks,

Swati