---
sourceDocument: Australia Asset Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-asset-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Asset Management

ft:clusterId :

    - itam

bundleId :

    - itam

workflow :

    - Technology


---

# Create a Coupa integration profile

# Create a Coupa integration profile {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Create a Coupa integration profile to verify the status of the procurement-scheduled jobs, entitlements, and entitlement import errors created through this profile.

## Before you begin

Role required: sam_admin

Create an OAuth 2.0 connection with Coupa to get the Client ID and Client Secret. For more information, see [OAuth 2.0 Getting Started with Coupa API](https://compass.coupa.com/en-us/products/core-platform/integration-playbooks-and-resources/integration-knowledge-articles/oauth-2.0-getting-started-with-coupa-api). Save the Client ID and Client Secret in a secure location for later use.  
You must set the following scopes while creating an OAuth 2.0 connection with Coupa.

* core.approval.configuration.read
* core.approval.read
* core.approval.write
* core.catalog.read
* core.common.read
* core.contract.read
* core.contract.write
* core.inventory.adjustment.read
* core.inventory.adjustment.write
* core.inventory.asn.read
* core.inventory.common.write
* core.inventory.consumption.read
* core.inventory.consumption.write
* core.inventory.receiving.read
* core.inventory.receiving.write
* core.inventory.return_to_supplier.read
* core.inventory.transfer.read
* core.inventory.transfer.write
* core.invoice.delete
* core.invoice.read
* core.invoice.write
* core.item.read
* core.item.write
* core.legal_entity.read
* core.purchase_order.read
* core.purchase_order.write
* core.requisition.read
* core.requisition.write
* core.sourcing.pending_supplier.read
* core.sourcing.pending_supplier.write
* core.sourcing.read
* core.sourcing.response.award.write
* core.sourcing.response.read
* core.sourcing.response.write
* core.sourcing.write
* core.supplier.read
* core.supplier.write
* core.user.read
* core.user.write

{#create-coupa-int-profile__ul_hqz_r1y_2xb}  
Note:  
If these scopes aren't associated with the Client ID and Client Secret, the OAuth token flow fails on ServiceNow.

## Procedure

1. Navigate to Software Asset WorkspaceLicense operationsPurchasingProcurement integrations.
2. Select New.
3. On the form, fill in the fields.  
   {#create-coupa-int-profile__table_oxb_lg4_pwb__entry__2}

   | Field | Description |
   |-|-|
   | Display name | Name of the procurement integration profile. For example, <kbd class="ph userinput">Coupa integration</kbd>. |
   | Connection \& Credentials | Connection and credential alias for Coupa. This field gets automatically populated to sn_coupa_spoke.Coupa_OAuth. |
   | Profile type | Type of integration profile. Select Coupa integration. |
   | Status | Status of the integration profile. * If you haven't published the integration profile, this field is automatically set to Draft. * If you've already published the integration profile, this field is automatically set to Published. {#create-coupa-int-profile__ul_mhy_4m4_pwb} |
   | Active | This field is visible and set to true only when the integration profile is published. If you set this field to false, the associated requisitions with this integration profile aren't created and tracked. |
   [Table 1. Create New Procurement Integration Profile]

   {#create-coupa-int-profile__table_oxb_lg4_pwb}
4. Select Save.
5. Select the Preview icon ![Preview icon]() next to the Connection \& Credentials field.  
   You get redirected to the Connection \& Credential Aliases form.
6. Select Create New Connection \& Credential in the Related Links section to create connection credential.
7. In the dialog box, fill in the fields.  
   {#create-coupa-int-profile__table_tg3_2sh_pwb__entry__2}

   | Field | Description |
   |-|-|
   | Name (Connection) | Name to identify the connection uniquely. For example, <kbd class="ph userinput">Coupa OAuth connnection</kbd>. |
   | Connection URL | URL to make a connection to Coupa. Use the https://\<coupa-instance-url\> format. * For customer instances, use the https://{organization_name}.coupahost.com format. * For partner and demo instances, use the https://{organization_name}.coupacloud.com format. {#create-coupa-int-profile__ul_njy_bvh_5wb} |
   | Name (Credential) | Name to identify the credential uniquely. For example, <kbd class="ph userinput">Coupa OAuth credential</kbd>. |
   | Token URL | URL used to generate OAuth token. Use the https://\<coupa-instance-url\>/oauth2/token format. |
   | OAuth Client ID | Identifier (Client ID) generated in Coupa. |
   | OAuth Client Secret | Secret (Client Secret) generated in Coupa. |
   [Table 2. Create Connection and Credential]

   {#create-coupa-int-profile__table_tg3_2sh_pwb}
8. Select Create and Get OAuth Token.  
   Your ServiceNow instance creates an OAuth for Coupa and then automatically returns you to the Integration Profile form.
9. **Optional:** Create a child alias that can uniquely identify the connection and credentials for this integration profile.  
   The first Coupa integration profile that you create uses the default (parent) connection and credential alias for Coupa. Each additional Coupa integration profile that you create needs a unique child alias that helps differentiate the connection and credentials between each integration profile.
   1. On the Connection \& Credential Aliases form, select the link under Child Aliases \> Parentalias=\*\*\* to add child aliases.
   2. Select New.
   3. Enter a name for the child alias in the Name field.
   4. Right-click the form header and then select Save.
   5. After the form reloads, select the Create New Connection \& Credential related link.
   6. Repeat steps 7 and 8.
   7. In the Connection \& Credential field of the Integration Profile form, select the lookup icon to locate and select the child alias that you created.  
      Selecting the child alias associates the alias with the integration profile. Your ServiceNow instance uses this alias to identify the connection and credentials for this integration profile.
   {#create-coupa-int-profile__substeps_fn2_xj3_5wb}
10. Select Publish.

## Result

After you publish the integration profile, the scheduled job ITAM - Sync Coupa purchase orders runs daily and fetches the status of the already created requisitions.  
Note:  
If you haven't created any requisition, the scheduled job doesn't run.

You can view this information by clicking the Procurement Integration Jobs tab.

## What to do next

Verify if the scheduled job ITAM - Sync Coupa purchase orders has run successfully by selecting the Integration Scheduled Job Results tab. If the job has failed, you can view the list of errors by following these steps:

1. On the Procurement integration profile form, select the Procurement Integration Job Log related list.
2. Open the job log record where the displayed status shows as failed.
3. Select the related list Asset Job Log Details to find out the reason for the job failure.
{#create-coupa-int-profile__ol_vtq_rzr_2xb}

Create software requisitions directly on Coupa through the ServiceNow
Procurement application to purchase software.

If you want to delete the Coupa integration profile, see [Deleting an external procurement application integration profile](https://servicenow-prod.fluidtopics.net/95fBjRfEPK8tYISv3Vwd2w "If you want to stop using an external procurement application for creating software requisitions through Software Asset Management, you can delete the integration profile.").

*[\>]: and then