upgradation

[Former Member]

hello,

when ever we are going for upgradaation, what are the objects that are going to be affected and what needs to be done in that case.

cheers

[Former Member]

Hi

Upgrade in itself is a big task. But still I'll try to give a brief on what is the work of an ABAPer.

SAP provides with the list of all the chnages and also the new functionalities being implemented in the new version. The changes would be like:

1.fields, tables, data elements, domains etc are changed.

-> changes could be in the data type or length.

2. Some Funtion Modules might become obsolete, newer version will be available.

Work of ABAPer is to

change the required changes in all the custom programs.

Also go through the URL

<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/4c/e93fbd4efc41d098271e1fba2ef25c/frameset.htm">http://help.sap.com/saphelp_erp2005/helpdata/en/4c/e93fbd4efc41d098271e1fba2ef25c/frameset.htm</a>

Hope this helps.

Lokesh

Pls. rewards appropriate points

[Former Member]

hai lokesh,

how will we come to know the changes that would have happen while upgradation,what about BDC's and user exits will that also be affected .

cheers

[Former Member]

Hi,

Normally if you are upgrading to ECC50 thats the enterprise version, you are required to do the UCCHECK transaction. This is nothing but in SE38 attributes of the program, you need to cehck the Unicode check button to X and this can be done directly through this UCCCheck transation which is available in SAP.Normally this is called a s Unicode checks for upgradation whoich is done as step one in technical upgrade.You need to run SAPU and SPDD to get the list of repository items that needs change. There is a good doocumentation for unicode upgrade by SAP. You can look into that,

If you need more info mail me.

Shobana

[Former Member]

Hi

You can subdivide your custom program in four main groups and give a priority to them

- Abap list: shouldn't need to be change (Priority low);

- Direct Input: shouldn't need to be change (Priority low);

- Copies of std program: you have to check and change if they don't work (Priority High);

- Interface and BDC: you have to check and change if they don't work (Priority High);

Other custom objetcs (as dictionary objects) shoudn't need to be change (Priority low);

SAP guarantees all enhanchements (as user exit) still work (Priority low);

Max

[Former Member]

Hi Rajani,

Watch out for the Release notes. Release notes of the version typically gives you information as to what changed. With your custom developments, what you need to worry about are those programs where you used some SAP function modules that are not for everyones use. SAP may have changed the functionality of some of those function modules and that may effect your code.

Monitor all those modifications/repairs you did to the system. They may be wiped out and you may have to reapply them after upgrade.

Dont forget to reward pts if it helps ;>)

Regards,

Rakesh.

[sreemsft]

Hi Rajani,

Upgrade is a big task as the above people mentioned.

Most of the reports, Interfaces and BDC will get effected.

In Reports and Interfaces you will get corrections in Function Modules which are become Obsolete in the newer version.

Coming to BDC's... In some new transactions some screens will be missed out and they will be replaced as Subscreens in the new version. So you need to change the code in BDC's where the screen number is found.. YOu need to use the Okay code to call a Subscreen.

In some transactions, some mandatory fields will be missed out or vice versa. In that case you do need to take care of them.

According to my knowledge.. Function Module replacement and BDC corrections are the only tough things in the Upgrade...

Thanks,

Sreekanth G