3348855 - Import jobs based to SAP S/4 Hana system failed after running one hour with error "Connection to service failed: Read timed out" in SAP Analytics Cloud (SAC)

Symptom

Import jobs based to SAP S/4 Hana system failed after running one hour with error "Connection to service failed: Read timed out (local port *** to address ***, remote port *** to address ***)" in SAP Analytics Cloud (SAC)
The ljs_trace.log file from the cloud connector will have an entry similar to:
2023-06-20 10:01:23,513 +0000#DEBUG#com.sap.core.connectivity.tunnel.core.Tunnel#tunnel-client-12-8#0xe1234a1#Unsubscribed connection with id: 0xe1234a1
2023-06-20 10:01:36,513 +0000#DEBUG#com.sap.core.connectivity.tunnel.client.sso.CallerPrincipalProviderImpl#tunnel-client-12-8#0xe1234a1#Could not unassign principal. No principal is found for connectionId: '0xe3702c70'

Environment

SAP Analytics Cloud, Enterprise Edition 2023.8.8
CF tenant running non-SAP data centers

Reproducing the Issue

Log on to SAC tenant running non-SAP data centers.
Create one import job/query with a large number of columns based on Import Data connection to SAP S/4HANA.
Run the import job/query.
=> The job will faill after runing 1 hour with error "Connection to service failed: Read timed out (local port *** to address ***, remote port *** to address ***)"

Cause

By default, SAC retrieves data from OData service in batches of:

S/4 HANA connection – 50K
IBP connection – 50K
Generic OData – 1K

When a single OData request takes longer than 350 seconds to process on the S/4 Hana side (batch = 50K), then it times out and the entire import jobs fails because:

All network requests from SAC tenants running in CF are routed by the AWS Network Load Balancer.
If there is no network request in over 350s, the Network Load Balancer closes the connection.
Documentation for reference: https://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html#connection-idle-timeout

Resolution

Optimize the S/4 query by adding filters or removing columns to allow the OData query to run in under 350 seconds.
To test this, use the gateway client (Transaction code /IWFND/GW_CLIENT) to run the OData query and see if it completes under the time limit.
=> Note: SAC will append $top=50000 to the request for each batch, so please make sure to include this property in the query.
Documentation on using the Gateway client can be found here.

Keywords

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-DES , Story Design & Visualizations , LOD-ANA-AQU , Import Data Connections (Acquiring Data) , Problem

Product

SAP Analytics Cloud 1.0