SAP Architecture Framework

Data Architecture
Rahul Padgaonkar
October, 2021
Unit Objectives

This unit outlines…

The unit discusses the Core Artifacts in relation to SAP Architecture concerning Data, i.e.
Data Architecture

After completing this unit, you will be able to…

 Understand the SAP Data Architecture Objectives
 The Core Artifacts in Data Architecture
 Understand the relationship between Business Architecture, Data Architecture, Application
Architecture and Technology Architecture

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 2

Sections

Contextualize – Main Actors in Data Architecture & Drivers in Data Architecture

Construct– Planning Data Architecture and Deliverables

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 3

Section 1: Contextualize
Main actors in Data Architecture & drivers in Data Architecture
Contextualize
What is Data Architecture

Describes and visualizes the governance,

Application
maintenance , distribution and storage of Data
Architecture
 Data Architecture describes how data is
maintained and governed by the business, i.e. how
the organization defines and manages its data as
an asset Business Technology
Architecture Architecture

Data
Architecture

SAP Data Architecture is not concerned with data modeling, database design or physical data
storage - this is covered in Solution Architecture
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 5
Contextualize
Data Architecture Objectives

Objectives
 Provide a comprehensive set of artifacts with relevant attributes of all data and information entities that exist or are
planned in the business environment.
 Based on the gaps between the current and future state data and information entities, help to develop a roadmap
outlining how the major additions, changes and retirements to data and information will be achieved

Benefits
 Having a clear and transparent plan for all data and information that is driven by and aligned to the business and IT
strategies.
 Ensuring that all data and information can be defined, managed and governed, with clear ownership by the
business.
 Realize cost savings through the consolidation and retirement of redundant data and information, reducing
unnecessary integration, and ensuring a „single version of the truth“ for data and information across the business.
 Improved SAP Architecture efficiency, delivering higher value to SAP Solution design and implementation
 Improved SAP Solution Portfolio Management process
 Enable Solution Architects to better design the data model change

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 6

Contextualize
Stakeholders in Data Architecture

Role Description
Business Unit  Define the rules and ownership of the organizations data
Business
Representative
Stakeholders

Data Steward  Play key roles in the governance of data, i.e. safeguard
Data Data Owner consistence and coherence of data in the organization
Stakeholders

Database Administrator  Support the technical aspects of data within the

Application Data Security specialist organization.
Stakeholders

Business Process Owner  Key consumer and producer of data

Technology
Stakeholders

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 7

What is Data
How information is constructed into data within the system

Meta Data Object Master Data Object + Activity + Variables = Transaction

Equipment Butter Date & Time

machine
Attribute Value Materiel Consumed
Vehicle
Attribute Value
Repair
Brand Char (Process Spare parts applied
Brand SPX Step)
Attribute Value
Type Char Downtime registered
Type
Brand HTC
D AF
Year Date Etc…
Year
Type 1981
TD-1
Meta Data Object
Year
H 1985

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 8

Data Equations
Origins of Data Flows and Data Classification

Activities + Variables + Master Data = Transaction Data

(Process Execution) (Operational)

Transaction Data + Measure / Norms = Performance Data

(Process Monitoring & Business Management) (Operational & Tactical)

(Strategic Management) (Strategic)

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 9

Be aware of different Data Types!

External Data Master Data Transactional Data Aggregated Management Data

Products & Services Market Surveys

Business Plans
Addresses, Areas
Customer Transactions
Customers
Asset Management Plan
Projects Events
Consents
Operational Assets Jobs & Schedules
Environmental data
Network model Volume measures
Policies & Procedures
External regulation Quality plan
Quality samples
Non-operational assets
Asset transactions
Suppliers Financial Data

Purchased Products & Supply transactions

Demand forecast Services
Stock Non-financial Performance
Stores Data

External People People transactions

Organisations Statutory reporting
Organisation Structure

= Many connections
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 10
Key Requirements
Data Architecture

In data architecture context, key requirements refer to the quality

characteristics of data and also include constraints

Data Quality as defined by many data integration vendors generally

include the following Data
 Timeliness – How timely is the availability of data Quality
 Accuracy – How accurate is the data created
 Relevance – How relevant it is to the current business processes
 Reliability – How reliable is the data
 Cleanliness – How clean is the data and its conformance to data standards

Data constraints might include

Application
 Accessibility – How easy it is to access and obtain data Interface
 Interpretability – How well is the meta data managed and is it easy to interpret the
data via programmatic means Enabling Application Design
Technology Constraints Considerations
 Data Skills – Availability of data and information skills within the enterprise
 Data Standards – Data related regulations that need to be conformed to
Development
Skills

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 11

Section 2: Construct
Core Artifact in Data Architecture
Core Artifacts
Data Architecture
Architecture Practice
Architecture
Requirements Requirements Stakeholder Initiative Transformation
principle
Catalog Map Map Goals Map Roadmap
catalog

Business Data Application Technology

SW Comp
Metadata Application
Strategy Map Deployment
Catalog Catalog
Model

Application
Balanced Data Process Instance
Architecture
Scorecard Matrix Strategy
Diagram
Capability
Map

Process Map

Business System
Footprint Landscape
Diagram Model

Data Interface
Organization
Distribution Catalog
Diagram
Diagram

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 13

Data Architecture core artifacts
Description and rationale

Data Distribution
Metadata Catalog Data Process Matrix
Diagram

Listed representation describing Matrix representation of (Master) Graphical Representation of data

