Standard where possible. Customization where appropriate.
SAP Custom Development
▷ Our Portfolio of Solutions
What we work on with you
Get Clarity Now
How does SAP benefit your company?
Andreas Förger
Managing Director
Procedure
- UnderstandingWho works with the app, in what situation, and what information do they need while doing so? We leave out the rest.
- DesigningThe interface follows your users’ workflow. Frequent actions are one click away, rare ones are easy to find, and unnecessary fields get cut.
- BuildingWe customize standard apps, extend existing ones, or build new ones. Technically, with Fiori Elements on RAP and CDS views.

Your benefits at a glance
- Process-orientedThe screen follows the workflow, not the table structure.
- EasyFewer clicks, more done.
- ResponsiveWorks the same at a desk as on a tablet.
- SAP standard technologyBuilt according to SAP’s current programming model, with no workarounds.
- IntuitiveNew users find their way around without a long onboarding period.
- Testable earlyYou’ll quickly see a working prototype with real data.
Procedure
- AnalyzingWe make visible what’s in your system: modifications, custom Z developments, usage, and dependencies, verified with the ABAP Test Cockpit. That includes the uncomfortable truth that a significant portion of it has gone unused for years.
- Assessing & prioritizingCleanly built classic ABAP with stable APIs counts as Level B under SAP’s Level Concept, and is therefore considered clean. It doesn’t need to be rebuilt. Level C, meaning access to unreleased SAP objects, can stay if it’s encapsulated and monitored via the ATC changelog. Our main focus for cleanup is Level D. And we’ll also tell you where even that doesn’t pay off.
- RebuildingWe implement what we recommend: refactoring to released APIs where SAP offers them, encapsulating access where it doesn’t, rebuilding with ABAP Cloud or on BTP, and retiring unused objects.
- Keeping it cleanSo the core stays clean after the project, we work with your team to set up ATC check variants, the changelog for SAP objects, development guidelines, and an approval process for new extensions.

Your benefits at a glance
- CustomWhat you need stays, just in the right place.
- SeamlessRelease changes become routine instead of a project.
- Cleaned upUnused code gets retired instead of dragged along.
- EconomicalCleaning up only where it pays off.
- Cloud-readyThe foundation for running in the cloud.
- SustainableRules and knowledge transfer to keep it clean.
Procedure
- Clear layeringBuilt on SAP’s Virtual Data Model: basic, composite, and consumption views, reusable instead of rebuilt for every requirement.
- Consistent metricsEach metric is defined only once and applies the same everywhere. That way, your numbers no longer differ from report to report.
- Built for the consumersWe know what Fiori, Embedded Analytics, SAC, Datasphere, and BW/4HANA require from the views, and we factor those requirements in from the start: annotations, hierarchies, extractability.

Your benefits at a glance
- Well-foundedClean layering instead of organically grown view sprawl.
- ConsistentMetrics defined once, not rebuilt five times.
- PerformantThe load time is decided in the views. That’s where we optimize.
- ConnectableIf a new front end comes along, the views are already prepared.
- From one teamWhoever develops the views here sits next to the people who build reports on them in SAC and BW.
- TraceableDescriptive names and documentation, so your team can build on it instead of despairing.
Procedure
- UnderstandingWhat do you really need? We look at the process that doesn’t fit into the standard and figure out why.
- Check the standardSometimes the standard can actually do it, just differently than you’re used to. Then you can skip the development entirely.
- Developing cleanlyIf not, where extensions belong: at the designated extension points, through released APIs, with ABAP Cloud or side-by-side on BTP. Where the standard offers no released APIs, we encapsulate the access in one place so it can be checked in a targeted way during release upgrades.

Your benefits at a glance
- Standard firstOnly what the standard doesn’t cover gets developed.
- Cleanly extendedAt the places SAP has designated for it.
- Upgrade-proofYour extensions survive release changes with minimal rework.
- Handover-readyDocumentation and code reviews, so your team can keep developing it.
- Process UnderstandingWe understand what’s behind the requirement.
- Hands-on approachConcept, development, and testing on the same team.