Sie sind auf Seite 1von 8

Common pain points in a system using a classic database:

1. Information explosion and massive amount of data


2. Consumerization of IT - People want instant access to information - in the moment - whether that is a moment
of risk or a moment of opportunity.
3. IT Cannot Deliver - to process and analyze massive amounts of data in real time

The Daily Challenges of Data Volume and Complexity


1. High flexibility
2. Complex system landscape
3. Immediate results
4. Massive growth of data volume
5. Skilled workforce

Main Drawbacks
1. Sub-optimal execution speed
Lack of responsiveness
User frustration
Unsupportable business processes
2. Lack of transparency
Need for aggregation
Outdated figures
Guessing current situation
3. Reactive business model
Missing opportunities
Competitive disadvantage

SAP HANA Offer


1. Amazing speed - 3600X
2. Amazing Amount of data - 460B rows of data in seconds
3. Amazing Value - 21% Average Revenue growth and 19% reduction in IT cost.
SAP HANA
• SAP HANA is a flexible, data-source-agnostic appliance that enables customers to analyze
large volumes of data from SAP and non-SAP systems in real-time, avoiding the need to
materialize transformations.
• SAP HANA appliance software is a Hardware and software combination that integrates a
number of SAP components, including the SAP HANA database and several data replication
systems: SAP Landscape Transformation, SAP HANA Direct Extractor Connections (DXC),
SAP Data Services or SAP Sybase Replication Server. •
• The SAP HANA database is a hybrid in-memory database that combines row-based, columnbased,
and object-based database technology. It is optimized to exploit the parallel processing
capabilities of modern multi-core CPU architectures. With this architecture, SAP applications
can benefit from current Hardware technologies.
SAP HANA provides a unique combination of Hardware and software innovations that have a
huge potential to optimize business applications running on SAP HANA.
SAP Hana has
1. Multi core processor (CPU)
2. Row/column base storage, Compression, Partioning, insert Only/Delta (Memory)
3. Storage Disks (BAckup)

Row and column storage

SAP HANA is able to store tables in row/column based data store.


Compression: SAP HANA works with bit encoded values and compresses repeated
values, which results in much less memory requirements than for a classical row store table.
Partitioning: Data Partitioning allows a much faster data processing, by making several processor cores work in
parallel on smaller sets of data.
Only Insert /Delta

Comparison between SAP S/4 HANA On-Premise and Cloud Editions

SAP S/4 HANA On-Premise Edition SAP S/4 HANA on Cloud Editions Hybrid
in-house application, Software as a Service (SaaS)

hosted on your organization’s servers that lives on SAP’s servers


maintained by your organization is maintained by SAP
Innovations are released yearly by SAP with innovations applied quarterly.
and implemented by your team.
the best fit for enterprises in any he best fit for companies that need
industry that need the full spectrum of a highly agile offering that covers
functionality combined with a high their core business scenarios, yet
degree of flexibility in customization. offers more flexibility and a faster
innovation cycle (quarterly as
opposed to yearly). It’s perfect for
businesses that are changing or
growing rapidly and want a platform
that can grow and change with
them.
Typically, these will be larger
enterprises with very well established
processes that they are not interested in
changing.

Three specific offerings are currently available as part of the SAP S/4HANA, cloud edition:

 SAP S/4HANA, cloud marketing edition – for the marketing line of business
 SAP S/4HANA, cloud project services edition – for the professional services industry
 SAP S/4HANA, cloud enterprise edition – for a full ERP scope

Development Repository Integration

From the development perspective it is possible to check in and out development objects,

connecting to a repository

XS Server
SAP HANA Extended Application Services (also known as XS Server) is a key aspect of SAP HANA as a
platform.

XS is an application server, Web server, and basis for an application development platform. All
components reside inside SAP HANA.
XS is not a completely separate technology that happens to be installed on the same Hardware
server as SAP HANA; XS is actually an extension of, and tightly integrated into, the SAP HANA

database.

SAP HANA Repository Packages and


Namespaces
In SAP HANA Application Services, a package typically consists of numerous repository objects; the
package specifies a namespace in which the repository objects exist. Every repository object is assigned to
a package, and each package must be assigned to a specific delivery unit.

In the repository, an object is uniquely identified by a combination of the following information:

 Package name
 Object name
 Object type
Note: Multiple objects of the same type can have the same object name if they belong to different packages.
Before you start the package development process, you need to consider the following important aspects:

 Package hierarchy

