Coupa
Coupa is a cloud platform for business spend management.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | ACCOUNTS, ACCOUNT_TYPE, ACCOUNT_VALIDATION_RULE, ADDRESS, ANNOUNCEMENT, APPROVAL, ASN_HEADER,BUDGET_LINE, BUDGET_LINE_ADJUSTMENT, BUSINESS_ENTITY, BUSINESS_GROUP, CHARGES, COMMODITY_TRANSLATION, COMMODITY, CONTRACT, CONTRACT_TEMPLATE, CP_PAYMENT, CURRENCIES, DATA_FILE_SOURCE, DEPARTMENT, EXCHANGE_RATE, EXPENSE_LINE, EXPENSE_REPORT, EXTERNAL_PAYMENT, INTEGRATION, INTEGRATION_ERROR, INTEGRATION_HISTORY_RECORD, INTEGRATION_RUN, RECEIVING_TRANSACTION, INVENTORY_ADJUSTMENT, INVENTORY_CONSUMPTION, INVENTORY_TRANSFER, RETURN_TO_SUPPLIER_TRANSACTION, INVOICE_HEADER, INVOICE_HEADER_WITH_PAYMENT_DATE, ITEM, LOOKUP_VALUE, MATCHING_ALLOCATION, ORDER_HEADER, ORDER_HEADER_CHANGE, ORDER_PAD, PAYMENT_TERM, PROJECT, QUOTE_REQUEST, QUOTE_RESPONSE, REQUISITION_HEADER, SHIPPING_TERM, SUPPLIER, SUPPLIER_INFORMATION, SUPPLIER_ITEM, SUPPLIER_RISK_AWARE_FEED, TASK, TAX_REGISTRATION, USER, USER_GROUP, and USER_GROUP_MEMBERSHIP tables. | |
| History mode | ||
| Custom data | ||
| Data blocking | ||
| Column hashing | ||
| Re-sync | ||
| Row filtering | ||
| API configurable | API configuration | |
| Priority-first sync | ||
| Fivetran data models | ||
| Private networking | ||
| Authorization via API |
Supported deployment models
We support the SaaS and Hybrid deployment models for the connector.
You must have an Enterprise or Business Critical plan to use the Hybrid Deployment model.
Setup guide
Follow our step-by-step Coupa setup guide to connect Coupa with your destination using Fivetran connectors.
Schema information
This schema applies to all Coupa connections.
Sync notes
The Coupa connector supports table re-syncs:
- A parent table re-sync triggers a re-sync of all associated child tables.
- A child table re-sync triggers a re-sync of its parent table and all associated child tables.
Deleting data
Records deleted or deactivated in Coupa may not be available through the Coupa API. To reliably capture deletes, we first mark all records in the destination as _fivetran_deleted = TRUE. We then reimport only the IDs of records present in the source. Records with IDs that are not returned by the API remain marked as _fivetran_deleted = TRUE.
Reimporting IDs can take longer than incremental syncs, so we only perform this process on weekends to avoid regular disruptions.