Can the SAP S/4HANA adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your SAP S/4HANA tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The SAP S/4HANA adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
What happens if SAP S/4HANA changes their API after we go live?
Our SRE team monitors SAP S/4HANA change announcements and rolls compatibility updates inside our maintenance retainer. If a breaking change ships, we own the migration; you don't pay extra to stay current and you don't field calls from the vendor.
How long does the SAP S/4HANA integration take to ship?
Our standard window is thirty days from signed scope to live SAP S/4HANA adapter in production, plus a one-week monitored stabilization phase. For Aurora, Illinois, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Aurora, Illinois. After go-live, the SAP S/4HANA adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.
Do we own the integration code at the end?
Yes. The Connectify SAP S/4HANA adapter ships with full source escrow rights — at any point you can request a snapshot of the code, configuration, and runbooks. We prefer you stay on our managed runtime, but you are never locked in.