Problem solve Get help with specific problems with your technologies, process and projects.

Using the correct SAP ABAP codes in SAP ECC 6.0

A SearchSAP.com reader is upgrading from SAP ECC R/3 4.7 to ECC 6.0 and wants to know if there is a list that identifies which SAP ABAP code is obsolete in ECC 6.0.

We're planning our upgrade to SAP ECC 6.0 from SAP ECC R/3 4.7 and I would like to know if there is a list that identifies which SAP ABAP code is obsolete in ECC 6.0. Is this information available for me to reference, since I'm responsible for making our modified code work?
The programs and applications that you have written, which run without errors on the source release, may indeed contain syntax or runtime errors after the upgrade, in the target release. These may be caused by additional developments of the SAP ABAP Workbench, changes to the ABAP syntax, or stronger syntax checks when you upgrade from one release to the next. You can solve these problems by adjusting your programs to the new version of the ABAP Workbench.

For information on what has changed between the different releases and how to adjust your customer developments (recommendations for adjustments and instructions), see the following SAP Notes:

SAP Note SAP Basis/SAP Web AS/SAP NW AS Release:

  • 178482 for SAP release 3.1 to 4.0
  • 178452 for SAP release 4.0 to 4.5
  • 178725 for SAP release 4.5 to 4.6
  • 367676 for SAP release 4.6 to 6.10
  • 452229 for SAP release 6.10 to 6.20
  • 689951 for SAP release 6.20 to 6.40
  • 857904 for SAP release 6.40 to 7.0

Be careful -- you need to go through every note which applies to your source release all the way up to your target release. When upgrading from SAP R/3 4.7 to SAP ECC 6.0, you need OSS Notes 689951 and 857904. When upgrading from R/3 4.6c to ECC 6.0, you need to go through OSS Notes 367676, 452229, 689951 and 857904.

In addition, if the upgrade is combined with a conversion to Unicode, only Unicode-compliant programs that comply with the stricter ABAP 6.10 syntax and semantics will run in a Unicode system, so you must ensure that all your programs are ABAP 6.10 compliant. This also applies to any SAP Programs you modified (see SAP Note 548016 for details), including customer exits that you use (see SAP Note 549143). To determine which SAP programs you modified, run SAP transaction code SE95. Run UCCHECK and enter the programs you want to check: all objects in the customer namespace, all objects of type FUGS and the SAP programs you modified.

The system profile parameter abap/unicode_check=on can be used to enforce the enhanced syntax check for all objects in non-Unicode systems. When setting this parameter, only Unicode-enabled objects (objects with the Unicode flag) are executable. Note: After setting the Unicode flag, automatically generated programs might need to be regenerated. The mentioned parameter should be set to the value "on" only, if all customer programs have been enabled according to transaction UCCHECK.

Dig Deeper on SAP Basis

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.