The following sections provide reference information for the upgrade scenarios. This reference information is provided to help with the upgrade process for the connector for SAP R/3 version 4.6 and IDocs.
The connector for SAP R/3 version 4.x uses the product namespace /CWLD/; the following guidelines facilitate the effort to make your ABAP handlers work in this renamed environment. See Business object processing in the ABAP Extension module for more information on how objects are processed and for background information for developing objects.
The functionality for converting transaction-based (Dynamic Retrieve and Dynamic Transaction) type business objects is provided through the new IBM WebSphere InterChange Server Station. The business object can be downloaded to a text file from transactions YXDY (Dynamic Retrieve) and YXTD (Dynamic Transaction) in the old system and then uploaded to the new tables using IBM WebSphere InterChange Server Station in the new system. Do this from the Tools tab using the Object MetaData option.
Keep the following in mind:
You must redirect SAP R/3 version 3.x business objects that begin with Y* to the product /CWLD/ namespace. Only the names have changed. SAP's "where used list" functionality greatly facilitates the search for all of the references that need to be changed. Following is a list of the most common references that need to be changed. Test to ensure your search is complete.
Table 18 shows the changes for the /CWLD/ namespace naming
convention. The parameter lists do not require changes.
Table 18. Namespace object name changes
Old name | New name |
---|---|
Interface parameters of the function modules | |
YXR_EVENT-OBJ_KEY | /CWLD/LOG_HEADER-OBJ_KEY (in three places) |
YXR_LOG_H-LOG_NR | /CWLD/LOG_HEADER-LOG_NR |
YXR_RFCRC-YXR_RFCRC | /CWLD/RFCRC_STRU-RFCRC |
Changes normally in the TOP include of the business object function group | |
YXR_CNST | /CWLD/CONSTANTS |
YXRIFRM0 | /CWLD/INBIDOC_FRMS0 |
Data elements |
|
YXR_VERB | /CWLD/OBJ_VERB |
Table structures |
|
YXR_CONFIG | /CWLD/CONF_VAL |
YXR_EVENTS | /CWLD/EVT_CUR |
YXR_LOG_I | /CWLD/LOG_ITEM |
YXR_RFC_S | /CWLD/OBJ_STRU |
Program referenced in the LOG_UPDATE perform statement | |
SAPLYXR1 | /CWLD/SAPLLOG |
Triggering function modules (the parameter lists do not require changes) | |
Y_XR_COMMIT_IDOC_RAISE_DELETE | /CWLD/ COMMIT_IDOC_RAISE_DELETE |
Y_XR_/ADD_TO_QUEUE | /CWLD/ADD_TO_QUEUE |
In addition to upgrading the custom objects and custom work, you must:
Give special consideration to production sites that already have events in the existing SAP R/3 version 4.x event tables. The transfer of these events from the existing event table to the new event table should be coordinated with IBM Technical Support.
This section applies to IBM WebSphere SAP R/3 version 3.x objects only.
Because you cannot transport IDoc objects from SAP R/3 version 3.x, you must manually re-create them in the new SAP R/3 system. To do this, you need to:
To capture the most useful representation of an IDoc, capture the overall structure that identifies all of the segments, and then capture business object definitions for each segment. Once you have a clear representation of the IDoc, you can us it to manually re-create it in the new system.
If you have access to the old and new systems, you can simply copy and paste the business objects between the systems. However, if both systems are not available, then you should record the IDoc and segment definitions outside of the SAP system for reference. Although this is optional, it is strongly recommended that you record the definitions.
To download the most useful representations of the IDocs and the segment definitions, first download the overall structure of the IDoc, and then download the IDoc segment definitions.
To download the overall IDoc structure:
The file is downloaded as a text file and can be viewed in any text editor.
You can download only one segment definition at a time. Repeat the following steps for each segment. To download a segment definition:
Make sure the Table Structure box is checked.
The file is downloaded as a text file and can be viewed in any text editor.
Once you have represented the object using text files, you can import them into a spreadsheet application to set up the object hierarchy. This facilitates the creation of IDoc segments, because you can cut and paste the fields directly into the segment editor in the SAP application.
Once you have a representation of the IDoc, you must manually re-create it in the new system. The SAP R/3 version 4.x environment uses different tables to store IDoc type and segment definitions than does SAP R/3 version 3.x. As a result, you must use SAP's tools to redefine the IDoc definitions to update the proper tables. There are two steps to this process:
A common error message encountered when re-creating segments by assigning the SAP R/3 version 3.x data element to the new segment field is Invalid data element. SAP replaced many of the SAP R/3 version 3.x data elements with data elements that have an underscore followed by the letter D (_D) at the end of the SAP R/3 version 3.x name. For example, CHARG in SAP R/3 version 3.x is Batch Number for the data element and is replaced in SAP R/3 version 4.x with CHARG_D.
If a data element does not exist in the new form, find a new form in the SAP R/3 version 4.x system. The data element must have the same type and length as the original in SAP R/3 version 3.x system. The description does not affect processing and is visible only in the log.
Attention: Do not rename the IDoc, segments, or segment fields because there is a direct relationship between the IDoc definition and the IBM WebSphere business object repository. In addition, the ABAP functions used to process the IDoc also rely on these names.