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.
Does it work with our existing SAP S/4HANA licenses?
Yes — the adapter rides on top of your existing SAP S/4HANA subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
Is this a packaged SAP S/4HANA connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.
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.
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.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Naperville, 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.