Skip to content
Database ⇄ Accounting and finance

SAP Hana to Workday integration — real-time, two-way sync

Keep SAP Hana and Workday 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 SAP Hana and Workday

Work with Workday's financial data straight from SAP Hana: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Time Off and Absence, Payroll Results, Suppliers, Customers and Invoices from Workday into SQL views, Schemas, Sequences, Triggers in SAP Hana and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against SAP Hana, and rows your code writes or updates flow back into Workday with validation, so the finance system stays the system of record.

Common use cases

  • 01 Push completed payroll results into a finance system or data warehouse each pay cycle.
  • 02 Import journal entries from external billing or expense systems into Workday Financials.
  • 03 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.
  • 04 Detect inserts, updates, and deletes on high-write tables via AFTER triggers or a last-modified column and replicate the deltas downstream near-real-time.

Common sync patterns

Internal tools without API plumbing

Build dashboards and back-office tools directly on SAP Hana; Stacksync handles the API calls, rate limits, and retries against Workday.

Write back safely

Updates written to the synced tables in SAP Hana propagate into Workday, so automations can create or correct finance records without custom integration code.

React to financial events

Changes in Workday appear in SAP Hana as row changes, so you can trigger downstream logic with the database tooling you already use.

What you can sync between SAP Hana and Workday

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.

SAP Hana objects Workday objects How this pairing syncs
Column store tables HANA's default table type, optimized for analytics; synced two-way as rows over the SQL interface with the primary key driving upserts and delete tracking. Time Off and Absence Balances and requests synced with scheduling and workforce tools. Column store tables is specific to SAP Hana and Time Off and Absence to Workday — each maps to any object or custom field on the other side.
Row store tables OLTP-oriented tables held fully in memory; read and written the same way through the SAP HANA client for high-write operational tables. Payroll Results Completed pay data exported to finance and benefits systems. Row store tables is specific to SAP Hana and Payroll Results to Workday — each maps to any object or custom field on the other side.
Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. Suppliers Workday Financials vendor records aligned with procurement tools. Calculation views is specific to SAP Hana and Suppliers to Workday — each maps to any object or custom field on the other side.
SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. Customers and Invoices Financials receivables objects synced for billing visibility where Workday Financials is used. SQL views is specific to SAP Hana and Customers and Invoices to Workday — each maps to any object or custom field on the other side.
Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. Journal Entries Accounting entries imported from external subledgers into Workday Financials. Schemas is specific to SAP Hana and Journal Entries to Workday — each maps to any object or custom field on the other side.
Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. Custom Reports (RaaS) Tenant-defined reports exposed as web service endpoints, often the practical read surface for syncs. Sequences is specific to SAP Hana and Custom Reports (RaaS) to Workday — each maps to any object or custom field on the other side.

How changes propagate between SAP Hana and Workday

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.

SAP Hana Workday Sub-second propagation

DetectionChanges in SAP Hana are captured at the source via change data capture — no polling loop against its API. Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table.

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

Workday SAP Hana Interval-based propagation

DetectionStacksync polls Workday for changes on an incremental schedule, reading only records changed since the previous pass. Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment.

DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • SAP Hana: No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
What ships with SAP Hana ⇄ Workday

Connect SAP Hana and Workday for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every SAP Hana–Workday connection.

Real-time

Two-way sync

Changes in SAP Hana or Workday instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever SAP Hana or Workday 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 SAP Hana or Workday record.

Observability

Monitoring

Track your SAP Hana ⇄ Workday sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between SAP Hana and Workday.

How the SAP Hana and Workday connectors work

SAP Hana

Integration surface
SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access
Authentication
Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting.
Change detection
Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table; system-versioned temporal tables and SLT/SDI provide trigger- and log-based CDC. No native webhooks.
Capabilities
read · write · CDC
Rate limits
No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.

Workday

Integration surface
SOAP Workday Web Services (WWS), a REST API, and Reports-as-a-Service (RaaS) endpoints for custom reports
Authentication
OAuth 2.0 for the REST API; integration system users with WS-Security or certificate-based auth for SOAP
Change detection
Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment; no general webhook surface
Capabilities
read · write
How it works

How to connect SAP Hana to Workday — 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 SAP Hana and Workday 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
    SAP Hana connected
    Workday connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the SAP Hana and Workday 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 · SAP Hana ⇄ Workday
    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
    SAP Hana Workday
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

SAP Hana and Workday 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
CSA STAR
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 529 integrations available for SAP Hana and Workday.

Popular · 8 of 529
Coworkers laughing in front of a laptop in a casual office setting

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