1. Home
  2. SAP ABAP — ERP & CRM

SAP that fits your business — without bending the core.

ABAP, RAP and CAP development for SAP ERP, CRM and BTP — OData services, CDS and AMDPs, flexible workflows, CPI integrations and Fiori apps. The same developer owns your request from spec to transport.

  • S/4HANA
  • SAP BTP
  • SAP ECC
  • SAP CRM
  • RAP · CAP
  • OData · CDS · AMDP
  • CPI
Developers at their desks in front of monitors

Code check passed — ready to transport

When standard SAP isn't enough.

Most requests start with one of these. Each has a clean answer that keeps your system upgrade-safe.

“Standard reports don't show what my team needs.”

Custom ALV reports and CDS-based views, built on the data you already have — fast, filterable and exportable.

“Our invoices and forms don't match customers or local rules.”

Smart Forms and Adobe Forms designed with your team, with output set up so the right document goes to the right place.

“SAP doesn't talk to our other systems.”

Interfaces over IDoc, BAPI, RFC and OData — monitored, with errors your team can actually act on.

“We're moving to S/4HANA. What will our custom code break?”

We start from usage data, retire the code nobody runs, and fix the rest — so you migrate less and break nothing.

“Approvals take days and live in email.”

Flexible workflows route each approval to the right person in My Inbox, with rules your process experts can adjust.

“We need a new app, but we don’t want to touch the SAP core.”

Side-by-side extensions on SAP BTP with CAP or RAP — the new app runs beside S/4HANA and your core stays clean.

What we build in SAP.

Modern, clean-core development on S/4HANA and SAP BTP — and the classic ABAP your business still runs on. One team, from spec to transport.

Modern SAP — S/4HANA & BTP

01

RAP — ABAP RESTful Application Programming Model

Transactional Fiori apps and APIs built as business objects: a CDS data model, a behaviour definition for create, update, validations and actions, and a service binding that publishes it.

  • Business objects
  • Behaviour definitions
  • Draft handling
  • Service binding
02

CAP — SAP Cloud Application Programming Model

Services and apps on SAP BTP in Node.js or Java, modelled in CDS — so new features run beside S/4HANA without touching its core.

  • Node.js
  • Java
  • CDS models
  • SAP HANA Cloud
03

OData services

OData V2 and V4 services that feed Fiori apps, portals and third-party systems — published from RAP or SAP Gateway.

  • OData V4
  • OData V2
  • SAP Gateway
  • Fiori Elements
04

CDS views & AMDPs

Core Data Services view entities for a clean data model, and ABAP Managed Database Procedures that push heavy logic down to SAP HANA in SQLScript.

  • CDS view entities
  • Annotations
  • AMDP
  • SQLScript
05

Flexible workflows

Approval flows for purchase requisitions, purchase orders and supplier invoices — start conditions, recipients and exception handling modelled in Manage Workflows, extended with your own rules where needed.

  • Manage Workflows
  • Multi-step approvals
  • My Inbox
  • Custom conditions
06

SAP BTP extensions

Side-by-side extensions on SAP Business Technology Platform — apps, APIs and events that keep your S/4HANA core clean and upgrade-safe.

  • ABAP Cloud
  • Clean core
  • Events
  • SAP Build Work Zone
07

CPI — Cloud Integration

Integration flows in SAP Integration Suite that connect S/4HANA with banks, portals, marketplaces and other systems — with mapping, routing, security and monitoring.

  • iFlows
  • Mapping
  • Adapters
  • Monitoring
08

Fiori & UI5

Simple apps for the jobs people do every day — on desktop, tablet and phone.

  • Fiori Elements
  • SAPUI5
  • Launchpad

Core ABAP — ECC & S/4HANA

09

Reports & uploads

ALV reports your teams can filter and export, mass uploads and scheduled background jobs.

  • ALV
  • BDC
  • LSMW
  • Background jobs
10

Enhancements & classic workflow

Extend standard SAP the supported way, so upgrades stay clean.

  • BAdIs
  • User exits
  • Enhancement spots
  • SAP Business Workflow
