SAP Knowledge Base Article - Public

3307074 - Guidelines for addressing SAP Datasphere issues within SAP Analytics Cloud

Symptom

This KBA provides guidance on:

  • Necesssary information to report a case in SAP Datasphere.
  • How to breakdown SAP Datasphere (DS) issues in SAP Analytics Cloud.
  • How to find the correct SAP product area (component) to report product issues.

    Environment

    • SAP Datasphere
    • SAP Analytics Cloud

    Resolution

    To improve the processing time and better support experience, please go through the steps and provide all necessary information as mentioned below:

    1. The issue occurs when running a Story in SAP Analytics Cloud (SAC), execute the underlying View or Analytic Model directly in SAP Datasphere (DS).

      • If the issue is reproducible in SAP Datasphere, create a support ticket for SAP Datasphere.

      • If the issue cannot be reproduced in SAP Datasphere due to constraints, try reproducing it in AfO (Analysis for Office). If the issue is reproducible in AfO, create a case for SAP Datasphere (refer to section A under resolution).

      • If the issue is not reproducible in SAP Datasphere or AfO, but only reproducible in SAC, then create a support case for SAC (refer to section A under resolution).

    2. Due to complexity of the scenario, it is not possible to reproduce the issue directly in SAP Datasphere.

      • In this case, open support case for SAC after following section A.

    1. When opening a case for SAP Datasphere or SAP Analytics Cloud, provide the following information:
      • Provide the information from the step 1 and 2.
      • If the story contains multiple tables or widgets, remove them until the one remains with the issue or create a copy of the story with only one widget.
      • Attach step-by-step documentation to reproduce the issue.
      • Create DS support user (KBA 2891554) and enable the support user creation for SAC (KBA 3200458).
      • DS and SAC tenant URL.
      • Provide the technical name of the impacted objects such as space, table/view, direct URL to story.
      • Record network trace and attach the HAR. file (see KBA 3405253).
      • Provide us the connection type between DS and SAC.
        • If it is live data connection, it is recommended to check the KBA 2832606)
        • If it is oData connection, it is recommended to check here, before opening a case)
      • If there is a performance issue, run SAC performance analysis tool as mentioned here.
      • If there is a performance issue, generate PlanViz Trace and attach the file to the case.

       

      See Also

      Keywords

      necessary information, guideline, troubleshooting, cloud, live connection, story , KBA , DS-MD , Modeling (Data Builder) , LOD-ANA-DES , Story Design & Visualizations , DS-BB , Business Builder , How To

      Product

      SAP Analytics Cloud all versions ; SAP Datasphere all versions