Skip to content
Security and identity ⇄ ERP

Onelogin to SAP S/4HANA integration — real-time, two-way sync

Keep Onelogin and SAP S/4HANA in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Onelogin and SAP S/4HANA

Keep the employee, group, and account records that SAP S/4HANA and Onelogin share aligned in real time, so a person added, moved, or offboarded in one system shows up correctly in the other within seconds.

An ERP and an identity system describe the same workforce from two angles. SAP S/4HANA holds the authoritative record of who works at the company, and often their department, title, manager, and cost center. Onelogin controls the accounts, groups, and access those same people use every day. When the two aren't connected, every hire, transfer, and departure has to be keyed twice, and the window between someone leaving in SAP S/4HANA and their account still being active in Onelogin is a real security exposure.

Stacksync syncs Deliveries, Journal Entries, Customer / Supplier Roles, Production Orders in SAP S/4HANA with Custom user fields, Users, Roles, Apps (app instances) in Onelogin in real time, with field-level mapping and conflict resolution in place of CSV exports and nightly jobs. A new hire, a department change, or a termination propagates within seconds, and where you want changes to flow both ways — the ERP's org data into the directory, account status back into the ERP — the same mapping handles it.

That matters most at offboarding and audit time. When the directory reflects the ERP's current headcount and org structure, disabling access no longer depends on someone remembering to update a second system, and access reviews start from a roster both sides already agree on.

Common use cases

  • 01 Push closed-won CRM opportunities into S/4HANA as sales orders without manual re-keying.
  • 02 Surface invoice and payment status from S/4HANA inside the CRM so account teams see open balances.
  • 03 Read Users, Apps, and Groups into a database for identity, license, and app-assignment inventory across the OneLogin account.
  • 04 Two-way sync Users between OneLogin and an HRIS or Postgres so new hires, attribute changes, and terminations provision and deprovision SSO accounts automatically.

Common sync patterns

Align group and department membership

When someone changes team or department, their group or organizational-unit membership updates to match, keeping access tied to their current role.

One roster on a shared key

People are matched across both systems on an identifier you choose, such as work email or employee ID, so there is a single accurate list of who is active.

Create accounts from new records

A person added in one system gets a matching account or record in the other automatically, so a new hire can be granted access without anyone re-keying their details.

What you can sync between Onelogin and SAP S/4HANA

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Onelogin objects SAP S/4HANA objects How this pairing syncs
Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. Customer / Supplier Roles Role-specific views of Business Partners mapped to CRM account types. Custom user fields is specific to Onelogin and Customer / Supplier Roles to SAP S/4HANA — each maps to any object or custom field on the other side.
Users User accounts (email, username, custom attributes, status, roles); full CRUD via the v2 Users API - create, update, delete, set password, lock/unlock, and add or remove role assignments. Production Orders Manufacturing order status surfaced in planning and operations tools. Users is specific to Onelogin and Production Orders to SAP S/4HANA — each maps to any object or custom field on the other side.
Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. Business Partners Unified customer and supplier master records, the anchor entity for CRM-to-ERP account syncs. Roles is specific to Onelogin and Business Partners to SAP S/4HANA — each maps to any object or custom field on the other side.
Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. Sales Orders Order headers and line items synced to CRMs and fulfillment systems as they are created or amended. Apps (app instances) is specific to Onelogin and Sales Orders to SAP S/4HANA — each maps to any object or custom field on the other side.
Groups Account groups used for mapping and reporting; listed and read through the API, which has no create or update endpoint, so groups are read-only. Purchase Orders Procurement documents shared with supplier portals and spend-management tools. Groups is specific to Onelogin and Purchase Orders to SAP S/4HANA — each maps to any object or custom field on the other side.
Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. Products / Materials Material master data distributed to e-commerce, PIM, and CRM catalogs. Mappings (mapping rules) is specific to Onelogin and Products / Materials to SAP S/4HANA — each maps to any object or custom field on the other side.

How changes propagate between Onelogin and SAP S/4HANA

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Onelogin SAP S/4HANA Sub-second propagation

DetectionOnelogin notifies Stacksync of record changes through webhook events. Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time.

DeliveryEach detected change is written to SAP S/4HANA through its API, with automatic retries and rate-limit backoff.

SAP S/4HANA Onelogin Interval-based propagation

DetectionStacksync polls SAP S/4HANA for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change timestamps exposed by the OData services.

DeliveryEach detected change is written to Onelogin through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Onelogin: Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.
  • SAP S/4HANA: Subject to the platform's API rate limits, which vary by edition and communication arrangement.
What ships with Onelogin ⇄ SAP S/4HANA

Connect Onelogin and SAP S/4HANA for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Onelogin–SAP S/4HANA connection.

Real-time

Two-way sync

Changes in Onelogin or SAP S/4HANA instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Onelogin or SAP S/4HANA data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Onelogin or SAP S/4HANA record.

Observability

Monitoring

Track your Onelogin ⇄ SAP S/4HANA sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Onelogin and SAP S/4HANA.

How the Onelogin and SAP S/4HANA connectors work

Onelogin

Integration surface
OneLogin API (REST, v1 and v2 resource endpoints on <subdomain>.onelogin.com) plus the Event Webhook (Event Broadcaster) for event delivery
Authentication
OAuth 2.0 client credentials - an admin generates an API credential pair (client_id + client_secret) in the OneLogin portal and exchanges it at POST /auth/oauth2/v2/token for a bearer access token sent on every call; each credential carries a scope (Manage all, Manage users, Read users, etc.) that governs read vs write.
Change detection
Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time; the Events API also supports polling with since/until time filters and pagination for historical backfill.
Capabilities
read · write · webhooks
Rate limits
Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.

SAP S/4HANA

Integration surface
OData REST APIs (v2/v4), with SOAP, BAPI/RFC, and IDoc interfaces on on-premise editions
Authentication
OAuth 2.0 with communication arrangements on cloud editions; basic auth or certificate-based on-premise
Change detection
Polling on change timestamps exposed by the OData services; business events can be emitted through SAP's event infrastructure on cloud editions
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits, which vary by edition and communication arrangement
How it works

How to connect Onelogin to SAP S/4HANA — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Onelogin and SAP S/4HANA with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Onelogin connected
    SAP S/4HANA connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Onelogin and SAP S/4HANA objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Onelogin ⇄ SAP S/4HANA
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Onelogin SAP S/4HANA
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Onelogin and SAP S/4HANA integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 507 integrations available for Onelogin and SAP S/4HANA.

Popular · 7 of 507
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.