Work of ABAP consultant

[Former Member]

Hi friends,

Can anybody explain me what exactly needs to be done to the following objects copied from a previous version(4.6) to ECC 6.0

Reports

BDCs

Scripts & Smartforms

Enhancements

BAPIs

Data Dictionary Objects

Thanks

[Former Member]

Hi,

If your question is answered, award relevant points to the replies you found helpful & close the thread.

Regards

Sayee

[Former Member]

Hi,

When an upgrade has been carried on a system, large number of data dictionary & repository objects get affected in the newer version.

1. You have to start with identifying the objects which have undergone a change. So 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. Following links contains necesary documentation on SPDD.

http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/6d66617d9011d396b60000e82de14a/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/6d66647d9011d396b60000e82de14a/content.htm

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.

Check the below link. It elaborates on adjusting repository objects.

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

3. Also check whether the custom programs have been copied properly. Remove any obsolete statements. Also replace the obsolete function modules. Function modules like WS_UPLOAD & DOWNLOAD have become obsolete in ECC 6.0.

4. In case of BDC, compare the screen with the older version. There is a possibility that few fields would have missed out. You may have to do some tweking in the program too. Same is the case with sap scripts.

5. Also make sure that the objects are unicode compatible.

Reward if useful.

Regards

Sayee

[Former Member]

Hi Harshu,

We are currently working with a technical upgrade from 4.6c to ECC6, so I would like to share some of the things I learned so far. I will add more later.

Reports

ABAPers need to check that the program passes unicode check, syntax check, no runtime errors and that the program logic stays the same.

-Conduct a Unicode Check (if you are upgrading Unicode), and fix the Unicode errors

-Search for standard objects that are referred in the program but are no longer existing in ECC6 (deleted structures, function modules, tables etc etc).

-Search for standard objects that are referred in the program but have been modified (function modules that changed parameter types, function modules that became obsolete, standard includes that changed their code or even changed a few functionalities)

BDCs

ABAPers need to check that screens and fields are still existing in ECC6.

-Check programs that call transactions or use BDC, check the screens (mostly hardcoded)

Data Dictionary Objects

As far as I know, BASIS will run something for Unicode conversion of Data Dictionary objects. I am not sure, though.

Hope this helps.

Regards,

Oscean Tortona