SAP Analytics Cloud Lifecycle Management Best Practices – Part 2:
Effective lifecycle management in SAP Analytics Cloud (SAC) depends on a comprehensive understanding of all its components. In the first part of this blog series, we discussed the importance of deciding on the number of tenants an organization should implement. In this second part, we will focus on Objects. Once you understand the role of Objects, moving data between systems will be a simple task. Before we dive into exporting and importing data between systems, it is important to have a basic understanding of objects and how to manage them effectively to avoid issues when attempting to update objects between multiple tenants.
What is an Object ID?
In simple terms, an Object ID is an alphanumeric code that is assigned to each object that is held in SAP Analytics Cloud (SAC). Objects are physical components of SAC including, but not limited to, models, stories, analytical applications, folders, predictive scenarios, and points of interest. Refer to the solution screenshot below for reference.
Each object has a unique ID that can be used to transfer between tenants to update the data of the environments.
Since all objects have unique IDs, it’s critical to consider that there is a certain level of risk of overwriting data when updates are attempted within the same environment. Hence why it’s often recommended to have multiple tenants to effectively manage changes to objects between environments.
When it comes to importing and exporting Objects, users have several options:
Option 1: File System (manual deployment) – Transport the content between a mixture of SAP and non-SAP data centers (between NEO and CF). By leveraging this tool, users may export or import content between systems using a .tgz file as well as share settings. However, it’s important to note that there is a limitation on the size of the file to be exported.
Option 2: Content Network – Access to sample content files and business scenarios in the cloud. With tool enables all of the processes to occur in the background, eliminating all manual labor.
By now, I hope you have a better understanding of how Objects can be used to transfer data between tenants. To learn more about lifecycle management in SAP Analytics Cloud, be sure to review the first part of this blog series on determining the number of tenants required for your organization and stay tuned for the upcoming third part of this series around importing objects to a .tgz file. Looking for in-depth training for you or your team? Discover all of our learning options curated and delivered by product experts to help you maximize the return on your SAP Analytics Cloud product investment.