Each vendor uses a dedicated namespace.


 Package type

Some packages contain content; other packages contain only other (sub)packages.
 Package naming conventions

There are recommendations and restrictions regarding package names.


Package Hierarchy

You can create a package hierarchy, for example, by establishing a parent-child type relationship between
packages. The assignment of packages to delivery units is independent of the package hierarchy; packages
in a parent-child relationship can belong to different delivery units. SAP recommends that you assign to
one specific delivery unit all packages that are part of a particular project or project area.

All content delivered by SAP should be in a sub-package of "sap". Partners and customers should choose
their own root package to reflect their own name and must not create packages or objects under the "sap"
root structural package. This ensures that customer or partner created content will not be overwritten by an
SAP delivery.

Note: SAP reserves the right to deliver without notification changes in packages and models below the "sap" root
structural package.

There are no system mechanisms for enforcing the package hierarchy. The "sap" root structural package is
not automatically protected. However, by default you cannot change the content of packages that did not
originate in the system. In addition, an authortization concept exists, which enables you to control who can
change what inside packages.

Package Types

SAP HANA Application Services provide or allow the following package types:

 Structural

Package only contains sub-packages; it cannot contain repository objects.


 Non-Structural

Package contains both repository objects and subpackages.

The following packages are delivered by default with the repository:

 sap
Transportable, structural package for content delivered by SAP. Partners and customers must not use
the sap package; they must create and use their own root package (to avoid deletion when SAP
updates/overwrites the sap package structure).
 system-local

Non-transportable, structural packages (and subpackages). This is similar to the concept of the $tmp
development class in SAP NetWeaver ABAP.
 system-local.generated

Transportable, structural packages for content that is not created by manual user interaction
 system-local.private

Transportable, structural sub-packages that belong to individual users and are named after these users
(and are exclusively reserved for these users). For example, system-
local.private.<user_name>
Package Naming Conventions

The following rules apply to package names:

 Permitted characters

Lower/upper case letters (aA-zZ), digits (0-9), hyphens (-), and dots (.) are permitted in package names.
Dots in a package name define a logical hierarchy. For example, "a.b.c" specifies a package "a" that
contains sub-package "b", which in turn contains sub-package "c".
 Forbidden characters

A package name must not start with either a dot (.) or a hyphen (-) and cannot contain two or more
consecutive dots (..).
 Package name length

The maximum permitted length of a package name is 190 characters


 Package namespace length

The name of the complete package namespace hierarchy (for example, "aa.bb.cc.zz" including dots)
must not be more than 190 characters long

Maintaining Delivery Units


A delivery unit (DU) is a collection of packages that are to be transported together. You assign all the packages belonging
to your application to the same DU to ensure that they are transported consistently together within your system
landscape. Each DU has a unique identity.
Prerequisites
To maintain delivery units with the SAP HANA Application Lifecycle Management, you must ensure the following

prerequisites are met:

 You have access to an SAP HANA system.


 You have been assigned the SAP HANA sap.hana.xs.lm.roles::Administrator user role.

 A vendor ID (repository namespace) is already defined.

Context
The identity of a delivery unit consists of two parts: a vendor name and a delivery-unit name. The combined ID ensures
that delivery units from different vendors are easy to distinguish and follows a pattern that SAP uses for all kinds of
software components.

To create and manage delivery units you first need to maintain the identity of the vendor, with whom the delivery units are
associated, and in whose namespace the packages that make up the delivery unit are stored. As part of the vendor ID
maintenance process, you must perform the following tasks:

Procedure
1. Understand delivery units.

You must be familiar with the conventions that exist for delivery-unit names and understand the phases of the

delivery-unit lifecycle.

2. Maintain details of the vendor ID associated with a delivery unit.

Delivery units are located in the namespace associated with the vendor who creates them and who manages the

delivery-unit's lifecycle.

3. Create a delivery unit.

Create a transportable “container” to hold the repository packages in application.

4. Assign packages to a delivery unit.

Add to a delivery unit the repository packages that make up your application.

5. Export a delivery unit.

You can export the contents of a delivery unit from the SAP HANA Repository to a compressed Zip archive, which you

can dowload to a client file system.

6. Import a delivery unit.


You can import the contents of a delivery unit into the SAP HANA Repository, for example, from a compressed Zip

archive, which you upload from a client file system.