Table of Contents

Search

  1. Preface
  2. Connectors and connections
  3. Connection configuration
  4. Connection properties
  5. Swagger file generation for REST V2 connections

Connections

Connections

Coupa V2 connection properties

Coupa V2 connection properties

When you create a Coupa V2 connection, you must configure the connection properties.
The following table describes the Coupa V2 connection properties:
Property
Description
Runtime Environment
The name of the runtime environment where you want to run the tasks.
Specify a Secure Agent, Hosted Agent, or serverless runtime environment.
Authentication
Select
Coupa V2
.
Base Url
Base URL to connect to Coupa API. Specify the base URL in the following format:
https://{instance_name}.coupahost.com/
For example, https://companyname.coupahost.com/
Authentication Type
Type of authentication for the Coupa V2 connection.
You can select the API Key authetication or OAuth 2.0 authentication.
Informatica recommends you to use OAuth 2.0 authentication to connect to Coupa.
COUPA API KEY
Required for API key authentication.
A unique API key to connect to the Coupa instance.
For more information about creating an Coupa API key, see the Coupa documentation.
Client ID
Required for OAuth 2.0 authentication.
The Coupa client ID required to generate a valid access token.
Specify the Coupa identifier as the client ID.
Client Secret
Required for OAuth 2.0 authentication.
The Coupa client secret required to generate a valid access token.
Specify the Coupa secret as the client secret.
Scope
Required for OAuth 2.0 authentication.
The scope used to authorize access to Coupa.
Enter the scope defined for the user in Coupa. To enter multiple scopes, separate each scope with a space.
Custom Field Config
Specify custom fields for Coupa objects.
Specify the custom fields in Coupa using the following format, where FieldName is value of the custom field name in Coupa, FieldType is the type of custom field, and IsAPIGlobalNamespace determines whether a custom field appears under root tag or custom-field tag in the
Field Mapping tab
:
Object1=FieldName1,FieldType,DataType, IsAPIGlobalNamespace;\
FieldName2,FieldType,DataType, IsAPIGlobalNamespace;\
FieldName3,FieldType,DataType,IsAPIGlobalNamespace
Object2=FieldName1,FieldType,DataType, IsAPIGlobalNamespace;\
FieldName2,FieldType,DataType, IsAPIGlobalNamespace
Object3=FieldName1,FieldType,DataType,IsAPIGlobalNamespace;\
FieldName2,FieldType,DataType,IsAPIGlobalNamespace;\
FieldName3,FieldType,DataType,IsAPIGlobalNamespace
Coupa V2 Connector supports only simple custom fields.
For example:
user-summary=custom_field1,Simple,String,true;\
custom_field2,Simple,String, false
requisition-header=requisition_cf1,Simple,String,true;\
requisition_cf2,Simple,Integer,false;\
requisition_cf3,Simple,Integer
user=user_customfield1,Simple,String,false;\
user_customfield_2,Simple,String,true
The Secure agent replaces underscore in the custom field name with hyphen and displays the custom field name in the
Field Mapping
tab.

0 COMMENTS

We’d like to hear from you!