1. Using the SAP Ariba Adapter with Oracle Integration 3
  2. Troubleshoot the SAP Ariba Adapter
  3. SAP Ariba Adapter Known Issues and Solutions

SAP Ariba Adapter Known Issues and Solutions

Note the following SAP Ariba Adapter issues and solutions.

Integration Execution Takes More than 310 Seconds

The following error occurs when you execute an integration that takes more than 310 seconds.
Timeout has occurred after 310 seconds.oracle.fabric.common.FabricInvocationException:oracle.soa.api.invocation.InvocationException: 
com.bea.wli.sb.transports.client.SBTimeoutException: Timeout has occurred after 310 seconds.

Solution: Select a smaller date range (that is, the from and to-date values when creating the integration).

ZIP File Extraction During the Export Process

The following error may occur while extracting a ZIP file during the export process.
Error sending bytes: Error while extracting contents from ZIP. No Entries found,
 it is either invalid or corrupt. :Application Error.”

Solution: Re-execute the integration after waiting for some time or update Oracle Integration to the latest release.

Task Name Does Not Match with the Integration ToolKit Name

The following SAP Ariba sandbox error occurs when the task name does not match with the integration toolkit name.

Error sending bytes: Error occurred while downloading from Ariba: Throwable 
caught: Unexpected Error: Can't coerce variant [Variant vrealm_2068 "vrealm_2068" 20680 
realm 11 ] in Realm [Realm id=2068 name=amgen-T label="Amgen - TEST" state=enabled 
variant=[Variant vrealm_2068 "vrealm_2068" 20680 realm 11 ] baseDomainVariant=vsap 
version=5 timeStateChanged=Tue Dec 06 00:00:00 PST 2016] to a different Realm [Realm id=2121 
name=bconedemoinabox label="Bristlecone, Inc." state=enabled variant=[Variant vrealm_2121 
"vrealm_2121" 21210 realm 12 ] baseDomainVariant=vsap version=7 timeStateChanged=Wed Jan 25 
00:00:00 PST 2017] || No stack available. :Application Error.

Solution: Ensure that the task name and integration toolkit name are the same.

  1. Open the buyer/sourcing data dictionary based upon the Ariba solution selection. See Prerequisites for Creating a Connection.
  2. Based upon your service type selection (that is, transactional or master type task), you can navigate in the data dictionary Excel workbook to edit the task name.
  3. For the transactional type task:
    1. Navigate to the Indexes worksheet in the data dictionary. Alternatively, click Ctrl + Left Click or scroll to the last worksheet, which is the Indexes worksheet.
    2. Search for the task name on the Indexes worksheet.
    3. Select the search result of the respective task and edit the task name under the task name column in the worksheet as per the integration toolkit name.
  4. For the master type task:
    1. Search CombinedDataPull (for the buyer) on the Indexes worksheet and double-click CombinedDataPull.
    2. Search for the task name on CombinedDataPull, select the respective task, and edit the task name as per the integration toolkit name.

    Similarly:

    1. Search Import Master Data Batch Pull (for sourcing) on the Indexes worksheet and double-click Import Master Data Batch Pull.
    2. Search for the task name on the Import Master Data Batch Pull, select the respective task, and edit the task name as per the Integration Toolkit name.
  5. Check the integration toolkit name.
    1. Log in to Ariba Spent Management.
    2. Navigate to Home > Administration (for buyer)/CoreAdministration (for sourcing) > Data Import/Export.
    3. Search for the task name in the search filters and click the search result.

      You can see the integration toolkit names.

    4. Use this name as the task name in the data dictionary.

      Note:

      In case of more than one integration toolKit name, use any one of them as the task name.
  6. Update the connection with the updated data dictionary.
  7. Review the new task name:
    1. Open the created integration.
    2. Open the SAP Ariba Adapter.
    3. On the Operations page, the new task name appears.