SAP development & extensions

Targeted extensions where the SAP standard is not enough

Where the standard is not enough, we build targeted extensions and applications: workflows, Fiori applications, integrations and individual functions. Along modern SAP and clean-core principles, so that your system stays upgrade-ready.

SAP Standard Fiori Apps CDS & APIs Extensions Integrations Workflows /M2D/

How we work

Understand first, then check, then build

Not every requirement needs code. That is why every development at M2 Digital starts with two questions: what should the process deliver, and what can SAP already do for it today?

Understand the requirement

Together with the department we clarify which problem is to be solved and how the procedure actually runs today. What counts is not the ticket but the process behind it.

Check the standard

We check whether standard functions and customising already cover the need. Very often they do, and then we tell you so.

Extend where it matters

If a genuine gap remains, we build the extension for it: lean, in our own namespace, through released interfaces and without touching the standard.

What we build

From the extension to the application of your own

All of it in our own partner namespace /M2D/, based on released interfaces and with the next release in mind.

  • Extensions within the standard. BAdIs, enhancement points and CDS views wherever the standard leaves a gap, without modifying it.
  • Fiori applications. Apps of your own in the launchpad, built with SAPUI5 and the RESTful Application Programming Model, in the look of your standard apps.
  • Workflows. Approval and release processes with the Flexible Workflow, and scenarios of our own where SAP does not ship one.
  • Integrations. Interfaces to surrounding systems via OData, APIs and RFC, in both directions and with clean error handling.
  • Individual functions. Reports, mass processing and operating aids for the cases in which the standard demands too many steps.

Our principle

Standard first. Extensions where they add value.

Not every requirement needs development. Where the standard is enough, we use it. Where an extension adds value, we build it upgrade-ready.

  1. 1
    Check the standard

    We first check every requirement against what the SAP standard can do.

  2. 2
    Extend sensibly

    Where the standard is not enough, we rely on clean extensions that stay as upgrade-ready as possible.

  3. 3
    Recommend clearly

    We recommend the solution that makes sense technically and for the business, not the one with the most development effort.

Which requirement does your standard not cover?

Tell us about the case. We will tell you whether it needs configuration, an extension or a solution of its own.

Newsletter

Stay up to date.

News about M2 Digital, SAP and our software solutions.