Upgrade for PLPR @ PSA Peugeot Citroën SAP potential scenario SAP Consulting Poissy - 2008, January the 23th

Upgrade for PLPR @ PSA Peugeot Citroën SAP potential scenario

SAP ConsultingPoissy - 2008, January the 23th

© SAP 2007 / Page 2

Agenda

1. System Landscape Optimization

a. Introduction

b. Client-transition service

2. CU & UC approach

3. Open points

4. Conclusion & next steps

© SAP 2007 / Page 3

Agenda


a. Introduction


2. CU & UC approach

3. Open points


© SAP 2007 / PSA MWB upgrade Page 4

SAP SLO

The SAP SLO team consists of experts for SLO issues from all areas of SAP development and consultingSLO has its own development groupand a specialized SLO consulting team

SLO Consulting

SLO Development

Experience from numerous projects

+ Successful team of consultants and developers Standardized services: The SLO service portfolio

SAP System Landscape Optimization

CU & UC


SLO – Service portfolio

Pre-defined services for typical business scenarios Service description

Standardized approach

Project plans, document templates

Full service (from planning to implementation)

Long-standing project experience

Extensive knowledge base

Configurable, extendable solutions for new requirements

SLO-specific tools Analysis tools

Conversion Workbench (CWB)

Migration Workbench (MWB)

Use of SAP standard methods and tools Legacy System Migration Workbench (LSMW), Batch Input, BAPI

Upgrade, Client Copy

System Landscape Consolidation&Harmonization

Organizational Structure Changes

Data Harmonization

Currency Conversions


SLO – System Landscape Changes

Focus Consolidate system landscapes

(production as well as non-production environments)

Change system landscape to meet changed requirements

Benefits Investment protection for your IT solutions

Cost optimization

Harmonization of business processes

Examples System analysis / system comparison

Merge clients or systems

Split clients or systems

Migrate / transfer a company code to a new or existing system

System Landscape Consolidation&Harmonization


Overview of technical methods

Conversion (using Conversion Workbench)

Change existing structures within one client / system Availability of data and document flow for all completed and open transactions in target

structure

Migration (using Migration Workbench) Transfer business objects across systems / clients

Add to / change existing structures in target system

Availability of data and document flow for all completed and open transactions in target structure in target system

Data transfer (using Legacy System Migration Workbench (LSMW)) SAP standard tool for legacy data transfer Can be used for reorganization purposes

Implement required structures Copy master data Transfer selected data (e. g. balances, open items)


1. Experience of more than 1800 reorganization projects

2. SOL Tools with pre-defined services for typical business scenarios

3. Standardized approach which is fully accepted by SAP support

4. Not related to key date

5. Data-Transfer at database level (fast access)

6. Data and document flow from all completed and open transactions can be made available in the target structure

Project on time and within budget

Fast and cost-effective implementation of changes

High quality of tried-and-tested solutions

To be sure to have a SAP supported solution

To minimize the downtime of the productive system

SLO - Optimization of existing IT landscapes

Six good reasons for SAP SLO Consulting ...

= your project success!

High degree of standardization: fast, safe, flexible and cost-efficient

© SAP 2007 / Page 9

Agenda


a. Introduction


2. CU & UC approach

3. Open points



06.12.2004BSS_Chart-library 1

Worldwide IT-integration approach

decentralizedSAP R/3 systemlandscape

Starting situation 20014.000 users

30 companies / 20 systems

regionalSAP R/3 systemlandscape

outlook for 20056.000 users

54 companies / 7 systems

BESSEurope

Juvena

AUS

Bode

USA

BASSAsia

BLASSSouth America

1. Multi Client System => Client Transfer


Customer: Marubeni Corporation

Challenges 1 SAP system replaces 10 existing systems Upgrade of the SAP R/3 system from release 3.1H to SAP R/3 Enterprise Transfer existing company code, distributed across 9 systems into a single system/server Merge purchasing organization, distributed across 4 systems into a single client/system Consolidation and Migration in a single project Successful data transfer of Marubeni-specific development into new target system Successful transfer of all historical data into new target system

Project objectives Consolidation of multiple systems System upgrade Reduction in IT infrastructure and total cost of ownership

„The system consolidation is regarded as an overall success because it helped usto reduce IT costs and to enhance the management decision-making process.“(Koji Shibagaki, General Manager, Information Strategy Department, Marubeni Corporation)

Experiences with SLO Within time and budget Efficient collaboration in the project team Intensive testing is important


Client 010

“PLPR ECC6”

Client-transition service by means of Migration Workbench - Principle

Client 010

“PLPR 4.6C”

MWB system

SAP SLO is able to run an upgrade combined with an OS/DB migration using MWB functionalities.

We’re enhancing this approach with the MDMP-Unicode-migration functionalities.

As the result of this operation ALL customizing, master and transaction data from the source client is upgraded, converted and transferred to the target client.


Realization – organization - 1

Operation done in different steps :

Functional upgrade

Test 0 Functional test cycles

Realization effort and planning will have to be validated during the assessment phase in accordance with PSA as is situation & objectives.

1 4 5

Go live

6

Project coordination

Technical preparation

Data migration &

upgrade

2 3


Realization organization – 2

1/ Functional upgrade

PSA / SAP partner / SAP consulting run all steps normally necessary for an upgrade

