Upgrade & Unicode Conversion sap basis 20 non-Unicode → sap netWeaver 0 sr1 and higher Unicode




старонка1/15
Дата канвертавання27.04.2016
Памер0.56 Mb.
  1   2   3   4   5   6   7   8   9   ...   15






Combined

Upgrade&Unicode Conversion

Guide

Upgrade & Unicode Conversion

SAP Basis 6.20 non-Unicode → SAP NetWeaver 7.0 SR1 and higher Unicode

Last update:



November 22, 2007

©


SAP AG

Neurottstraße 16

69190 Walldorf

Germany


T +49/18 05/34 34 24

F +49/18 05/34 34 20



www.sap.com
Copyright 2007 SAP AG All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Documentation on SAP Service Marketplace

You can find this documentation at the following address:



http://service.sap.com/Unicode@sap

Typographic Conventions





Type Style

Represents

Example Text

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation



Example text

Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text

Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

Example text

Exact user entry. These are words or characters that you enter into the system exactly as they appear in the documentation.



Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

EXAMPLE TEXT

Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icons

Icon

Meaning



Background



Caution



Example



Function



Note



Recommendation



Syntax



Combined Upgrade & Unicode Conversion Guide 7

Before You Start 7


Restrictions 8
Upgrade Specific Restrictions 8
Application Specific Restrictions 8
General Restrictions 9

Requirements 9
Component-specific Requirements 9
Software Requirements 10
Database Requirements for MAXDB 10
Frontend Requirements 11
Private Use Area in Unicode Systems 11

General Description 11

Chronological Order of the CU&UC Steps 13

Tools 13

Step by Step 14

1. Preparation 15

1.1 Unicode-enabled ABAP programs 15

1.2 Convert customer code pages 17

1.3 Upgrade 17

1.4 Data Maintenance 18

1.4.1 Reducing Data Volume 18
1.4.2 Pre- Conversion Correction of Table Data 18
1.4.3 Maintenance of Language Flag 19
1.4.4 Consistency Check for Cluster Tables 21
1.4.5 Archived Data after Unicode Conversion 21
1.4.6 Printing Old Spool Requests after Unicode Conversion 21

2. Unicode Preconversion Phase in Basis 6.20 21

2.1 Preconversion Analysis: SPUMG Scans 22

2.1.1 Resetting data 22

2.2 Database Check 23

2.2.1 Reset All Scans 23
2.2.2 Initialize/Edit Language Lists 24
2.2.2.1 Restrictions 24
2.2.3 SPUMG Settings 27
2.2.4 Initialize Worklist 30
2.2.4.1 Export Control Table 31
2.2.4.2 Exception List 32
2.2.4.3 Monitor 34
2.2.4.4 Status 35
2.2.4.5 SPUMG Main Log 35
2.2.5 Scan 1: Consistency Check 35

2.3 MDMP Preconversion 39

2.3.1 Manually Assign the Code Page for an Entire Table 40
2.3.2 Creating the Vocabulary 40
2.3.2.1 Scan 2: Tables without Language Information 41
2.3.2.3 Scan 3: Tables with Ambiguous Language Information 42
Invalid Language Keys 43
2.3.2.4 INDX-type Tables 44
2.3.2.5 INDX Analysis 45
2.3.3 Update Database Statistics 45
2.3.4 Maintaining the Vocabulary 46
2.3.4.1 Assignment Options 46
2.3.4.2 Vocabulary Transfer 47
2.3.4.3 Scan 4: Tables with Language Information 49
2.3.4.4 Hint Management 51
2.3.4.5 Manually Assign Language 54
2.3.4.6 INDX Repair 56
2.3.4.7 INDX Log 57
2.3.5 Scan 5: Reprocess 57
2.3.5.1 Reprocess Log 58
2.3.6 Resolving Collisions 59

2.4 Final Preparation Steps 60


3. Upgrade 62

3.1 System Uptime 62

3.1.1 Phase UCMIG_DECISION (Module Initialization) 62
3.1.2 Phase BIND_PATCH (Module Extension) 62
3.1.3 Phase UCMIG_REQINC 62
3.1.4 Phase UCMIG_STATUS_CHK1 64

3.2 Shadow System 64

3.2.1 Phase JOB_UMG_COPY_RESULTS 64
3.2.2 Phase RUN_RADCUCNT_ALL 65

3.3 System Downtime 65

3.3.1 Phase JOB_UMG_FILL_RLOAD 65
3.3.2 Phase RUN_RADCUCNT_NEW 65

3.4 Post-Upgrade Activities 65


4. Unicode Conversion Phase 65

4.1 Additional Preparation Steps in SAP NW 7.0 non-UC 67

4.2 Database Export and Import 70

4.2.1. Database Export 71
4.2.1.1. R3load Log Messages 72
4.2.2. Transfer Files to Target Host 74
4.2.3. Database Import 74

5. Unicode Conversion Completion Phase 76

5.1 First Steps 77

5.2 Conversion Completion 81

5.2.1 Completion Categories 82
5.2.2 Completion Types in SUMG 84
5.2.3 Completion Procedure 84
5.2.3.1 Automatical Completion 85
5.2.3.2 Manual Repair 86
5.2.3.3 SUMG Main Log 90
5.2.4 Resetting SUMG Data 90

6. SAP Notes 90

7. Appendix 93
6.1. Reports/Programs 93
6.2. SPUMG Message Types 96
6.3. SUMG Worklist (MDMP only) 98
  1   2   3   4   5   6   7   8   9   ...   15


База данных защищена авторским правом ©shkola.of.by 2016
звярнуцца да адміністрацыі

    Галоўная старонка