Business Drivers on Innovation Project of Marcegaglia · Upgrade from SAP R/3 to . SAP S/4HANA . SAP BI . ... Check/fix SPAU/SPDD . ... Sign off SAP Upgrade project . Transport TRs

Marco Campi Chief Information Officer , Marcegaglia S.p.A.

Gianluca Simeone SAP HANA & S/4HANA Architect, Capgemini Italy

Business Drivers on Innovation Project of Marcegaglia

2 Copyright © Capgemini 2015. All Rights Reserved

Business Drivers on Innovation Project of Marcegaglia | Date

Context

Requirements 1

Innovation Roadmap 2

Upgrade to SAP S/4HANA 3

Benefits 4



Context

Requirements 1



Benefits 4



Requirements

Disegno nuovo modello operativo Necessità di dar seguito alle evoluzioni di processo richiesto dal Management

Aumentare il livello di standardizzazione dei processi e dati Implementare il nuovo modello sfruttando le Best-Practice standard SAP

Armonizzazione soluzione cross-country Semplificare e applicare il modello nelle diverse società del Gruppo

Evoluzione dei sistemi informativi, digitalizzazione Rinnovare e semplificare la mappa applicativa e sistemistica



Requirements

Disegno nuovo modello operativo Necessità di dar seguito alle evoluzioni di processo richiesto dal Business Management

Amministrazione Tesoreria Credit Management

Acquisti materiali no-core SCM

BI, Datawarehouse CRM

Organizzazioni Commerciali Order Entry Fatturazione Programmazione Produzione Spedizioni

Aree di Business di intervento Approccio conservativo

Abilitatore di nuove soluzioni all’interno di un programma di miglioramento dei processi e delle soluzioni. I percorsi di miglioramento sono «indipendenti» tra di loro.



Requirements

Aumentare il livello di standardizzazione dei processi e dati Implementare il nuovo modello sfruttando le Best-Practices standard SAP

Nel corso degli anni alcune scelte implementative hanno dovuto seguire un percorso «Custom Oriented» in funzione della release SAP R/3 4.0b in essere, allontanandosi dal concetto di «Zero Modification» che vede invece la minimizzazione degli sviluppi Custom, privilegiando l’utilizzo di funzionalità standard SAP.

La release del gestionale SAP ha «veicolato» scelte sia a livello di processo, sia a livello di programmazione ma anche a livello infrastrutturale.

In modo «distruttivo» in alcuni versi, in modo «non-distruttivo» in altri, il progetto in corso vuole lanciare un segnale di ritorno all’adozione delle Best-Practice, ad esempio tramite: Aggiornamento dei sistemi gestionali all’ultima release; Nuova piattaforma di SAP BusinessObjects BI e sistema SAP CRM; Introduzione di una piattaforma EAI (middleware, SAP PO) per la centralizzazione delle interfacce; Utilizzo delle funzionalità standard SAP, ad esempio del verticale Mill (DIMP).



Requirements

Armonizzazione soluzione cross-country Semplificare e applicare il modello nelle diverse società del Gruppo

Nel corso degli anni il Gruppo Marcegaglia è cresciuto anche grazie ad alcuni investimenti all’estero in particolare in Brasile, Polonia, Cina, UK, US, Russia, Romania e Turchia Come spesso accade, partendo dal sistema IT core centrale italiano le country estere sono state dotate sin dall’inizio del sistema SAP aziendale anche in release differenti Il progetto in corso vuole anche mettere ordine all’intero parco IT, con l’obiettivo di avere a regime un unico gestionale SAP S/4 HANA centralizzato, la Business-Suite complete basata su SAP HANA.



Requirements

Evoluzione dei sistemi informativi Rinnovare e semplificare la mappa applicativa e sistemistica

La mappa applicativa dei sistemi informativi di Marcegaglia evidenzia alcune particolarità:

Release SAP R/3 del gestionale con quasi 3Tb di dati; Diverse installazioni produttive del gestionale SAP, in release differenti, per la gestione delle diverse

società del Gruppo; Interfacciamento tra sistemi complesso, senza l’adozione di un sistema middleware centralizzato; User-Experience limitata (prevalentemente SAP-GUI) che non consente l’utilizzo del sistema

in mobilità (tablet, smartphone); Reporting Commerciale e di Controllo di Gestione da riprogettare; Sistema CRM totalmente «custom» da riprogettare su prodotto specifico di mercato.



Context

Requirements 1



Benefits 4



Innovation Roadmap Stream Finance and HANA, Re-Engineering Operations, Model extension

Program Key-Point: upgrade with single downtime from SAP R/3 4.0b to SAP S/4HANA

Re-Engineering Accounting Processes, Procurement Materials no-core

