SAP ECC and Monday.com integration

What moves between them

Purchase orders and vendors flow from SAP ECC into Monday.com Items on a customer-configured board. SAP ECC is queried via OData REST (polling on a daily or weekly schedule set by the customer) or via inbound IDoc messages pushed by customer RFC agent configuration, and each record becomes a Monday.com Item with columns mapping to PO number, vendor ID, GL account, amount, and cost center. Vendor master records created in Monday.com flow back into SAP ECC as new vendors via BAPI_VENDOR_CREATE, and updated vendor details via BAPI_VENDOR_CHANGE. GL accounts and cost centers stay synchronized in both directions by reading SAP ECC's GL account and cost center master tables and updating Monday.com columns accordingly. The flow is asynchronous and may be triggered manually or on a schedule.

How ml-connector handles it

ml-connector accepts the customer's SAP ECC OData gateway URL and HTTP Basic Auth credentials, and stores them encrypted. On each poll cycle, it queries SAP ECC's OData services for new or changed purchase orders and vendors (using RFC_READ_TABLE with a row-width-aware query to avoid the 512-character limit), then translates each record into a Monday.com GraphQL mutation. Column values are JSON-encoded strings as required by Monday.com's API. For reverse flow, ml-connector listens for Monday.com webhooks on a registered board (verifying the challenge on first registration) and converts Item data into BAPI function module calls, sending them through the customer's RFC agent connection. The RFC agent must run on the customer's network with either SAP NetConnector or Java Connector installed and configured. ml-connector tracks which records have been synced to avoid duplicates (using SAP ECC's REF_DOC_NO field for purchase orders and unique board Item IDs for Monday.com), retries failed calls with exponential backoff when SAP ECC returns COMMUNICATION_FAILURE or Monday.com rate-limits (429 status), and maintains an audit log of every record moved in both directions.

A real-world example

A mid-market distributor uses SAP ECC for purchasing, vendors, and cost accounting, but its operations and finance teams use Monday.com for workflow and spend visibility. Before the integration, the procurement team posted new purchase orders into both SAP ECC and Monday.com by hand, and vendor changes had to be entered into SAP ECC before they appeared on the Monday.com board. This lag meant the board was often out of sync with the actual vendor records in SAP. With SAP ECC and Monday.com connected, each new SAP purchase order automatically lands on the Monday.com board with the GL account and cost center pre-filled, and new vendor records entered on the Monday.com board are pushed into SAP ECC within minutes. The finance team now has a real-time view of purchasing activity without manual entry, and the two systems stay consistent.

What you can do

• •Sync purchase orders and their line items from SAP ECC into Monday.com Items, with GL account and cost center columns auto-populated.
• •Create new vendors on a Monday.com board and automatically post them into SAP ECC using BAPI_VENDOR_CREATE and BAPI_VENDOR_CHANGE.
• •Keep GL account and cost center master records in sync between SAP ECC and Monday.com by polling SAP master tables and updating board columns.
• •Handle RFC/BAPI calls through the customer's on-premises SAP agent and OData v2 polling on a customer-controlled schedule.
• •Maintain deduplication and a full audit trail of every purchase order, vendor, and GL account moved between systems, with manual replay on failure.

Questions

Does Monday.com have native purchase order or vendor objects?

No. Monday.com is a work operating system built on Boards, Items, and Columns. Customers define their own finance boards with columns that represent purchase order number, vendor ID, GL account, cost center, and amount. ml-connector maps SAP ECC purchase orders and vendors to Monday.com Items and auto-fills the columns based on the configuration.

Does the SAP ECC RFC agent need to be installed for this integration to work?

Yes, if you want to push vendor or purchase order data from Monday.com back into SAP ECC. The RFC agent (SAP NetConnector or Java Connector) must run on your network and be configured to accept inbound calls. For reading SAP ECC data into Monday.com (pull-only), you can use OData v2 via the SAP Gateway, which does not require an agent.

What happens if a purchase order is updated in both SAP ECC and Monday.com at the same time?

ml-connector tracks each record using SAP ECC's external reference field (REF_DOC_NO) and Monday.com's unique Item ID to detect duplicates and avoid re-importing the same record twice. If a conflict occurs, the most recent change (based on timestamp) takes precedence, and the audit trail logs both attempts so you can manually review and adjust if needed.