Custom SAP Development

ABAP, Fiori and BTP development that fits your process, keeps the core clean and survives the next upgrade.

GlueData
Sanlam
Wastepro
FINN
Southco
OSIsoft
Sports Basement
SALT Analytics
AME Africa
Lock & Stern
ClearOn
WEG
Savantis
Sanquin
Hua Hai Pharma
Rumpke
GlueData
Sanlam
Wastepro
FINN
Southco
OSIsoft
Sports Basement
SALT Analytics
AME Africa
Lock & Stern
ClearOn
WEG
Savantis
Sanquin
Hua Hai Pharma
Rumpke

What we do

  1. We build what standard SAP does not.

    Reports, uploads, interfaces, enhancements and Fiori apps, written for your process and nobody else’s.

  2. We keep the core clean where it counts.

    Enhancements through BAdIs, custom fields and BTP extensions instead of modifications, so your next upgrade is an upgrade and not a rewrite.

  3. We fix the code that has run for ten years.

    Short dumps traced to the line. Hard-coded values found and removed. Custom programs made to survive the next release.

  4. We make Fiori tiles for the work people actually do.

    Custom apps, queries turned into tiles, catalogs and roles that match the job rather than the org chart.

  5. We document what we build.

    A technical specification, test evidence and a change record for every object, so the next developer is not guessing.

  6. We test before we transport.

    Every development proven in QA with the business before production. Nothing is built directly in QA, ever.

What that looks like in practice

The report that came back blank

A custom asset report opened to an empty page in the upgraded system. It relied on an element the new release had retired. We rewrote it for the new release and had the asset team test it in sandbox before go-live, so the first month-end on the new system was not the first time anyone saw it.

The file missing one tax code

A new company code’s tax jurisdiction never appeared in the outbound file to the accounts-payable platform. We traced the program through the three tables it reads to one unmaintained address record. Maintained, transported, and the next morning’s file was accepted.

The hard-coding review

A landscape’s custom programs were full of hard-coded plants and company codes, so every acquisition meant a developer. We reviewed them, moved the values into configuration, and the next new plant needed no code change at all.

Where custom SAP code goes wrong

The same four things, in almost every landscape we inherit.

  • Custom code nobody owns and nobody dares to change.
  • Hard-coded plants, company codes and dates.
  • Changes made directly in QA and never transported.
  • Developments without a specification, so the business cannot say what they should do.

What we build with

Every tool and technique our developers use, by layer.

ABAP

  • Classic ABAP
  • ABAP RESTful Application Programming Model (RAP)
  • CDS views
  • BAdIs and user exits
  • BAPIs and function modules
  • Enhancement framework
  • ABAP Test Cockpit (ATC)
  • Performance optimisation on HANA

Fiori and UI

  • SAPUI5 and Fiori elements
  • Fiori launchpad and SAP Build Work Zone
  • Custom fields and logic
  • Catalogs, groups and roles
  • Queries (SQVI, SQ01) as tiles
  • Fiori spaces and pages

Integration and data

  • SAP Integration Suite flows
  • IDoc and EDI
  • OData and SOAP services
  • File interfaces to banks and third parties
  • LSMW and upload programs
  • BRF+ output determination
  • DMEE payment formats

Platforms

  • SAP BTP (Cloud Foundry)
  • OutSystems
  • Neptune DXP
  • Python utilities

Clean core and remediation

  • Custom code remediation for S/4HANA
  • Simplification item fixes
  • Hard-coding reviews
  • Clean ABAP style
  • Technical specifications and documentation
  • Transport discipline

Signs you need us

  • A custom program fails and nobody knows what it does.
  • The upgrade’s custom-code list is longer than the budget.
  • Every new plant needs a developer.
  • The last developer left with the documentation in their head.
Talk to a developer

You can find us here

We have a strong global presence, marking our commitment to delivering tech excellence in key markets worldwide.

Colorado
14133 Downing Street Brighton,
Colorado 80602
Contact us
Cape Town
Regus Business Center, 1st Floor,
Willowbridge, Cape Town
Contact us
Haarlem
Frame Offices B.V.,
Haarlem, Netherlands
Contact us

AI that reads your custom code

The ETZ AI Platform reads your ABAP, explains what a program does and where it will break on the next release, and proposes the change, with SAP-grade authorisation and an audit trail on every action.

  • Runs in your own SAP BTP subaccount. SAP data never transits ETZ.
  • Your SAP authorisations decide what it may see and do, not the AI.
  • Every action lands on an append-only audit record.
Available on the SAP Store (opens in a new tab)