SAP CRM on HANA on Marketing & Sales

New-GL, Simple Finance, Simple Logistic

Datawarehouse greenfield implementation SAP BI on HANA; Suite BusinessObjects 4.1 introduction;

BI on SAS, Hyperion dismissed

Simple Finance, Simple Logistic

SAP CRM on HANA

Installation Re-Engineering Business Processes

Upgrade from SAP R/3 to

SAP S/4HANA

SAP BI on HANA

Installation



Context

Requirements 1



Benefits 4



Upgrade to SAP S/4HANA Capgemini Solution approach for HANA migration

Value Upgrade for HANA

Are we ready to move to HANA ?

System Prerequisite Management

Where do we deploy the Hardware ?

Deployment Options

How do we install the Software ?

Installation Options

How do we upgrade & migrate

our systems to HANA ?

Implementation Options

On going SAP

Landscape

Development Quality

Production

2 4

7

UpgradeProject

Landscape

Dual

Main

tena

nce

1 3

DEV’ QAS’ PRD’

CSB

60

Oracle DB

HANA DB

Oracle DB

HANA DB

Oracle DB

HANA DB

Oracle DB

DEV

Oracle DB

QAS

Oracle DB

PRD

Oracle DB

HANA DB

5 8



Upgrade to SAP S/4HANA System Prerequisites Management

As part of the migration offering, Capgemini provides necessary services and tools (Capture) to do the prerequisites management

EP, PI, BW – if used in conjunction with SAP Business Suite, then those SAP Netweaver Hubs have to be upgraded to 7.3 or higher before. See SAP Note 1388258

Not all SAP & 3rd party Add-Ons are currently supported

Check early: Table “CVERS“ and compare against relevant SAP Notes for each SAP application

SAP S/4HANA is based SAP NW AS ABAP >=7.40

Not supporting dual-stack installations.

Dual-stack systems must be split before migrating to HANA

Version Interoperability with SAP NetWeaver Hubs Possible Restrictions Dual-Stack Systems

SAP HANA runs natively on Unicode only

SAP Business Suite 7 i2013 is the recommended minimum release for SAP Suite on HANA

Unicode Minimum Release Levels



Upgrade to SAP S/4HANA Deployment and Installation Options

Switching to SAP HANA does not impact application servers or frontends

New SAP HANA DB HW is required, nothing else changes

SAP HANA appliance runs on SUSE Linux (SLES)

See SAP Note 1514966 (SAP HANA: Sizing SAP In-Memory Database)

Sizing for New Installations: See http://service.sap.com/sizing

ABAP sizing reports for Migration to SAP HANA: SAP Business Suite: SAP Note 1872170

Landscape Impact Sizing

Multiple components on one database (MCOD): Deploy white-listed applications together on the same HANA DB

Multiple components on one system (MCOS): Multiple SAP HANA databases

On-premise or SAP Cloud powered by SAP HANA

Scale-up: Increasing size of one server

Scale-out: horizontally by adding servers**

Virtualization

Installation Options Deployment Options

** Scale-Out installations only with restricted availability so far.



Upgrade to SAP S/4HANA Upgrade & Migration

Update the software version or Support Package Stack of a SAP NetWeaver-based system to a level supported for the migration

Replacement for SAPehpi, SAPup, SAPJup, JSPM, CEupdateManager, and SolManUp Additional Information: http://service.sap.com/sltoolset Source

SW Ver. Target

SW Ver.

Software Update Manager (SUM)

Migrate a system at the required software level required for SAP HANA Unicode conversion of an existing system as a part of the migration Installation of a new system on SAP HANA. Additional Information: http://service.sap.com/sltoolset Target

SW Ver.

Software Provisioning Manager (SWPM)

Upgrade an existing NetWeaver-based system and migrate to SAP HANA in a single step Preferred toolset for migrating to SAP HANA Additional Information: SAP Note 1799545 – Conditions: using DMO of SUM for SAP BW systems SAP Note 1875197 – Conditions: using DMO of SUM for Business Suite systems

Source SW Ver.

SAP HANA

Target SW Ver.

Database Migration Option of Software Update Manager (DMO of SUM)

SAP HANA

Target SW Ver.



Upgrade to SAP S/4HANA Installation, Upgrade & Migration using Capgemini Methodology and Tools (1/2)

Initiation Preparation

Organizational Change Management/Training

Technical Infrastructure Management

Solution Maintenance & Support

Program / Project Management

Project approval from the Business

Prepare & upgrade Dev server

Define the SAP HANA installation technique

Define the archiving scope and plan

Define the disaster recovery and High

availability plan

Create/Validate test scripts/Scenarios

Define the SAP HANA deployment strategy

