Gobas GmbH Streamlines SAP ABAP OO with
Enterprise Architect

Q.TRANS/4EA by Gobas GmbH is a plug-in for Enterprise Architect that connects directly with S/4 HANA and SAP R/3. It lets users instantly generate UML diagrams from SAP ABAP OO code, offering clear visibility into custom development projects.

In the world of SAP development, especially with the growing complexity of in-house ABAP Object-Oriented (ABAP OO) projects, keeping a clear overview of application structures and dependencies is critical. Gobas GmbH, a group of IT companies in Germany, recognized this need firsthand through their work with SAP clients. As model-driven development gained traction in the SAP space, they saw a growing demand for tools that could simplify understanding, documenting, and managing SAP custom development.

To meet this need, Gobas developed Q.TRANS/4EA, a plug-in for Sparx Systems Enterprise Architect. This tool provides a direct bridge between SAP systems and modeling environments—allowing teams to instantly visualize, analyze, and document their SAP ABAP OO developments without needing to install anything within SAP itself.

Challenge

SAP development teams often face a few common hurdles:

Hard-to-track customizations
As IT landscapes grow, it’s easy to lose track of custom ABAP developments and their interconnections.
Manual and outdated documentation
Maintaining up-to-date documentation is time-consuming and often falls behind, making it difficult to support or evolve systems confidently.
Disjointed tools and integration gaps
Previous methods required intermediate formats (like XMI) or SAP-side installations, creating friction and limiting adoption.
Limited visibility for quality assurance
Analyzing code quality and architecture relied on manual work or external tools, slowing down debugging and increasing risks.

Various Costs Involved in an SAP Project’s Lifetime (Source: Gobas)

Solution

Gobas GmbH’s Q.TRANS/4EA plug-in leverages the power of Sparx Systems Enterprise Architect to create a direct, hassle-free connection with SAP systems such as S/4 HANA and SAP R/3. Under the guidance of Managing Director Markus Abel, Gobas eliminated the need for any source code installations on the SAP side. Instead, the plug-in uses SAP’s Eclipse interface, enabling Enterprise Architect to connect directly with SAP.

Cost difference between Standard and Model-driven development approach (Source: Gobas)

This direct integration allows users to instantly generate clear UML diagrams from ABAP OO code with a single click. The result is a real-time, visual overview of SAP development projects that stays up to date as changes occur. By streamlining the integration process, Gobas not only simplifies analysis and documentation but also reduces the overall technology stack.

In practical terms, this means that development teams can quickly identify dependencies, debug issues, and plan enhancements—all within the familiar environment of Enterprise Architect. The solution’s intuitive design and automation of previously manual tasks save time and lower maintenance costs, helping teams focus on improving their custom SAP solutions.