How to troubleshoot - Issues while importing the ABAP transport
The Advanced Business Application Programming (ABAP) transport is imported in the SAP system to support data collection. You must import the ABAP transport before configuring the SAP agent.
You might face the following issues while importing the ABAP transport:
- The component version of transport does not match the component version of target system
- Return code 12 error when you import the ABAP transport
This blog answers how to resolve these issues.
Issue 1: Mismatch of component versions
On the SAP system, when you use the STMS transaction to import the ITMK711_00xxxU.ITM transport requests, the following error message is displayed:
1 of 1 requests do not match the component version of the target system
Cause
From the SAP Basis version 702, or later, the transport program (tp) verifies whether the component version of the transport and the component version of the system where you want to import the transport are the same. If the component versions do not match, the version inconsistency is displayed in the import queue of the SAP system, as shown in the following image.
Solution
Complete the following steps to resolve the version mismatch issue:
- On the SAP system, open the Import Transport Request window.
- Click the tick mark icon to proceed further to import the ABAP transport.
Issue 2: Return code 12 error while importing the ABAP transport
You are unable to import the ABAP transport and receive the following error message:
Program terminated (job: RDDEXECL, no.: 11272600)
See job log Execution of programs after import (XPRA) End date and time: 20130906112742 Ended with return code: ===> 12 <===
Cause
See job log Execution of programs after import (XPRA) End date and time: 20130906112742 Ended with return code: ===> 12 <===
Cause
The SAPLSTUW program is not started at run time because the program is not generated and activated on the SAP system.
Remember: When you import the ABAP transport, the return code 12 error is displayed due to one of the following reasons:
- The SAPLSTUW program is not started at run time
- Import is canceled because the required object is missing
- Objects are not active
- Program terminated because the RDDEXECL job was not working
- Connection problem between systems
Use the following solution if the SAPLSTUW program is not generated and activated on the SAP system.
Solution
Complete the following steps to generate and activate the SAPLSTUW program:
- Log in to the SAP system and open the SAP GUI.
- In the ABAP Editor: Initial Screen window, select SE38. The SE38 is the transaction code to create, modify, and display a program.
- In the Program field, enter SAPLSTUW as the program name.
- In the Subobjects area, select Source code and click Display.
- In the ABAP Editor: Display FunctionalPool SAPLSTUW window, click Program > Generate.
When the SAPLSTUW program is generated, the following message is displayed at the bottom of the window:
Program SAPLSTUW successfully generated - Click the Activate icon to activate the SAPLSTUW program and save the changes in the database.
When the SAPLSTUW program is activated, the following message is displayed at the bottom of the window:
Active object generated
After you complete these steps, import the ABAP transport again.
If you have any further questions on the troubleshooting issues while importing the ABAP transport on the SAP system, please add a comment to this blog post.