SAP Knowledge Base Article - Preview

3174537 - ITK retry mechanism for reloading the failed data

Symptom

Integration Toolkit (ITK) is single threaded so it can handle only one request at a time. With an import task already running, you cannot invoke a new import for same task.
If a scenario occurs where an outbound task triggers at the Oracle end to start the import task in SAP Ariba while an import task is already running in SAP Ariba, the task fails. Checking the failed task in the log shows:

Ariba data pull event ‘CombinedDataPull’ was busy at that time and service is not available.

Unavailable to service Event CombinedDataPull: server busy. || No stack available. "Data transfer **incomplete** due to temporary failure on the remote service.

Also, the error message in the logs reads: data transfer temporary failure, will retry request at the next invocation.

The data does not process in the next run and we have to manually run the jobs during these scenarios. But the error logs shows, "will retry request at next invocation". Can you please let us know why the data is not picked in next ITK invocation?


Read more...

Product

SAP Ariba Procurement, cloud edition all versions

Keywords

ITK, integrated toolkit, reload, task, failed , KBA , BNS-ARI-CP-CORE , Core Administration , BNS-ARI-CM , Catalog Management , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.