Coupa Release Notes – Fivetran Support Portal

August 2022link

We now support the OAuth 2.0 authentication. If you are using the API Key authentication, you need to migrate to OAuth 2.0 before December 1, 2022. You can migrate to OAuth 2.0 by editing the connection parameters and providing the Client ID and Client Secret instead of the API Key. See our Coupa Setup Guide for details about how to obtain them.

April 2022link

We have added a new table, SUPPLIER_ADDRESS, that stores the supplier’s address.

February 2022link

We are deprecating the following tables:

EASY_FORM
EASY_FORM_WIDGET
EASY_FORM_WIDGET_RULE

January 2022link

We have have added the following new tables:

EASY_FORM_DATA
EASY_FORM_WIDGET_DATA
EASY_FORM_APPROVAL_MAPPING

We have linked the APPROVAL and EASY_FORM_DATA tables by adding the easy_form_id column as a foreign key in the APPROVAL table.

EASY_FORM_DATA is a child table of the USER table. To sync the EASY_FORM_DATA table, select it on the Schema tab in your Fivetran dashboard and re-sync the USER table.

May 2021link

Our Coupa connector is now generally available.

Read our Coupa connector documentation.

We have added a new column, custom_fields, to all the tables except the mapping tables (tables whose names end with the _MAPPING suffix). We will sync the custom fields as JSON objects.

April 2021link

We have added two new tables, EXPENSE_LINE_DAILY_PER_DIEM and PER_DIEM_DEDUCTION.

We have renamed the EASYFORM_WIDGET_RULE table to EASY_FORM_WIDGET_RULE.

We have added a new column, custom_fields, to the following tables to sync custom fields as JSON objects:

USER
ORDER_HEADER
INVOICE_HEADER
INVOICE_LINE

We will deprecate the following columns from the USER table after July 30, 2021:

custom_fields_costCenter
custom_fields_dadsArea
custom_fields_dadsDistrict
custom_fields_dadsDivision
custom_fields_dadsStore
custom_fields_division
custom_fields_endDate
custom_fields_orgUnitNName
custom_fields_region

Be sure to update your queries before we deprecate the columns.

March 2021link

We have fixed a bug where the attributes of the EXPENSE_MILEAGE_VEHICLE_TYPE table were added to the separate EXPENSE_TRIP_MILEAGE table. We no longer add the attributes of the EXPENSE_MILEAGE_VEHICLE_TYPE table to the EXPENSE_TRIP_MILEAGE table.

We have renamed the following tables in the Schema tab of your connector details page to align them with the source table names:

CHARGES to CHARGE
PROJECT_BUSINESS_GROUP_RELATION to PROJECT_BUSINESS_GROUP_MAPPING
PROJECT_USER_RELATION to PROJECT_USER_MAPPING
SHIPPING_TERM_BUSINESS_GROUP_RELATION to SHIPPING_TERM_BUSINESS_GROUP_MAPPING
UOM to UNIT_OF_MEASURE

These name changes will not impact your destination tables.

February 2021link

Coupa is a cloud platform for business spend management.