| Status | Approved |
| Owner | |
| Stakeholders | |
| LeanIX Link | SAP Analytics Cloud - SyWay |
Introduction
SAP Analytics Cloud (SAC) is the presentation tool for SAP reporting.
It is also the tool used for planning
Purpose
The purpose of this document is to understand the architecture required to support the implementationThe SAP Analytics and Reporting Approach explains what will be implemented and the SAP Analytics and Reporting Standards details how it will be implemented.
This document explains the landscape and integration of the solution
Scope & Objectives
The existing version of SAC being used by HR and BW will be deprecated
Certain SaaS applications have an embedded version of SAC
- SuccessFactors (used extensively as a single instance and security is natively controlled)
- Asset Performance Management (not to be used as 3 instances and offers no benefit to the enterprise version discussed here)
Non-Functional Requirements
| Requirement Identifier | Requirement Description |
|---|---|
Terminology
- SAP Business Content (BCT): Predefined solution provided by SAP for a functional area
- Instance: An entity refers to the entire system including the software and all technical components (DB, application server etc.). E.g., SAC Production.
- Environment/Tier: Refers to systems that are used for the different stages of the project lifecycle. Each environment serves a distinct purpose and has a dedicated instance to ensure stability and integrity. E.g., Development, QAS.
- Landscape: Refers to all the environment for an application or entire project. E.g., S/4HANA landscape, SyWay landscape.
- CUI: CUI and export controlled data are both highly sensitive.
- CMMC 2: Second iteration of the Cybersecurity Maturity Model Certification
- SaaS Deployment Model: Subscription where you pay for the service vs Consumption where you pay for the usage
Application Architecture
Architectural Decisions and Requirements
Below Table provides the details of the architectural decisions made based on the rationale.
| Architectural Decision | Description | Rationale |
|---|---|---|
| SSL and SNC will be configured for SAC to encrypt web and RFC traffic | Based on SyWay implementation approach, all data in transit must be encrypted. | Security is vital |
| Configure SSO for SAC | As part of SyWay project, a common authentication mechanism (e.g., SAML) will be adopted | For ease of access and unified user experience. |
| Seamless planning | To enable seamless planning, Both DSP and SAC must be deployed in the same data centre and hosted by the same hyperscaler | SAP limitation and meeting Syensqo preferences |
| SAP Business Content (BCT) | Start by leveraging the SAP BCT to deliver reports with less effort | Faster implementation |
| Landscape | 3 tier landscape | SAC is a subscription model so we have to pay per instance |
Application Architecture Design
Customer Number | 3008440 |
|---|---|
Cloud Provider | MS Azure |
Cloud Region | Netherlands |
Service model | Software as a Service |
Licence | SAP Cloud Platform Enterprise Agreement (CPEA) |
Deployment model | We are using the Public model |
Database | HANA Cloud |
Application Architecture Components
SAC is the presentation tool for SAP solutions as depicted below:
| SAC Component | Description |
|---|---|
| Story | Formatted reporting |
| Data Analyser | Self service (slice and dice) reporting tool |
| Excel | SAP Analytics Cloud, add-in for Microsoft Excel |
| Planning | Planning functionality with the ability to retract plan data back into S/4 |
| Catalogue | Easy access to published stories |
SAP Datasphere (DSP)
DSP is the cloud data warehouse used to extract transform and load data from SAP systems
SAP Analytics Cloud and SAP Datasphere tenants can only be linked in a 1:1 relationship. One SAP Analytics Cloud tenant can be linked with only one Datasphere tenant.
It only supports a CORS INA connection
When using the SAC – Datasphere live connection, SAC currently has the following product limitations:
Analytics
- Custom Shapes for Geo Maps are not supported
- Version based variance features are not supported on SAP Datasphere data.
- Version Mapping is not supported for SAP Datasphere data.
- Blending is not supported.
- Linked Dimension is only supported for SAP Datasphere models from the same Space. It is not supported across Spaces.
- R-Visualizations are not supported.
- Comment Widgets are not supported
- Copy Widgets between stories is not supported
- Import Pages from Stories that contain Datasphere models is not supported
Planning
SAC Planning data can now be stored in Datasphere with seamless planning. However, seamless planning still requires the import of data into the SAC model and is not based on the SAP Datasphere live connection.
OData
This is required for retraction of data to S/4
With seamless planning the data resides in DSP, but retraction only works from SAC to S/4, hence the data needs to be loaded into SAC first.
S/4HANA
ADFS
Application Security
Classification
Authentication
Authorisation
Communication Security
Data Security
Other Controls
System Landscape
Development Environment
Project Test Environment
Quality Environment
Production Environment
Operation Architecture
Change and Configuration Management
Transport Management
Release Management
Monitoring
Application Monitoring
System Monitoring
Sizing
High Availability
Disaster Recovery
Backup/Restore
Maintenance Plan
Service Introduction
Application Category
Support Team
Skill required
Checklist
Exceptions
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||