sap releasewechsel auf erp 6.0 unter komplexen bedingungen matthias gramm-schwarze / continental ag

SAP Releasewechsel auf ERP 6.0 unter komplexen Bedingungen

Matthias Gramm-Schwarze / Continental AG

MySAP ERP Upgrade – Matthias Gramm-Schwarze 2

MY SAP ERP Upgrade 22.01.2009Agenda

1. Project Scope

2. Involved SAP system environment

I. WAMOS (WArehouse Management and Optimization System)

II. TEMPO (Tire Enterprise Migration and Process Optimization)

III. PP (Production planning system)

3. Realization

4. Challenges & Highlights

5. Questions & Answers


MY SAP ERP UpgradeRequirements 1/2

Parallel projects has to be accomplished

Parallel projects has to be realized before and right after the going live dates.

Synchronization of development activities, based on different releases and (non-)unicode platforms.

Synchronize IT teams to one global team

Some local requirements had been done by local teams

Country / Company code specific testing has to be covered.

Reduce overall downtime to a minimum

All downtime relevant upgrade and unicode conversion activities has to be reduce to a minimum.

Realization of combined upgrade and unicode conversion (CUUC) for two SAP system environments

Start release SAP ERP 4.6C, without Unicode (UC), based on MDMP implementation

Target release ECC 6.0 with UC (technical upgrade!)


MY SAP ERP UpgradeRequirements 2/2

Going Live has to be accomplished with negative impacts to business process

Specially the following month / year end activities

Cross-system processes / Interface management

Project must be in time and in budget

In time realization was absolutely necessary due to dependencies to following project go live dates, specially at 1rd of January 2009.


Global Footprint: System WAMOS (SAP R/3)

Europe, part I

Herstal / RF/RDCAachen / PWHKorbach / RDC/PWHAskim RDCJarqlund / RDCEspoo / RDCGislaved / RDCWarschau / RDCIsernhagen / RFStöcken / SLSOtrokovice / RF/PWHTraiskirchen / RDCTimisoara / PWHStraubing / RF/EDCSacalacz / RDCUlm / RF/RDCRome / RDCSomaglia / RDCGrans / RDCMadrid / RDC----------------Total 20

Russia

Moskau / RDC

NAFTA

Gainsville / DCColumbus / DCCharlotte / PWHTexcoco / DCSan Louis Potosi / PWHMonterey / DCOntario / DCMt. Vernon (RF) / PWH-----------Total 8

Texas / DC (scheduled)Canada / DC (scheduled)

Brazil

Jundai / DCCamacari / PWH---------------------Total 2

Asia Shanghai / RDCAlo Setar / RDCMY-East / RDCMY-North / RDCMY-KO / RDCMY-KC / RDCMY-South / RDCMY-PJ / PWHMY-Central / RDCAS-Exessive / PWH---------------------------Total 10

South Africa

Johannesburg / DCCape Town / RDCDurban / RDCPort Elizabeth / PWH/RDC---------------------Total 4

Europe, part II

Lisboa / RDCLousado / PWHNeuendorf / RDCMer / RDCSarreguimine / RDCClairoix / RDC-----------------------Total 6


Upgrade WAMOSBasics

D054.6C

Q064.6C

Q054.6C

P064.6C

P054.6C

0 weeks 29 weeks-16 weeks

EU / Africa

NAFTA / Asia

Codepages (MDMP): 7( 1100 / 1401 / 1500 / 1610 / 8000 / 8300 / 8400 )Installed languages: 21( DE, EN, ES, FR, NL, SV, FI, PT, DA, NO / PL, CZ, SK, RO, HU / RU / TR / JA / ZH / ZF )


Upgrade WAMOSProject landscape

D056.0

Q066.0

Q056.0

P064.6C

P054.6C

Temp. Transport

Temp. Transport


X054.6C

Y054.6C

Y064.6C

Z066.0

Z056.0

EU / Africa

NAFTA / Asia

S056.0


Global Footprint: System TEMPO (SAP R/3)

Europe Sales Companies

GermanyBelgiumFranceItalySpainPolandHungaryPortugalAustriaSwitzerlandCzech RepublicFinlandSwedenNorwayDenmarkUnited KingdomRumaniaRussia----------------Total 20

Europe Plants

Slovakia 1Germany 3France 2Portugal 1Austria 1Czech Republic 1Romania 1------------------------------------------Total 10

Europe: 4500 UserAmerica: 1300 UserAsia: 300 UserAfrica: 200 User----------------------Total ~ 6300 User

NAFTA

SalesUSCANMexico------------Total 3

PlantsUS Charlotte

Mount VernonAldora

Mexico SLP ----------Total 4

Brazil Sales JundaiPlant Camarcari Total 2

Asia Sales China

