Marquis IQ connects to SAP Business One and SAP S/4HANA, cloud and on-premises, via the Service Layer REST API and OData APIs, extracting clean manufacturing and financial data and delivering the PE-grade reporting that BusinessObjects and SAP Analytics Cloud weren't designed to provide.
Whether your portfolio companies run SAP Business One or SAP S/4HANA, the analytics story is the same: mature, reliable ERPs with native reporting tools built for transactional visibility, not PE-grade operational intelligence. BusinessObjects produces well-formatted static documents. SAP Analytics Cloud requires significant licensing and configuration investment. Neither was designed to answer the cross-entity, trend-over-time, margin-by-product-line questions that PE firms ask at every board meeting.
For PE portfolios where one site runs SAP Business One, another runs S/4HANA, and others run Epicor or Dynamics, the consolidation problem compounds across all of them. Marquis connects to each SAP product via its native API: Service Layer for Business One, OData APIs for S/4HANA, and reconciles customer and item masters across every entity before building the consolidated dataset.
Marquis connects to both SAP products through their native APIs: the Service Layer REST API for Business One, and OData APIs for S/4HANA. No direct HANA database queries, no fragile custom scripts, no changes required to your SAP configuration.
SAP Business One Cloud is SAP's hosted version of Business One, running on SAP HANA Cloud and managed by SAP partners. The Marquis connector uses the Service Layer REST API, SAP's official published interface for Business One integrations. Cloud release updates and patch cycles don't break the connector, and no direct database access is required. Incremental extraction keeps data current without performance impact on the B1 tenant.
SAP Business One on-premises, running on SQL Server or SAP HANA, uses the same Service Layer REST API that the cloud version exposes, making the connector architecture consistent across deployment models. Where the Service Layer isn't available, Marquis falls back to the DI API with schema knowledge specific to the B1 data model, including how B1 structures its item master, sales orders, production orders, and financial transactions in both HANA and SQL Server backends.
SAP S/4HANA Cloud is SAP's next-generation enterprise ERP, purpose-built on the SAP HANA in-memory database and delivered as a managed cloud service. The Marquis connector reaches S/4HANA Cloud through SAP's OData APIs, the same interface SAP certifies for third-party integrations, extracting financials, production orders, purchasing, and inventory data without requiring SAP BTP middleware or custom ABAP development. Automatic quarterly release cycles in S/4HANA Cloud do not affect the connector.
SAP S/4HANA on-premises is the installed version of SAP's enterprise flagship, commonly found in larger PE portfolio companies running S/4HANA alongside older acquired entities on SAP ECC or Business One. Marquis connects via OData APIs and, where required, RFC/BAPI function modules, extracting financial, production, and supply chain data regardless of whether the system is on private infrastructure or a cloud-hosted private instance. ECC environments migrating toward S/4HANA are handled the same way.
Both SAP Business One and S/4HANA expose published, documented APIs designed for external integrations. Marquis uses them the right way: no direct HANA database queries, no fragile custom ABAP scripts, no changes to your SAP configuration.
Tell us which SAP product you're on, cloud or on-premises, and how many entities you're consolidating. We'll walk through exactly what analytics are available from day one of your SAP connection.
Connection via the SAP Service Layer REST API, no changes to your B1 configuration or involvement from your SAP partner required.