SAP
Clean-core SAP development for finance and core processes.
Led by a senior SAP technical consultant with 8 years across Big 4 and enterprise SAP teams. For companies on S/4HANA or ECC, and for SAP partners in Singapore and Australia.
FocusFinance and core enterprise processes · S/4HANA and ECC
| Your situation | What we do | How to start |
|---|---|---|
| Moving to S/4HANA and custom code needs adapting | Code-check (ATC) analysis, simplification items, remediation of affected objects | Code audit, then scoped fix |
| Too much Z-code and every upgrade hurts | Retire unused code, rebuild extensions on RAP and released APIs | Code audit, then scoped fix |
| Old user exits and modifications keep breaking | Refactor to BAdIs and released extension points, with unit tests | Scoped project |
| Finance needs reports or apps standard SAP does not give | CDS-based reports and OData services for Fiori or web apps | Scoped project |
| Other systems need SAP data | Secure OData and REST APIs, built with our custom app team where needed | Scoped project |
| A backlog of small ABAP changes and fixes | A named developer working your backlog, in your stand-ups | Month-to-month developer |
| You are a partner short of ABAP or RAP developers | Developers working under your technical lead and transport process | Partner capacity |
Nothing modified in the core
Released APIs and extension points only, so upgrades stay simple.
ABAP Cloud and RAP
New development follows the ABAP Cloud model wherever the release allows it.
Code checks before every transport
ATC runs clean, including S/4HANA readiness checks, before anything moves.
Logic pushed to the database
CDS views and AMDP instead of large loops over finance tables.
ABAP Unit on business logic
Tests written with the code and re-run when it changes.
Technical specs kept current
Every object documented, so the next developer can pick it up.
The request
Finance wants an extra check before a supplier invoice posts.
Requirement agreed with the process owner; standard behaviour reviewed first.
The right route
Simple rules stay with key-user tools. Logic goes into SAP. Separate apps go to BTP.
Clean-core extension options compared: key-user extensibility, on-stack ABAP Cloud, or side-by-side on SAP BTP.
The build
The check is added at a supported extension point, with tests.
Released BAdI implemented in ABAP Cloud; ABAP Unit tests cover the rule and its exceptions.
The release
Moved to production through your transport process. Upgrades leave it untouched.
ATC clean, transported through CTS or ChaRM, technical spec updated.
The question
Finance needs open items by profit centre, with drill-down to documents.
Fields mapped to standard finance data; existing released CDS views checked before building anything new.
The data model
A layered model over standard SAP data. Nothing copied out.
CDS view stack (basic, composite, consumption) with annotations and access controls.
The service
The data is made available to an app or analytics tool.
OData V4 service through a RAP service definition and binding; authorisations enforced in the view.
The result
Users get a Fiori app or analytics view that stays current with SAP data.
Fiori elements list report or analytical consumption; code checks clean, transported.
ATC with S/4HANA readiness checks, usage data (SCMON/SUSG), SQL traces on key reports, and SAP clean-core extensibility guidelines.
| ID | Area | Finding | Severity | Effort | Fix by |
|---|---|---|---|---|---|
| SAP-01 | Clean core | 19 core modifications replaceable with released BAdIs | High | L | 90 days |
| SAP-02 | S/4HANA readiness | 27 objects reading tables changed in S/4HANA | High | M | 60 days |
| SAP-03 | Performance | Unindexed loops over BSEG in 8 month-end reports | High | M | 30 days |
| SAP-04 | Code in use | 312 unused Z programs and forms to retire | Medium | S | 60 days |
| SAP-05 | Code quality | 140 priority-1 ATC findings in finance enhancements | Medium | M | 60 days |
| SAP-06 | Transports | 43 open development transports older than 180 days | Low | S | 30 days |
Custom code remediation for S/4HANA
Adapting custom code to the S/4HANA data model: simplification items, changed tables and code-check findings.
RAP applications and extensions
Transactional apps and extensions on the RESTful ABAP Programming model, using behaviour definitions and released APIs.
CDS views and OData services
Reporting views and services over finance and core data, for Fiori apps, analytics and other systems.
Enhancements in modern ABAP
BAdIs, enhancements, interfaces and forms written in object-oriented ABAP, with unit tests.
SAP technical lead
Design, build and code review, with 8 years across Big 4 and enterprise SAP teams.
ABAP and BTP developers
Vetted by the lead and added for the scope, working to the same standards.
Your functional team or SI
Owns process design and configuration. We build alongside them.
SAP FAQ
Do you work on ECC as well as S/4HANA?
Yes. Enhancements and fixes on ECC, and preparing custom code for a move to S/4HANA.
Do you provide functional consultants?
No. We focus on technical work: ABAP, RAP, CDS, OData and BTP. We work alongside your functional team or SAP partner.
Can you work with our SI or SAP partner?
Yes. Our developer works under their technical lead, standards and transport process.
Are you an SAP partner?
No. We are an independent team of SAP developers.
What does a code audit need from us?
Read access to a development or quality system, and usage data (SCMON or SUSG) where available. Scope, timing and any fee are agreed on a short call.
Talk to our SAP lead
A code audit, a scoped build, or a named developer.