11

Forms

Invoices, delivery notes, purchase orders and statements that look right and print right.

  • Smart Forms
  • Adobe Forms
  • SAPscript migration
12

Interfaces

SAP connected to warehouses, banks, portals and CRMs.

  • IDoc
  • BAPI
  • RFC
  • REST / SOAP
13

S/4HANA readiness

Know what your custom code will do on S/4HANA before you move — and fix it early.

  • Usage analysis
  • ATC checks
  • Code remediation
  • Performance tuning
14

SAP CRM

WebUI screens shaped around your sales and service teams — a skill few teams still offer.

  • WebUI
  • BOL / GenIL
  • One Order
  • Actions

Every object checked before it reaches you.

Quality gates we apply to everything we write — so the next upgrade is a non-event.

Code checks

ATC and Code Inspector run on every object we hand over.

Peer review

A second developer reads the code before it moves on.

Unit tests

ABAP Unit where the logic matters, so changes don't break it later.

Documentation

A technical spec and transport notes your team can maintain from.

How we deliver.

Six steps, each with something you can see and sign off.

  1. 1

    Requirement

    We agree what “done” looks like.

  2. 2

    Design

    A short technical design you approve.

  3. 3

    Build

    Clean code, in your development system.

  4. 4

    Test & review

    Checks, peer review and unit tests.

  5. 5

    UAT

    We support your users while they test.

  6. 6

    Transport

    Moved to production, documented.

Ways to work with us.

Pick the shape that fits the work. You get the scope and price in writing before anything starts.

Code assessment

A review of your custom code or S/4HANA readiness, with a ranked list of what to fix.

Fixed-scope project

A defined set of reports, forms, interfaces or apps, delivered to an agreed plan.

Dedicated developer

An ABAP developer working in your team's rhythm, part-time or full-time.

Support retainer

Monthly hours for fixes, small changes and month-end help.

Sample SAP projects.

Described by industry and region only — we never name clients.

ATC check: no S/4HANA findings
  • S/4HANA readiness
  • United States

Custom code cleared for S/4HANA

Challenge ·
Years of custom ABAP, and nobody knew what was still used.
What we built ·
Usage analysis, ATC checks, fixes for live code and retirement of the rest.
Outcome ·
A smaller, upgrade-safe custom code base.
Invoice layout approved
  • Forms
  • Africa

Invoices that fit the business

Challenge ·
Standard outputs didn't match local tax and customer needs.
What we built ·
Redesigned Adobe and Smart Forms with proper output setup.
Outcome ·
Documents customers and auditors accept first time.
IDoc processed successfully
  • Interfaces
  • Africa

SAP and the warehouse, finally talking

Challenge ·
Stock movements were re-keyed between SAP and the warehouse system.
What we built ·
IDoc and BAPI interfaces with error monitoring.
Outcome ·
Movements post once, in both systems.

All projects

SAP questions

Do you work in classic ABAP or the newer models?

Both. We maintain and extend classic ABAP in ECC, and build with CDS, RAP and Fiori on S/4HANA — choosing what fits your system, not what's fashionable.

Can you work alongside our SAP partner or in-house team?

Yes. We often take a defined piece — reports, forms, interfaces, code readiness — and follow your development standards and transport process.

Will our custom code survive the move to S/4HANA?

Some will, some won't, and some isn't used at all. A readiness assessment tells you which is which before you commit to the move.

Do you build on SAP BTP?

Yes — CAP and RAP apps, ABAP Cloud extensions and integration flows in SAP Integration Suite (CPI), set up so your S/4HANA core stays clean.

Do you still support SAP CRM?

Yes — WebUI enhancements, BOL/GenIL extensions and One Order changes. It's a skill fewer teams keep, and many businesses still run on it.

Can you work across our time zone?

We work with teams in the Middle East, the US, Africa and India, and plan calls and releases around your working day.

Talk to an ABAP developer this week.

Bring the requirement, or just the problem. You’ll speak to the developer who would build it — not an account manager.