Finalize the migration option

Check/plan for SAP Add-ons & Legacy systems

Project Charter & Assess dependencies

SAP Assessment & Scope

Inventory of custom objects & Interfaces

Check Solution Manager & other SAP component

Governance model & RACI

Define and agree freeze concept

Build Cutover plan

Secure new hardware/ environment from data

center & Sizing

Define GO/NO GO criteria

Workshop and Know. Trans. For AS-IS

processes

Define/detail scope and project plan

Connectivity & Logical set up

Test Strategy & Planning

Define communication & first announcement

Define & agree budget

Finalize the SAP HANA Hosting strategy

Create HANA awareness

Prepare & upgrade The Sandbox

Perform the Migration step

Check the technical sanity of the system

Adapt the ABAP guidelines based

on HANA

Check/fix SPAU/SPDD



Upgrade to SAP S/4HANA Installation, Upgrade & Migration using Capgemini Methodology and Tools (2/2)

Realization Go Live & Support

Organizational Change Management/Training

Technical Infrastructure Management

Solution Maintenance & Support

Program / Project Management

GO Decision from Business

Prepare & upgrade Dev server

Fix all issues

Finalize cut over plan and down time details

Prepare, upgrade & migrate the sandbox for

a mock upgrade

Conduct training (for delta functionality)

Transport TRs from Quality server

Perform technical and functional unit testing

Retrofit Custom dev.

Prepare, upgrade & migrate the DEV server

ABAP code adaptations for HANA compliancy

Check/fix SPAU/SPDD

Fixes & Delta Configuration

Fix the UAT issues

Load and performance test

Conduct User Acceptance Testing

Validate all Interfaces

Prepare, upgrade & migrate the Quality server

Conduct Integration testing

Transport TRs from Dev server

Fix the integration test issues

Prepare UAT plan & scripts

Prepare, upgrade & migrate the PRD server

Validate & Sign off PRD system

Go Live

Post Go Live support

Sign off SAP Upgrade project

Transport TRs from Quality server

Final Preparation



Upgrade to SAP S/4HANA Different starting points

Fiori

SAP ERP

SAP HANA

UPDATES – New functionality via EHP

TECHNICAL - InMemory Excution

ANALYTICAL - RealTime with HanaLive

OPERATIONAL - Process Optimization

SIMPLIFIC – Landscape & Processes

Innovation – Perfect Entreprise sFIN sLOG sERP …

Suite on Hana (SoH)

Fiori

SAP ERP

SAP HANA


TECHNICAL - InMemory Excution

ANALYTICAL - RealTime with HanaLive

OPERATIONAL - Process Optimization

SIMPLIFICATION - Landscape

Suite on anyDB

Fiori

SAP ERP

Any DB




Upgrade to SAP S/4HANA Different starting points

Customer running SAP ECC

< ECC 6.0 EhP7

Implement Simple Finance Add-On

DB Migration to HANA Platform

Upgrade to ECC 6.0 EhP 7

1

2

3

Customer running SAP ECC 6.0 EhP7

Implement Simple Finance Add-on

DB Migration to HANA Platform

1

2

Customer running SAP ECC

6.0 EhP7 on HANA

Implement Simple Finance,

Simple Logistics, Add-on

1



More than 1.300 end-users More than 2.500 custom objects Starting from release SAP R/3 Unicode, EhP: DB Migration Option (DMO) SAP FIORI, Screen Personas SAP Simple Finance SAP BI on HANA SAP CRM on HANA SAP Solution Manager

Upgrade to SAP S/4HANA Business Drivers on Marcegaglia

SOURCE SAP R/3 4.0b

TARGET SAP ERP on HANA

Pur preservando le aree non soggette ad evoluzioni applicative immediate, il nuovo sistema upgradato consentirà di:

Gestire dati transazionali ed analitici in modo più semplice;

Aprirsi nativamente al web e al mobile per semplificare o esternalizzare alcuni processi;

Attivare i nuovi moduli standard SAP disponibili solo su tecnologia SAP HANA;

Abilitare diversi fattori di innovazione all’interno del gestionale SAP;

Abilitare una User-Experience moderna;

Superare i limiti tecnologici degli attuali sistemi.

ACCELERATE

SIMPLIFY

INNOVATE

In-Memory Computing Traditional

Application

Database



Upgrade to SAP S/4HANA Marcegaglia use-case: technical tasks

Appl.Servers

SAP HANA db (o.s. SUSE)

R/3 4.0

ERP on HANA

ERP 6.0 on SQL

ERP 6.07 on SQL

P01

P1N P1N

P1N P1N

P1N

P1N



Upgrade to SAP S/4HANA Marcegaglia use-case: functional tasks

