SAP Business One development support and retainer.
What we build.
Bug fixes
Errors in add-ons, integrations, portals, queries and reports found after go-live: reproduced, fixed, tested on a test company and delivered with a note of what changed.
SAP Business One upgrade testing
When you move to a new version or patch level, we test your add-ons, integrations and reports on a test company first and fix what the new version breaks, before it reaches production.
Add-on compatibility
Add-ons rebuilt or repackaged for the SAP Business One version you run, with a check of the forms, menus and events they depend on.
HANA compatibility
Queries, formatted searches, procedures and code that sends SQL checked and corrected for SAP HANA, if you run it or are moving to it.
Small changes
A new field on a screen, an extra validation, a changed approval rule, another column in a report: small requests handled inside the retainer.
New reports and queries
Crystal Reports, layouts, queries and dashboards for new questions the business asks, for SQL Server and HANA.
Integration monitoring
Checks on the links between SAP Business One and other systems (Service Layer or DI API integrations, portals, e-commerce, e-invoicing): failed calls looked at, causes found, fixes made.
Code review of work by others
For add-ons and integrations that someone else built, we review the code and the setup first, then tell you what we can safely support and what needs work.
Change log and documentation
Every change is recorded and the documentation is kept current, so your team or your SAP partner can follow what was done.
See also: Custom SAP Business One add-on development · SAP Business One SQL Server to HANA migration · SAP Business One development · SAP Business One in the United States
Built for teams like yours.
Companies whose SAP Business One add-on or integration was built by Kodenova and whose 3 free months are over
Companies with add-ons or integrations built by someone else that no longer have a developer behind them
SAP Business One partners who want a senior developer on call for their customers’ custom code
How a project runs.
- Start: for our own projects, support simply continues after the 3 free months. For code built by others, we first review it.
- Code review (others’ work only): we read the add-on or integration, check how it connects to SAP Business One, and report what we can support and what has risks.
- Proposal: scope of the retainer, what counts as a small change, how requests are sent, and the response times, written into the proposal.
- Requests: you send them by email to [email protected] or by WhatsApp; each one is logged, and each fix or change is tested on a test company before it goes to production.
- Upgrades: before a SAP Business One upgrade, we test your custom code on a test company copy and fix what the new version changes.
- Reporting: a change log and updated documentation, so you can see what was done and why.
What happens after the 3 months of free support?
The 3 months of free post-go-live support cover fixes and small adjustments to what we delivered. After that you can stop, or continue with an optional monthly retainer. The retainer scope and the response times are written into the proposal; nothing starts without your agreement.
What usually breaks after a SAP Business One upgrade?
Custom code breaks where it depends on something the new version changed. UI API add-ons can fail when a standard form changes and the add-on looks for an item that moved or was renamed. Add-ons built for an older SDK version may need rebuilding and repackaging. Service Layer integrations can be affected by changes to objects, fields or behaviour in a new version. SQL written for SQL Server can fail on HANA, where names are case-sensitive and functions differ.
That is why upgrades are tested on a test company first: we run the add-ons, integrations, queries and reports there, fix what fails, and only then does anything go to production.
Can you support add-ons that someone else built?
Yes, after a code review. We read the code and the setup first, then tell you in writing what we can support and what carries risk, such as missing source code, missing documentation or unsafe database access. Where something is not safe to support as it is, we say so and propose the fix.
What does your SAP partner still do?
Kodenova is independent and works alongside your SAP partner. Your partner keeps the licences, the SAP Business One system and SAP’s standard support. We support the custom code around it: add-ons, integrations, portals, queries and reports. When a problem is in SAP’s standard software, we document it so your partner can take it up with SAP.
Who owns the code, and can we leave?
You do. The client owns the source code, database and documentation after each paid phase, so you can stop the retainer at any time and continue with your own team or another provider.
How do you find the cause of a failing posting or integration?
We start from the error SAP returns. DI API and Service Layer errors carry codes that point to the cause, and failed integration calls are traced back to the request that caused them, then reproduced on a test company before anything is changed.
SAP Business One development support and retainer: common questions
Is support after go-live really free?
Yes, for 3 months after go-live. Every Kodenova project includes 3 months of free post-go-live support for fixes and small adjustments. After that, monthly support is optional.
What does the monthly retainer cover?
Bug fixes, SAP Business One upgrade and add-on compatibility testing, HANA compatibility, small changes, new reports and queries, and monitoring of integrations. The exact scope is written into the proposal.
What response time do you guarantee?
Response times are agreed in the proposal, so they match what your business needs. We do not publish a fixed response time on this page.
Can you support add-ons or integrations that Kodenova did not build?
Yes, after a code review. We read the code and the setup, tell you what we can support and what needs work, and then include it in the retainer.
Is Kodenova an SAP partner, and who supports SAP itself?
No. Kodenova is independent and works alongside your SAP partner. Your partner keeps the licences and SAP’s own support for the standard system; we support the custom code: add-ons, integrations, portals and reports.
Who owns the code, and is there lock-in?
You own the source code, database and documentation after each paid phase. There is no lock-in: you can stop the retainer and continue with your own team or another provider.
SAP Business One development
Any add-on your business needs: plant maintenance, payroll, approvals, warehouse, integrations and reports for SAP Business One.
SAP Business One add-onsCustom SAP Business One add-on development
Native UI API screens, DI API and Service Layer logic, UDFs, UDTs, validations and integrations, tested and packaged for the Extension Manager.
SAP Business One on HANASAP Business One SQL Server to HANA migration
Database move, T-SQL to HANA SQL for queries, formatted searches, procedures and Crystal Reports, add-on checks, data reconciliation and a parallel run.
SAP Business One e-commerceSAP Business One e-commerce integration
Shopify, WooCommerce and Magento connected to SAP Business One: items, stock, prices, orders, customers, invoices, payments and fulfilment status.
SAP Business One integrationSAP Business One API integration
Service Layer and DI API integrations between SAP Business One and banks, logistics and couriers, marketplaces, CRMs, payment gateways and other systems.
SAP Business One reportingSAP Business One reports and dashboards
Crystal Reports layouts and reports, query reports, Power BI and web dashboards for SAP Business One on SQL Server and HANA.
E-invoicingE-invoicing integration
Government e-invoicing connected directly to SAP Business One and ERPs: ZATCA, SRI, FEL, DTE and Panama FE.
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.
