Upgrading sap programs from one version to another version

[Former Member]

Hi All,

I want to know how to upgrade sap programs from one version to another version,Please help me...

Regards,

Raj.

[Former Member]

SAP takes care of there own programs. You will have to test your critical programs to ensure they still work as before. Some may get syntax errors because of changes to ABAP (rare). Some will dump because interfaces to FMs changed. Some may return incorrect results. fortunately, most work as before.

Rob

[Former Member]

Hi,

few screens exist in the older version and those screens may not exist in the newer versions and few ok codes donot function properly. Here is also where upgrading from one version to another is required. Most of the changes are Function Module Replacements and Syntax Error corrections are done in upgrades. Few companies develop their own tool which replaces the obsolete FM of older versions with newer FM's.

Regards,

Santosh

Message was edited by: Santosh Kumar Patha

Message was edited by: Santosh Kumar Patha

Message was edited by: Santosh Kumar Patha

[Former Member]

The seriousness and the complexity of the upgrade is primarily dependent on the version of the older SAP system. The Upgrade from 4.6 -> 4.7 is relatively easier and faster than that of an upgrade from 3.0 -> 4.7.

Most of the <b>function modules</b> in the older system have been reworked and would be marked as obsolete in the target version. (This could be seen in EPC Error Analysis & warnings).For example Function modules like Upload, Download, WS_Download, WS_Upload,WS_File_Delete, WS_Filename_get, Popup_to_confirm_step etc. These obsolete Fm's can be easily replaced with Fm's like Gui_Upload,Gui_Download, etc. There are few other complex Fms for which you have to do through R&D to find out the replacements.

Apart from replacing obsolete Fms one has to correct those <b>syntax errors</b> that may occur in the target version. There is a lot of variations in Syntax standards across versions.

Further more many <b>transactions</b> would have been reworked. Some Fields would be missing in the old system or a field would have been made a Key-Field in the new version , some screens would be missing or would have been addded. Also some <b>Tables</b> would have been flagged as obsolete and we need to find replacement for those obsolete Database tables.

It would be wise to do a R&D for all the programs in the system before Upgradation. This would really give us an idea about the complexity of the task and we can plan our Upgrade work effectively.

regards,

cartik

<b></b><b></b>

[Former Member]

hi Raj,

Go through the following link:

Also go through the URL

url=http://help.sap.com/saphelp_erp2005/helpdata/en/4c/e93fbd4efc41d098271e1fba2ef25c/frameset.htm]http://help.sap.com/saphelp_erp2005/helpdata/en/4c/e93fbd4efc41d098271e1fba2ef25c/frameset.htm[/url]

hope it helps you...

Regards,

Anuradha.B

[Former Member]

hi,

The only thing we have to consider while upgrading from one version to another is whether the program is working as itis in new version or not.

Mostly the problem is with the function modules where the parameters are same but the type of parameters may be changed (ex: from Char to string).In some cases some new mandatory fileds are added. And some of the function modules may not work in the new version.For those we have to findout the FM which is working similar to the old one.

When the Upgrade is from too older versions like 3.0 then we have to take care transaction changes. where the screen numbers may change and ok_codes may change.

and some mandatory fileds are required to add in some of the screens.

Thanks,

Swamy

[Former Member]

This can be quickly split into 2 groups.

Z programs:

A) Are these still used?

B) Copies of standard SAP programs. Apply changes to keep in line with the SAP code.

C) Test: if they do not work should they be corrected or re-written, (BDC vs BAPI).

D) Eventually look to remove obsolete function calls.

SAP programs:

99% of these will be changed with out you having to do any thing.

The others should be highlighted in transaction SPAU.? These will need changing because of OSS notes or enhancements. For OSS notes review these to see if they apply to your new release (or patch). Generally the easiest thing to do is 'Revert to standard' and then apply the new version of the OSS note.

Remember to check your user exits and enhancements, some of the functionallity may now be standard.

MattG