All integrations
ERP integration

Factory Labs + SAP Integration: Live ERP Reads, No Middleware

How Factory Labs integrates with SAP S/4HANA Cloud, S/4HANA on-premise, and Business One. Live order, inventory, and pricing reads via the SAP gateway service. No Boomi, no MuleSoft, no sync window.

Updated 2026-05-17 Β· Official SAP site

Factory Labs reads from SAP at request time. There is no middleware layer holding a copy of your SAP data. When a sales rep opens an account in Factory, the order history, pricing, inventory, and credit status are live queries against SAP, normalized through the Factory SAP gateway service and surfaced in the CRM's UI.

This page covers the supported SAP products, what the integration actually does, how to set it up, and what to expect operationally.

What we support

The Factory Labs SAP gateway handles three SAP product families:

  • SAP S/4HANA Cloud. OData v4 API surface. Sub-100ms response times from co-located Factory tenants.
  • SAP S/4HANA on-premise. OData v4 if exposed; fallback to SOAP-based BAPIs through SAP Gateway / NetWeaver Gateway. Requires firewall rules.
  • SAP Business One. Service Layer (REST) or DI API. Most B1 customers on-premise; cloud B1 also supported.

The same Factory CRM tenant can read from multiple SAP systems concurrently (multi-company groups, for example) by configuring multiple connection profiles.

What the integration does

The Factory CRM account view live-queries SAP for:

  • Order history. Open orders, recent shipments, line items, contract pricing applied at order time. Pulled fresh on page load, no cache below the gateway TTL.
  • Inventory. On-hand quantity by warehouse, available-to-promise calculations, lead times.
  • Pricing. Contract pricing for the specific customer, list pricing, volume break tiers. Refreshed on demand.
  • Credit. Credit limit, current outstanding A/R, credit hold status. Surfaced inline in the CRM so reps see it before placing a new order.
  • Master data. Customer master, contact roles, ship-to and bill-to addresses, payment terms.

Write-back: order placement (create new sales orders from quotes), customer master updates (contact additions, addresses), case linking (a CRM case can reference a specific SAP delivery or invoice number).

How it works

The Factory SAP gateway is a separate service that lives between the CRM and SAP. It:

  1. Translates Factory's normalized JSON Account shape into SAP's OData / BAPI requests.
  2. Holds short-TTL caches (30s for inventory, 5 min for pricing, 1 hr for master data) that absorb traffic without becoming a second copy.
  3. Handles retry, circuit-breaking, and graceful degradation when SAP is unreachable.
  4. Maps SAP custom fields into Factory's JSONB custom-field surface so customizations propagate without schema migrations on either side.

There is no scheduled sync job. The CRM does not poll SAP. Every read is on demand, every write is direct.

How to set it up

  1. Identify the SAP technical endpoint. OData v4 base URL for S/4HANA, Service Layer base URL for B1.
  2. Provision a service user in SAP. Read access to customers, sales orders, inventory, pricing. Write access to sales orders if you want order placement.
  3. Add the connection in Factory. Settings β†’ Integrations β†’ ERP β†’ SAP. Paste the endpoint, the service user credentials, and the company code. Test the connection.
  4. Map fields (optional). Standard fields auto-map. Custom fields can be mapped via the admin UI in 5 minutes. See the SAP integration docs.
  5. Smoke-test on a known customer. Open the SAP-native customer ID in Factory's contact search; verify the order history and pricing render.

End to end this is typically a 30-90 minute setup for S/4HANA Cloud and 2-4 hours for on-premise S/4HANA (the latter mostly firewall + service user work in SAP, not in Factory).

What this means for your team

For sales reps:

  • The account page shows the live SAP order history. No more "let me check SAP."
  • Pricing on quotes is the SAP contract price as of this second.
  • Inventory check is live; no stale snapshot.
  • Credit hold is surfaced inline; reps see it before they place an order.

For sales ops:

  • No reconciliation report between Factory and SAP. The data is the data.
  • The Boomi or MuleSoft connector previously bridging Factory to SAP can be turned off (or never installed in the first place).
  • Custom fields added in SAP propagate into Factory's JSONB store on the next read; no field-map deployment.

For IT / SAP basis:

  • One service user, one set of API scopes, one auditable access pattern.
  • No middleware tenant to operate, secure, or upgrade.
  • Connection credentials live in Factory's per-tenant HKDF-derived encryption store. See the security overview.

Pricing notes

The SAP gateway is included in every Factory Labs plan from Growth ($45/user/month) up. No per-API-call fee, no per-record fee, no separate "SAP connector license." See the pricing page for plan details.

This is structurally different from the typical Salesforce + Boomi shape, where the Boomi tenant for a single SAP integration runs $24,000-36,000/year on top of the CRM license, plus the partner build ($80,000-150,000) and the maintenance retainer.

Frequently asked questions

Does Factory Labs support multiple SAP company codes? Yes. A single Factory tenant can be wired to multiple SAP company codes via separate connection profiles, with role-based access controlling which Factory users can see which company's data.

What if SAP goes down? The gateway holds a short-TTL cache (30s for inventory, longer for less-volatile data) so the CRM degrades gracefully rather than failing completely. Reads of cached data continue; new reads fail with a clear "SAP unavailable" message.

Does the integration work with SAP custom Z-tables? Yes if they are exposed through OData or BAPI. The gateway can map custom Z-tables into Factory's custom field surface; some Z-table modeling work may be required on the SAP side to expose them.

What about IDoc? For high-volume event-driven flows (delivery confirmations, invoice events), the gateway can consume IDocs via SAP PI / PO or through HTTP push. Most read-side use cases do not require this.

Can we run Factory Labs alongside an existing Salesforce + Boomi setup? Yes during migration. Factory can read from SAP independently while Boomi continues to sync to Salesforce. Once Factory is the source of truth, Boomi can be decommissioned.