1. Extend Oracle Sales and Service business objects with document collaboration
  2. Troubleshoot Integration Issues

Troubleshoot Integration Issues

If the OCM document collaboration integration did not work as expected in the Oracle Sales and Service business object, then the following steps can be performed to identify the issue:

If the OCM integration is not working as expected:
  1. If the Documents tab is missing from the Oracle Sales and Service business object, verify that the current user is in the correct Oracle Sales and Service sandbox and that you're creating the business object (in this case opportunities) that has been implemented for this integration.
  2. If you get the following error, make sure that the API Authentication has been configured correctly and that the Web Services are using this connection:
    oracle.binding.expr.ServiceInvocationException: JBO-29000: Unexpected exception caught: 
oracle.adf.model.connection.rest.exception.RestConnectionException, 
msg=JBO-57001: Invocation of service URL used in connection failed with status code 401 Unauthorized.
  3. Make sure that the current user has enterprise access to OCM.
  4. Verify that the user logged into the Oracle Sales and Service application is also the same user logged into OCM.
  5. Review all steps in the documentation above to verify that they have been completed and with the correct values. Use the images given in the steps as they should look identical to what you have configured.
  6. Verify that the OCM server URL is configured correctly in the Web Services as well as the Mashup (not the <OCMServerURL> as seen in the figures).
  7. Verify that the Token URI is configured correctly in the Web Services IDCS OAUTH security (not the <idcsServerURL> as seen in the figures).
  8. Log in as the OCM enterprise integration user and verify that a folder is created under the OCM parent folder with the name of the Oracle Sales and Service business object. If not, then verify that the OCMRootFolderId variable is correct.
  9. Verify that the user was shared to the related OCM folder by selecting Members in the upper right of the OCM UI.
If the OCM embedded UI is still not loading look at the Oracle Sales and Service debug logs:
  1. Make sure you’re in the sandbox that you create for this integration.
  2. Choose Tools and Application Composer from the upper left of the page.
  3. Select Common Setup and then Runtime Messages from the left navigation menu.
  4. Select the Enable Application Script Logging check box.
  5. Create a new Oracle Sales and Service business object with this OCM integration and once created, select the Document tab within the object.
  6. Walk through the part of the integration that is failing (for example, Create New Opportunity).
  7. Go back to the Runtime Messages to see if the logs give you more information about why this integration might have failed.