Step 1 of 4 Beginner 8 min

Why Your IDE Choice Is a Clean Core Decision

Lesson 1 — 'VS Code or Eclipse' sounds like a personal preference question. It isn't, not entirely — one of these two IDEs structurally cannot build the patterns that break Clean Core. Here's why that matters more than which one you personally prefer.

S
s4ready.ai Team

“VS Code or Eclipse” sounds like a personal preference question — the kind of thing two developers argue about over coffee and never really resolve. It isn’t entirely a preference question, and the reason why is the whole point of this lesson.

The constraint that’s actually a feature

SAP’s VS Code extension for ABAP only speaks the ABAP Cloud model. No classic Dynpro, no Web Dynpro — not because SAP forgot to add them, but because leaving them out steers every developer who picks up the extension toward released APIs, CDS, and RAP from the very first keystroke.

VS Code and Eclipse ADT, same backend, different reachBoth IDEs share the same ABAP language server backend. Eclipse ADT still supports classic Dynpro and Web Dynpro alongside modern ABAP Cloud objects. VS Code ADT speaks ABAP Cloud only, which structurally prevents building the patterns that break Clean Core.ECLIPSE ADTFull object coverage —classic Dynpro, Web Dynpro,and ABAP Cloud, all supportedVS CODE ADTABAP Cloud only —structurally cannot buildthe patterns that break Clean Core
Same backend, same language server — the difference is which object types each client is willing to show you.

Neither IDE is “winning” — that’s not the right question

Eclipse ADT isn’t being deprecated, and it isn’t losing anything — it’s been updated in step and remains fully supported, with full object-type coverage. The right question isn’t “which IDE is better.” It’s: for greenfield, Clean-Core work, does it help to use a tool that can’t accidentally build the wrong pattern? For maintaining legacy Dynpro screens, you need Eclipse — VS Code genuinely cannot help you there, by design.

Try it yourself

Think of the last piece of custom ABAP you touched, or one you know well from a project. Would VS Code’s ABAP extension have even let you build it, given it only speaks ABAP Cloud? If the honest answer is no, that’s not a limitation to work around — it’s a signal about which category that code actually falls into, and whether it belongs on a remediation list from the migration journey.

Go deeper

For the full GA announcement, the object-type list, and the honest caveats (the bundled MCP server’s platform support), read ABAP in VS Code is Now GA and the detailed VS Code ADT vs Eclipse ADT comparison.

Key takeaways

  • VS Code’s ABAP extension speaks ABAP Cloud only — a constraint that structurally steers development toward Clean Core.
  • Eclipse ADT remains fully supported with full object coverage — this is a coexistence story, not a replacement story.
  • The real question isn’t “which is better.” It’s which tool matches the kind of code you’re actually building.

Next: the layer stack that replaced BOPF for transactional development — RAP, in one picture.

← Journey overview RAP in One Picture: The Layer Stack That Replaced BOPF →