Importing the Transports

Important: If you are installing FlexNet Manager for SAP Applications on a system running SAP Basis 702 or higher, the system might display a warning message with the explanation The installed release does not match or Does not match component version. This is because SAP Basis 702 systems or higher compare the support pack level of the target system with that of the objects in the transport that you are trying to import. If the support pack levels do not match, a warning message might be displayed. This is not a concern for FlexNet Manager for SAP Applications transports, because all objects in FlexNet Manager for SAP Applications transports are in the /LICMAN/ namespace.

To avoid such a warning message, on the Import Transport Request dialog, click the Options tab and select the Ignore Invalid Component Version check box. For more information, refer to the following SAP documentation: SAP Knowledge Base Article 1688610 and SAP Note 1742547.

To import the transports:

1. Determine an SAP system that is running SAP Basis version 7.x and that is assigned as primary/parent system.
2. Import the AdminModule transport for the SAP Basis release into the primary system. After FlexNet Manager for SAP Applications has been installed, the SAP Admin module will run on this primary system.
3. Import the appropriate Roles transport that matches the SAP Basis release into the primary system. The Roles transport is client dependent.
4. Import the Roles transport into all dependent SAP systems that you want to manage using FlexNet Manager for SAP Applications. Ensure that you import the transport that is appropriate for the relevant SAP Basis version of each dependent SAP system. The Roles transport is client dependent.
5. Import the Satellite transport into all dependent SAP systems that you want to manage using FlexNet Manager for SAP Applications. Ensure that you import the transport that is appropriate for the relevant SAP Basis version of each dependent SAP system. (It is not necessary to import the Satellite transport into the SAP system that contains the SAP Admin module.)
   Note: This step is required if you do not want to execute the USMM to collect license data and user data, or if you do not want to use RFC_READ_TABLE. It is also required for Activity Check data collection through the staging database monitor, due to the limitations of RFC_READ_TABLE.

   Important: If you are importing the Satellite transport into an SAP system running SAP Basis release 6.2, the import might fail and a transport request error might occur (for more information, see the transport log). This is due to a transport limitation between SAP Basis release 6.* and 7.0 in SAP. To fix this limitation, it is recommended that you update the SAP kernel according to the information in the SAP Note 454321 - Transports between Basis Release 6.* and 7.0.