TaiwanMalaysia

Plant Petaling Jaya

Malaysia Alor SetarAlor Gajah

Technology Centre Total 7

South Africa

Sales PEPlant PE 2


Upgrade TEMPOBasics


Codepages (MDMP): 7( 1100 / 1401 / 1500 / 1610 / 8000 / 8300 / 8400 )Installed languages: 21( DE, EN, ES, FR, NL, SV, FI, PT, DA, NO / PL, CZ, SK, RO, HU / RU / TR / JA / ZH / ZF )

D504.6C

Q504.6C

Q514.6C

Q524.6C

P504.6C

P514.6C

P524.6C

Temp. Transport

Temp. Transport

Asia

Europe / Africa

NAFTA


Upgrade TEMPOProject landscape

D506.0

Q506.0

Q516.0

Q526.0

P504.6C

P514.6C

P524.6C

X504.6C

Y514.6C

Temp. Transport

Y524.6C

Temp. Transport

Y504.6C

Z516.0

Temp. Transport

Z506.0

Z526.0


Asia

Europe / Africa

NAFTA

S506.0


MY SAP ERP UpgradeTiming

1. Preparation Phase

2. PP upgrade

3. Upgrade/Unicode

• D50 / D05

• Q51 / Q52 / Q06

• Q50 / Q05

4. BAT 1 Test IT /CKU

5. BAT 2 Central (US / Europe / Asia)

6. BAT 3 Local (US / Europe / Asia)

7. Go Live US / AS

8. Go Live Europe

Project milestones 01/08 01/0905/08 06/08 07/08 08/08 09/08 10/08 11/08 12/08

“Thanks Giving”

Hard

Frozen

Zone

“P20 upgrade”

“Christmas”

“Week 42 + 43”

“Week 35”

“Week 31 + 32”

Q-Systems available

Going Live dates


Upgrade TEMPO Phase 0: Upgrade / Unicode Preparation

D504.6C

Q504.6C

Q514.6C

Q524.6C

P504.6C

P514.6C

P524.6C

Transport

S504.6C

PREPAREUpgrade to 6.0SPDD/SPAUUC-Tools availableUC-Preparation

Z-Programs

0 weeks 29 weeks

System Copy


Upgrade TEMPO Phase 1: Implementation X50 & Upgrade D50

D506.0

Q504.6C

Q514.6C

Q524.6C

P504.6C

P514.6C

P524.6C

X504.6C

PREPAREUpgrade to 6.0SPDD/SPAUUC-Tools availableUC-PreparationZ-ProgramsUC-Migration∆ - Customizing

S506.0

Temp. Transport

-16 weeks 0 weeks 8 weeks 29 weeks

System copy


Phase 1: Upgrade D50Activities regarding temporary D-system

Soft Frozen ZoneMay 17th until Nov 9th Select ‘X50_TRANPORT’ from the attribute value list:


Phase 1: Upgrade D50Activities regarding temporary D-system

Soft Frozen ZoneMay 17th until Nov 9th Then add the X50 transport request number to the value field:

If multiple transport requests have been created in X50 for the same object, they can be combined into one new transport in D50 with the latest status. To have a complete overview in D50 you should add all related X50 transport numbers to the D50 transport ( each transport request number as a separate entry in the attributes ! )

Don’t forget to save the entries you made

All ‘doubled’ X50 transport requests in D50 have to be released and will be transported to Q5x and P5x once the new ECC 6.0 systems are available ( even though the original X50 transport has already been sent to the ‘old’ P50 ! ) in order to have all systems in sync.


Upgrade TEMPO Phase 2c: Upgrade Q-Systems

D506.0

Q506.0

Q516.0

Q526.0

P504.6C

P514.6C

P524.6C

X504.6C

Y514.6C

Temp. Transport

Y524.6C

Temp. Transport

Y504.6C



S506.0


Upgrade TEMPO Phase 2c: Upgrade BATs (Business Acceptance Test 3)

D506.0

Q506.0

Q516.0

Q526.0

P504.6C

P514.6C

P524.6C

X504.6C

Y514.6C

Temp. Transport

Y524.6C

Temp. Transport

Y504.6C

TESTING:

- Participants: ~ 430 people (Business-Keyuser + IT)

- Locations: Charlotte (NC), Vienna (A), Hanover (D), Lousado (PT), Kuala Lumpur (MY), Jundai (BR), SLP (MEX)

- Tool: SAP Solution Manager

- Test cases: ~ 100.000 (nearly 2000 cases x 50 companies)

-Result: Business sign off !!!


Begin hard frozen zone, right after sign-off.


Upgrade TEMPO Phase 3b: Performance Tuning, e.g. P52

D506.0

Q506.0

Q516.0

Q526.0

P504.6C

