Queries for users and reports
Saved queries, report data sources, and formatted search logic.
HANA & SQL
Use the database layer carefully and transparently.
Well-written queries and procedures give SAP Business One better reports, validations, and diagnostics. Poorly written ones create hidden dependencies. We keep database logic documented and supportable.
- Saudi Arabia
- GCC
- SAP Business One
What's included
What we can review and deliver
Validation rules
Transaction checks that stop incorrect documents before they are posted.
Stored procedures and views
Reusable logic for reporting and integration, written for HANA or SQL Server.
Data extraction and reconciliation
Extracts for audits, analysis, and checks between modules.
Performance review
Slow reports and queries reviewed and rewritten where needed.
SQL Server to HANA
Review and conversion of custom logic when the database platform changes.
Working principle
We read data with queries and write it through supported interfaces such as the DI API and Service Layer — never with direct updates to SAP Business One tables.
When this helps
Signs it is time to look at this
- Reports take too long or time out.
- Wrong documents keep getting posted and are corrected afterwards.
- Custom logic exists in the database but nobody knows what it does.
- You are moving from SQL Server to SAP HANA.
How we approach it
A controlled sequence, not guesswork
- Read before writingUnderstand existing logic and its dependencies.
- Build against test dataDevelop and validate outside production first.
- Reconcile resultsCheck output against standard reports and known totals.
- Document and hand overEvery object is named, commented, and listed.
Questions
Common questions
Is it safe to add custom database logic to SAP Business One?
Yes, when it stays within supported approaches: read-only queries, views, and the validation hooks SAP Business One provides. Direct data changes are not one of them.
Do queries need to be rewritten when moving to HANA?
Often, yes. Syntax and some functions differ between SQL Server and HANA, so custom queries, procedures, and report sources need review.
Can you explain logic someone else wrote?
Yes. We review existing objects and document what they do, where they are used, and what depends on them.
Start with context
Show us the process, the problem, and the expected result.
For an existing system, include the SAP Business One version, database platform, affected process, and a sample if available. For new work, share the scope and key business requirements.