Functional scoping Upgrade of development / test system Delta-customizing New functionalities integration Adoption of customizing for new release-functionalities Repository adoption Adoption / enhancement of authorizations / profiles Define functional tests

Normal tasks of an upgrade project, to be discussed / checked ….



2/ Technical preparationPSA / SAP partner / SAP consulting

Creation of target ECC 6-system containing only standard customizing (already in unicode and on the right OS/DB)

Copying the development-system Customizing copy of the prod-system to this new system Delete the other "rubbish-clients" Upgrade this Apply functional upgrade changes to this new system Normal tasks of an upgrade project, to be discussed / checked ….

SAP SLO

Configure MWB



3/ Data Migration & upgrade

SAP SLO

Data migration and upgradeVerify technical completeness

4/ Test 0

PSA / SAP partner / SAP consulting & SAP SLO

Transport of all enhancements doneUnit test Reconciliation aspects



5/ Functional test cycles

PSA / SAP partner / SAP consulting & SAP SLORefresh test environmentApply functional enhancementsData migration and upgradeEntire functional testing:

– Completeness (reporting)– Document links – Business processes

Reconciliation aspects Nbr of test to be validated

6/ Go live

PSA / SAP partner / SAP consulting & SAP SLOApply functional enhancementsData migration and upgradeSupport


SLO-Migration Workbench (MWB)

DDICDDIC DDICDDIC

List of tables

List of tables

RenamesRenames

ABAP generator

ABAP generator

ControlControl

ABAPABAPABAPABAPABAPABAPWriteABAP

WriteABAP

ABAPABAPABAPABAPABAPABAPReadABAP

ReadABAP

DBDB DBDB

Source system Target system

MWB


MWB, LSMW – Where is the difference?

* If SAP standards were adhered to

Migration (MWB) Data transfer (LSMW)

How are changes made? Directly at databaselevel

SAP standard interfaces

Will data from completed transactions (history) be changed? yes no

Are changes across different releases possible?yes yes

Are changes on cross-client / cross-system level possible?

yes yes

Does document flow remain intact? possible no

Is key date visible in target system? no yes

Are customer-specific developments included? SLO Standard*

Additional workrequired

Performance, particularly for large amounts of data high low

Changes in production system System lockOnline possible for small data portions

Project depends on key date no yes


Potential IT landscape

prd / qa bis

prd / qa bis010

Rep CIC

PRDPRD

010Rep CIC

QAQA

010Rep CIC Data

Migration & Upgrade

dev bisdev bis010

Rep CIC

devdev

010Rep CIC

Upgrade

enhancements

PRD copyPRD copy

010Rep CIC

MWBMWB

Rep CIC

System copy

System copy & upgrade

Set up of an empty ECC 6-system (already in unicode

and on the right OS/DB)

© SAP 2007 / Page 21

Agenda


a. Introduction


2. CU & UC approach

3. Open points


© SAP 2007 / PSA MWB upgrade Page 22© SAP 2007 / Page 22

Scénario CU & UC


Scénario CU & UC


Scénario CU & UC

© SAP 2007 / Page 25

Agenda


a. Introduction


2. CU & UC approach

3. Open points



Open points

Understand how the different codepages are used Which are the code pages used ? Codepages aligned to company codes and controlling areas ? Code-pages mixed ?

SLO MDMP Unicode status & final availability

PSA objectives & planning

© SAP 2007 / Page 27

Agenda


a. Introduction


2. CU & UC approach

3. Open points



Conclusion – SAP remarks – 1

An alternative to the SLO approach could be to execute a CU&UM operation Having all the requirements being realised by a purely “data transfer approach” appears to

contains a significant level of risks (coherence, data integrity) Technical & economic facts

High usage of specialized tools minimize manual efforts Predefined scenarios / Preconfigured solutions Easy adaptation to cover customer specifics

SAP provides first hand technical product know-how “All inclusive” service offering from strategy to technical realization

Full range of services including project management and responsibility Choice of alternative approaches with regards to cost and time

Tool-based analysis for well-defined, reliable project estimates Unique “Tools”-based approach

Data consistency as main goal All data (customizing, master data, transaction data) included in approach Integration fully covered, consistency between applications guaranteed Standardized services provide better quality results that manual methods


Conclusion – SAP remarks – 2

Experience & knowledge SAP SLO has been participating in many merge projects worldwide in the recent years. Thus

a wide range of experiences has been gathered taking in account specific customer requirements and working in close relationship with consulting partners.

The SAP SLO approach will allow that all data from source system will be available in the target system within the wished organization.

This will facilitate the next closing operation (monthly, quarterly, yearly..), all data reporting.

And will avoid breaks in document flows, need to set up temporary work around to allow business continuation.


Next steps

Technical assessment Selection of the upgrade approach taking in account

– SAP potentials scenario– PSA constraints & objectives

Roadmap construction Technical tests execution ….


ContactsSAP France SA23-25, rue Delarivière Lefoullon - La Défense 992064 PARIS - La Défense Cedexwww.sap.com

Guillaume YvonTechnical ArchitectT +33 1 44 45 27 09M +33 6 21 09 70 76Mail: [email protected]

Jean François FlochSLO Consulting ManagerT +33 1.44.45.21.32M +33 6 16 02 36 73Mail: [email protected]

Documents

Upgrade for PLPR @ PSA Peugeot Citroën SAP potential scenario SAP Consulting Poissy - 2008, January the 23th