SAP Knowledge Base Article - Public

2987799 - [Best Practice] How to troubleshoot advanced features based on Live Data Connection to SAP BW in SAP Analytics Cloud (SAC)

Symptom

Environment

  • SAP Analytics Cloud (Enterprise) 2020.14

Resolution

For Scenario 1 & 2

  • Please always ensure that you can test the related Live Data connection (Edit > Save) with Advanced Features enabled.
    => If you observe any error when saving the Live Data connection with with Advanced Features enabled, please go through all required steps:
  • Please always ensure that you can view same story from browser based on same Live Data connection to SAP BW using a Direct connection.
    => If it works in browser, then you can try to create a new Tunnel type connection to simulate the responses when creating scheduled publications to view stories in mobile app as they are working in same structure through SAP Cloud Connector (SCC).  If same issue could be reproduced using Tunnel type connection, you can follow the steps as below to continue your troubleshooting.
    => Otherwise, it would be pure Live BW issue and please reach SAP Support using component LOD-ANA-LDC-BW.

For Scenario 3

  • Collect end-to-end trace involving SAC > SCC > ABAP ( See SAP KBA 2746754):
    • SAP Cloud Connector traces
      • Cloud Connector Loggers (ljs_trace.log) in Debug level 
      • Payload Trace (traffic_trace_<account id>_on_<landscapehost>.trc)
    • ICM traces
    • HTTP trace
      • For SAC, it is better to follow procedure described in SAP KBA 2280022 - How to collect a HTTP archive (HAR) file (Chrome developer tools network trace) in SAP Analytics Cloud
  • After that, you can start your troubleshooting by going through all of traces:
    • Firstly, identity in HTTP trace failed request and also the error in response.
      => Examples of Request URL:
      • https://<your SAC URL>/lcs/scc/tunnel/<Connection name>/sap/bw/ina/GetServerInfo
      • https://<your SAC URL>/lcs/scc/tunnel/<Connection name>/sap(Session-Id)/bw/ina/GetResponse
    • Go to SCC traces or ICM traces and search with the Session-Id to check if you can find same error in either of them around same time.
      => Note: as the Session-Id may be divided into multiple lines in SCC Payload Trace or truncated in ICM traces, it is suggested to search using several characters (less than 10) only in the beginning of Session-Id.
      • If same error for Session-Id observed in HTTP trace can be found in ICM traces, please reach your ICM expert to look into the ICM trace or reach SAP Support using component BC-CST-IC.
      • If same error for Session-Id observed in HTTP trace can be found in SCC Traces only but not ICM traces, please reach your SCC expert or reach SAP Support using component BC-MID-SCC.
      • If same error for Session-Id observed in HTTP trace can be found in neither SCC traces nor ICM traces, please reach SAP Support using component LOD-ANA-LDC-HAN.

See Also

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

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 , KBA , LOD-ANA-LDC-HAN , SAC Live Data Connection HANA , LOD-ANA-MOB , SAC Mobile , How To

Product

SAP Analytics Cloud 1.0