Upgrading ABAP handlers has two steps.
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.
To upgrade an adapter-provide ABAP handler from one SAP R/3 version to another:
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.
Custom work done in the ABAP component of the connector needs to be manually applied to the new SAP R/3 ABAP component of the connector. For example, you need to manually apply any changes to adapter-provided ABAP handlers such as IDoc Handler or Dynamic Transaction.
If changes were made, you can avoid conflicts by downloading the custom work as text files, not as transport files. Use the corresponding old program as a reference for updating /CWLD/TRIGGERING_RESTRICTIONS.
If you do not have an SAP R/3 version 3.x environment and IDocs, then skip this step.
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".
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".
For user exits, the precise location may be different now. Search for key SAP lines of code to make a best approximation.
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".