SPAU

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://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

Regards,

Raj.

Former Member · ‎2008 Apr 23

Hi,

SPAU:-

This is for repository objects (programs, functions, classes, etc.). These have to be compared to the previous versions too and any missing bespoke code is to re-inserted.

Also plz go through the following link..

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

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

do reward if usefull

Vijay

Former Member · ‎2008 Apr 23

Hi,

See the blog

/people/sap.user72/blog/2005/03/22/sample-code-to-create-purchase-order-using-bapi-in-r3

Regards

Kiran Sure

Former Member · ‎2008 Apr 23

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://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://help.sap.com/saphelp_erp2005vp/helpdata/en/2e/6d66587d9011d396b60000e82de14a/frameset.htm

1.Developer need to run the Transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system.

2. After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified. This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.

3. Run SPUMG Transaction for Unicode Conversion in non-Unicode system. SPUM4 in 4.6c.

4. Then we need to move Z/Y Objects. Need to do Extended programming check, SQL trace, Unit testing, Integration testing, Final testing, Regression Testing, Acceptance Testing etc.

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.

When you upgrade the dev environment you may generate a transport in SPDD (at the begin of ACT_* phase) and at the end of upgrade for SPAU.

You may then include this transport in the next system upgrade (QAS) system, The Upgrade program will ask you this at prepare.

The procedure is well explained in The SAP on-line help (http://help.sap.com)

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

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

http://www.thespot4sap.com/upgrade_guide_v2.pdf

Hope this Helps

Reward points if useful