SAP S/4HANA and Monday.com integration

What moves between them

The main flow runs from SAP S/4HANA into Monday.com. Supplier master data and purchase orders are read from SAP on a polling schedule and synced as board items in Monday.com, with columns for supplier name, order ID, amount, currency, and status. GL accounts and cost centers from SAP are synced to Monday.com boards as reference columns so procurement allocations stay within valid financial dimensions. Monday.com is write-only on the connector side; changes to procurement status or approvals can be read back into SAP via polling but are not pushed.

How ml-connector handles it

ml-connector stores both credential sets encrypted and manages OAuth 2.0 token refresh for SAP so tokens are refreshed before expiry. On the SAP side it polls supplier and purchase order endpoints with LastChangeDateTime filters to retrieve only new and modified records since the last sync, and handles OData pagination. On the Monday.com side it creates or updates board items by mapping SAP purchase orders to items and SAP GL accounts to column values, respecting Monday.com's rate limits and query complexity constraints. Because SAP has no webhooks, polling is tied to your procurement cycle (daily or on-demand) rather than real-time push. Supplier and GL account data is mapped first to ensure every purchase order references a valid supplier and cost center on the Monday.com board.

A real-world example

A mid-sized manufacturing company runs SAP S/4HANA for procurement and finance, and uses Monday.com boards to manage purchase approvals and supplier performance. Before the integration, procurement staff entered purchase orders manually into Monday.com for tracking, duplicating data already in SAP, and the finance team could not easily see which orders were approved or pending without switching between systems. With SAP S/4HANA and Monday.com connected, each new purchase order and supplier appears automatically on the tracking board with GL account and cost center populated from SAP, approval workflows are visible in Monday.com, and the procurement team works from a single source of truth without manual re-entry.

What you can do

• •Read suppliers, purchase orders, and purchase requisitions from SAP S/4HANA and sync them as items to Monday.com boards.
• •Populate GL accounts and cost centers from SAP as reference columns on Monday.com so procurement allocations stay within valid financial dimensions.
• •Authenticate SAP with OAuth 2.0 and Monday.com with Personal API Token or OAuth, managing token refresh and expiry.
• •Poll SAP on a schedule tied to your procurement cycle, with timestamp filters to retrieve only new and modified records.
• •Track every supplier and order record with a full audit trail and replay capability if a sync fails.

Questions

Which direction does data move between SAP S/4HANA and Monday.com?

The main flow is SAP S/4HANA into Monday.com. Suppliers, purchase orders, GL accounts, and cost centers are read from SAP and synced to Monday.com boards as items and reference columns. Changes to procurement status in Monday.com can be read back into SAP via polling but are not pushed back automatically.

Does SAP S/4HANA have webhooks for real-time sync?

No. SAP S/4HANA has no native webhooks for cloud connectors. ml-connector polls SAP OData endpoints on a schedule tied to your procurement cycle, using timestamp filters to retrieve only new and modified records since the last sync. Real-time push would require SAP BTP Event Mesh, which is a separate paid service.

How does ml-connector handle SAP OAuth tokens and Monday.com rate limits?

ml-connector caches SAP OAuth tokens and refreshes them before expiry so authentication never interrupts a sync. For Monday.com it respects rate limits per plan tier and query complexity constraints, batching board mutations within the 40 per minute limit so large syncs do not trigger rate-limit errors.