move to s/4 hana konverzija sap ecc · pre-requisites and limitations update spam to version 59 or...

Post on 26-May-2020

2 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

MOVE to S/4 HANA – Konverzija SAP ECC rešenja na novu platformu

03.10.2019Slobodan.Malbasic@malbasoft.com

Sadržaj:

• Preduslovi (tehnički) za konverziju

• Alati koji se koriste u procesu konverzije – prepreke na koje nailazimo

• Održavanje i razvoj sistema posle završene konverzije

Honor the Past, Celebrate the Present, Embrace the Future

!!! !!! !!!

Kada (i kako) se odlučiti za promene?

Izabrati pravilan „business case“ Revitalizacija postojećeg data centra

Promena modela podrškeIzbor neke od novih tehnologija:

BD,IoT,AI,MLReinženjering poslovnih procesaIzbor novog modela licenciranja

Merdžovanje ili akvizicija

Iskoristite svoju šansu!

Nemojte da zakasnite!

Vrlo precizno i pravilno planiranje

projekta

Izbor tima (timova) koji učestvuju na

projektu

Angažovati eksperte iz pojedinih oblasti Iskoristiti pomoć

koju SAP nudi besplatno za

projekte konverzije!

Organizacija projekta

Jasno postavljeni ciljevi Migrirati sistem

ECC 6.0 EHP4 na S/4HANA do

01.07 (3 meseca)

Opredeliti značajne materijalne, finansijske i ljudske resurse za

projekat

Metodologija projekta:Korišćenjem resursa koji su na raspolaganju,

preporuka od strane SAP-a i sopstvenog iskustva u sličnim projektima uraditi test

konverziju i obezbediti funkcionalan S/4HANA sistem pre početka projekta

konverzije!

Prve prepreke

Win ili LinuxMSSQL ili Oracle

Ili DB2 ☺

Koji su minimalno

potrebni uslovi za konverziju ???

SUM is offered in two versions since 11.09.2017:

SUM 2.0 is for ABAP single stacks, targeting systems based on BASIS 7.50 and higher(exception: SUM 2.0 is used for ZDO even if target is BASIS 7.40 or lower)SUM 1.0 is always used if the source system is either a dual-stack system, or a Java stackSUM 1.0 is used for ABAP stack if target is based on BASIS 7.40 or lower

Preduslov za konverziju !!!

System Conversion DetailsPre-requisites and limitations

Update SPAM to version 59 or higher (SPAM version 66 or higher for SAP S/4HANA 1709 and higher)

The following checks can be executed in parallel (without the stack XML from MP)

Software Update Manager prerequisite check (see SUM conversion guide)

ABAP custom code checks

Documents related to conversionSAP S/4HANA on SAP Help Portal

Steps in the conversion processMaintenance Planner conversion pre-Checks: Checks your add-ons and business functions to ensure compatibility with SAP S/4HANA. Also creates the stack file used for the actual conversion

Checks the compatibility of add-on software component versions present on a given ERP technical system with SAP S/4HANA.

Checks existence of a valid read RFC destination to the technical system from the SAP Solution Manager in the customer landscape. This is required to retrieve the business function

Checks if there are business functions in the technical system which are not supported in the SAP S/4HANA. The results of this check may vary based on the selected support package

Checks for existence of a connected Java system. If a dependency exists to a Java system, the conversion planning stops and can only continue if the product maintenance dependency

Checks if the note 2186164 is deployed on the SAP Solution Manager. If not applied, the conversion planning is stopped.

Conversion pre-checks: To check the system,

Execute program R_S4_PRE_TRANSITION_CHECKS for targets till SAP S/4HANA 1610.

Execute program /SDF/RC_START_CHECK for SAP S/4HANA 1709 and above targets on the ERP system.

Custom code check tool: Checks your custom code against a list of simplifications developed for SAP S/4HANA. Ideally you perform these checks at the same time as your prechecks

General and application-specific preparations: Manual activities to prepare your system and applications.

Software Update Manager(SUM): Automates the conversion process and deploys the SAP S/4HANA software.

Application-specific follow-up activities: Manual follow-up activities may also be required.

Sizing (DB sizing)

• Početna veličina DB ~ 1 TB

• X = 1 TB / 4

• X = 256 GB (RAM)

• Y = 256 * 4 = 1024 GB (DISK)

Potrebno je konsultovati preko 300 i primeniti preko

200 SAP Nota i dokumenata!

Konverzija Biznis Partnera

CV integracija

Ova oblast po nama zaslužuje

poseban projekat!

Preklapanje intervala brojeva!

Z programi

Integracije, interfejsi

Zaostali razvoji, započeta i

nedovršena podešavanja

Naša preporuka je da se projekti ove vrste ne izvode u

„kućnim“ uslovima!

SAP Fiori

Coming kao SAP PCoE partner!SAP sertifikovani konsultanti!

Sa mrežom iskusnih konsultanata i podizvođača

(kao Malbasoft npr.)

Hvala na pažnji!

GO LIVE 01.07.2019! Prva S/4HANA konverzija u regionu!

Dodatak:

https://support.sap.com/content/dam/support/en_us/library/ssp/alm/sap-solution-manager/sap-support-backbone-update/Backbone_Update_Overview.pdf

Sad je stvarno kraj ☺

top related