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 

Resolution

For Scenario 1 & 2

  • Ensure you can test the related Live Data connection (Edit > Save) with Advanced Features enabled. 
  • Ensure you can view the same story from a browser using a Direct connection to the same SAP BW system.

    • If the story works in the browser, create a new Tunnel type connection to simulate the responses for scheduled publications and mobile app viewing (both route through SAP Cloud Connector in the same structure). If the same issue is reproducible using a Tunnel connection, follow the steps below to continue troubleshooting.
    • If the issue does not reproduce with a Direct connection, this is a pure Live BW issue — contact SAP Support using component LOD-ANA-LDC-BW.

For Scenario 3

  • Collect end-to-end trace involving SAC > SCC > ABAP ( See SAP KBA 2746754 - Log and Trace files to troubleshoot scenarios involving SAP BTP > SCC > AS ABAP):
    • 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, follow the procedure in KBA 2280022 - How to collect a HTTP archive (HAR) file (Chrome developer tools network trace) in SAP Analytics Cloud
  • Review all traces:
    1. In the HTTP trace, identify the failed request and the error in the response. Example request URLs:
      => Examples of Request URL:
      1. https://<your SAC URL>/lcs/scc/tunnel/<Connection name>/sap/bw/ina/GetServerInfo
      2. https://<your SAC URL>/lcs/scc/tunnel/<Connection name>/sap(Session-Id)/bw/ina/GetResponse
    2. 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.
      1. 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.
      2. 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.
      3. 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