Skip to content

Service

SAP Business One addon development

I build custom addons for SAP Business One that cover what the standard product does not: business-specific validation, new screens inside the ERP, automation between documents, and connections to external systems. I work daily with the SAP Business One SDK, both DI API and UI API, on SQL Server and SAP HANA.

What's included

  • UI API addons

    Forms, fields and menus native to the SAP Business One client, indistinguishable from the standard product.

  • DI API integrations

    Creating and updating documents through the ERP business logic, never by writing straight to the tables.

  • Service Layer and REST

    Connecting SAP Business One to online stores, mobile apps and third-party services through Service Layer.

  • Reports and Crystal Reports

    Document layouts and reports that match how the business actually works, with queries tuned for HANA or SQL Server.

What a custom addon actually solves

SAP Business One covers standard processes well, but almost no company operates exactly the standard way. When the team starts keeping parallel spreadsheets, copying data between screens, or repeating the same manual check on every order, there is an addon waiting to be written.

A well-designed addon lives inside the ERP: users do not switch tools, export nothing, and learn no new interface. They see one more field, a validation that warns before saving, or a button that produces in a second what used to take twenty minutes.

My rule is simple: if the standard does it, use the standard. Custom development is for what is genuinely specific to your business.

How I run a SAP Business One project

I start by sitting with the people who use the ERP every day, not only with the people who manage it. Most real requirements show up while watching someone enter orders, not while reading a specification document.

Then I scope the work in writing and split it into small deliveries. I would rather ship something working in two weeks and adjust it than disappear for three months and present something that does not fit.

Development is in C# on the SAP Business One SDK, under version control, tested against a copy of the real database. Nothing reaches production without having run against real data first.

On delivery you get the addon installer, technical documentation and a training session with the users. The source code is yours if we agree so.

Frequently asked questions

Do you work with both SAP HANA and SQL Server?

Yes, both. Queries and procedures are written for the specific engine, since syntax and performance differ between them.

Can you maintain an addon another company built?

Yes, provided the source code exists. I start by reviewing and documenting what it does before changing anything.

How long does an addon take?

A focused automation is usually two to four weeks. A full integration with an external system, one to three months. I give a fixed estimate after the analysis phase.

Contact

Let's work together on your next project

If you have a SAP Business One project, a pending integration or simply a question, send me a message. I reply to everything.

Location
Palma, Mallorca