Upgrading ABAP handlers

Upgrading ABAP handlers has two steps.

  1. Resolve any compilation errors that may arise when introducing your ABAP handlers into an environment with a different version of the ABAP Extension Module.
  2. Evaluate the functionality that the business object provides in the newer SAP R/3 version. For example, the business object may operate properly but may not return the right information; or maybe the business object no longer functions because SAP has changed the screens for the Call Transaction.

This section details the processes of the first step, such as packaging the business object's ABAP handler and providing guidelines for possible compilation conflict points. The second step is not addressed in this section. See Developing business objects for the ABAP Extension module for more information on extending the functionality of your objects.

Attention: Once you upgrade an object, it is considered custom work even if it was originally developed by IBM.

Upgrade ABAP handlers when:

Essentially the upgrade procedure is the same. The only difference is that upgrading a previously implemented business object requires you to package the business object into a transport file as the second step.

Note:
If you have objects in SAP R/3 version 4.6 that do not take advantage of the IBM product namespace, you need to upgrade those objects to the namespace.

To upgrade an adapter-provide ABAP handler from one SAP R/3 version to another:

  1. Verify that the latest version of the ABAP Extension Module transport files for your version of SAP R/3 are installed.
  2. Package existing business objects into transport files. Note that if you are upgrading an business object that has not been modified for your implementation, skip to step 3, because you should be able to use the original transport that was loaded.

    Use the adapter-delivered transport files as templates for what should be included for each business object. This may include function groups, IDoc definitions, and Dynamic Retrieve and Dynamic Transaction data.

  3. For IDocs (that define ABAP handler business objects) in an SAP R/3 version 3.x system only, capture the structure and segment definitions of the IDocs and then manually re-create them in the new system.

    If you do not have an SAP R/3 version 3.x environment and IDocs, then skip this step.

  4. Install the business object transport files. You should have your local BASIS administrator install the transports for the business objects you packaged in step 1.

    The BASIS administrator should use all of the override codes available for the transport. This forces the business objects into the environment even if there are compilation errors. Before importing the business objects, the BASIS administrator should know that you may encounter inconsistencies during the import process.

    For more information on installing these transport files, see Connector transport file installation.

  5. 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 business 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.

    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".

  6. Apply the event detection mechanisms.

    For user exits, the precise location may be different now. Search for key SAP lines of code to make a best approximation.

  7. 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.

    For information on testing business objects, see"Testing a business object for the ABAP Extension module".

Copyright IBM Corp. 2003, 2004