Custom SAP Business One add-on development.
What we build.
UI API screens
Native SAP Business One forms, menus, matrices and grids with Choose From List, built with the UI API so they look and behave like standard screens.
DI API and Service Layer logic
Documents, business partners, items and journal entries created and updated through the DI API or the Service Layer, with SAP’s own validation, never with direct SQL writes.
UDTs, UDFs and UDOs
Your own fields, tables and objects, created by the add-on at start-up so every company database gets them.
Validations and approval flows
SBO_SP_TransactionNotification rules that stop bad data at the source, and approval steps for documents, prices and payments.
Barcode and warehouse screens
Scanning screens for receiving, picking, deliveries and stock transfers, with items, batches and serial numbers checked as they are scanned.
Integrations
Connections to e-commerce, banks, e-invoicing platforms and external apps through the Service Layer or the DI API.
Built for teams like yours.
Companies running SAP Business One that need a screen, rule or integration SAP does not ship
SAP Business One partners who need a development team for a customer add-on
Companies that need an add-on to run on SAP HANA as well as SQL Server
How a project runs.
- Specification and discovery: a free discovery call, then a written specification of the screens, fields, rules and documents, based on your SAP Business One version, database and current process.
- Architecture: we choose the UI API, DI API or Service Layer for each part of the add-on and design the UDFs, UDTs and queries for SQL Server, SAP HANA or both.
- Build with weekly demos: you see working screens every week, not just status reports.
- Testing: user acceptance testing (UAT) on a copy of your company database, with normal user accounts, before anything reaches production.
- Documentation: setup notes, the UDFs, UDTs and settings the add-on creates, and a guide for users.
- Packaging for the Extension Manager: the add-on is packaged with the SDK’s ExtensionPackage tool and an .ard registration file, with a fixed extension name and an increasing version number.
- Go-live and support: installation in production, then 3 months of free support: fixes and small adjustments after go-live, then optional monthly support.
Who owns the source code?
You do. The client owns the source code and documentation of the add-on. You can keep developing it with your own team or your SAP Business One partner, or ask us to keep supporting it.
Will the add-on keep working after SAP Business One upgrades?
No developer can promise that a future SAP release will never affect an add-on, so we treat upgrade compatibility as a process, not a guarantee. We build only on the published APIs (UI API, DI API and Service Layer), do not depend on the internal layout of standard screens, and never write to SAP tables with SQL.
Before delivery we test the add-on against your SAP Business One version and patch level, and on both SQL Server and SAP HANA builds when your company uses, or plans to use, both. Before you upgrade production, re-test the add-on on an upgraded copy of the company.
How are milestones and pricing set?
Each project is split into phases with a fixed price per phase, agreed in the written proposal together with the scope and timeline. Payment is per phase, and every week you see a working demo, so each milestone ends with software you can test.
We do not publish prices, because every add-on is scoped first. What drives the cost is explained in the questions below.
What support do you get after go-live?
Every project includes 3 months of free post-go-live support for fixes and small adjustments, then optional monthly support. If you need a defined response time, ask for it in the proposal so it is written into the support terms.
Where we have done this.
ZATCA Phase 2 bridge for SAP Business One
A ready-to-install bridge that clears and reports SAP Business One invoices to ZATCA, with a friendly web interface on top of a background sync service.
Read case study →GermanyProduction add-ons, portals and 3CX telephony for SAP B1
Long-term SAP Business One development for a German company: production add-ons, web portals and integration of 3CX telephony with SAP B1.
Read case study →Latin AmericaCommission payment and product conversion portal on SAP B1
A Spanish-language portal connected to SAP Business One for commission calculation, approval and payment, plus product conversion and replenishment.
Read case study →Related guides: SAP Business One add-on development guide · DI API error codes (-5002, -1029, -2035) · SBO_SP_TransactionNotification examples (SQL Server and HANA) · Service Layer guide (login, $filter, paging)
Free tools: Formatted search (FMS) builder · Service Layer request builder · SAP B1 query library · SAP B1 table reference
Custom SAP Business One add-on development: common questions
What drives the cost of a custom SAP Business One add-on?
The number of screens and rules, how many SAP objects the add-on reads and writes, integrations with other systems, whether it must run on SQL Server, SAP HANA or both, the number of company databases, and how much testing and data preparation is needed. We scope this first and quote a fixed price per phase; we do not publish price lists.
How long does an add-on project take?
It depends on the scope, so the timeline is part of the written proposal. Every project runs through the same phases: specification, architecture, build with weekly demos, testing on a copy of your company database, documentation, Extension Manager packaging and go-live, followed by 3 months of free support.
Do you build add-ons for SQL Server and SAP HANA?
Yes. HANA compares text case-sensitively and uses a different SQL dialect, so queries, stored procedures and TransactionNotification rules are written and tested for each database the add-on must support.
Do you package the add-on for the Extension Manager?
Yes. The add-on is packaged with the SDK tool ExtensionPackage.exe into a zip with an .ard registration file. An administrator imports it in the Extension Manager and assigns it to the company; later versions are imported under the same name with a higher version number.
Who owns the source code of the add-on?
You do. The client owns the source code and documentation.
Can you work with our SAP partner?
Yes. Kodenova is an independent development studio, not an SAP partner, so we work alongside your SAP Business One partner, or behind them under their brand, with clear specifications, code handover and support.
SAP Business One development
Any add-on your business needs: plant maintenance, payroll, approvals, warehouse, integrations and reports for SAP Business One.
E-invoicingE-invoicing integration
Government e-invoicing connected directly to SAP Business One and ERPs: ZATCA, SRI, FEL, DTE and Panama FE.
PortalsWeb & B2B portals
Customer, vendor, commission and employee portals connected to SAP Business One.
Ready to get started?
Tell us what you need. You get a clear technical answer, a fixed scope and a price, usually within 24 hours.
