Troubleshoot SAP Concur Adapter Connection Issues
The following issues can occur when using the SAP Concur Adapter. Review the following table to identify solutions for these issues.
| Issue | Solution |
|---|---|
| Why is the Payment Batch API not visible in the Adapter Endpoint Configuration Wizard? | You may have selected Professional Edition on the Connections page instead of Standard edition and provided credentials for the Standard Edition, or vice versa. Identify your SAP Concur edition and provide the correct credentials. See Identify the SAP Concur Application Edition. Also, check whether the Payment Batch API is enabled. You must enable the permissions for the Extract API and Payment Batch API for the registered application as a prerequisite to configuring the SAP Concur Adapter. See Enable the Permissions for the Extract API and Payment Batch API for the Registered Application. |
| Why am I unable to see the Payment Batch API after changing the edition to use Standard Edition instead of Professional Edition on the Connections page? |
|
| Why is the SubmitJobRequest operation for the Extract API not visible in the Adapter Endpoint Configuration Wizard? | You may have selected Standard Edition on the Connection page and provided credentials for the Professional Edition. Identify your SAP Concur application edition and provide the correct credentials. See Identify the SAP Concur Application Edition. |
| Why is the Extract API/Payment Batch API not visible in the Adapter Endpoint Configuration Wizard while configuring the SAP Concur Adapter connection for the Standard Edition? | You need to enable the Extract API/Payment Batch API in the SAP Concur application. See Enable the Permissions for the Extract API and Payment Batch API for the Registered Application. |
Why does the SAP Concur Adapter show the error Unable to configure the operations once you select the Extract API in the SAP Concur Adapter?
|
You need to enable the Extract API/ Payment Batch API in the SAP Concur application. See Enable the Permissions for the Extract API and Payment Batch API for the Registered Application. |
| Why am I unable to see the option Register Partner Application in the SAP Concur portal? I need to complete the necessary prerequisites for establishing a connection with the SAP Concur Adapter. | Ensure that you are logged in as an SAP Concur administrator to complete the necessary prerequisites for establishing a connection with the SAP Concur Adapter. If you are unable to see options such as Register Partner Application after logging in as an SAP Concur administrator, this may be due to privilege issues. In such cases, it is recommended that you contact the SAP Concur support team for further assistance and troubleshooting. |
| Do I have to enter the client ID and client secret for the Concur Resource Owner Password Credentials Policy? |
The Resource Owner Password Credentials security policy requires the client ID, client secret, user name, and password whereas the Concur Resource Owner Password Credentials Policy (deprecated) required the consumer key, consumer secret, user name, and password. SAP Concur has deprecated the Concur Resource Owner Password Credentials Policy. However, if you import the older IAR file into an instance with new release details, you may see Client Id and Client Secret fields. You don't need to enter details for these fields and can continue defining the connection with the necessary parameters described in Create a Connection. Oracle Integration is working on this known issue and corrections will be reflected in an upcoming release. |
at the far right for the respective connection, and select