洞察
关于让遗留现代化变得可信的现场笔记。
关于为变更降险、加速迁移、并把 AI 安全带入维系核心的系统的务实视角。
更多英文文章
2026-09-27 · 7 min英文
Which business processes does your SAP custom code change?
Almost every company knows how many custom programs it has. Hardly any know which processes they change or whether the reason still holds. One anonymised customer system, a worked hire-to-retire example and what an agent needs to answer the question.
阅读2026-09-10 · 9 min英文
ABAP MCP server: what an agent can ask about your SAP custom code
Two kinds of ABAP MCP server, the read-only tools of the Sysparency MCP server over the knowledge graph of your custom code, the questions each one answers, why the graph saves tokens, and what an agent did with them before it wrote a line.
阅读2026-09-08 · 9 min英文
Twelve Dynpro transactions, one Fiori launchpad: how an agent migrated a 25-year-old application fully autonomously
Dynpro to Fiori without a screen-by-screen conversion: twelve SAP GUI module pools became one launchpad with three Fiori Elements apps, a dashboard and four RAP business objects. What selection screens, PAI checks and F4 helps became, when a Dynpro should stay, and why the decisions came from the whole picture.
阅读2026-05-12 · 4 min英文
Retiring the most expensive sentence in enterprise IT
“We’re not sure what happens if we touch that.” It never appears on an invoice — but it taxes every initiative that touches a legacy system.
阅读2026-04-28 · 5 min英文
The as-is baseline that doesn’t go stale
Hand-written as-is documentation is obsolete on delivery. Deriving it from the code makes it complete, current, and defensible.
阅读2026-04-10 · 4 min英文
Grounding AI on legacy systems
Agentic coding tools guess when pointed at undocumented code. A deterministic, cited model is what makes AI-assisted modernization safe.
阅读2021-01-27 · 4 min英文
Different types of software documentation
Process or product, user or system: the kinds of documentation a software system needs, and why the hand-written ones age from the day they are finished.
阅读