Michael Doblinger, Solution Architect. 20 years of SAP Business One, 100 % independent.
First understand where the focus lies. Then decide what standard can do. And only develop what's truly missing.
Almost every SAP Business One project starts with a list of customization requests, and almost every one of these lists is too long. Customizing is not the problem. Unfiltered customizing is: expensive to build, more expensive to maintain, risky at every upgrade. That is why my work does not start with code, but with the question of what the standard already covers.
Whatever remains after the analysis is built to survive upgrades and to be handed over: via the Service Layer and native extensions instead of fragile add-ons.
Mandatory fields, validations, buttons, permissions: the same small Web Client customizations, in every project again. That is exactly why I built the JustCust Platform. Configure instead of code, deployed as native SAP standard.
A few projects from 20 years of SAP Business One, anonymized but concrete.
30 minutes are usually enough to know whether a project is worth it. Sometimes the answer is: you do not need me. That is a result, too.
Michael Doblinger, Solution Architect. 20 years of SAP Business One, 100 % independent.
What I built recently, honestly documented, deployed natively
A release button as a native Web Client extension: configured visually, scripted with logic, deployed via the Extension Manager — in hours, not a UI5 sprint.
Read more →A release button that appears only above 10% discount and only for the "Head of Sales" role — role-based, multilingual, configured not coded. And what it means for partners.
Read more →Many tools manipulate the Web Client DOM — pretty today, broken at the next SAP upgrade. Why native MTAR extensions are the more sustainable architecture, and what partners should take from it.
Read more →