Treasury Project Export

The Treasury Project export uses only a single set of header columns.

Export of these records is included as a Standard CSV Export.

Note

Because Integration Transaction Formats are not available for Treasury objects, you cannot configure the columns for this export. 

Column Name Description Req'd Unique Type Allowable Values
UniqueID GuID given by the system FALSE FALSE
IntegerID Integer ID given by the system FALSE FALSE integer
Abbreviation Abbreviation of the project TRUE string
Name Name of the project FALSE string
Internal Reference Internal reference of the project (used for integrations) TRUE
Is Active Indicates whether the project is active FALSE
Classic User IntegerID (Entered User) Classic User IntegerID (Entered User) FALSE FALSE integer
Core User IntegerID (Entered User) Core User IntegerID (Entered User) FALSE FALSE integer
Entered Date and time when the project was entered FALSE FALSE
Classic User IntegerID (Changed User) Classic User IntegerID (Changed User) FALSE FALSE integer
Core User IntegerID (Changed User) Core User IntegerID (Changed User) FALSE FALSE integer
Changed Date and time when the project was changed the last time FALSE FALSE

Related Items


Build on the Coupa Platform

Our API-based open integration platform lets technology partners and independent software vendors (ISVs) integrate their products with Coupa

The Coupa Core API

Our RESTful API provides robust access to read, edit, or integrate your data with the Coupa platform.

Get Started with the API

General information about using the Coupa API and when you should consider using CSV.

OAuth 2.0 and OIDC

Coupa is deprecating legacy API Keys and requiring the use of OAuth 2.0 / OIDC. Starting with R34, no new API Keys will be issued, and API Keys will no longer be supported with R35.