Error When Discovering REST Services or SOAP Services through the Oracle ERP Cloud Adapter

You can receive the following errors when trying to discover REST services or SOAP services through the Oracle ERP Cloud Adapter.

REST Services Error

If you receive the following error when trying to discover REST services, verify that you also receive the error outside of Oracle Integration by running the curl command described in the Goal section of Doc ID 2576807.1 at My Oracle Support (MOS). If the error occurs, follow the steps in this MOS document to resolve this issue.

An error occurred while loading the application catalog, ERROR: Exception while parsing the REST 
application catalog fscmRestApp. Error accessing the URL: https://hostname.oraclecloud.com:443/fscmRestApi/
resources/latest/describe?metadataMode=minimal - received HTTP Response Code: 400; Reason Bad Request. This 
might be because REST APIs are not enabled on the application. Please contact your Application Administrator.

SOAP Services Error

If you receive the following error when trying to discover SOAP services, you must verify the entries in your service catalog.
Failed to located the service endpoint for the service {http://xmlns.oracle.com/apps/financials
/commonModules/shared/model/erpIntegrationService/}ErpIntegrationService. Please contact the administrator..
Integration TEST_SUBMIT_ESS (1.0) cannot be activated.{0}. ; Failed to located the service endpoint for 
the service {http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/}
ErpIntegrationService
For example, perform the following steps:
  1. Invoke ServiceCatalog from the SOAP UI client with the following payload:
    client https://elor.fa.us2.oraclecloud.com/fndAppCoreServices/ServiceCatalogService?wsdl
    The payload should look as follows:
    <soapenv:Body>
      <typ:getAllServiceEndPoints/>
    </soapenv:Body>
  2. Add authentication and time stamp headers to your payload.
  3. For any missing services, contact Oracle Fusion Applications Support to have those services added to the service catalog.
  4. Reactivate your integration.