the (master) data entities within the data entities cross referenced to entities, and the relationships
architecture, i.e. data describing business process entities. between the data entities and
data (entities).  The objective is to have a clear applications.
 The objective of the Catalog is to overview which (master) data entities  The Data Distribution Diagram shows
ensure that all data is coherently and are processed per business process the Data Lifecycle (where data is
consistently defined, so it can be to be able to assess (master) data created, read, updated and deleted)
managed and governed, with clear impacts in business process and highlights data duplication and
ownership by the business. changes. redundancy.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 14

Data Architecture
Core Artifacts – A detailed view

Data Process matrix

Meta Data Catalog

Data Distribution Diagram

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 15

Core Artifacts in Data Architecture
SAP Architecture Meta Model entities used to compose the artifacts

Orchestrate the Function into Operations, utilizing the Capability

Process (Actors and Roles are not included as they are not applicable at this level of detail)

A factual representation of a specific piece of quantitative or qualitative information, usually related to

Data
processing of information by application

Represents automated functionality, independent of a particular implementation or instance. (e.g. can

Application
represent all sales order applications in the organization)

Artifact entity Supporting/Related entity

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 16

Core Artifact – Meta Data Catalog
Defining data in the organization

A Meta Data Catalog (or Repository) provides data that describes any aspect of an enterprise’s information
assets and enables the organization to use and manage these assets.
 It is a repository of Data Object and Field definitions and various business system related characteristics. This includes:
Business rules and process relevance, data activities (data quality, etc.), people and organizations involved, locations of
data such as master & secondary systems, access controls, limitations (security, SOX, etc.), timing and events and the
data lifecycle components (create => maintain => delete).
 It provides an easy to read and current view of “Data Reality” from Business and IT viewpoints. It bridges the borders
between Business and IT, allowing impact analysis of all new data requirements, identifies gaps regarding the target data
architecture and defines corresponding roadmaps
 It helps to clearly understand how and where enterprise data entities are created, stored, transported, and reported
 It provides a holistic view of the entire enterprise environment, not only useful for a specific business function, but enable
utilization across any type of business.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 17

Core Artifact – Meta Data Catalog
Example

Key
(For Sorting)
LoB
Data Object
Data Object Variant
Data Type
Business Definition
Process Relevance
(according to Process Map - Level 1)
Process Relevance
(according to Process Map - Level 2)
Data Ownership - Business Owner (LoB
Level)
Data Ownership - Process Owner
Rules for Creation
Rules for Updates
Business Rules for Archiving and Deletion

Data quality dimensions and KPIs

Impact of Data Defects
Systems for Creation and Updates
Additional Systems for Updates only
Additional Systems for Display only
Replication Frequency and Technology
CHECK REPLIZIERUNG
Replication Ownership and Monitoring
Process
Relevance for internal and external
Regulations

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 18

Core Artifact – Meta Data Catalog (1/2)
Approach for creating the Core Artifact

The creation of a Meta Data Catalog is primarily based on discussions with Data Architecture Stakeholders,
such as the Business Unit Representative, the Business Process Owner or the Data Steward. It usually follows
4 phases:
 Phase A: Catalog Definition (Based on discussion results with all Data Architecture Stakeholders)
– Agree on structure and level of details for initial version, i.e. gathering of stakeholder requirements
– Define Meta Data Catalog Usage scenarios
– Define roadmap for Meta Data Catalog content delivery and evolution
 Phase B: Deliver Baseline Catalog Version
– In this version the High Priority (Prio 1) Data Objects plus Business and IT Attributes are named. start filling with content
 Phase C: Deliver Catalog Version 2 – extend to all data objects
– Extend the Baseline Version with Data Objects having specifically High Priority 1 Business and IT Attributes. These
Priority Attributes have been identified based on the Phase B exercise.
 Phase D: Deliver Final Version – non priority objects to complete the overall version
– Include non priority Objects to complete the overall Version having all Data Objects and all Attributes captured in the
Meta Data Catalog

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 19

Core Artifact – Meta Data Catalog (2/2)
Approach for creating the Core Artifact

Upon completion of the 4 phases:

 Publish Meta Data Model and Educate users
– The Meta Data Catalog is made available. The users of the Meta Data Catalog will have to be trained in the proper
usage and maintenance of the Catalog, based on the individual roles and their intended usage of the Catalog.
 Consolidate Core Artifacts
– Migrate and retire (Core) Artifacts based on the Meta Data Catalog. There are / will be several Artifacts in which
reference to Meta Data is made, any update to the Meta data Catalog should therefore be propagated into these
Artifacts.
 Run Meta Data Catalog update process
– A number of steps and check with Data Architecture Stakeholders to ensure consistency, coherence and compliancy to
data standards, in essence a governance check
 Measure usage and benefits
– On an ongoing basis the usage / consumption of Data Objects based on Meta Data is measured. This will identify which
Data Objects are actually used in terms of frequency, volume and (application and system) location. These
measurements provide valuable input in the lifecycle of master data

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 20

Core Artifact – Data Process Matrix
Data related to processes

Data Process Matrix

 The Data Process Matrix relates (Master) Data
Objects to Business Processes.
 The Data Process Matrix will highlight the n:m
relations between processes and the required data in
that process.

Provides a clear overview of data turnover (usage / generation) in business processes.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 21

Core Artifact – Data Process Matrix
Approach for creating the Core Artifact

The Data Process Matrix development is also basically a mapping exercise, done together with subject matter
experts such as the Business Process Owner, the Business Architect, the Business Unit Representative, etc.
 The key Inputs: Process Map (as discussed in Unit 05) and the Meta Data Catalog.
