SAP Knowledge Base Article - Public

3740616 - Shared analytic model across spaces not visible in SAC Story/Analyzer - SAP datasphere

Symptom

  • Analytic model created and deployed in a space and shared to another space is not visible in SAP Analytics Cloud (SAC) when accessing from the shared space via a live data connection.
  • Same behavior will be applied for MS Excel, and other clients, tools, and apps.

Environment

  • SAP Datasphere

Reproducing the Issue

  1. Create and deploy an Analytic Model in space "A"
  2. Share the model to space "B"
  3. In SAC, use the live data connection to the space "B" and try to find/use the shared Analytic Model

Cause

  • Sharing an Analytic Model grants cross-space access to the original object but does not create the model as an entity in the shared (consumption) space. SAC lists models that exist in the selected space; opening the shared model redirects to its source space by design.

Resolution

  1. In the target (consumption) space, create a new Analytic Model using the shared artifact (for example, a shared view) from the source space as input.
  2. Validate and deploy the new Analytic Model in the (consumption) space.
  3. In SAC, access the live data connection to the consumption space; the newly created Analytic Model should now be visible and consumable.

See Also

Keywords

datasphere, sac, live data connection, analytic model, shared model, cross-space sharing, consumption space,  not visible in sac, data builder,  cross space, share , KBA , DS-MD-AM , Analytic Model , LOD-ANA-DES , Story Design & Visualizations , Problem

Product

SAP Datasphere all versions