When our company decided to move to S/4HANA, I was tasked with preparing our custom ABAP code for the transition. This post walks through how I used the Custom Code Migration Worklist (CCMSIDB) and the Simplification Database to identify, analyze, and remediate legacy code.
Subtopics & Answers:
What is CCMSIDB and why it matters in S/4HANA conversion It’s the engine behind SAP’s Custom Code Migration Worklist, comparing your codebase against the Simplification Database to flag incompatible objects.
Setting up the Simplification Database in NetWeaver 7.5 I downloaded the ZIP file from SAP Marketplace and imported it using
SYCM_UPLOAD_SIMPLIFIC_INFO.Running the Custom Code Analyzer and importing results I used
SYCM_UPLOAD_REPOSITORY_INFOto feed in our code references and usage data.Interpreting the Worklist output The ALV-style report showed which objects were obsolete, modified, or required attention — with direct links to SAP Notes.
Remediation strategy and collaboration with developers We prioritized high-impact objects and used ATC checks to validate fixes.
Lessons learned from using CCMSIDB It saved us weeks of manual analysis and gave us confidence in our migration readiness.
No comments:
Post a Comment