– Together with the Business Stakeholders mentioned an analysis of processes is made, to compare with the Objects in
the Meta Data Catalog. A “hit” between a process and a Meta Data Object is then plotted in the matrix. (As shown on the
Example slide)
– During the cross-reference activities a clear structure should be established for;
▫ Master (Data) Process – The processes which trigger the creation of new Master Data entities, based on the Meta
Data Objects. (e.g. the process “create new customer”
▫ Process Hierarchy – a structure of process outlining where Master Data is used and consumed as a reference for the
data in the organization

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 22

Core Artifact – Data Distribution Diagram (for one data object)
Data related to applications and systems

 Data Object  Applications relations to provide a

holistic overview of the existence of Data Objects
in all business applications and systems.
 The Data Distribution Diagram also show the
master and secondary business applications and
systems, the level of data integration and the
lifecycle stages.
 The diagram can be used for data lineage
analysis (common task for Data Architects)

Provides a clear definition of which application components in the landscape will serve as the system
of record or reference for enterprise data
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 23
Core Artifact – Data Distribution Diagram
Approach for creating the Core Artifact

The Data Distribution Diagram is basically a mapping exercise, done together with subject matter experts such
as the Application Architect, the Technology Architect, Solution Architects, Database Administrators, etc.
 The key Inputs: Application Architecture Diagram (as discussed in Unit 06), the Software Component Deployment Model
(as discussed in Unit 08) and the Meta Data Catalog.
– Based on discussions and analysis the result will be “putting the color on the map”, i.e. the Application Architecture
Diagram plus the related Software Component Deployment Model form the map in which the Meta Data Objects are
colored in. (As shown on the Example slide)
– While coloring the plot:
▫ Provide a clear definition of which application components in the diagram will serve as the system of record or the
system of reference for the Meta Data Objects, i.e. where is the single source of truth for master data, based on meta
data.
▫ Establish clear (naming) conventions for; Application / Systems (together with the Architects), Replication Technology,
Replication Frequency, Create Read Update Delete definitions, etc. as these will affect / impact the data life cycle.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 24

Data-Driven Architecture
with SAP Data Intelligence
Data Management Framework (The DAMA Wheel)
*derived from DMBOK2 (https://dama.org/content/body-knowledge)

1. Data Strategy is the overarching practice to consider all domains from holistic perspective
ensuring an alignment between Business and IT strategy
2. Data Governance provides direction and oversight for data management by establishing a
system of decision rights over data that accounts for the needs of the enterprise.
3. Data Architecture defines the blueprint for managing data assets by aligning with
organizational strategy to establish strategic data requirements and designs to meet these
Data Data requirements.
Architecture Modeling & 4. Data Modeling and Design is the process of discovering, analyzing, representing, and
Design communicating data requirements in a precise form called the data model.
5. Data Storage and Operations includes the design, implementation, and support of stored data
Data Data Storage & to maximize its value. Operations provide support throughout the data lifecycle from planning
Quality Operations incl. for to disposal of data
Data Strategy Retention 6. Data Security ensures that data privacy and confidentiality are maintained, that data is not
breached, and that data is accessed appropriately.
C/4H
7. Data Integration and Interoperability includes processes related to the movement and
Metadata
f Data consolidation of data within and between data stores, applications, and organizations.
SAC Security 8. Document and Content Management includes planning, implementation, and control activities
S/4H
incl. Privacy used to manage the lifecycle of data and information found in a range of unstructured media,
especially documents needed to support legal and regulatory compliance requirements.
Data 9. Reference and Master Data includes ongoing reconciliation and maintenance of core critical
Warehousing & Data Governance shared data to enable consistent use across systems of the most accurate, timely, and relevant
Business Data Integration &
version of truth about essential business entities.
Intelligence interoperability
10. Data Warehousing and Business Intelligence includes the planning, implementation, and
Reference & Document & control processes to manage decision support data and to enable knowledge workers to get
Master Data Content value from data via analysis and reporting.
Management 11. Metadata includes planning, implementation, and control activities to enable access to high
quality, integrated Metadata, including definitions, models, data flows, and other information
critical to understanding data and the systems through which it is created, maintained, and
accessed.
Modified 12. Data Quality includes the planning and implementation of quality management techniques to
Original version measure, assess, and improve the fitness of data for use within an organization.
version
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 26
SAP Data Management Domains and related products *derived from DMBOK2
Potentially not all SAP Products are shown

 SAP Analytics Cloud (SAC)

 SAP PowerDesigner  SAP Data Intelligence
 SAP HANA

 SAP Information Steward (IS)  SAP HANA

Data Data  SAP Cloud Platform Big Data Services (BDS)
 SAP Data Services (DS) Architecture Modeling &  SAP Information Lifecycle Management for
 SAP Agile Data Prep Design
 SAP HANA Smart Data Retention & System Decommissioning
Quality (SDQ) Data Data Storage &
Quality Operations incl.
Retention  SAP Information Lifecycle
Data Strategy Management for GDPR
C/4H  SAP Cloud Platform Security
 SAP Information Steward (IS)
f Data  SAP GRC Governance, Risk and
 SAP Data Intelligence Metadata
SAC Security Compliance
S/4H
incl. Privacy

Data  SAP Data Intelligence

Warehousing & Data Governance  SAP Data Services (DS)
Business Data Integration &
Intelligence interoperability  SAP Smart Data Integration (SDI)
 SAP Data Warehouse Cloud  SAP Replication Server (SLT)
 SAP BW/4HANA Reference Document &
& Master Content  SAP HANA Smart Data Streaming (SDS)
 SAP Data Intelligence Management  SAP Smart Data Access (SDA)
Data
 SAP Analytics Cloud (SAC)  SAP Cloud Platform Integration (CPI)
 SAP LT Landscape Transformation for
 SAP Master Data Governance (MDG) Data Migration
 SAP MDG Retail & Fashion Extension by Utopia  OpenText Solutions
 SAP Data Intelligence
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 27
Data Management is the key for Business Process improvement

Business
Processes
Data Integration Operationalization

Data Insights

Data Processing

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 28

But Data Management is difficult

71% 53% 82%

Struggle to connect big Enterprises are not yet Recognize that orchestrating
data to enterprise data treating data as a data and processes is critical1
and business processes1 business asset2

1 Forrester Consulting, 2019 Hybrid Data Management Drives Innovation and Growth
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 30
2 NewVantage Partners’ 2019 Big Data and AI Executive Survey
Why is Data Management so difficult?
Data
cataloging

Data
Quality Non-SAP
Applications
Data
ingestion
ELT Data
masking
Machine
Learning
Streaming
Analytics
SAP Event
Applications Cloud Data Stream
Lakes processing

Video
Processing
Data 3rd party
Data Image replication databases
ETL cleansing Processing
Data
profiling Graph
processing

Time Speech
series Recognition
3rd party Data
Semi-structured Meta Data
Warehouses Text management
& unstructured
analytics data

Geospatial
Processing
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 30
Modern Data Management needs Data Orchestration, beyond data integration

Data
Diversity
Data Orchestration
(HTAP, Big Data, Cloud etc.)
Streaming, IoT, ML, Big Data,
Advanced Analytics, Insight 2
Action…
Analytics Integration
ETL, EDW, BI, MIS, Data
Marts…
Application Integration
MFT, EAI, ESB, SOA, B2B,
BPM/BRM…

Data Value

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 31

SAP Data Intelligence, a pillar of the SAP BTP
Enabling and end-to-end data fabric

SAP Analytics Cloud

Business Intelligence Augmented Analytics Enterprise Planning

SAP BTP – Data Management & Analytics

SAP Data Warehouse Cloud SAP Data Intelligence

Cloud
Business Layer *

Data Spaces Data Catalog

SAP HANA Cloud Orchestration

Multi-model Engines
Integration
Tiered Data Storage

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL *planned 33
 Find more details in the appendix
SAP Data Intelligence – Core Capabilities

SAP Data Intelligence

Data Integration Data Processing Data Catalog

Connect and Extract meaning from Discover, classify,
integrate everything, data, orchestrating profile, understand
structured, any mix of engines and prepare all your
unstructured or enterprise data assets
streaming

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 33

Data Management Defined

Data Management Classifications

In the Data Management practice area, data, at the highest level, is broken down in to two classifications:
1. Managed Data – system persisted data that is organized, validated and verified (which may include some level of data
quality remediation). Managed Data can be Harmonized in a single system/repository that excludes process controls.
2. Governed Data – managed data that includes domain/object specific process controls to ensure sustained accuracy,
completeness, enrichment and integrity.

So, there is Governed Data and Ungoverned Data, both having relevant Data Management. In regards to Governed Data,
governance is the enforcement of Data Policy on specific data domain and data object Create, Maintain, Archive and
Distribution processes.
In this section, we’ll provide an overview of Data Management relevant to SAP S/4HANA and connected SAP Products within
a System Landscape. The important point is to architect data quality within an SAP landscape.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 34

Dimensions of Data Management
Data Domains Processes IT Systems
 Meta Data  Create  Tools & Applications
 Reference Data  Maintain  Deployment Option
 Master Data  Archive  Business Scenarios
 Transactional Data  Distribute/Replicate  Integration

Manage Define Govern Validate/Verify

Analyze Evaluate Improve
Report Approve

Organization
Explicit ownership for data objects and processes. Assigned responsibility for data objects and for
processes. Assigned responsibility for Data Quality. Defined communication and decision channels
involving Business and IT

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 35

Dimensions of Data Management Described
Data Domains Processes (Governed) IT Systems
 Meta Data – data about data  Create and Maintain – any  Tools & Applications – Data
 Reference Data – data that is update task / activity Quality tools, integrated Data
never or rarely changed (think performed on any Master Governance solutions
in terms of Customizing / Data domain/object within the  Deployment Options – data
Configuration data) system governance solutions can be
 Master Data – the nouns of  Archive – extraction of either co-deployed (i.e.
data (people, places, things) dormant, unused data from an embedded on the productive
and data domains like active productive system and system) or Hub
Product, Finance, Business loaded to a data warehouse  Business Scenarios –
Partner, etc. or other data store relevant to governed Master
 Transactional Data –  Distribute/Replicate – moving Data, data Business
operational data specific to approved data from the Scenarios are either
the buy (Procurement), sell governed source system to Consolidated (federated
(Sales and Distribution) and one or many consuming system of origin) or
financial (AR/AP) activities of business application systems Centralized create/maintain
the business – executed processes
against relevant Master Data  Integration – relevant to Cloud
to Cloud, Cloud to on-Premise
and on-Premise to on-
Premise

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 36

Master Data Management
Master Data Management – Alternative Governance Solutions

SAP MDG and SimpleMDG

SAP Master Data Governance (MDG) solution is positioned for large-scale, high-complexity data domain master data
governance. Detailed information on SAP MDG is provided in following slides. It is available via the SAP Store. SAP MDG
runs on S/4HANA Cloud Edition and OnPrem. UI is SAP NetWeaver Business Client and Fiori.

SimpleMDG is a partner developed solution by Laidon Group for Cloud only usage and is available via the SAP Store. It is
positioned for master data governance initiatives that are budget constrained with low to medium governance complexity.
SimpleMDG runs exclusively on SAP BTP.
Both solutions include standard SAP Data Domain/Object Models and integration capability via SAP Cloud Integrator
(including Cloud Platform Integration Suite). UI is exclusively Fiori based. SAP MDG additionally utilizes SAP Data
Replication Framework (DRF) for replication to both SAP and non-SAP business applications.

These are both Application Level Solutions and do not support direct database to database connectivity.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 39

 Master Data Management – SimpleMDG
Centralized Data Governance on SAP BTP, Fiori based application

Value Drivers Industry LoB

Situation and Challenges • Simple and fast data policies, standards and • Cross-industry • Multinational
• Organizations are losing on average $15 million annually due to poor data quality and business rules through Simple configuration Corporations
need a solution that can provide trusted data menu • Finance
• Companies are struggling to manage master data with manual process or custom • Ensure enterprise and regulatory data • Supply Chain Planning
application that they know is not sustainable compliance
• Business needs an application to configure and enforce data policy through business • Increase user adoption, adaptability and faster
rules and approval workflow efficiently deployment from feature-rich zero code
• Organizations need a master data governance solution that is simple, easy but effective development solution GTM Focus
in providing data quality • Low Cost Deployment, Low TCO and Fast
ROI  Americas  APJ and GC
− United States − Singapore
Solution Innovation − Canada − South Korea
− Mexico − Japan
• Intuitive admin functions enable rapid implementation with no programming skills
 EMEA − Australia
required
− Germany − New Zealand
• Consumer-grade UX, easily configurable workflow and business rules encourage quick
− France − Vietnam
adaptability for all of business
− Netherlands − Taiwan
• Seamlessly integrated with Cloud Platform SDK
• Rich capabilities readily available for effortless activation
• Instant messaging and collaborating tool throughout the request process to enhance
audit trail functionality by reducing any untraceable email trail Minimum Solution Environment
• BTP/SAP Cloud Platform
Positioning
• Small, Medium & Large Enterprises
• Low to Medium Data Governance Complexity Additional Information
• All SAP Cloud offerings, HEC and On-Premise S/4HANA Please follow link(s) below for references, demos,
• SAP ECC compatibility utilized in transition readiness for Move to S/4HANA pricing or contact details.
• Budget constrained Initiatives
W ebsite: SimpleMDG | SAP Master Data
Governance Solution
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL SAP Store: 40
https://store.sap.com/dcp/en/search/simplemdg
Typical approaches to master data management
Central governance and distribution / de-central ownership and consolidation

LoB customer LoB procurement LoB finance LoB production Other LoB

Systems under central governance

SAP Master Data Governance
– central governance
Create master data in line with business
processes (such as integrated product
Enterprise development or supplier management)
SAP Master Data Governance master data
– consolidation
Consolidate master data into a single view SAP Master Data Governance
for accurate analytics and operational – data quality management
insight (continuously or on request, such as Manage master data quality by defining,
for initial load or mergers and acquisitions) enforcing, monitoring, and improving quality
Systems not under central governance

Legacy systems Reporting and analytics Business networks Cloud

All typical approaches are supported: central governance with distribution, decentralized ownership with consolidation, data quality monitoring with remediation

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 40

Master data governance in hybrid landscapes
Synchronized master data across on-premise and on-demand solutions

All systems always in synch Real-life customer example: SAP MDG managing prospect
and customer data between cloud and on premise systems
 Master data creation can happen in on-demand systems, on-premise
systems, or in SAP MDG on SAP S/4HANA
 De-central creation triggers a process in SAP MDG on SAP S/4HANA
 After approval, enriched high-quality master data is replicated to all
relevant cloud and on-premise systems

Opportunities
SAP MDG and SimpleMDG provide adaptable integration

Customers
Prospects
Cloud

 Integration scenarios can be implemented based on standard

capabilities, like for example using extendable SOA services Enrich Validate Approve
SAP ERP
SAP ERP
 Any system can be involved as source and/or target, with certain SAP Master Data Governance Key
mapping
SAP ERP
Inquiries …

constraints Fulfillmen …
t

 Pre-built integration for selected SAP systems

Invoicing …

Move to the cloud at your own speed

 A master data hub (like MDG) that synchronizes master data across On Premise
Systems
on-premise and on-demand solutions is a prerequisite for your system
landscape simplification and your step-by-step move to the cloud
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 41
 Find more details in the appendix

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 42

Unit Summary

This unit outlines…

The Core Artifacts in relation to SAP Architecture concerning Data, i.e. Data Architecture

After completing this unit, you will be able to…

 Understand the SAP Data Architecture Objectives
 Understand the Core Artifacts in Data Architecture
 Understand the relationship between Business Architecture, Data Architecture, Application
Architecture and Technology Architecture

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 43

Appendix
Is not available in the video version of this unit
-> go to the PDF version

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 44

SAP Global Data Types
Building Blocks for Interfaces (web services)

1
Global data type Example::
1 ..* (SAP) BankAccountContractID
1 ..*
1
Core data type
(CCTS) Example: Identifier
1 ..*
1
Primitive data type Examples: float, string, token,
(XSD) and binary

SAP developed a global data type catalog (GDT) as part of the SOA-
Enablement of the SAP Business Suite and other SAP products. Most
extensive usage is in SAP Banking products.
Characteristics GDTs are SAP-wide defined and reconciled data types with business
 Standard (ISO 15000-5 and UN/CEFACT CCTS) related content as they occur in standards.
 Defined in SAP Enterprise Service Repository (ESR) The GDTs are used to define the web service interfaces which expose
 Semantic building blocks for interfaces (reuse) functionality of SAP applications.

The complete GDT catalog is a 16840 pages PDF which is publicly available on this SAP Community wiki site:
https://wiki.scn.sap.com/wiki/display/GDT/SAP+Global+Data+Type+Catalog+-+pdf+version
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 45
Data-Driven Architecture
with SAP Data Intelligence
Why is Data Management so difficult?
Enterprise IT is challenged to a whole new degree!

Integration Processing Discovery

• Structured, unstructured, • Several heterogeneous • Discover the available

streaming engines data sets, and find out
• Batch, (near) real-time • Diverse processing their semantics
• Transactional, Analytical, patterns (offline, lambda,
Hybrid event-driven …)

Quality Compliance Operations

• Data inconsistencies and • Data privacy and protection • Distributed landscapes,

fragmentation • Data lineage and auditing cloud and on-prem
• Biased data sets • Elastic scaling
• ML model life cycle • Monitoring

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 47

With SAP Data Intelligence You Can

Create powerful data pipelines for Manage metadata across a diverse data Harness machine learning to
data integration and to landscape and create a data catalog discover hidden insights as part of
orchestrate the data processing and business glossary your data pipelines

SAP Data Intelligence transforms distributed data sprawls into vital

data insights, delivering innovation at scale.

Access & Govern & Prepare & Build scalable Operationalize Monitor &
connect data discover data label data & flexible machine learning scale
data pipelines

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 48

SAP Data Intelligence enabling Hybrid Data Management
Leverage existing SAP EIM tools

Orchestration
SAP Information SAP Data
SAP Data SAP Data Steward Intelligence
Services Intelligence
Common Support W ide
Connections Span of Data
[Data Lake]

Operationalization Metadata 3rd Party

Partner

 Extend reach of Data Services  Reuse Information Steward

assets across diverse system landscapes rules within Data Intelligence
 Orchestrate Data Services jobs  Shared glossary of terms
within Data Intelligence pipelines  Metadata shared across
 Enhance enterprise business applications, augmented by ML
processes with high value data and learning models
insights from external systems

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 49

A real-life example: HR Best Fit with SuccessFactors
The business objective: find best fits within workforce to cover job postings

Data Integration Data Processing Business Process

SAP HR data

SFSF Seniority data

Knowledge Scoring Data

Job posting
Location Data
vs.
Best Fit Model Employees
Score
Areas & Knowledge
Data

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 50

HR Best Fit with SuccessFactors
The as-is before Data Intelligence: manual integration and weekly batches

Manual
Employee point-to-point
Personal Data & integrations Weekly
Job Position
Data
updates

Employee
Seniority Data
Excel sheet with
Best Fitting
Data extracts to
Best Fit Employees,
Excel files
refreshed weekly

Areas &
Knowledge Data

Employee
Knowledge
Point-to-point
Scoring Data
data extract

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 51

HR Best Fit with SuccessFactors
The solution with Data Intelligence: streamlined operationalization, real-time insights

Real Time
Employee Matching by Job
Personal Data & SAP Data Intelligence
Job Position
Posting Code
Data

Employee
Seniority Data
Best Fitting
Score Scaling Employee List
Best Fit according to related to input
Location job posting

Areas &
Knowledge Data

Employee
Knowledge
Data Intelligence
Scoring Data Distance Data
pipelines
Employee – job
posting location
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 52
SAP Data Intelligence – Deployment Options

SAP Data Intelligence

full managed cloud

on-premise
service on SAP BTP

SAP Business
Technology
Gardener Platform
Kubernetes

On-premise public cloud

installations Kubernetes service private cloud public cloud

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 53

SAP Data Intelligence, cloud edition – Connectivity

Hyperscaler 1
Infrastructure
Customer Network 1

Hyperscaler 2
VPN Infrastructure

SAP Data Open

Intelligence
Endpoint

SAP Business
Customer Network 2 Technology
Platform

SAP Cloud
Connector

SAP BW/4 HANA

public cloud

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 54

SAP Data Intelligence – Why it is different

Single end-to-end tool

Discover and catalog your data, integrate it and orchestrate,
manage ML operations, all in one single product.

Multi-cloud, agnostic and open

Adaptable architecture built on open technologies, available as-a-service,
or BYOL in the cloud on any hyperscaler or on premise.

Re-use existing on-prem investments

Natively reuse and connect all SAP on prem technologies
(HANA, BW, Data Services, SLT etc.)

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 55

Data Management
with SAP MDG
SAP Master Data Governance, Central Governance
Process flow

External Providers External Services

SAP Master Data Governance

Re-use existing business logic, Collaboration
integrate external services Adaptable workflow
for data enrichment, address
Auditable change process
cleansing, duplicate detection, …
2 3
Maintain Validate Approve Replicate
Central maintenance of 1 4
master data in staging area
Automatic replication to
non-SAP and SAP systems

Business Processes

5
Adapt

Adaptation / enrichment
in local systems
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 57
SAP Master Data Governance, Consolidation
Process flow

Calculate Best
Data Load Initial Check Standardize Match Validate Activate
Record

Open to SAP HANA View loaded data Validate and enrich Find duplicates based Create “Best Validate best records Provide consolidated
smart data integration, and check data address data on customer-specific Records” based on against backend master data for
non-HANA based quality based on matching rules approved match customizing to verify analytical or
Possibility to connect
SAP ETL backend groups whether records can operational use
to 3rd party tools for
mechanisms, customizing Review match result be activated
standardization and BRF+ can be used for
non-SAP ETL options, Option to activate
enrichment customer-specific
or data import from file Validate against directly, or indirectly
Best Record
Usage of BRF+ for ctrl. governance triggering post
Calculation
standardization and checks (BAdI, BRF+) processing using
enrichment Review Best Record central governance
Calculation result

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 58

SAP Master Data Governance, Data Quality Management
Process flow

Define Quality Enter Quality Monitor Quality Improve Quality

Requirements are defined based on Ensure quality at point of e ntry Operational motivation: detect issues Correct data and drive the correction
your company’s business processes before processes fail process
Consider all entry-points: si ngle
Priorities are set according to value, changes, mass changes, l oad scenarios, Tactical: ensure progress an d Fix data entry processes
impact, and quality evolution in daily business, projects, … performance of current activ itie Evolve the definition of quality
► Experts collaborate to define needed ► Rule-based checks in al l processes of Strategic: enable achieveme s
► Tools to fix data and to improve
quality level and required checks SAP MDG new initiatives nts, define
checks at point of entry
► The system helps to identify ► Easy to consume monitori
additional meaningful rules trend reporting ng and

Karl Singer
StevenOlsen

StevenOlsen

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 59

Master data quality management
Improve the quality of your business partner and product data

In a nutshell …
Business user application to define master data quality rules, striving for consistent usage across all points of
entry and enabling data quality monitoring and remediation.
Business value
Define Quality Enter Quality Monitor Quality Improve Quality

Central place for master data quality rules. Providing transparency

on business aspects, usages and technical implementations,
consistent quality definition, and continuous evaluation and
monitoring
 Business partner and product master data covered as packaged
applications, and platform for custom-defined objects
 Collaboratively describe, catalog, and implement rules for data quality
evaluation
 Schedule quality evaluations, analyze evaluation results and initiate
correction of erroneous data
 Get an overview on current data quality status and KPIs
 Allow for drill down analysis of data quality scores along multiple
dimensions

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 60

Mass processing
Effective process to execute mass changes for attributes

In a nutshell …
Highly effective mass change process enabling master data stewards to perform bulk changes in business partner,
customer, supplier, and product data.
Business value
 Highly effective data processing option for master data specialists

 Efficiently edit individual fields or make bulk changes by using a tabular UI with
the ability to filter and sort data

 Confidence and transparency when changing large volumes of data through

statistics, change indicators and ability to validate prior to activating changes

 Packaging, queuing, and parallelization contribute to enhanced performance

even when processing large volumes of data

 Upload changed records from CSV or Excel© file to incorporate offline

processing and other information sources

 Background execution enables users to close the application while processing

continues. Users can check the status or proceed with their work later.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 61

 SAP Master Data Governance
Integrated Object Model

Out-of-the box delivery of proven data models for operational and financial master data
Financials Material Supplier & Customer Enterprise Asset Mgmt. ** Retail & Fashion Mgmt. ***

Business Partner Attributes

Purch. Basic & Classification Data

Asset Structure s
GL Account* / General Data & W ork Centers Descriptions Units of Measure
Basic & Classification Data

Chart of Accounts Descriptions Central Data Roles Tax Bill of Material

Equipment Master

Asset
Linear
Cost Element* / Units of Measure Bank Details Identification Textile Components
Accounting ,Controlling and Consolidation

Hierarchies Functional Location & Fiber Codes

Quality Data Tax Numbers Industry Sectors
Financial Reporting Object Links and Networks Characteristics
Structures: Addresses with Usage and Versions Assignment & Variants
EAN, UPC
Balance Sheet, Distribution Curve

Capabilities
Maintenance Plans

Work Management
P&L Statement Classification Business Partner Relationships

& Procurement
Maintenance Items Purchase Info Record
Cost Center / Document Link
Hierarchies Supplier Attributes Customer Attributes Purchasing Org / Vendor / Site
Measuring Points
Profit Center / Sales Data General Data General Data Stores Distribution Cntrs.
Task Lists

FMS Logistics, Listing, Sales

Logistics Data

Hierarchies Listing Layout Module

Plant Data Comp. Code Data Service Master
Internal Order Comp. Code Data Point of Sales Sales Org. Data
Storage & Sales Area Data Assortment Season Assignmt.
Company W arehouse Data Header: Identifying and Quantity,

Bill of Material
Purchasing Data Tax Indicators Additionals Article Hierarchy
Validity Data, Material Data, Texts
Consolidation: Production Version Substitution Additional Texts

MRO
Item, Group & Contract Account Attributes Item: Detail, Quantity, Status, Document Management System
Hierarchies, Unit, MRP and Purchasing Data,
Value

Valuation, Costing,
Break Down Category Material Ledger General Data Partner-specific Data Text and Document Assignment Segmentation Seasons

* User interface integration between GL Account and Cost Element only supported in SAP MDG on SAP S/4HANA ** SAP MDG, enterprise asset mgmt extension by Utopia *** SAP MDG, retail & fashion mgmt. extension by Utopia
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 62
Cloud based master data sharing in context of Enterprise master data mgmt.
Apply Master Data capabilities along the business use cases

Demand-driven Benefits and value-add

master data consumption  Modular and easily scalable
by cloud applications  Potential re-use of master data
without own persistency in apps

 Scalable access to master

micro
service
micro data for all cloud applications
service
micro
service
 CRUD services, federation and
Master data services on Master Data micro replication (OData/SOAP) for
SAP Cloud Platform for Service for
service
re-use by cloud applications
Business Partner
flexible master data integration  Cross-application consistency
and linking of master data by
Key Mapping

SAP MDG

 Provisioning of trusted master

SAP Master Data Governance for Enterprise Master Data
data in high quality throughout
enterprise master data management all business processes
in hybrid landscapes SAP S/4HANA, SAP Business Suite,
3rd party applications

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 63

Data-In Hub Concept – DIH
An example of Data-Driven Architecture
Transformation challenges
why Data-In Hub was created

Cloud
apps

Lost
Legacy
SAP innovation
Multi-year value
projects
Business
disruption
Legacy
nonSAP
Data Digital Core
loss
High risk
of failure Slow SCP, IOT

Acquired
business
ERP value delivery

As-Is (Now) Transformation journey To-Be (2020+)

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 65
SAP Data-In Hub
Key use cases

 Real-time analytics based on multiple

Central Reporting - disparate data sources and data lakes
One Source of Truth
 On-the-fly mapping and harmonization

 Data profiling and cleansing

Implementation and
 Data harmonization and governance
Transformation
 Data migration to SAP S/4 HANA

SAP

Non-SAP
SAP MDG SAP BW on HANA

Service Layer
SAP BPC

SAP
Applications
 Instant visibility for the business
Enterprise Data Hub

SAP Integration
 Synergy realization support

Real Time Replication – No Transform

Enterprise Data HUB

Merger & Acquisition

Virtual Harmonization
SAP Delivered

F
Applications
I
/

oData

Support
Services

 Infrastructure for M&A “playbook”

SAP Harmonized Store

Micro-Services Layer
o Data Services
w Store
Ra

Non-SAP
Non-SAP
Applications

Efficient execution of divestitures

SAP Data Services SAP Info Steward SAP SDI/SDQ

SAP HANA
(platform)


m
M
A
P

t
I

.
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 66
Next generation transformation using Data-In Hub
How it works

1 Set up DiH system

powered by SAP HANA
Data Data
Analytics Set up real time replication
3
Quality
5
Readiness
2 from sources into RAW data
Cloud store
apps

3 Start real-time reporting on

Virtual data models
and profiling of source data
4
Legacy
2
Harmonize and cleanse
SAP
Digital Core 4
relevant data on-the-fly
Real time
data feed Rules &
6
5 Analytics and reporting on
Mappings

SAP HANA Platform

Extracted
RAW
Cleansed
Harmonized Staging real time harmonized data
Legacy
Data-In Hub Load harmonized data into
nonSAP 1 (HANA) 6 S/4 HANA environment
once it is available
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 67
Data-In Hub as a transformation platform
what is different?

One central set of transformation rules for both analytics and data migration

End-to-end coverage of the transformation process with one integrated tool set for

 Data quality analysis and profiling

 Transformation and mappings
 Data construction
 Data load into S/4 HANA
 Result validation
 Migration documentation
 Master data management

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 68

Data-In Hub on premise
High level architecture

SAP Analytics Cloud

Dashboards
Apps

BW/4 HANA

DiH (HANA Enterprise)

Data
SAP ERP
Warehouse
Data Models
S/4 HANA

Data
S/4 HANA
Lake Security
MDG

IoT Non SAP

OP Rules
Data OP
Data Mappings

Excel

Data intelligence OP (Data Hub)

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 69

Evolution of Data-In Hub

DiH DiH
On Prem Cloud

2015-2019 … 2020+
 On premise/private cloud  Private or public cloud
 Static  Elastic
 Limited  Unlimited

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 70

SAP HANA Cloud Services
basis for the next generation of DiH

SAP HANA Cloud Services

A single gateway to all your trusted data

TECHNOLOGIES

SAP Analytics Cloud SAP Data Warehouse Cloud SAP HANA Cloud
Analytics technology – business End-to-end data warehouse in Next-gen database Platform as-
intelligence (BI), planning, and the cloud that combines data a-Service with full capabilities to
predictive analytics – in a single management processes with manage OLTP, OLAP and HTAP
solution advanced analytics workloads

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 71

Data-In Hub cloud
High level architecture

SAP Analytics Cloud

Apps
Dashboards

SAP Data Warehouse Cloud

Stories

SAP HANA Cloud

Data S/4 HANA OP
SAP ERP OP
Warehouse OP
Data Models
MDG OP
Data
S/4 HANA OP
Lake Security
S/4 HANA Cloud Non SAP Cloud

IoT Non SAP

OP Rules Cloud
Data OP
Data Mappings Data
SAP Cloud Platform

Excel

Data intelligence (Cloud)

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 72

SAP Data-In Hub
Important facts

1. Data-In Hub was designed to support large SAP customers

during complex transformation and innovation projects

2. Data-In Hub is NOT a product

It is rather a concept and an innovative deployment option for
SAP HANA and EIM solutions

3. Data-In Hub is a highly flexible concept that adapts to the very diverse
requirements and existing tools in each customer’s landscape

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 73

Follow us

www.sap.com/contactsap

© 2019 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related present ation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/copyright for additional trademark information and notices.