P514.6C

P524.6C

X504.6C

Y514.6C

Temp. Transport

Y524.6C

Temp. Transport

Y504.6C

Z516.0

Temp. Transport

Z506.0

Z526.0


UC runtime optimization

Temp. Transport

0 weeks 23 weeks 29 weeks-16 weeks


Upgrade TEMPO Phase 4b: Upgrade NAFTA / ASIA

D506.0

Q506.0

Q516.0

Q526.0

P504.6C

P516.0

P526.0

X504.6C

Y514.6C

Y524.6C

Y504.6C

PREPAREUpgrade to 6.0SPDD/SPAUUC-Tools availableUC-PreparationUC-DecisionsUC-Migration∆ - Customizing

Temp. Transport

0 weeks 26 weeks 29 weeks-16 weeks



Upgrade TEMPO Phase 4c: Upgrade Europe

D506.0

Q506.0

Q516.0

Q526.0

P506.0

P516.0

P526.0

X504.6C

Y514.6C

Y524.6C

Y504.6C


29 weeks-16 weeks 0 weeks


2

14

MY SAP ERP UpgradeGoing Live Timing: Asia and Americas

Friday, 28th of Nov 2008 Sunday, 30th of Nov 2008 Monday, 1st of Dec 2008

22 UTC !!!

M1

P1

15 18

P2

M2

24 3

P3 P4

14

P7P6

4

P5

9

P8

M3 M4

22 UTC !!!

P1

15 18

P2

20 22

P3 P4

5

P7P6

13

P5

24

P8

22 UTC !!!

M1

P1

15 18

P2

M2

23 1

P3 P4

8

P7P6

22

P5

3

P8

M3 M4

M1 M2 M3 M4

Begin of downtime for ALL systems

P06

P51

P52

System unavailability

18

Restore/Recovery duration to 4.6C

Saturday, 29th of Nov 2008

Offline Phases - Px:P1 - Conti specific upgrade preparationP2 - ECC 6.0 upgradeP3 - UC - preparationP4 - UC - exportP5 – UC - Schema implementationP6 – UC – importP7 - Post UC activitiesP8 - Conti specific post upgrade activities, incl. BAT4


IT team: coming together H - HQ

23

24

MY SAP ERP UpgradeGoing Live Timing: Europe

Wednesday, 24th of Dec 2008

Thursday, 25th of Dec 2008

Friday, 26th of Dec 2008

12 UTC !!!

M1

P1

Release of ECC 6.0Begin of downtime

Saturday, 27th of Dec 2008

10 13

P2

M2

18 20

P3 P4

5

P7P6

13

P5 P8

M3 M4

14

Sunday, 28th of Dec 2008

13

M5

15

P9

812 UTC !!!

M1

P1

5 8

P2

M2

19 1

P3 P4

13

P7P6

3

P5 P8

M3 M4

14 13

M5

15

P9

P05

P50

3

System unavailability Restore/Recovery duration to 4.6C

Buffer

Buffer

8

8

Offline Phases - Px:P1 - Conti specific upgrade preparationP2 - ECC 6.0 upgradeP3 - UC - preparationP4 - UC - exportP5 – UC - Schema implementationP6 – UC – importP7 - Post UC activitiesP8 - Conti specific post upgrade activities, incl. BAT4


MY SAP ERP UpgradeChallenges & Highlights 1/2 (related to this project)

Communication is all !!!

In case of outsourcing: Integrate your outsourcing partner as soon as possible.

“Distribute presentation and pick up the phone.”

Start archiving and reorganization as soon as possible

Expand the retention periods for archiving objects (Business alignment !!!)

Use “SAP Data Management Guide” for large tables.

Always use newest Unicode Tools

Newest SPUM4 and SPUMG transaction updates provides necessary features, specially for large database/tables.

Only use proven UC tools! SAP quality assurance has not take place in this area.

Become familiar with the UC tools.

Check out default settings for specific tables (default code page!)


MY SAP ERP UpgradeChallenges & Highlights 2/2 (related to this project)

Use native speaker for unicode conversion

Train them in using SPUMG & SPUM4 transactions

Specially for large systems with many different languages, use native speaker.

Use “SAP upgrade coach”

Specially during UC conversion tests

Focus on UC conversion (within this project!)

Use appropriate testing tool

Usage of SAP Solution Manager was the right decision.

Interface handling easier than expected

By usage of central message hub (SAP XI)


Questions?

otherwise

Thanks for your attention!

MY SAP ERP Upgrade

sap releasewechsel auf erp 6.0 unter komplexen bedingungen matthias gramm-schwarze / continental ag

Documents

south rdc

east rdc

central rdc

ko rdc

north rdc

kc rdc

sap erp upgrade requirements

release sap erp