Professional Documents
Culture Documents
Overview
The HANA Platform despite the fact that it has been available in the SAP offer for a
long time and is exceptionally encouraging is simply beginning in business. The
arrangement is as yet being produced and the principal movement activities are
occurring under the supervision of SAP specialists. Their part is to give proposals
and experience with respect to the approach to arranging the work and forms of the
tools to be utilized during the update and system migration.
For the reasons of system migration to HANA, SAP likewise gives a free service that
encourages the recognition of support areas and impact on the change of execution
of the system which has as of now been installed on the HANA Platform. The
administration is known as the Business Situation Proposal for Suite on
HANA and includes the investigation of a properly arranged explanation of the
utilization and execution of transactions in the clients system.
The whole undertaking is led as per SAP standards and best practices created by
the Project Management Institute, which forces elevated expectations of behavior
and guarantees higher security and upgrades the odds of the venture being
effective and successful.
Preparation
Migration
Optimization
a. Preparation
The planning procedure ought to start with figuring out what equipment will
be expected to migrate to the HANA database. The equipment for HANA is
conveyed by confirmed SAP partners, for example, Dell, Fujitsu, HP, IBM,
CISCO, as prepared to-utilize servers (SAP HANA Appliance) including
introduced HANA software.
a. Migration
The procedure of the SAP system database movement to the SAP HANA
platform is altogether not the same as the migration between different
platforms (in SAP, this sort of venture is known as an OS/DB migration).
The migration process for most SAP systems will must be performed in two stages:
After the migration has been finished and the system has been dispatched on the
HANA Platform, it is important to redo the system itself and the related
environment. Along these lines, the accompanying activities ought to be arranged:
standard specialized steps after the migration (as with different platforms),
technical joining steps checking the correspondence with different
systems,
Going Live OS/DB Movement Check Service the second session of the
system check after the relocation proposals from the report ought to be executed
in the system.
a. Optimization
2. Risks
a. Choose your own group painstakingly who could gel with Execution group and
are adequately engaged to take business choices/give inputs, generally the
issues of non-collaboration, postponed/no reactions and doubt could snowball
into significant acceleration affecting venture courses of events.
a. All of us dont care for change, yet acknowledge it. Clients, who are
continuously working at a specific software without stopping for even a
minute, for a considerable length of time, will undoubtedly feel on edge while
moving to SAP. Along these lines, might it be trepidation of learning (or
whatever other), it should be tended to appropriately, much before the Go-
Live.
a. You need somebody (from your side) to work intimately with the vendor
team, to screen advance nearly consistently, to search for the
chinks/warnings at each stage, in short to take after what has been secured
in before focuses. In either case, guarantee the right senior stakeholders are
included in the Project Steering Committee. Sense of self administration is
one more fragile assignment you have to handle competently. Guarantee the
Controlling Panel meets at preplanned interims and issues are tabled/tended
to.
3. Knowledge Exchange
a. Ensure vendor team is documenting and putting away it on the assigned spot
Project Charter
Project Plan
Business Blueprint
Functional details
Technical details
a. Please dependably utilize most recent kernels, R3load and R3ta devices
for export/import procedure to dodge blunders.
a. With SWPM 1.0 SP3 PL6, assortment of new choices is accessible in SWPM
where you can pick distinctive export choices like sort the export in view
of size or run time or rehash export without running R3szchk once
more.
a. It may happen that after migration to HANA, some ABAP Code execution is
bad and significantly slower than past database. This may be on the grounds
that improvement is not done in ABAP according to suggestions.
a. SAP has released report that can help you to locate the potential Data
suppliers that can be resigned when utilizing HANA.
a. In a few cases, you will confront issue where customers are not ready to
interface with SAP HANA scale out hubs. This may be because of how scale
out architecture is designed.
a. For more previous versions i.e. till SAP HANA SP5, you can arrange SUM for
SAP HANA.
1. 8. Execution Improvement
a. Row store memory is a considerable measure greater than real data size
since row store tables develop by allocating a 64 MB section, furthermore,
shrivels by same. On the off chance that you have erased lots of information
from row store tables and afterward a great deal of sparse segments is
available. Besides, keeping in mind the end goal to free up the space,
reorganization will be essential.
a. If you need to recognize issues identified with primary keys and unique
constraints.
a. In case you discover that a few tables are not divided or distributed
accurately over many HANA nodes.
This is not the last rundown of all activities to do migration to SAP HANA and you
have to allude to system copy guides, SAP release notes and SCN and so on for
detail process.
9. Vendor Experiences