Solution Manager

1

System Landscape Test Management Training Authorization

Profiles

ABAP 1

Adjustment standard objects enhancements

Adjustment custom objects (interface, batch-input, others)

HANA Optimization

Customizing 1

Delta Customizing Obsolete transaction Functional

Enhancements



Upgrade to SAP S/4HANA Marcegaglia use-case: HANA Optimization

ABAP/4 Optimization, on traditional programming language, managed by different tasks: Mandatory: DB-Hints, ORDER-BY, Pool-Table Non-Mandatory: SELECT *, index, WHERE clausole

Statistical records (STAD) ABAP Trace Tool (SAT) SQL Trace (ST05) SQL Monitor (SQLM) ABAP Test Cockpit (ATC) SAP Code Inspector (SCI) SQL Performance Tuning (SWLT)

New SAP HANA native applications, UI HTML5, Native SQL-Script on SAP HANA executed in-memory and triggered from stack-ABAP Netweaver.

Application Server

SAP Netweaver 7.4

SAP HANA

SAP HANA XS SAP Fiori App Content



Upgrade to SAP S/4HANA Marcegaglia use-case: first results

SAP HANA ~ 650Gb

MS SQL ~ 3Tb

Optimized for traditional-DB Response Faster

100% 75% 22% 3%

In-Memory Computing Traditional

Application

Database



Upgrade to SAP S/4HANA Marcegaglia use-case: Target Landscape

S/4 S/4 S/4

Landscape AS-IS SAP R/3 4.0b 3Tb MS-SQL 2000, 32bit

MCOS-MCOD 512Gb

DEV QUA PRD

Landscape TO-BE SAP S/4HANA Appliance 2Tb

Landscape SAP BI on HANA Appliance 512Gb

Landscape TO-BE SAP CRM on HANA Appliance 512Gb

P01 T01 D01

BI BI BI

CRM CRM CRM



Context

Requirements 1



Benefits 4



Benefits

Business Suite on HANA SAP S/4HANA, BI, CRM on HANA

User Experience SAP Fiori, Screen Personas, Multi-Device, Multi-Interaction

Pronti per nuove future evoluzioni Business-Suite pronta ad accogliere ulteriori evoluzioni e trasformazioni

Digital Transformation in corso Al passo con i tempi in ottica trasformazione



Benefits

Business Suite on HANA SAP S/4HANA, BI, CRM on HANA

SAP HANA Platform

SAP S/4HANA SAP BI SAP CRM

Other SAP Systems Third-Party Applications Custom Applications



Benefits

https://www.youtube.com/watch?v=jFY_911ShWA

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer

User Experience SAP Fiori, Screen Personas, Multi-Device, Multi-Interaction



Benefits

No thanks! We are too

busy

Are you too busy

to improve ?

Digital Transformation in corso Al passo con i tempi in ottica trasformazione



Contacts

SAP S/4HANA installation available on Capgemini Cloud for a Demo

Marco Campi Chief Information Officer Marcegaglia S.p.A. [email protected]

https://it.linkedin.com/pub/dir/Marco/Campi

Gianluca Simeone Managing Consulting Capgemini Italy [email protected] https://it.linkedin.com/in/gsimeone @extgisi

http://www.linkedin.com/company/capgemini


http://www.twitter.com/capgemini

www.capgemini.com

The information contained in this presentation is proprietary. © 2015 Capgemini. All rights reserved. Rightshore® is a trademark belonging to Capgemini.

Capgemini Attualmente con 180.000 dipendenti in più di 40 paesi nel mondo, Capgemini è uno dei principali fornitori mondiali di servizi di consulenza, information technology e outsourcing. Nel 2014 il Gruppo Capgemini ha registrato ricavi per 10,573 miliardi di euro. Con i propri clienti Capgemini progetta e realizza specifiche soluzioni di business, tecnologiche e digitali, per soddisfare le loro esigenze di innovazione e competitività. L’organizzazione profondamente multiculturale contraddistingue da sempre il Gruppo Capgemini, che utilizza un approccio di lavoro unico e distintivo – la Collaborative Business Experience™ – e un modello globale di produzione distribuita denominato Rightshore®. Per maggiori dettagli: www.it.capgemini.com Rightshore® è un marchio appartenente a Capgemini

http://www.facebook.com/Capgemini


http://www.twitter.com/capgemini

http://www.youtube.com/capgemini

http://www.slideshare.net/capgemini

http://www.it.capgemini.com/

Business Drivers on Innovation Project of Marcegaglia · Upgrade from SAP R/3 to . SAP S/4HANA . SAP BI . ... Check/fix SPAU/SPDD . ... Sign off SAP Upgrade project . Transport TRs

Documents