Introduction
In this blog, I will share the details of the issue, troubleshooting steps, and the solution that helped me resolve the long running phase: PREP_IMPORT/TOOLIMP_I during conversion in SUM tool.
During a recent ECC to SAP S/4HANA 2023 conversion project using DMO with System Move (DoDMO), we encountered a major performance bottleneck.
The SUM phase PREP_IMPORT/TOOLIMP_I, which typically should not take very long, ended up running for more than 30 hours without completing.
Background
Source system: ECC 6 EHP 8 on DB2 v11.5.9.0Target system: S/4HANA 2023 FPS01SUM version: SUM 2.0 SP23Method: DMOVE to S/4 using DoDMOOS version: SLES 15 SP05 (both Source and target)
The conversion was progressing smoothly until the phase PREP_IMPORT/TOOLIMP_I.
The Issue:
During the conversion, Software Update Manager (SUM) entered the phase PREP_IMPORT/TOOLIMP_I and it was running very slow.
This phase is part of the preparation import steps and is mainly responsible for:
Importing tool-related transport objects into the shadow system.These objects are necessary for SUM to run subsequent phases.It typically involves R3trans and tp calls that execute DDIC and tool transports.
Expected Behavior
Normally, this step should finish within a few min to hour (depending on system size and DB performance).
The logs (TOOLIMP_I.LOG) should show a sequence of transport requests being imported with steady progress.
How we Overcame the Issue
After confirming that the TOOLIMP_I phase was progressing extremely slowly with no obvious system bottleneck, I decided to take corrective action. Below are the exact steps that resolved the issue.
Terminate Processes
Killed all R3trans and tp put processes running on the Additional Application Server (AAS) where SUM was initiated.Also killed the SAPup process on the AAS to terminate the running phase PREP_IMPORT/TOOLIMP_I.
Ensure DIR_PUT Consistency
The parameter DIR_PUT (checked in transaction RZ11) must be consistent between the Primary Application Server (PAS) and the AAS.
Example: DIR_PUT = /usr/sap/<SID>/SUM/abap
In my case, SUM was started from a different mount point on AAS:
/Migration/SUM
To fix this, I created a soft link under /usr/sap/<SID>/SUM pointing to the /Migration/SUM directory.
Copy SUM Directory
Copied the entire SUM directory from the AAS to PAS on below location
/usr/sap/<SID>/
Adjust TOOLIMPI.TPP
Edit the file: /usr/sap/<SID>/SUM/abap/var/TOOLIMPI.TPP on the PAS and make sure its points correctly to PAS folders and files. Below is the screenshot showing how the file was correctly edited on PAS.
What is TOOLIMPI.TPP?
This is the tp parameter profile for the TOOLIMP_I phase.It tells the tp tool how to perform the transport import.SUM generates this dynamically for each import phase.Key things it controls include: transport directory paths, buffer handling, import options, trace level, and return codes.
Clean Up Old TMP Files
Navigate to /usr/sap/<SID>/SUM/abap/tmp/
Deleted/renamed all files starting with SAPI*. These files were remnants of the failed run on AAS, and new ones would be generated for the PAS-based execution in below steps
Manually Trigger tp Import
Executed the tp command manually on PAS in dialog mode:
tp pf=/usr/sap/<SID>/SUM/abap/var/TOOLIMPI.TPP put <SID>
This command performed the transport import for TOOLIMP_I runs in dialog, wait for the command to complete successfully, it has taken 1:15 hour in our case.
Meanwhile, new log files were generated under the tmp directory.
Sync Buffer File from PAS to AAS
Once the manual import finished, the buffer file in SUM directory of AAS was replaced with buffer file in the SUM directory of PAS:
Buffer file location: /usr/sap/<SID>/SUM/abap/buffer/<SID>
Copied this updated buffer file back to the SUM directory in AAS from SUM directory in PAS to ensure consistency.
Resume SUM on the AAS
Return to the SUM URL.Selected “Repeat Phase” (not “Start from Beginning”).
SUM Moves On to next phase
SUM recognized from the updated buffer file that the TOOLIMP_I phase had already completed successfully and proceeded to next phase.
Result:
The long runtime in PREP_IMPORT/TOOLIMP_I during my DoDMO-based S/4HANA conversion was a valuable lesson in how even “preparation” phases can turn into critical bottlenecks. By carefully analyzing SUM behavior, ensuring environment consistency, and using controlled manual intervention, I was able to resolve an issue that had stalled for more than 30 hours and guide SUM back on track. This experience reinforced the importance of understanding SUM’s internal processes, maintaining flexibility in troubleshooting, and always preparing for unexpected challenges during complex system conversions.
IntroductionIn this blog, I will share the details of the issue, troubleshooting steps, and the solution that helped me resolve the long running phase: PREP_IMPORT/TOOLIMP_I during conversion in SUM tool.During a recent ECC to SAP S/4HANA 2023 conversion project using DMO with System Move (DoDMO), we encountered a major performance bottleneck.The SUM phase PREP_IMPORT/TOOLIMP_I, which typically should not take very long, ended up running for more than 30 hours without completing. BackgroundSource system: ECC 6 EHP 8 on DB2 v11.5.9.0Target system: S/4HANA 2023 FPS01SUM version: SUM 2.0 SP23Method: DMOVE to S/4 using DoDMOOS version: SLES 15 SP05 (both Source and target)The conversion was progressing smoothly until the phase PREP_IMPORT/TOOLIMP_I.The Issue:During the conversion, Software Update Manager (SUM) entered the phase PREP_IMPORT/TOOLIMP_I and it was running very slow.This phase is part of the preparation import steps and is mainly responsible for:Importing tool-related transport objects into the shadow system.These objects are necessary for SUM to run subsequent phases.It typically involves R3trans and tp calls that execute DDIC and tool transports.Expected BehaviorNormally, this step should finish within a few min to hour (depending on system size and DB performance).The logs (TOOLIMP_I.LOG) should show a sequence of transport requests being imported with steady progress. How we Overcame the IssueAfter confirming that the TOOLIMP_I phase was progressing extremely slowly with no obvious system bottleneck, I decided to take corrective action. Below are the exact steps that resolved the issue.Terminate ProcessesKilled all R3trans and tp put processes running on the Additional Application Server (AAS) where SUM was initiated.Also killed the SAPup process on the AAS to terminate the running phase PREP_IMPORT/TOOLIMP_I.Ensure DIR_PUT ConsistencyThe parameter DIR_PUT (checked in transaction RZ11) must be consistent between the Primary Application Server (PAS) and the AAS.Example: DIR_PUT = /usr/sap/<SID>/SUM/abapIn my case, SUM was started from a different mount point on AAS:/Migration/SUMTo fix this, I created a soft link under /usr/sap/<SID>/SUM pointing to the /Migration/SUM directory.Copy SUM DirectoryCopied the entire SUM directory from the AAS to PAS on below location/usr/sap/<SID>/Adjust TOOLIMPI.TPPEdit the file: /usr/sap/<SID>/SUM/abap/var/TOOLIMPI.TPP on the PAS and make sure its points correctly to PAS folders and files. Below is the screenshot showing how the file was correctly edited on PAS.What is TOOLIMPI.TPP?This is the tp parameter profile for the TOOLIMP_I phase.It tells the tp tool how to perform the transport import.SUM generates this dynamically for each import phase.Key things it controls include: transport directory paths, buffer handling, import options, trace level, and return codes.Clean Up Old TMP FilesNavigate to /usr/sap/<SID>/SUM/abap/tmp/Deleted/renamed all files starting with SAPI*. These files were remnants of the failed run on AAS, and new ones would be generated for the PAS-based execution in below stepsManually Trigger tp ImportExecuted the tp command manually on PAS in dialog mode:tp pf=/usr/sap/<SID>/SUM/abap/var/TOOLIMPI.TPP put <SID>This command performed the transport import for TOOLIMP_I runs in dialog, wait for the command to complete successfully, it has taken 1:15 hour in our case.Meanwhile, new log files were generated under the tmp directory.Sync Buffer File from PAS to AASOnce the manual import finished, the buffer file in SUM directory of AAS was replaced with buffer file in the SUM directory of PAS:Buffer file location: /usr/sap/<SID>/SUM/abap/buffer/<SID>Copied this updated buffer file back to the SUM directory in AAS from SUM directory in PAS to ensure consistency.Resume SUM on the AASReturn to the SUM URL.Selected “Repeat Phase” (not “Start from Beginning”).SUM Moves On to next phaseSUM recognized from the updated buffer file that the TOOLIMP_I phase had already completed successfully and proceeded to next phase.Result:The long runtime in PREP_IMPORT/TOOLIMP_I during my DoDMO-based S/4HANA conversion was a valuable lesson in how even “preparation” phases can turn into critical bottlenecks. By carefully analyzing SUM behavior, ensuring environment consistency, and using controlled manual intervention, I was able to resolve an issue that had stalled for more than 30 hours and guide SUM back on track. This experience reinforced the importance of understanding SUM’s internal processes, maintaining flexibility in troubleshooting, and always preparing for unexpected challenges during complex system conversions. Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
