3334305 - Error "Failed to connection to server: Read timed out" appears in SAP Analytics Cloud (SAC) while running import job to acquire data from OData service exposed from SAP S/4HANA On-Premise system

• Error "Failed to connection to server: Read timed out" appears in SAP Analytics Cloud (SAC) while running import job to acquire data from OData service exposed from SAP S/4HANA On-Premise system
• When trying to create a new model by creating one exact same query based on same OData service connection, it fails with error "<Query Name> has failed to upload because of an error in the plugin service.  "
• The following error message comes from the external data service; status: 500 body: 500 Connection Timed Out

• SAP Analytics Cloud (Enterprise)
• SAP S/4HANA On-Premise

1. Log on to SAC tenant.
2. In one existing model, switch to Data Management.
3. Run one existing job based on Import Data connection to either SAP S/4HANA or OData Service connection pointing to one OData service exposed from SAP S/4HANA. 
   => It takes around 1 hour to run and finally shows error "Failed to connection to server: Read timed out" appears in Status panel.
   
4. Try to create a new model by copying the existing job/query based on same import data connection.
   => It fails with error "<Query name> has failed to upload because of an error in the plugin service.  "

• By capturing OData call inside S/4HANA system with SAP Gateway Tracing Tool as per SAP KBA 2960901 and then running the same OData call with Gateway client (T-code: /IWFND/GW_Client), it fails with ICMETIMEOUT error (500 Connection Time out)  .
  • If there are multiple OData calls captured in Gateway trace due to batching with $Top and $Skip, please run each OData call separately.
  • If ICMETIMEOUT error (500 Connection Time out) doesn't happen when running all of OData calls with  Gateway client (T-code: /IWFND/GW_Client), please refer to SAP KBA 3348855 about same issue/error caused by idle connection timeout in AWS load balancer applied to CF tenants.
• It is also confirmed with T-code: SMICM that the ICM  Time-out for HTTPS port of S/4HANA system is 3600 seconds, which is the reason why the timeout error is shown in SAC after running the import job over 1 hour. 

• Option 1: Increase ICM time out in S/4HANA system
• Option 2 (Recommended):
  • Split the import job into multiple jobs by adding more filter to decrease not only time to execute the OData call inside S/4HANA system but also the volume returned to SAC in each running
  • It is always suggested to test each OData call firstly using GW client (T-code: /IWFND/GW_Client) to ensure that it could be completed before ICM Time out.

• 2569847 - Where can you find SAC user assistance (help) to use, configure, and operate it more effectively?
• Have a question? Ask it here and let our amazing SAP community help! Or reply and share your knowledge!
• 2487011 - What information do I need to provide when opening an incident for SAP Analytics Cloud?
• 2511489 - Troubleshooting performance issues in SAP Analytics Cloud
• Search for SAP Analytics Cloud content using Google or Bing:
  • https://www.google.com/search?q=site%3Ahttps%3A%2F%2Fuserapps.support.sap.com+SAP+Analytics+Cloud
  • https://www.bing.com/search?q=site%3Ahttps%3A%2F%2Fuserapps.support.sap.com+SAP+Analytics+Cloud
  • Note: Add relevant text or warning/error messages to the text search field to filter results.
• SAP Analytics Cloud Connection Guide
• Getting Started with SAP Analytics Cloud Expert Community page
• SAP Analytics Cloud Get More Help and SAP Support
• Need More Help? Contact Support or visit the solution finder today!

Your feedback is important to help us improve our knowledge base.

SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, Time out, Timeout, ICM, ICMETIMEOUT, OData, Schedule, Import, Acquire, load, upload, SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Connection, Sac, Connector, Live, Acquisition, Up, Set, setup, Model, BW, Connect, Story, Tenant, Import, Failed, Using, Working, SAML, SSO, sapanalyticscloud, sap analytical cloud, sap analytical cloud, SAC, sap analyst cloud, connected, failure, stopped, sap analyst cloud, https://hcs.cloud.sap, https://hanacloudservices.cloud.sap, https://cloudanalytics.accounts.ondemand.com, https://hanacloudservices-us.accounts.ondemand.com, https://www.sap.com, https://help.sap.com, predictive analytics (analysis), data analysis (analytics) tools, analytics tools, sap analytics cloud, data literacy, advanced analytics, data democratization, analytics software, real time analytics, self service analytics, advanced data analytics, analytics as a service, analytics cloud / cloud analytics, saas analytics, cloud bi, enterprise planning, cloud data analytics, cloud based analytics, analytics cloud platform, modern analytics, real time analysis, cloud analytics solution(s), what is sap analytics cloud, cloud analytics tools, analytics in the cloud, cloud analytics software epm, business intelligence,  , KBA , LOD-ANA-AQU-ODATA , Acquiring Data into SAC using an ODATA connection , Problem