The transport files for the adapter for mySAP.com contain a variety of objects, such as table structures, functions, and data. These development objects must be imported into your SAP installation to provide specific functionality required by the ABAP Extension Module.
Each transport file is included in a .zip file. For example, the transport file for the SAP version 4.x Primary transport is located in the 4_Primary.zip file.
Once the required transport files have been successfully loaded, the business object-specific transports can be loaded in any order. See the transport note included in each transport .zip file for detailed information about the transport file.
Create the namespace for the connector before installing the connector transport files. This step is mandatory for SAP version 4.0, as some of the transports will fail if the namespace is not created.
ABAP objects in the connector's namespace cannot be modified until you make the Namespace available for modification. To update SAP4.x delivered ABAP objects, you must have a repair license to modify the objects. Contact IBM technical support to obtain the license.
The connector includes two connector transport files. Modifications required by the adapter are handled by these connector transport files.
To ensure that all necessary tables are created before the data for those
tables is added, you must install the transports in the order listed.
These files can be found in
ProductDir\connectors\SAP\dependencies, where
ProductDir represents the directory where the connector
is installed.
Table 40. Connector transport files by version
Version of SAP | Transport files |
---|---|
V.4.0, V.4.5, V.4.6 |
|
V.4.7 |
|
The functionality provided by the Primary and Infrastructure files is as
follows.
Table 41. Connector transport file functionality
File | Functionality |
---|---|
Primary | This transport file contains the following elements:
|
Infrastructure | This client-independent transport file contains the following
elements:
|
The connector transport files make all necessary modifications to SAP by importing programs and other development objects delivered with the connector. They do not alter any SAP programs or modify user exits.
Attention: If you are reapplying transports, note that this resets your environment. Any development done prior to reapplying the transport files will be overwritten.
In the following instructions, SID refers to the SAP system ID, and <TransportFileName> refers to the name of the transport file. However, the characters that make up the transport file name appear in a different order in the installation directory from the way the name is passed as a parameter to the various tp commands. In the \usr\sap\trans\cofiles directory, the format of a transport file name is K9xxxxx.SID, but when the filename is passed as a parameter it has the format SIDK9xxxxx. For example, the file name K912345.D30 is passed as a parameter as D30K912345 because D30 is the SID of the source system.
Attention: Do not change the names of the connector transport files.
To install the transports:
tp connect <SID>
If this command fails, try adding the path of the tpparam file as a second parameter:
tp connect <SID> pf = <path of tpparam>
For example, if the SID is P11 and the path of the tpparam file is \usr\sap\trans\bin\tpparam, the command is:
tp connect P11 pf = \usr\sap\trans\bin\tpparam
If tp connect succeeds when you specify the path of the tpparam file and fails when you do not, you should specify the optional tpparam path in the commands described in step 3.
In \usr\sap\trans\bin, execute the following commands for each transport, in the order specified:
tp addtobuffer <TransportFileName> <SID> pf = tpparamFilePath tp import <TransportFileName> <SID> u023689 CLIENT=<CLIENT#> pf = tpparamFilePath
In the Transport Management s system (transaction STMS):
You must install the transports in the order listed in Connector transport file installation.
After the transports are installed, change the development class to follow the migration path of your development classes. Use IBM WebSphere BI Station (transaction /n/CWLD/HOME) to do the following:
Attention: Any changes you make to development objects that were in the connector transports should be well documented outside of SAP. Changes can be overwritten by the next release of transport files. If changes are overwritten, they must be reapplied manually. For more information on upgrade issues, see Upgrading the ABAP Extension Module.