Agenda

1.

Focus on Unicode Conversion

2.

Monet program context

Copyright 2011 Accenture All Rights Reserved.

Monet Program
Unicode Migration steps

The minimum SP levels for the Unicode Conversion is SAP_BASIS 7.00 SP15 or
SAP_BASIS 7.00 EhP 1 SP03. The main Unicode conversion steps are listed in the following table :
Phase Action Consistency Check for Cluster Tables Conversion of customer-defined Code Pages Preparation Make ABAP Programs Unicodecompliant Reducing Data Volume Language Flag Maintenance Additional Preparation Steps SPUMG Database Check Final Preparation Steps Database Conversion Conversion Completion Unicode Conversion Phase Final Steps in the Unicode System SPUMG and Statistics Update Generate nametabs Create the Unicode database Run final reports and maintain tables System Copy (downtime) Post-Processing Steps (downtime) Purpose Check and analyze inconsistencies in Cluster Tables Required if own code pages exist (ex.: printer code pages) Check that all customer programs are Unicode-enabled (UCCHECK) Ensure that obsolete table entries are deleted and that the Text Lang flag is correctly set for all tables Run transaction SPUMG to check the consistency of the database Preconversion (uptime) When

Planning Phase (weeks before preconversion)

Copyright 2011 Accenture All Rights Reserved.

Monet Program
Unicode Conversion scenarios
The Unicode Conversion is done through an export/import of the SAP database. There are 2 main
scenarios for Unicode conversion :

Scenario 1 : Export on the SAP source system and import on the SAP target system are done sequentially. This scenario is generally used when the source system and the target sytem are located on 2 different datacenter

Files transfer

Scenario 2 : Export on the SAP source system and import on the SAP target system are done in parallel. This scenario is generally used when the source system and the target system are on the same datacenter

Copyright 2011 Accenture All Rights Reserved.

Monet Program
Unicode Conversion down time factors

The down time estimation is given by the ABAP program UMG_R3LOAD_RUNTIME_PREDICTION The relevant technical factors for conversion down time are the following :
Conversion scenario :
Export/import phases done in parallel Export/Import phases done sequentially

Hardware :
Export : Source DB host CPU Source DB host IO Application server CPU for export Import Application server CPU for import Target DB host CPU Target DB host IO

Database :
Database size

Others :
Time to backup the system
Copyright 2011 Accenture All Rights Reserved.

Monet Program
Unicode Conversion down time optimization

The main possibilities to reduce the conversion down time are the following :
Splitting large tables : Large tables are processed in many small packages Parallelize the export and import process (Migration Monitor)

Distribute export and import jobs among additional machines (Distribution Monitor)

Optimize Database settings (OSS note 936441)

Copyright 2011 Accenture All Rights Reserved.

Monet Program
Unicode Hardware impact

The Unicode conversion has a technical impact on the hardware requirements (see
table hereunder)
Technical component CPU RAM Network bandwidth Database size Unicode impact +10% +50% 0% +10% Comment Modern processors showed 10% increase SAP Application servers are based on UTF-16 No impact on network requirement +10% is the observed maximum increase for large ORACLE database (DB size > 200 Go)

Copyright 2011 Accenture All Rights Reserved.

Agenda

1.

Focus on Unicode Conversion

2.

Monet program context

Monet Program
Unicode Neopost context
Context
Neopost decided to include the Unicode conversion into the Monet V1 project. Unicode is necessary to deploy the Monet core model in Asia (so the Unicode conversion after the deployment is not studied here)

Complexity
The Monet program V1 is built on the hypothesis of a technical merge with a complexity factor : an IT transformation project (SAP platform and datacenter renewal) run in parallel

Question
What is the good strategy for the Unicode conversion ?
Scenario 1 : Setup the project environments by copy and run afterwards the Unicode conversion Scenario 2 (alternative) : Merge the move and unicode operations in one step (export/import phase in common). In this case, these operations are a pre-requirement to the Monet program

Preferred answer
Our recommendation is the scenario 1 because :
The risk is reduced because operations are done in sequence The Unicode conversion is independent of the move operations Schedules are less interdependent.

Copyright 2011 Accenture All Rights Reserved.

Monet Program
Unicode System Landscape and software logistic
The system landscape and the software logistic could be :
1
Project Line (Unicode) 1. Unicode conversion 2. Monet customizing / developpement

DEV MONET
Copy

INT MONET
Copy

PRE PROD MONET

Copy

OT report

Production Line (Non Unicode)

DEV OASIS

INT OASIS

PRE PROD OASIS

PROD OASIS

New Production Line (Unicode)

DEV MONET

1. Unicode conversion 2. Monet customizing / developpement

INT MONET

PRE PROD MONET

PROD MONET

Old Production Line (Non Unicode)

DEV OASIS

INT OASIS

PRE PROD OASIS

Copyright 2011 Accenture All Rights Reserved.