Solved: SPAU for Custom program.

abhishek_bhattacharjee · ‎10-09-2007

Hello,

I am new to Upgrade project.

Is it required to adjust a customer program (z or y programs) using SPAU. If yes, please let us know why we need to adjust a custom program...

Any documentation on SPAU would be appreciated.

Kind Regards,

Abhishek.

Former Member · ‎10-09-2007

Hi,

You don't need to adjust your Z programs for the upgrade..Unless if you have copied a standard sap program to create a z program..And sap has changed the standard sap program in the upgrade..Then you have to re-copy the program and do your custom modification..

Thanks

Naren

Former Member · ‎10-09-2007

SPAU and SPDD are done only for standard programs. If any custom program uses, any standard program include or any component, it will also appear in the list (provided there were some changes in standard program element).

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.

check this

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

ashish

Former Member · ‎10-09-2007

Hi,

You don't need to adjust your Z programs for the upgrade..Unless if you have copied a standard sap program to create a z program..And sap has changed the standard sap program in the upgrade..Then you have to re-copy the program and do your custom modification..

Thanks

Naren

Former Member · ‎10-09-2007

You have to aware of all related program like BDC's , Screens related errors and all dictionary related problems.

Some function modules may become obsolete, and some screens will change

abnd some new fields will be added in the new versions etc.

Also take care of SPAU and SPDD tcodes.

You should be able to know about Unicode concept in sap.

Upgrading within a new version of SAP R/3 :

The upgrade process for the SAP R/3 application does not modify any of the adapter's ABAP development, but it may modify the SAP R/3 application so that some of the adapter's ABAP development does not work properly.

This section describes how to upgrade the adapter's ABAP development in an upgraded SAP R/3 application. Before you can upgrade the adapter, you must have already upgraded your SAP R/3 application.

To upgrade the adapter's ABAP development:

Install the latest ABAP Extension Module transport files for the correct version of the SAP R/3 application.

You must install the correct version-specific transport files. For details on installing these transport files, see Connector transport file installation.

Compile all programs and resolve syntax errors associated with the ABAP development.

The easiest way to find syntax errors is to generate each function group associated with each object and fix the errors one at time. Repeat this process until all function groups compile successfully. Be sure to generate any other programs such as triggering programs that are not associated with a function group. Be aware that minor updates may need to be made to your ABAP triggering programs after applying the required new transports to upgrade the adapter.

If you are upgrading to SAP R/3 version 4.x, note that the 4.x ABAP handlers use the product namespace /CWLD/. For special considerations for upgrading to the connector supporting SAP R/3 version 4.x, see Connector for SAP R/3.

Test the new environment and make modifications as needed.

Only a full system test enables you to work out any problems with the upgrade. Test your event detection mechanisms by running the appropriate transaction or program and sending business objects to the SAP system. Use the connector's log within the SAP system to help identify other issues.

chk this

http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22

also chk these 2 notes in service.sap.com

Technical Upgrade is only a version upgrade without any functionality changes.

The objects that are needed to be upgraded are:

Includes

Function Groups / Function Modules

Programs / Reports

OSS Notes

SAP Repository Objects

SAP Data Dictionary Objects

Domains, Data Elements