OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured APIs across the declared product scope
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
Service Layer returns structured business-object data in the deployed company scope.
Service Layer data retrieval options ↗
GET retrieval and entity collections · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
Follow collection continuation links to enumerate supported objects; this is not a consistent database backup.
Business One Service Layer paging ↗
Retrieve Records with Paging · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
The assessed object route supports filters, projections and ordering; exposed SQL views are a distinct configured route.
Service Layer data retrieval options ↗
Data retrieval options · Checked 2026-10-16
Access cost barrier -
-
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
The complete fixed access entitlement and API fees relative to the lowest paid plan are not established by the reviewed technical documentation.
Business One Service Layer authentication ↗
Business One Service Layer authentication · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
Eligibility for a chosen third-party application, beyond the documented technical authorization, remains unestablished.
Business One Service Layer authentication ↗
Business One Service Layer authentication · Checked 2026-10-16
Downstream permission -
-
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
Applicable downstream processing, redistribution and AI-use conditions remain unestablished for the declared route.
Business One Service Layer authentication ↗
Business One Service Layer authentication · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update across business domains
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
Business partner and item resources document POST/PATCH operations, subject to business-object validation.
Business One Service Layer object operations ↗
BusinessPartners and Items operations · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
A client can log in and call Service Layer with an authorized company user; licensing for a chosen outside operator remains separate.
Business One Service Layer authentication ↗
Login and subsequent API requests · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism -
-
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
A general updated-record extraction contract is not established for every assessed object.
Business One Service Layer authentication ↗
Business One Service Layer authentication · Checked 2026-10-16
Limit visibility -
-
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
An inactive login expires after 30 minutes by default; clients must establish a fresh session when it expires. No universal requests-per-second quota is established.
Business One Service Layer authentication ↗
Logout; SessionTimeout · Checked 2026-10-16
CDC and deletion capture -
-
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
Complete deletion identity coverage is not established on this assessed route.
Business One Service Layer authentication ↗
Business One Service Layer authentication · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
A fresh authorized collection traversal can rebuild the scoped current record set. It does not replay intermediate states or recover historical deleted payloads; verify paging completeness before replacing a prior copy.
Business One Service Layer paging ↗
Current-state collection retrieval · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
Collection responses provide customer-held JSON records for the selected API objects.
Business One Service Layer paging ↗
JSON collections and continuation links · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
The reviewed extraction documentation does not establish contractual retrieval rights after cancellation or license termination.
Business One Service Layer authentication ↗
Business One Service Layer authentication · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
Portable object records are established, while whole-company files, history and extensions remain unverified.
Service Layer data retrieval options ↗
Structured Service Layer output · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
Applications can implement logic using authenticated object calls; portable native workflow definitions are not established here.
Business One Service Layer authentication ↗
Consuming Service Layer · Checked 2026-10-16
Rights to custom logic -
-
SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded.
Ownership, reusable export and independent execution rights for native workflow artifacts remain unestablished.
Business One Service Layer authentication ↗
Business One Service Layer authentication · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
A company database name and authorized SAP user establish a Service Layer session. Customer-managed authentication does not by itself settle third-party licensing or distribution conditions.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Business-object JSON collections support projection, filters, ordering and continuation links. Service Layer metadata reflects supported objects; database SQL and an API collection are separate interfaces.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer company Service Layer session | session | Customer | Not confirmed | product and contract scope | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The current interface reference documents session expiry and configurable connection behavior. It does not establish a universal API surcharge or a lowest entitled customer license.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
POST and PATCH operate on named business objects, including business partners and inventory items. Object permissions and the business rules of the deployed version still apply.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Collection paging supports repeated reads, but no universal changed/deleted feed or retained replay contract is established for this Service Layer scope. An idle session expires after 30 minutes by default; that is an authentication lifetime, not change retention.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. Complete deletion identity coverage is not established on this assessed route. | Business One Service Layer authentication ↗Business One Service Layer authenticationChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedSAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. A fresh authorized collection traversal can rebuild the scoped current record set. It does not replay intermediate states or recover historical deleted payloads; verify paging completeness before replacing a prior copy. | Business One Service Layer paging ↗Current-state collection retrievalChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Customers can retain structured object responses. This supports a scoped record copy, without proving a complete backup of documents, relationships, history and custom ERP extensions (direct database extraction requires a separate assessment).
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
User-defined objects and fields extend the API model. This review credits external application code; reusable native procedure ownership and independent execution remain unestablished.
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured APIs across the declared product scopeSAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. Service Layer returns structured business-object data in the deployed company scope. | Service Layer data retrieval options ↗GET retrieval and entity collectionsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsSAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. Follow collection continuation links to enumerate supported objects; this is not a consistent database backup. | Business One Service Layer paging ↗Retrieve Records with PagingChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersSAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. The assessed object route supports filters, projections and ordering; exposed SQL views are a distinct configured route. | Service Layer data retrieval options ↗Data retrieval optionsChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. Eligibility for a chosen third-party application, beyond the documented technical authorization, remains unestablished. | Business One Service Layer authentication ↗Business One Service Layer authenticationChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. The complete fixed access entitlement and API fees relative to the lowest paid plan are not established by the reviewed technical documentation. | Business One Service Layer authentication ↗Business One Service Layer authenticationChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. Applicable downstream processing, redistribution and AI-use conditions remain unestablished for the declared route. | Business One Service Layer authentication ↗Business One Service Layer authenticationChecked 2026-10-16 |
| Which external write operations are documented? | Create and update across business domainsSAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. Business partner and item resources document POST/PATCH operations, subject to business-object validation. | Business One Service Layer object operations ↗BusinessPartners and Items operationsChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionSAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. A client can log in and call Service Layer with an authorized company user; licensing for a chosen outside operator remains separate. | Business One Service Layer authentication ↗Login and subsequent API requestsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | -SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. A general updated-record extraction contract is not established for every assessed object. | Business One Service Layer authentication ↗Business One Service Layer authenticationChecked 2026-10-16 |
| How are integration limits disclosed? | -SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. An inactive login expires after 30 minutes by default; clients must establish a fresh session when it expires. No universal requests-per-second quota is established. | Business One Service Layer authentication ↗Logout; SessionTimeoutChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsSAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. Collection responses provide customer-held JSON records for the selected API objects. | Business One Service Layer paging ↗JSON collections and continuation linksChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. The reviewed extraction documentation does not establish contractual retrieval rights after cancellation or license termination. | Business One Service Layer authentication ↗Business One Service Layer authenticationChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedSAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. Applications can implement logic using authenticated object calls; portable native workflow definitions are not established here. | Business One Service Layer authentication ↗Consuming Service LayerChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -SAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. Ownership, reusable export and independent execution rights for native workflow artifacts remain unestablished. | Business One Service Layer authentication ↗Business One Service Layer authenticationChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedSAP Business One 10.0 Service Layer OData v4: customer-managed company session, business-object collections and writes; direct SQL replication and complete ERP database restore are excluded. Portable object records are established, while whole-company files, history and extensions remain unverified. | Service Layer data retrieval options ↗Structured Service Layer outputChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Third-party eligibility: Eligibility for a chosen third-party application, beyond the documented technical authorization, remains unestablished.
- Access cost barrier: The complete fixed access entitlement and API fees relative to the lowest paid plan are not established by the reviewed technical documentation.
- Downstream permission: Applicable downstream processing, redistribution and AI-use conditions remain unestablished for the declared route.
- Refresh mechanism: A general updated-record extraction contract is not established for every assessed object.
- Limit visibility: An inactive login expires after 30 minutes by default; clients must establish a fresh session when it expires. No universal requests-per-second quota is established.
- Post-cancellation access: The reviewed extraction documentation does not establish contractual retrieval rights after cancellation or license termination.
- Rights to custom logic: Ownership, reusable export and independent execution rights for native workflow artifacts remain unestablished.
- CDC and deletion capture: Complete deletion identity coverage is not established on this assessed route.
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.