Symptom
1.
After completed a system upgrade task by using SUM, when checking UPGANA.XML file and TDO (Technical Downtime Optimization) results, find the Execution Runtime displayed in UPGANA and TDO are different.
- For example: UPGANA file shows Total runtime for Execution is: 23hours 25minutes
- However, for the same task, TDO shows the Execution runtime is 21hours 5 minutes
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
2.
Checking SAPupConsole.log, it shows same result of Execution time with TDO.
- For example:
>> 2025/06/13 09:59:54 START OF PHASE MAIN_PROFSTART/STOPSAP_TRANS
<< 2025/06/14 07:05:45 END OF PHASE MAIN_UPTRANS/UPCONF
Time gap: 21hours 5 mins.
(Please note: Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental. The numbers and time-points used above are only used as examples. In real situation, the real numbers and time-points could be different.)
Read more...
Environment
SAP AS ABAP system.
Product
Keywords
Time, Time-cost, UPGANA, UPGANA.XML, TDO, Technical Downtime Optimization, Execution, Runtime, Execution phase, SAPupConsole.log , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview