Inheriting Legacy SAP Automation: eCATT and Solution Manager Test Suite

Keep this: job aid

Legacy SAP automation assessment card

• Read eCATT: test configuration = script + system data container + test data (variants); SECATT opens everything.
• System data containers map logical targets to RFC/HTTP destinations: change targets there, not in scripts.
• Driver mix predicts fragility: FUN stable, TCD screen-sequence sensitive, SAPGUI UI-sensitive, external tools depend on third parties.
• Inventory usage: last execution, last result, owner for every configuration and test plan.
• Measure stability (three runs), coverage of the S/4HANA process scope, repair hours per release, and real business checks.
• Flag ECC paths replaced in S/4HANA, such as customer and vendor master moving to the business partner.
• SolMan 7.2: mainstream maintenance to end 2027; optional extended maintenance to end 2030 for selected areas (SAP Note 3255311); cite current SAP sources.
• Cloud ALM orchestrates testing and integrates automation providers; it does not run eCATT; SDT is one-time, no sync, no rollback.
• Decide per script: retire, rebuild (priority: high value, high cost) or keep temporarily with an exit date.
• Retire only when a replacement ran green and the process owner agrees; record it in Cloud ALM.