UC_master_guide_SAP.doc

8/14/2019 UC_master_guide_SAP.doc

1/38

Single Code Page System Conversion to Unicode NW 7.01

Single Code Page System Conversion to Unicode .....3

Restrictions ......................................................................4

Requirements...................................................................4

eneral !escri"tion ........................................................#

C$ronological %rder o& t$e Conversion Ste"s.............'

1. Pre"aration...................................................................7

1.1 Consistency C$ec( &or Cluster )a*les......................................7

1.+ Conversion o& customer,de&ined code "ages...........................7

1.3 -a(e /P "rograms Unicode,com"liant................................

1.4 !elete -atc$code !s................................................................10 1.# Reducing !ata 2olume..............................................................10

1.#.1 Pre,Conversion Correction o& )a*le !ata.............................10

1.' anguage lag -aintenance.....................................................1+

1.7 Printing %ld S"ool Requests a&ter t$e Unicode Conversion.13

1. %) !ocuments a&ter t$e Unicode Conversion......................13

1.5 )ranslation 6nvironment ..........................................................14

+. Unicode Preconversion P$ase.................................14

+.1 SPU-.............................................................................14

+.1.1 Restart SPU-........................................................................14 +.1.+ Welcome to SPU-................................................................14

+.1.3 6ce"tion ist..........................................................................14

+.1.4 dditional Pre"aration Ste"s.................................................1#

+.1.# anguage ist..........................................................................1

+.1.' SPU- Settings......................................................................15

+.1.7 nitiali8ing t$e Wor(list...........................................................15

+.1. Consistency C$ec( ................................................................+0

+.+ inal Pre"aration Ste"s .................................................++

+.+.1 SPU- U"dates .....................................................................++ +.+.+ C$ec( -atc$code !s.............................................................+3

+.+.3 Nameta* $andling...................................................................+3

+.+.4 )a*les 9it$ o*solete data.......................................................+4

+.+.# dditional !o9ntime Ste"s.....................................................+#

3. Unicode Conversion P$ase......................................+'

3.1 !ata*ase 6"ort and m"ort..........................................+7 3.1.1 !ata*ase 6"ort......................................................................+

3.1.+ )rans&er iles to )arget :ost ................................................31

3.1.3 !ata*ase m"ort......................................................................31

+005,01,1#

1


2/38


3/38


Single Code Page System Conversionto UnicodeSP NetWeaver 7.0 including 6$P 4

Pur"ose

This document details the steps necessary to convert an existing non-Unicode SAP Systemwith one standard non-Unicode system code page to Unicode.

2alidity

The Unicode Conversion is released for Single Code Page systems on release SAP Basis.!" and higher. #f your system is running on a lower SAP Basis release$ you must upgradefirst and convert afterwards or use the procedure descri%ed in SAP &ote '!()!'.

!ocumentation

There are several Single Code Page Conversion *uides availa%le for download from SAP&ote+",+,).ae sure you have downloaded the correct version of the Single Code PageConversion to Unicode *uide. This document is valid for SAP &/ )."+.

#n addition to the 0Single Code Page Conversion to Unicode *uide1 you need the SystemCopy *uide for your release. The System Copy *uide is re2uired for the Unicode ConversionPhase which is in fact a System Copy procedure with special code page settings. 3ou candownload the valid System Copy *uides from the SAP Service aretplace at4

http455www.service.sap.com5install&/)"#nstallation$ section System Copy for 67P+ S8+4ABAP$ABAP 9 :ava.

:o9 to c$ec( i& t$e system is a Single Code Page System

#f you are not sure whether your system is a Single Code Page system or not$ open data%ase

ta%le TCP;B in transaction S6+. #f this ta%le contains only one entry$ it is a Single CodePage system.

#f TCP;B contains more than one entry$ the system is an ;P system.

m"ortant SP Notes

SAP &otes mentioned in this document contain reports or corrections for download$ oradditional information which is su%


4/38


Application-specific information

,="'++ 0Unicode restrictions for 85> 6nterprise$ 6CC ,."$ 6CC ."14

Component-specific restrictions

)'''+ 0ulti-?anguage and Unicode support of mySAP solutions14

8ecent information a%out Unicode-ena%led mySAP solutions

),=), 0Unicode Conversion4 Trou%leshooting14

Trou%leshooting *uide for Unicode Conversions

Restrictions+. The conversion of systems using code page (>=" @7ong ong Supplementary CharacterSet are only availa%le as on a "ro=ect *asis 9it$ SP involvement. See !.+.,?anguage ?ist page +(D for details. ;ownload the supplementary documentation0Conversion of 7SCS Systems to Unicode1 from SAP &ote ,,+>==.

!. 3ou can not install a Unicode system with a non-Unicode system in one data%ase@CE;.

!/+,8;%S4 8ead SAP &ote +"(!+,for information a%out CE; with Unicode and non-Unicode systems on ;B!-F5ES.

>. SAP Unicode systems are not released for #nformix. See chapter>. Unicode ConversionPhase page!!Dfor details a%out data%ase change and simultaneous Unicode

conversion.=. Conversion from Unicode to non-Unicode is not possi%le.

,. Third Party products4 #f you are using software from other vendors$ chec whether it isUnicode-compliant . Note t$at >SP certi&ied? does not im"ly >Unicode com"liance?.

. &ote the restrictions for Unicode Solution anager monitoring non-Unicode systems withax;B data%ase @SAP &ote '!=,".

). B/ systems4 Gollow SAP &ote )>,>>*e&orestarting Unicode conversion of B/systems. Etherwise pro%lems during data extraction can occur after the conversion.

RequirementsSo&t9are Requirements

ae sure that all re2uired ;H;s for the system copy are availa%le. Gor details$ refer to theSystem Copy *uide$ sections Planningand Database Independent System Copy.

rontend Requirements

Requirements4 SAP recommends that you install SAP *U# ).+" with thelatest Patch ?evel.
https://service.sap.com/~sapidb/012006153200001591522002E.ITFhttps://websmp102.sap-ag.de/~sapidb/011000358700009560682001E.ITFhttp://service.sap.com/sap/support/notes/765475https://service.sap.com/sap/support/notes/551344http://service.sap.com/sap/support/notes/1068215http://www.service.sap.com/sap/support/notes/924650http://www.service.sap.com/sap/support/notes/673533http://www.service.sap.com/sap/support/notes/673533https://service.sap.com/~sapidb/012006153200001591522002E.ITFhttps://websmp102.sap-ag.de/~sapidb/011000358700009560682001E.ITFhttp://service.sap.com/sap/support/notes/765475https://service.sap.com/sap/support/notes/551344http://service.sap.com/sap/support/notes/1068215http://www.service.sap.com/sap/support/notes/924650http://www.service.sap.com/sap/support/notes/673533


5/38


!ocumentation4 0SAP*U# for /indows4 #+(& User *uide14 3ou candownload this documentation from SAP &ote ,"((,=

Status4 re2uired.

&ote

Gor full support of languages with multi-%yte system locales @:apanese$ Traditional Chinese$Simplified Chinese and orean SAP *U# for /indows .=" or higher is re2uired.

Com"onent,s"eci&ic Requirements

+. #f you use 78 functionality in your SAP system$ you have to process additional stepswhich are descri%ed in SAP &ote,)>"==.

Caution

#f you perform the standard procedure without the additional steps$ data loss will %e theresult. SP does not ta(e any res"onsi*ility in t$is case@

!. #f you use SAP Effice functionality in your SAP system$ read SAP &ote '+=")for furtherinformation on Unicode conversion.

>. #f you use the SAP liveCache tool$ read SAP &ote >!>,)@SC =." and higher forinformation a%out %acing up the liveCache data %efore the system conversion.

=. #f you use the Credit Card 6ncryption function$ note that all encrypted card num%ers aredecrypted *e&orethe Unicode Conversion. Gollow the instructions in SAP &ote ))">.

,. #f you use SAP 6asy ;ocument anagement @6asy;S$ follow the instructions in SAP&ote+",+)".

. Conversion of C8 systems4 &ote that Business Transaction duration data must %esaved *e&orethe Unicode Conversion. Gollow SAP &ote ++!!'(.

). #f you use Automatic Payment Transactions @Payment Program5Payment Transfer$ readSAP &ote+>'"!!'.

(. #f you use a Content Server @;ocument anagement Services$ follow the instructions inSAP &ote++!+"(.

Private Use rea in Unicode Systems

Customers with Asian system code pages @:apanese$ orean$ Simplified Chinese$ andTraditional Chinese that have %een using the user defina%le areas are advised to read SAP

&ote)!',=to chec the mapping of the user defined characters to Unicode.

eneral !escri"tionTo convert a non-Unicode system to Unicode$ all character data @i.e. text data in the non-Unicode data%ase must %e converted to Unicode. The overall conversion procedure is aSystem Copy with special code page settings. The actual data conversion to Unicode is doneduring the export. Gor further information a%out system copy optimiFation$ go towww.service.sap.com5systemcopyoptimiFation.

+005,01,1#

#
https://websmp104.sap-ag.de/~sapidb/012006153200000066352002E.ITFhttps://websmp102.sap-ag.de/~sapidb/012006153200001915872002E.ITFhttps://websmp102.sap-ag.de/~sapidb/012006153200001915872002E.ITFhttps://websmp102.sap-ag.de/~sapidb/012003146900000323992003E.ITFhttps://websmp203.sap-ag.de/~sapidb/012006153200000525952003E.ITFhttps://websmp203.sap-ag.de/~sapidb/012006153200000525952003E.ITFhttp://service.sap.com/sap/support/notes/766703http://service.sap.com/sap/support/notes/766703http://www.service.sap.com/sap/support/notes/1056170http://www.service.sap.com/sap/support/notes/1056170http://www.service.sap.com/sap/support/notes/1056170http://www.service.sap.com/sap/support/notes/1122968http://www.service.sap.com/sap/support/notes/1390229http://www.service.sap.com/sap/support/notes/1390229http://www.service.sap.com/sap/support/notes/1390229http://www.service.sap.com/sap/support/notes/1612108http://www.service.sap.com/sap/support/notes/1612108http://www.service.sap.com/sap/support/notes/1612108https://websmp102.sap-ag.de/~sapidb/012006153200000132722004E.ITFhttps://websmp102.sap-ag.de/~sapidb/012006153200000132722004E.ITFhttps://service.sap.com/systemcopyhttps://websmp104.sap-ag.de/~sapidb/012006153200000066352002E.ITFhttps://websmp102.sap-ag.de/~sapidb/012006153200001915872002E.ITFhttps://websmp102.sap-ag.de/~sapidb/012003146900000323992003E.ITFhttps://websmp203.sap-ag.de/~sapidb/012006153200000525952003E.ITFhttp://service.sap.com/sap/support/notes/766703http://www.service.sap.com/sap/support/notes/1056170http://www.service.sap.com/sap/support/notes/1122968http://www.service.sap.com/sap/support/notes/1390229http://www.service.sap.com/sap/support/notes/1612108https://websmp102.sap-ag.de/~sapidb/012006153200000132722004E.ITFhttps://service.sap.com/systemcopy


6/38


C$ronological %rder o& t$e Conversion

Ste"s

P$ase ction Section Pur"ose W$en

Preparation Code pagesand programs

ConsistencyChec for ClusterTa%les

page)D

Chec andanalyFeinconsistencies inCluster Ta%les

Planning Phase

@wees %eforepreconversion

Conversion ofcustomer-defined

Code Pagespage)D

8e2uired if owncode pages exist

@ex.4 printer codepages

ae ABAPProgramsUnicode-compliantpage(D

Chec that allcustomerprograms areUnicode-ena%led.

Ta%les andTa%le entries

8educing ;ataHolume page +"D

?anguage Glagaintenancepage+!D

AdditionalPreparation Stepspage+,D

6nsure thato%solete ta%leentries are deleted

and that the TextLang.flag iscorrectly set for allta%les.

;ata%aseChec

;ata Analysis SPU* page+=D 8un transactionSPU* to checthe consistency ofthe data%ase.

Preconversion

@uptime

Updates

&ameta%7andling

AdditionalPreparationSteps

Ginal PreparationSteps page!!D

SPU* andStatistics Update

*eneratenameta%s

;ata%aseConversion

6xport @incl.Conversionand #mport

UnicodeConversion Phasepage!!D

Create theUnicode data%ase

System Copy

@downtime

Conversion

Completion

GinaliFation Girst Steps in the

Unicode System

8un final reports

and maintain

Post-Processing


7/38


page >> D ta%les Steps

@downtime

NoteA

The authoriFation profile re2uired for the entire system conversion process is SAPIA??.

1. Pre"aration1.1 Consistency C$ec( &or Cluster )a*les

Programs4 8eport S;B#IC?UST68IC76C

!ocumentation4 SAP &otes +>=(",,J+"))=">

Status4 mandatory.

3ou use report S;B#IC?UST68IC76Cto search for initial cluster records in cluster ta%les.#nitial cluster records must %e removed %efore the data%ase exportJ otherwise the exportmight cancel. SAP &ote +>=(",,provides a description of the report and explains how toproceed when initial cluster records are found. Gor information a%out the latest version of thereport$ read SAP &ote +"))=">.

S;B#IC?UST68IC76C is not restricted to systems which will %e converted to Unicodeafterwards. 3ou can use it as a regular maintenance tas in all systems. 3ou can execute thereport anytime and as often as needed independent from SPU*.

The runtime of S;B#IC?UST68IC76C is dependent on the siFe of the ta%le clusters. &otethat for very large ta%le clusters it might tae up to several days. )$ere&ore you s$ouldeecute t$is c$ec( at a very early stage o& t$e Unicode Conversion Pro=ect .

6xecute report S;B#IC?UST68IC76C in transaction S6>(. En the selection screen

choose Execute Cluster Checkand press . En the next screen select ProgramExecutein Backgroundfrom the menu %ar. #f the overall status of the last chec run contains errors$follow the instructions in SAP &ote +>=(",,.

1.+ Conversion o& customer,de&ined code "ages

Customer code pages which %egin with K'K must %e converted to comply with the new$Unicode-%ased code page structures. #n most cases such code pages are printer codepages.

Programs4 8SCP"+!

!ocumentation4 SAP &otes=(,=,,and ,++)>!J,>=)!"Jonline documentation intransaction SCP

Status4 mandatory @only if code pages 'xxx exist..

Remote Code Page C$ec(

+005,01,1#

7
http://www.service.sap.com/sap/support/notes/1348055http://www.service.sap.com/sap/support/notes/1348055http://www.service.sap.com/sap/support/notes/1077403http://www.service.sap.com/sap/support/notes/1348055http://www.service.sap.com/sap/support/notes/1077403http://www.service.sap.com/sap/support/notes/1348055http://www.service.sap.com/sap/support/notes/1348055https://websmp202.sap-ag.de/~sapidb/011000358700000138172002E.ITFhttps://websmp202.sap-ag.de/~sapidb/011000358700000138172002E.ITFhttps://service.sap.com/sap/support/notes/511732https://service.sap.com/sap/support/notes/511732https://service.sap.com/sap/support/notes/534720https://service.sap.com/sap/support/notes/534720http://www.service.sap.com/sap/support/notes/1348055http://www.service.sap.com/sap/support/notes/1077403http://www.service.sap.com/sap/support/notes/1348055http://www.service.sap.com/sap/support/notes/1077403http://www.service.sap.com/sap/support/notes/1348055https://websmp202.sap-ag.de/~sapidb/011000358700000138172002E.ITFhttps://service.sap.com/sap/support/notes/511732https://service.sap.com/sap/support/notes/534720


8/38


Programs4 U*IC76CI8GC

!ocumentation4 online documentation in transaction S6>(

Status4 recommended.

Before the Unicode Conversion it is useful to chec your own TCP5#P-connections and ad( as descri%edin the online documentation to chec if the connection %etween the local system where yourun U*I8GCIC76C and a remote TCP5#P destination is consistent regarding theinvolved local and remote code pages.

#n a connection %etween a non-Unicode single code page system A and a remote non-Unicode single code page 8GC client or server B the code pages must match.

&ote

3ou can run U*IC76CI8GC in non-Unicode Systems only.

1.3 -a(e /P "rograms Unicode,com"liant

Enly programs that comply with the stricter ABAP .+" syntax and semantics will run in aUnicode system. 3ou must ensure that4

+. All your own programs are ABAP .+" compliant.

!. All SAP programs you modified @SAP &ote ,=("+ L including customer exits thatyou use @SAP &ote ,='+=> - are ABAP .+" compliant.

To determine which SAP programs you modified$ run transaction S6',.

Programs4 transactions UCC76C and SCEH

!ocumentation4 transaction ABAP76?P$ search with eyword KUnicodeKSystem ;ocumentation in UCC76C and SCEHSAP &otes4 >))J,='+=>J,=("+J++>'>!,@general information$additional helper tools$ etc.

Asian @especially orean customers4 SAP &ote +"")")>

Status4 mandatory.

8un UCC76C and enter the programs you want to chec4 all o%


9/38


or warnings for static errors$ or where potential errors are possi%le$ %ut some errors can only%e detected at runtime. 3ou can monitor your testing with SCEH.

&ote

#f you use C5C99 programs$ they must also %e Unicode-ena%led @see 8GC-;ocumentationon SAP Service aretplace. *o to service.sap.com5rfc-li%rary. Select edia Library8GC ?i%rary *uide.

Unicode 6n$anced Synta C$ec(

The system profile parameter abap/unicode_check=oncan %e used to enforce theenhanced syntax chec for all o%!+)+= P6">4 Technical information on features

=')(," Condition maintenance reports and Unicode

,>=+) Unicode indicator for BE8 o%


10/38


1.4 !elete -atc$code !s

B)$is section is only required &or Su""ort Pac(ages lo9er t$an SP07. Wit$ SP07 and

$ig$er )W)%%01 is included in re"ort U-D!!D!%WN)-6DS)6PS.E

Program4 T/TEE?"+

!ocumentation4 SAP &ote!=("

Status4 re2uired.

8un report T/TEE?"+ to find all active pool-matchcode #;s. This is important %ecausematchode #;s are not supported in Unicode SAP systems and must %e handled %efore theUnicode Conversion as descri%ed in SAP &ote !=(".

NoteA

#t is recommended to run T/TEE?"+ at this point of time during the Unicode ConversionPro.

;o not start the 6xport %efore all matchcode #;s have %een deletedO 8un this report untilmessage 0Chec successful$ no action necessary1 is shownO

1.# Reducing !ata 2olume

#f not descri%ed differently in the relevant SAP &otes$ you can carry out all the steps in thischapter during system uptime.

This section provides information a%out ta%les which show the largest growth in data volume.

The content of this section relates to data gathered in systems with SAP 85> 8elease =." andlater. Before starting the Unicode preconversion SAP recommends that you delete and5orarchive o%solete data from these ta%les in order to improve the system performance duringthe conversion procedure.

!ocumentationA SAP &ote)'=,J SAP &ote +=!!(!!J SAP &ote >(!,(J;ataanagement *uide.

3ou can download the !ata -anagement uidefrom the SAPService aretplace4 http455service.sap.com5ilm;ata Archiving.

StatusA recommended

8ead SAP &ote )'=, for details. 8ead the 0;ata anagement *uide1 for detailedinformation on how to maintain ta%les with large data volume in all SAP 85> systems.

Gollow the steps descri%ed in SAP &ote +=!!(!!.

1.#.1 Pre,Conversion Correction o& )a*le !ata

#f you have carried out a pro


11/38


SP )ec$nology /usiness Services , dress -anagementA

)a*lesA A;8C and A;8P ta%les

!ocumentationA SAP &ote)>'=+

StatusA recommended

SAP recommends that you maintain corrupt records in A;8C and A;8P ta%les according toSAP &ote )>'=+.

FC- ta*les GConversion )a*lesHA

)a*lesA C Qta%leInameR

!ocumentationA System Copy *uide$ Section Technical PreparationsKJ

SAP &ote'>(,

StatusA recommended

;elete C ta%les from the source system as descri%ed in SAP &ote '>(,.

/W System conversionsA

)a*les4 Ta%les starting with 5B#"5"

!ocumentation4 SAP &ote=='('+

Status4 mandatory

;elete temporary data%ase o%>>'=

StatusA mandatory

There are wrong master language entries for AGS o%>>'=.

!oc nter&ace;6A %rgani8ing t$e c$ange "ointer log ta*lesA

)a*leA B;CP$ B;CPS$ B;CP!

!ocumentationA SAP &otes>",=!$ ,+>=,=$ )>'!+"

StatusA mandatory

There are two options for handling the change pointer log ta%les4

+. 3ou use the change pointer storage as descri%ed in SAP &ote >",=!.

Use report 8B;CPC?8 to maintain B;CP! according to SAP &ote ,+>=,=. Usereport T8B;CPC?8 to maintain B;CP and B;CPS according to SAP &ote)>'!+".

!. 3ou use the old change pointer storage.

Use report 8B;CPC?8 to maintain B;CP and B;CPS according to SAP &ote

,+>=,=. 3ou do not need to maintain B;CP!.

+005,01,1#

11
https://service.sap.com/sap/support/notes/673941https://service.sap.com/sap/support/notes/673941https://service.sap.com/~sapidb/011000358700000972722004Ehttps://service.sap.com/sap/support/notes/9385https://service.sap.com/sap/support/notes/9385https://service.sap.com/sap/support/notes/449891https://service.sap.com/sap/support/notes/449891https://service.sap.com/sap/support/notes/1363394https://service.sap.com/sap/support/notes/1363394https://service.sap.com/sap/support/notes/1363394http://www.service.sap.com/sap/support/notes/305462http://www.service.sap.com/sap/support/notes/305462https://service.sap.com/sap/support/notes/513454https://service.sap.com/sap/support/notes/739210https://service.sap.com/sap/support/notes/673941https://service.sap.com/~sapidb/011000358700000972722004Ehttps://service.sap.com/sap/support/notes/9385https://service.sap.com/sap/support/notes/449891https://service.sap.com/sap/support/notes/1363394http://www.service.sap.com/sap/support/notes/305462https://service.sap.com/sap/support/notes/513454https://service.sap.com/sap/support/notes/739210


12/38


)$is ste" is only required in SP 01;0+;03. Wit$ SP 04 it is included in re"ortU-D!!DPR6PDS)6P.

)erminology and glossary tet ta*les Ge.g. S)6R-D)6I)HA!ocumentationA SAP &ote+!("='=

StatusA mandatory

Terminology and glossary text ta%les @e.g. ST68IT6MT with 6& language ey containsome entries with non-)%it ASC## characters. Such entries are o%solete and should %edeleted. 8un report T68I;6?6T6I#&CE886CTIC7A8S6T as descri%ed in SAP &ote+!("='=.

)$e last t9o ste"s in t$is c$a"ter are only required in SP 01;0+. )$e corrections aredelivered 9it$ SP 03.

P,P,/A S"ecial $andling &or ta*le )#6!) requiredA

)a*leA T,*6G;ATA

!ocumentationA SAP &ote+!>',,)

StatusA mandatory

T,*6G;ATA is a container ta%le$ i.e. structured data @text and %inary data are stored in thecharacter lie field T,*6G;ATA-;ATA+. Gor the Unicode preparation a special handling hasto %e done for ta%le T,*6G;ATA$ taing the su%structure of the container field into account.

Gollow the description in SAP &ote +!>',,).

S"ecial $andling &or ta*le !/)/% requiredA

)a*leA ;BTAB?E*

!ocumentationA SAP &ote+!,,,,

StatusA mandatory

;BTAB?E* is a container ta%le$ i.e. structured data @text and %inary data are stored in thecharacter lie field ;BTAB?E*-?E*63. Gor the Unicode preparation a special handlinghas to %e done for ta%le ;BTAB?E*$ taing the su%structure of the container field intoaccount.

Gollow the description in SAP &ote +!,,,,.

1.' anguage lag -aintenance

As of 8elease .!" all ?A&* fields have a ;ata ;ictionary @;;#C attri%ute Text Lang.@indicator for a language field. This flag specifies that the ?A&* field determines the codepage of the character data in that ta%le. Text Lang.flags are evaluated during 8GCcommunication %etween Unicode and non-Unicode systems to ensure that the correctcharacter conversion is used.

The flags are not re2uired in SPU*$ %ut will %e evaluated %y 8>trans during transports.After the conversion the flags are re2uired for communication via 8GC.
https://service.sap.com/sap/support/notes/1280494https://service.sap.com/sap/support/notes/1280494https://service.sap.com/sap/support/notes/1280494https://service.sap.com/sap/support/notes/1239557https://service.sap.com/sap/support/notes/1239557https://service.sap.com/sap/support/notes/1239557http://www.service.sap.com/sap/support/notes/1255556http://www.service.sap.com/sap/support/notes/1255556http://www.service.sap.com/sap/support/notes/1255556http://www.service.sap.com/sap/support/notes/1255556http://www.service.sap.com/sap/support/notes/1255556https://service.sap.com/sap/support/notes/1280494https://service.sap.com/sap/support/notes/1239557http://www.service.sap.com/sap/support/notes/1255556http://www.service.sap.com/sap/support/notes/1255556


13/38


ae sure you run the most recent version of 8A;&T?A&*. SAP &ote =(")+providesa detailed and release-specific documentation of the text flag handling.

8un report 8A;&T?A&*page >)D to set the Text Lang.flag for all ta%les with one

?A&*5SP8AS field. This report should %e run in the %acground$ since it may tae severalhours.

There are special cases when the flag should %e turned off after 8A;&T?A&* has run4

The ?A&* field does not specify the code page of the character data in the ta%le$ %utsome other language property. #n this case the Text Lang.flag must %e turned off toensure that the data is not converted with the wrong code page.

/hen a ta%le has more than one ?A&* field$ only onemay %e set. Gor ta%les withmore than one ?A&* field$ there are two possi%le options4

a. 6ither one of the ?A&* fields determines the code page of the data and the

Text Lang.flag must %e set for the correct field$ or

%. neither of the ?A&* fields determines the code page of the data and theText Lang.flag should not %e set for either of the ?A&* fields

/hen 8A;&T?A&* is finished$ SAP recommends resetting all nameta% %uffers. 6nter 5&A in the transaction code field and press 6&T68.

Transports into a system can cause the Text ?ang. flag value to %e overwritten. #t is thereforenecessary to @rerun 8A;&T?A&* directly %efore the Consistency Chec in order toactualiFe the flags.

But note that the Text lang.flag maintenance must also %e finished %efore the ConsistencyChec is started. #f you do any changes as descri%ed in this section after the Consistency$you must reset the changed ta%les and rerun the Consistency Chec for those ta%les.

After you have run 8A;&T?A&* please read SAP &ote )!(>,carefully. 3ou will findinformation a%out how to maintain special ta%les which could %e affected %y wrong dataconversion after the Text lang. flag has %een set.

1.7 Printing %ld S"ool Requests a&ter t$e Unicode Conversion

After the conversion it will %e pro%lematic to print out spool re2uests which have %een created%efore the conversion. There is no possi%ility to recover the spool re2uests after the Unicodeconversion.

8ead SAP &ote (=!)).3ou will f ind a step-%y-step description on how to handle such spoolre2uests %efore %eginning the conversion procedure.

1. %) !ocuments a&ter t$e Unicode Conversion

ETG documents that were created %efore the Unicode conversion can not %e processed after

the Unicode conversion and they cannot %e created again in the Unicode system. To save

+005,01,1#

13
https://websmp202.sap-ag.de/~sapidb/011000358700011747102001E.ITFhttps://websmp202.sap-ag.de/~sapidb/011000358700011747102001E.ITFhttps://websmp202.sap-ag.de/~sapidb/012006153200000768452003E.ITFhttps://websmp102.sap-ag.de/~sapidb/012006153200000142872005D.ITFhttps://websmp102.sap-ag.de/~sapidb/012006153200000142872005D.ITFhttps://websmp202.sap-ag.de/~sapidb/011000358700011747102001E.ITFhttps://websmp202.sap-ag.de/~sapidb/012006153200000768452003E.ITFhttps://websmp102.sap-ag.de/~sapidb/012006153200000142872005D.ITF


14/38


your ETG documents you can convert them into P;G using report8SBCSICE&H68TIETGIGE8IUCE;6. This report is delivered with SAP &ote +>='=+>.Gollow the instructions in SAP &ote+>='=+>B6GE86 %eginning the conversion procedure.

1.5 )ranslation 6nvironment

#f you use the SAP translation environment @transaction S6> you must export the ProposalPool in the non-Unicode system. /hen the Unicode Conversion is finished$ you must importthe Proposal Pool into the Unicode system @see chap. =.Unicode Conversion Completion.Gollow the instructions in SAP &ote+",,(!"$scenario >.

+. Unicode Preconversion P$ase

!ata*ase C$ec(SPU* is used to prepare the data%ase ta%les of a non-Unicode system for the conversionto Unicode. All steps in the Unicode Preconversion Phase are designed to %e run at systemuptime @i.e. when users are logged on to the system. The system conversion is carried out%y the separate tool 8>loadpage!!D during the data%ase export. 8>load uses the results ofSPU* which are stored in the 6xport Control Ta%le and the ?anguage ?istpage+(D.

&ote4 #t is only possi%le to perform the data conversion during the export phaseO

+.1 SPU-+.1.1 Restart SPU-

#t is mandatory that all data are completely deleted %efore starting the data%ase checO *o toScanner !estart SP"#.

After a restart$ you will %e displayed the entrance screen of SPU*. All data which mighthave %een already entered in SPU* are now deleted.

+.1.+ Welcome to SPU-

The entrance screen is divided into two sections. #n the upper section you will find generalinformation and a couple of lins to Unicode information sites.

#n the lower section there are three push%uttons with additional In$o %uttons. 6achpush%utton triggers a mandatory action to %e performed %efore the worlist for theConsistency Chec can %e initialiFed. The chec%ox %ould you like to replace code page&&'' (ith &&)' in the Language Listcan %e optionally selected in case the frontend codepage ++"" has %een used with system code page ++"".

The last push%uttonContinue (ith transaction SP"#will trigger the automaticalinitialiFation of the ?anguage ?ist and lead to the Consistency Chec screen.

+.1.3 6ce"tion ist
http://www.service.sap.com/sap/support/notes/1349413http://www.service.sap.com/sap/support/notes/1349413http://www.service.sap.com/sap/support/notes/1349413http://www.service.sap.com/sap/support/notes/1349413http://www.service.sap.com/sap/support/notes/1055820http://www.service.sap.com/sap/support/notes/1055820http://www.service.sap.com/sap/support/notes/1055820http://www.service.sap.com/sap/support/notes/1349413http://www.service.sap.com/sap/support/notes/1349413http://www.service.sap.com/sap/support/notes/1055820


15/38


The 6xception ?ist contains SAP delivered ta%les which store data from only one language$for example ta%les with only :apanese or only *erman data.

The exception list is provided as M? file attached to SAP &ote ''''". 3ou must uploadthis file once. Select Do(nload Exception List $rom note **)**'and save the M? file to

your local PC.Then select "pdate the SP"# exception tablesand upload the M? file.

3ou can display the content via Exception List De$ault Exception Listafter the

Consistency Checkhas %een executed.

This list of ta%les is predefined %y SAP. #n principle it is possi%le to add or remove ta%les fromthe 6xception ?ist$ %ut it is not recommended to change the default content in Single CodePage systems.

3ou can proceed after the confirmation message "pload o$ exceptions success$ully $inishedis displayed.

+.1.4 dditional Pre"aration Ste"sSelect push%utton Start additional preparation steps. 8eportAdditional Preparation Stepsconsists of several reports which were created for deleting corrupt or o%solete ta%le data prior

to Unicode conversion. En the next screen the included reports are displayed. ChooseBackground. All reports will %e executed automatically in se2uential order.

&ote4

3ou cannot proceed with SPU* until you have executed U*IA;;IP86PIST6P onceusing the %acground option. #t is possi%le that some reports included inU*IA;;IP86PIST6P are not availa%le in the system.#n this case$ chec whether you can implement them with S&ET6. #f the correspondingsoftware components do not exist in your system you can proceed with SPU*.

#f you need to rerun one or more selected reports later$ you can use %utton . #t is notpossi%le to use this option %efore U*IA;;IP86PIST6P has %een run using the%acground option.

Re"ort nameSo&t9areCom"onent

W$at does t$ere"ortJ

SPNote

5B6H+5CAI;6?IEBSE?6T6IB6H+6A-APP? ;elete entries from

ta%les 5B6H+5$ 5;S;5and 5HSE5

('),))

5B6H+5CAI;6?IEBSE?6T6IB6H>6A-APP? ;elete entries from

5B6H>5 ta%les ('),))

A*8IASSISTA8I"IP8EB?6

SAPIBAS#S ;elete entries fromta%les US8+"$US8++$ US8+! andUS8+>

++=(+

BH6;IS8HI'+)IUC;I;6!6&

6A-APP? Everwrite *ermanprogram names inta%le 5B6H!56;'+)with 6nglish text

+!)=)==

CE8ISE;#IUCE;6SAPIBAS#S ;elete entries from

A;8C from groupSE;#

)+!+'

+005,01,1#

1#
https://service.sap.com/sap/support/notes/996990http://www.service.sap.com/sap/support/notes/897577http://www.service.sap.com/sap/support/notes/897577http://www.service.sap.com/sap/support/notes/1146816http://www.service.sap.com/sap/support/notes/1274744https://service.sap.com/sap/support/notes/712619https://service.sap.com/sap/support/notes/996990http://www.service.sap.com/sap/support/notes/897577http://www.service.sap.com/sap/support/notes/897577http://www.service.sap.com/sap/support/notes/1146816http://www.service.sap.com/sap/support/notes/1274744https://service.sap.com/sap/support/notes/712619


16/38


C3ITC3;IUCE;6SAPIAPP? ;elete entries from

ta%le TC3;('''>+

;6?6T6IT",'USAPIAPP? ;elete inconsistent

entry from ta%le

T",'U

+!)='=,

;SI;6?6T6ICE88UPT;ATAIT;/;SAPIAPP? ;elete entries from

Ta%le T;/;''+,=+

6CATTICE&HIM?;ATA!MST8

SAPIBAS#S convert M? datafrom 6CN ta%les fromC7A8-%ased fileformat to %inaryformat

++,>+>"

6G*IC?6A8IT6MTG#6?;S

SAPIABA ;elete entries fromta%les 6G8$6G8ST8$ 6GC?$6GC?ST8$

6G*ICE??6CT#E&

+>+!),)

*8#MI;6?6T6I8/I6MT8ACTSSAPIAPP? ;elete extracts for

8eport /riter('!")

*ICE88IBA:PI#&IS6T76A;68T

SAPIAPP? ;elete entries fromta%le S6T76A;68Twith su%class BA:P

+!,'+)(

7A8UT)!"

SAPI785SAPI78CA8@in 6hPapplications

;elete entries fromT)A8)!

++"+!,'

#&;MI#/I;6?6T6

SAPIBAS#S ;elete entries from

ta%le #&;M @86?#; #/

+!'!+!,

#&;MICI;6?6T6SAPIABA ;elete entries from

ta%le #&;M+",,=>+

#&;MI6I;6?6T6SAPIAPP? ;elete entries from

ta%le #&;M @86?#; 6

+>+()"

#&;MIUI;6?6T6SAPIAPP? ;elete entries from

ta%le #&;M @86?#; U

+>"!"=!

#&;MIPCIP6I;6?6T6SAPIBAS#S ;elete entries from

ta%le #&;M @86?#; VPCW or VP6W

+"('"+!

#&;MIP8I;6?6T6SAPIBAS#S ;elete entries from

ta%le #&;M @86?#; P8

+!'+!

#&;MIS6I;6?6T6

SAPIBAS#S ;elete entries fromta%le #&;M @86?#; H and 86?#; 8T

+!'==+=

#&;MIS7I;6?6T6SAPIBAS#S ;elete entries from

ta%le #&;M @86?#; S7

'('")"

#&;MISI;6?6T6 SAPIABA ;elete entries from ')))!
https://service.sap.com/~sapidb/012003146900000650522005E.ITFhttp://www.service.sap.com/sap/support/notes/1274945https://service.sap.com/sap/support/notes/991541http://www.service.sap.com/sap/support/notes/1153130http://www.service.sap.com/sap/support/notes/1312757https://service.sap.com/~sapidb/012003146900000567482005E.ITFhttp://www.service.sap.com/sap/support/notes/1259178http://www.service.sap.com/sap/support/notes/1101259http://www.service.sap.com/sap/support/notes/1292125http://www.service.sap.com/sap/support/notes/1055431http://www.service.sap.com/sap/support/notes/1318670http://www.service.sap.com/sap/support/notes/1302042http://www.service.sap.com/sap/support/notes/1089012http://www.service.sap.com/sap/support/notes/1291662http://www.service.sap.com/sap/support/notes/1294414https://service.sap.com/sap/support/notes/989070http://www.service.sap.com/sap/support/notes/977726https://service.sap.com/~sapidb/012003146900000650522005E.ITFhttp://www.service.sap.com/sap/support/notes/1274945https://service.sap.com/sap/support/notes/991541http://www.service.sap.com/sap/support/notes/1153130http://www.service.sap.com/sap/support/notes/1312757https://service.sap.com/~sapidb/012003146900000567482005E.ITFhttp://www.service.sap.com/sap/support/notes/1259178http://www.service.sap.com/sap/support/notes/1101259http://www.service.sap.com/sap/support/notes/1292125http://www.service.sap.com/sap/support/notes/1055431http://www.service.sap.com/sap/support/notes/1318670http://www.service.sap.com/sap/support/notes/1302042http://www.service.sap.com/sap/support/notes/1089012http://www.service.sap.com/sap/support/notes/1291662http://www.service.sap.com/sap/support/notes/1294414https://service.sap.com/sap/support/notes/989070http://www.service.sap.com/sap/support/notes/977726


17/38


ta%le #&;M @86?#; S

8*MIS6TSITEI="

SAPIAPP? ;elete entries fromta%les T(""S$

T(""M$ T(""3 andS6T;ATA

'!((,'

8GPA3IUCE;6IHA8#A&TS

SAPIAPP? Convert variants ofprogramSAPGPA3 @cross-client

+>((='

8#SS8I;6?IA??I6&T8#6SITA++

&ot nown ;elete entries fromta%les TA++$T8' andT8'A++

+>='"

8#SS8I;6?IA??I6&T8#6SITBA*&ot nown ;elete entries from

ta%le TBA*+>='"

8PU=)"A;:USTIT,!C, SAPI788MM ;elete entries fromT,!C,

)'!),

8SBCSISE68I86GIUP;AT6SAPIBAS#S Ad(""

8SI;IC?6A&UPIT;ITAB?6SAPIBAS#S ;elete content from

ta%les T;+" andT;++

)(+!++

8S;B=P86PIUCPCSAPIBAS#S ;elete entries from

SN ta%les'>!">=

8SSC;IC76CIE?;I6&T8#6SSAPIBAS#S ;elete entries from

C;PES+"'=)"

8SSPAIP86PA86IUCSAPIBAS#S ;elete content of

ECSCP?EB:((','

8STMC?6A8TT;T*SAPIBAS#S ;elete entries from

ta%le TT;T*''!(,)

8SI;6?6T6IHA8#A&TISPAC6SAPIBAS#S ;elete empty entries

from ta%le HA8#@86?#; XHMX

++>!(,"

8SIG#??IT8;#8I8?EA;SAPIBAS#S Gill 86PES8C-

8?EA;(=>>!

8SISC8PI;"!"SIC?6A&

SAPIBAS#S ;elete screensource codes with

invalid eys fromta%les ;"!"S and;3&PSEU8C6

()""+

8SIT6ST86PE8TI;6?6T6IE&?#&6SAPIBAS#S ;elete old test

reports from function%uilder

'>+(!=

8SIT6STI86PE8TI*6&68AT6I:EBSAPIBAS#S See relevant SAP

&ote'>+(!=

8SITPA8AIPA8T6MTIC?6A&SAPIBAS#S ;elete entries from

ta%le TPA8A in fieldPA8T6MT

+!,+=(

8UT;;")T?A SAPIBAS#S ;elete entries from +!),!,=

+005,01,1#

17
https://service.sap.com/~sapidb/012006153200000198492006E.ITFhttp://www.service.sap.com/sap/support/notes/1388649http://www.service.sap.com/sap/support/notes/1364690http://www.service.sap.com/sap/support/notes/1364690https://websmp202.sap-ag.de/~sapidb/012003146900000194562003E.ITFhttp://www.service.sap.com/sap/support/notes/1003800http://service.sap.com/sap/support/notes/781211https://service.sap.com/~sapidb/012006153200000235242006E.ITFhttp://www.service.sap.com/sap/support/notes/1096470https://service.sap.com/~sapidb/012003146900000534272005E.ITFhttps://service.sap.com/sap/support/notes/992857http://www.service.sap.com/sap/support/notes/1132850https://service.sap.com/~sapidb/012003146900000248442003E.ITFhttps://service.sap.com/~sapidb/012006153200000281912005E.ITFhttp://www.service.sap.com/sap/support/notes/931824http://www.service.sap.com/sap/support/notes/931824http://www.service.sap.com/sap/support/notes/1256148http://www.service.sap.com/sap/support/notes/1275254https://service.sap.com/~sapidb/012006153200000198492006E.ITFhttp://www.service.sap.com/sap/support/notes/1388649http://www.service.sap.com/sap/support/notes/1364690http://www.service.sap.com/sap/support/notes/1364690https://websmp202.sap-ag.de/~sapidb/012003146900000194562003E.ITFhttp://www.service.sap.com/sap/support/notes/1003800http://service.sap.com/sap/support/notes/781211https://service.sap.com/~sapidb/012006153200000235242006E.ITFhttp://www.service.sap.com/sap/support/notes/1096470https://service.sap.com/~sapidb/012003146900000534272005E.ITFhttps://service.sap.com/sap/support/notes/992857http://www.service.sap.com/sap/support/notes/1132850https://service.sap.com/~sapidb/012003146900000248442003E.ITFhttps://service.sap.com/~sapidb/012006153200000281912005E.ITFhttp://www.service.sap.com/sap/support/notes/931824http://www.service.sap.com/sap/support/notes/931824http://www.service.sap.com/sap/support/notes/1256148http://www.service.sap.com/sap/support/notes/1275254


18/38


ta%le ;;")T

SAP8S6U*SAPIBAS#S ;elete entries from

ta%le 8SPT6MTS,=!>"!

S;B#IPEE?IC?6A&68SAPIBAS#S ;elete entries for

TCP""$ TCP"+ orTT;CG from ATAB

'!"+>(

S6EIC?6A&IT3P6S8C

SAPIBAS#S Correct entries inta%le S6CEPE;G@fields T3P6S8Cand T3P8SCI?6&*

++=,>"

S#ACI;6?6T6I#&HA?#;

SAPIBAS#S Correct characters in#ACS68HP and#ACSICJE%solete entries in#AC#6?

(!+'J+>=,">>

STSTCPI86PA#8

SAPIBAS#S ;elete entries from

TSTCP (')""!

T68I;6?6T6I#&CE886CTIC7A8S6T

SAPIBAS#S ;elete erroneousterminology andglossary text fromST68IT6MT

+!("='=

#f the system code page is ++"" you should chec whether the frontend code page @or SAP*U# code page is also ++"". 8un report 8SCP""+> in transaction S6>( and chec$ if ++""is displayed in field Character set o$ S+Pgui. #f yes$ users are a%le to input characters whichare not covered %y the system code page. Such characters L for example the 6uro sign - willget lost during the data%ase conversion %ecause they are not stored on the data%ase. 3oucan prevent this at least for characters in transparent ta%les %y switching to ++" in the

SPU* ?anguage ?ist.

Select chec%ox (ould you like to replace code page &&'' (ith &&)' in the Language List,&ote that there is no automatical replacement option for other code pages than ++"".

Afterwards choose push%utton Continue (ith transaction SP"#.

3ou are now on the ta%strip Consistency Check. The ?anguage ?ist is now initialiFed andfilled$ and the default settings for SPU* are set.

+.1.# anguage ist

All languages which are productively used in your system are now inserted in the ?anguage

?ist as activelanguages in conload uses the correct code page for languages which are not installed in thesystem %ut nevertheless occur in ta%les with language information.

8ecommendation4

Select EditLanguage Listfrom the SPU* menu$ and chec whether all productivelyused languages are mared as active languages. #f you are not sure which languages areproductively used in your system$ do the following4

Call S6>($ enter report 8SCP#&ST and press -. En the next screen select Current /LScon$igto display the current i+(n settings. #n the following section the language eys of all

productively used languages are listed4
http://www.service.sap.com/sap/support/notes/542302https://service.sap.com/sap/support/notes/920138http://www.service.sap.com/sap/support/notes/1164530https://service.sap.com/~sapidb/012003146900000349272005E.ITFhttps://service.sap.com/~sapidb/012003146900000349272005E.ITFhttp://www.service.sap.com/sap/support/notes/1345033https://service.sap.com/~sapidb/012003146900000617532005E.ITFhttp://www.service.sap.com/sap/support/notes/1280494http://www.service.sap.com/sap/support/notes/542302https://service.sap.com/sap/support/notes/920138http://www.service.sap.com/sap/support/notes/1164530https://service.sap.com/~sapidb/012003146900000349272005E.ITFhttp://www.service.sap.com/sap/support/notes/1345033https://service.sap.com/~sapidb/012003146900000617532005E.ITFhttp://www.service.sap.com/sap/support/notes/1280494


19/38


Database table entries TCP0I Processed language(s) entry

Systems 9it$ Code Page 340

#f you use code page (>=" @Traditional Chinese 7SCS Hers.+ in your system$ you mustperform additional preparation steps as descri%ed in the supplementary documentation0Conversion of 7SCS Systems to Unicode1. ;ownload from SAP &ote ,,+>==.

Systems 9it$ Code Page 300

;epending on font and input method it is possi%le that 7SCS characters have %een enteredin systems with code page (>"" @Traditional Chinese Big,$ %ased on S CP',". #f this isthe case$ proceed as descri%ed in section Systems 9it$ Code Page 340.

+.1.' SPU- Settings

;epending on the system type the settings for the data%ase chec have different defaultvalues. These default values are descri%ed in the G+ help documentation of each input field.To access the SPU* Settings selectScannerSettings. #n general$ SAP recommendsthat you eep the default values.

There are cases where you should change the default value of the lo*al all*ac( CodePage. Gor example4

#f you have replaced code page ++"" with ++" on the SP"# %elcome Screen$you should change the *lo%al Gall%ac Code Page from ++"" to ++".

#f the system code page is ++"$ apply SAP &ote +=,'".

All code pages which are used for the conversion must %e roundtrip compati%le. This meansthat a roundtrip conversion @for example4 ++" Unicode ++" must %e possi%le.Therefore the system executes a roundtrip compati%ility chec when you enter a new *lo%alGall%ac Code Page.

+.1.7 nitiali8ing t$e Wor(list

Select ScannerInitiali0e%orklist. ;epending on the data volume the initialiFation


20/38


Select Scanner "pdate%orklist.

SPU- -ain og

Chec the main log regularly. Select Scannerain Logfrom the menu %ar.

+.1. Consistency C$ec(

Select Schedule %orker 1obsfrom the tool%ar$ and then set the time and date for the

worer


21/38


and reset the ta%le in the CC /orlist.

+ A %acground


22/38


Select the ta%le@s you want to reset and then select in the tool%ar.

ResultA

The ta%les have status INITI! again. They are deleted from the 6xport Control Ta%le %utnot from the /orlist of the Consistency Chec.

&ote

Ta%les which have %een deleted from the data%ase are automatically deleted from the CCworlist.

:o9 to eclude ta*les &rom e"ort

#t is not possi%le to exclude a ta%le from the export %y adding it to the 6xception ?ist. Theta%le will %e automatically entered in the 6xport Control Ta%le and therefore still %e exported.

&ote

#f you want to exclude a ta%le from export after the Consistency Chec$ you must4

+. ;rop the ta%le from the data%ase

!. ;elete the ta%le entry from the nameta% ta%les ;;GTM$ ;;&TG$ ;;&TT on data%ase level

>. 8eset the ta%le in the Consistency Chec @see section 8esetting Ta%les in the /orlist of

the Consistency Checpage!+D

+.+ inal Pre"aration Ste"s

+.+.1 SPU- U"dates

#f there is a time difference %etween the scan and the data%ase export$ it may happen thata new ta%le has %een created or a Support Pacage has %rought a new ta%le with it. #nsuch a case$ the preconversion must %e rerun right %efore the export is carried out toensure that the data change is reflected in the 6xport Control Ta%le.

Proceed as follows4

+. Update the worlist.#n SPU* select Scanner%orklist"pdate %orklist.!. Select onitorfrom the tool%ar. The onitor will show you if new ta%les were added

to the system. Those ta%les have the status 0#nitial1. Gor those ta%les the ConsistencyChecpage!"D needs to %e run.

>. Select Scanner"pdate Log.After you have updated the worlist$ this log displays all ta%les which have %eenadded or changed after the consistency chec. 3ou can now reset those ta%les in the


23/38


worlist of the consistency chec and rerun the consistency chec. Afterwards$ theresetted ta%les will %e removed from the log.

+.+.+ C$ec( -atc$code !s

B)$is section is only required &or Su""ort Pac(ages lo9er t$an SP07. Wit$ SP07 and$ig$er )W)%%01 is included in re"ort U-D!!D!%WN)-6DS)6PS.E

8un report T/TEE?"+ again to chec whether there are still existing active matchcode #;s.#f yes$ proceed as descri%ed in chapter +.= ;elete atchcode #;spage +"D.

NoteA

;o not start the export %efore all matchcode #;s have %een deletedO8un this report untilmessage 0Chec successful$ no action necessary1 is shownO

+.+.3 Nameta* $andling

1. !elete entries &rom !!N)DC%N2DUC and !!N))DC%N2DUCA

;elete the ta%le entries on data%ase level.

+. Create t$e nameta*s.

Caution

;o not import new ;;#C o%


24/38


3. Afterwards you must create the missing nameta%s for the corrected o%.

4. &ter t$e nameta*s $ave *een success&ully created you s$ould u"date t$edata*ase statistics &or t$e alternative active nameta*s !!N)DC%N2DUC and

!!N))DC%N2DUC in order to im"rove t$e "er&ormance o& t$e R3load e"ort"rocedure.

Perform the statistics update on data%ase level. 3ou can expect a runtime of at leastseveral minutes.

+.+.4 )a*les 9it$ o*solete data

B)$is section is only required &or Su""ort Pac(ages lo9er t$an SP07. Wit$ SP07 and$ig$er s(i" t$is section and "er&orm t$e ste"s descri*ed in +.+.# dditional !o9ntimeSte"sinstead.E

The following ta%les need special treatment directly %efore the data%ase export @not duringsystem uptimeO.

Proceed as descri%ed in the corresponding SAP &otes in column -ore in&ormation.

!o not maintain t$e ta*les manually@

)a*les -et$od -orein&ormation

;;S7PHA?,"

Personal 7elpHalues

3ou cannot use personal value lists from ta%le;;S7PHA?," and generated selection reports@namespace 5+BCG=+5 of the input help @G= after aUnicode conversion. 3ou must delete them %efore theconversion and create them again in the Unicodesystem during runtime.

Use report U-D4DC6NUPaccording to SAP&ote +!),+='.

+!),+='

*86P

8eport /riter4 Gile ofStored 8eports

After a Unicode conversion$ extracts for 8eport /riterreports cannot %e used anymore. 6xtracts should %edeleted %efore the conversion to avoid converting dataunnecessarily.

(>)+(=J

('!")

*88T8eport /riter48untime informationfor generatedprograms

To avoid converting data of ta%le *88Tunnecessarily$ the generated programs can %e deletedwith report RR!NC.

(>)+(=

86PES8C

8eport Source Code

Use report U-D4DC6NUPonlyO

!o not maintain t$e ta*le manually@

+!),+='
https://service.sap.com/sap/support/notes/1275149https://service.sap.com/~sapidb/012006153200000080842005D.ITFhttps://service.sap.com/~sapidb/012003146900000567482005D.ITFhttps://service.sap.com/~sapidb/012006153200000080842005D.ITFhttps://service.sap.com/sap/support/notes/1275149https://service.sap.com/sap/support/notes/1275149https://service.sap.com/~sapidb/012006153200000080842005D.ITFhttps://service.sap.com/~sapidb/012003146900000567482005D.ITFhttps://service.sap.com/~sapidb/012006153200000080842005D.ITFhttps://service.sap.com/sap/support/notes/1275149


25/38


TA;#8

;irectory of8epository E%


26/38


8S?A&*!" ;;GTM$ ;"!"?$ ;"!"?#&G$;3&P?EA;$ ;"!+?$ ;"!+?#&G$;3&PTMT?;$ ;>=,T$ ;>=T$;>=!?$ TT866?EA;T$ ?T;MT

110910

U*I;6?6T6ISS?EA; TCP""$ T"""$ STM? 1132495

U*IC76CIAPP?#CAT#E&ITABS The following ta%les are checed4T#C&H$78PA;&&$ *88T$HB;ATA$ HB7;8$ HBE;. #f thechec reports errors or warnings$ theta%les must %e handled as descri%edin SAP &ote +=!''>,.

1429935

U*IC76CI&A6TABS 1428028

U*IC76CI&A6TABITABS ;;MTGICE&HIUC$;;MTTICE&HIUC

1426513

3. Unicode Conversion P$ase

ProgramA R3loadThe default conversion procedure is to export the entire data%ase using SAPinst @whichcontrols 8>load$ create a new Unicode data%ase$ and then import the data%ase usingSAPinst again @internally 8>load. 3ou can choose either the 0Two Server ethod1 which isrecommended. #n this case you %uild the Unicode data%ase on an additional server. #f youchoose the 0Ene Server ethod1 you must delete the non-Unicode data%ase %efore. #n factyou perform %oth a system copy using SAPinst @as descri%ed in the relevant System Co"yuidementioned %elow and simultaneously a data%ase conversion to Unicode. Theconversion is performed %y 8>load during the e"ort "rocedure. Gor %uilding the Unicodesystem you use the export files generated during the export procedure instead of the exportmedia provided %y SAP.

&ote

3ou can choose either the homogeneous or the heterogeneous system copy method. #f youwant to perform a data%ase or platform change during the conversion process$ choose theheterogeneous system copy method.

;ocumentation4

Gor this chapter you must use the System Copy *uide in parallel. 3ou can download the validSystem Copy *uide for your release from http455www.service.sap.com5install&/)".#nstallation$ section System Copy for 67P+ S8+4ABAP$ABAP 9 :ava.

!o9ntime 6stimation

#f you want to gain a rough estimation of the expected system downtime$ run reportU*I8>?EA;I8U&T#6IP86;#CT#E& in transaction S6>(.
http://www.service.sap.com/sap/support/notes/110910http://www.service.sap.com/sap/support/notes/1132495http://www.service.sap.com/sap/support/notes/1429935http://www.service.sap.com/sap/support/notes/1428028http://www.service.sap.com/sap/support/notes/1426513http://www.service.sap.com/installNW70http://www.service.sap.com/installNW70https://service.sap.com/~sapidb/011000358700000514722009E.pdfhttps://service.sap.com/~sapidb/011000358700000514732009E.pdfhttps://service.sap.com/~sapidb/011000358700000514732009E.pdfhttp://www.service.sap.com/sap/support/notes/110910http://www.service.sap.com/sap/support/notes/1132495http://www.service.sap.com/sap/support/notes/1429935http://www.service.sap.com/sap/support/notes/1428028http://www.service.sap.com/sap/support/notes/1426513http://www.service.sap.com/installNW70https://service.sap.com/~sapidb/011000358700000514722009E.pdfhttps://service.sap.com/~sapidb/011000358700000514732009E.pdf


27/38


#n addition SAP &ote (,)"(+provides information a%out methods and tools for optimiFationof the export and import procedure.

!o not delete non,Unicode system immediately a&ter t$e im"ortAfter %oth export5conversion and system copy has %een successfully completed$ SAPrecommends eeping the non-Unicode system for the duration of the testing period of theUnicode system. Afterwards the non-Unicode system can %e deleted using the standardprocedure.

/- !/+ U!/ &or UNI and Windo9sA )a*les"ace si8es &or conversion Unicode , nonUnicode

To get the appropriate ta%lespace siFes for #B ;B! U;B for UM and /indows$ install8>sFch B6GE86 the conversion. 3ou can download from SAP Service aretplace at

service.sap.com5patches Qyour productR Qyour releaseR Z Binary Patches. To avoid wastingspace in your ;B! U;B for UM and /indows ta%lespaces we strongly recommend that youcreate all ta%lespaces in the target data%ase with extent siFe !.

NoteA

This is not the default for all SAPinst releases up to and including SAP &et/eaver !""= S8+.3ou therefore need to manually adload copy procedure of non-Unicode system toUnicode system.

ae sure that all re2uired C;s5;H;s are availa%le now as descri%ed in section Software8e2uirementsin this document page =D.

#mport the latest SAP ernel patch as descri%ed in SAP &ote +'=and the applica%le8>load version.

Requirements4 Use the latest 8>load version and the latest version of 8>ldctl and8>sFch for your release

!ocumentationA , t$is document

, System Co"y uidefor your release. The System Copy *uidescan %e downloaded from4http455www.service.sap.com5install&/)"#nstallation$ section

System Copy for 67P+ S8+4ABAP$ABAP 9 :ava.

Gor detailed information a%out o"timi8ation o& t$e system co"y"rocedurego tohttps455service.sap.com5systemcopy-R optimiFation.

Status4 re2uired.

Perform the export from the non-Unicode system @source system$ install the target systemand import the data%ase files that you have exported from the source system as descri%ed inthe System Copy #uide4

+005,01,1#

+7
https://websmp104.sap-ag.de/~sapidb/012003146900000292122005E.ITFhttp://www.service.sap.com/sap/support/notes/19466http://www.service.sap.com/sap/support/notes/19466http://www.service.sap.com/installNW70https://service.sap.com/~sapidb/011000358700000514722009E.pdfhttps://service.sap.com/~sapidb/011000358700000514732009E.pdfhttps://service.sap.com/~sapidb/011000358700000514732009E.pdfhttps://service.sap.com/systemcopy%20https://service.sap.com/systemcopy%20https://service.sap.com/systemcopy%20https://websmp104.sap-ag.de/~sapidb/012003146900000292122005E.ITFhttp://www.service.sap.com/sap/support/notes/19466http://www.service.sap.com/installNW70https://service.sap.com/~sapidb/011000358700000514722009E.pdfhttps://service.sap.com/~sapidb/011000358700000514732009E.pdfhttps://service.sap.com/systemcopy%20


28/38


07omogeneous and 7eterogeneous System Copy for SAP Systems Based on Q86?6AS6R1

Section4 System Co"y Procedures on M%P6R)N SS)6-O1

#t is not possi%le to perform the Unicode conversion during the importO ae sure you convertthe ;P data during export phase %y calling 8>load with parameter X-datacodepage =+"!Xor X-datacodepage =+">X @details see section >.+.+ ;ata%ase 6xport.

8ead section Software 8e2uirementspage =D.

Unicode Conversion 9it$ data*ase c$angeA m"ortant in&ormation &or n&ormi

data*ases

#f you plan to convert an #nformix data%ase$ follow the instructions in SAP &ote (++=>+B6GE86 the data%ase exportO

/- !/+ Universal !ata*ase &or iSeriesA

Before starting the installation$ follow the instructions in SAP &ote ++,(,">0iSeries4 Settingenvironment Haria%les for SAPinst1.

3.1.1 !ata*ase 6"ort

+. Perform the necessary preparation steps %efore starting SAPinst.

!. 8ead the document 0Unicode Conversion4 Tips and Trics for #mproving theConversion Time1.

>. Perform the data%ase export in the non-Unicode system @source system asdescri%ed in the relevant section of the System Copy #uide5Running SPinst to6"ort t$e !ata*ase.

=. /hen running SAPinst to export the data%ase and SAPinst prompts for #eneralExport ParametersData $ile code page mae sure the code page of the targetsystem depending on the %yte order of its CPU is entered @see SAP &ote ,,!==4

#f the target platform @e.g. ?inux$ ESG+$ &T uses a little endian CPU @e.g. Alpha

or #ntel CPU$ enter 4103. #f the target platform @e.g. 7P-UM$ A#M$ SunES$ ES5>'" uses a %ig endian CPU

@e.g. Sun SuperSPA8C$ enter 410+.

Caution

Be aware that this parameter depends on the processor architecture$ not on theoperating system.

ae sure that the most recent non-Unicode 8>ldctl @SAP ernel is used for the export.

&ote the additionalinformationfor the Unicode Conversion during the export of the data%ase4
https://service.sap.com/sap/support/notes/1158503https://service.sap.com/sap/support/notes/1158503https://service.sap.com/~sapidb/012006153200001712552002E.ITFhttps://service.sap.com/sap/support/notes/1158503https://service.sap.com/~sapidb/012006153200001712552002E.ITF


29/38


Server Necessary Ste"s urt$er n&ormation

-S SF Server only ;uring the installation$ thecollation setting must %e

fixed.

See SAP &ote"""!)

%racle only /hen running SAPinst toexport the data%ase andSAPinst prompts forDatabase Instance

Parameters#eneral

SettingsDatabase

character set mae sure thecharacter set of the sourcedata*aseis entered @e.g.U),$ W6!6CorUS7SC.

See System Copy #uide$sections #nput for 6xporting3our ;ata%ase

ll servers ;uring the export of thesource system 8>load writeslog files into the installationdirectory of the sourcesystem. The file names arelie SAPN.log for exampleSAPAPP?!.log. #f you createown pacages for the files$the file names are lieQTAB?6&A6RN.log.

The SAPNlog files orQTAB?6&A6RN.log filesshould %e saved for latererror analyis.

R3load og -essages

-sg.)y"e

!e&inition !escri"tion CorrectionSte"s

6rror "rror #ro$%Codepage handling (&'CP) code% *+

,table_na$e- .No suchobect &o1 not #ound2

This error can occurwhen a new ta%le wasadded to the system.

Update the worlist and executestep ! for ta%le Qta%leInameR@see section SPU* Updates

page !!D.

8ead SAP &ote >>(+= for details.

6rror &ecei3ed return code*04+ #ro$ rscp5C'tartTab

This error might occurwhen ta%le clustersand cluster ta%leshave differentlanguage information.

Chec entries in the 6xportControl Ta%le. ae sure the fieldCodepage!ecognitionis notempty and also chec the fieldsLang. -ld. And Lang. Pos.

6rror "rror 1hen retrie3ingphysical na$etab #ortable ,table na$e-

6rror during 6"ortA

The Unicode nameta%has not %een created

or there have %een

#f this message occursrepeatedly$ go %ac to transactionSPU* and create the Unicodenameta% @again @see chapter

+005,01,1#

+5
https://service.sap.com/~sapidb/012006153200000174172003E.ITFhttps://service.sap.com/~sapidb/012006153200000174172003E.ITFhttps://service.sap.com/~sapidb/012006153200000174172003E.ITF


30/38


errors during thecreation.

&ameta% 7andlingpage!>D.

SAP &ote '>!))' descri%es%asic information a%out how to

analyse nameta% pro%lems.6rror during m"ort48>load performs adata conversion andcannot read thenameta%. #t could %eone of the followingconversion types4

a The conversionfrom a non-Unicode toa Unicode code pagewas performed.

% The endiannes haschanged @=+"! Q-R=+">.

a The conversion to Unicodeshould always %e performedduring the 6xport$ repeataccording to chapter ;ata%ase6xport page!(D.

% ae sure that the 8>loadpacage containing the nameta%information is imported first.

6rror "rror #ro$%Codepage handling (&'CP)

code% 6* &'CP"T77!7N8The data 1as longer thanthe bu##er9

lang5:CP5ap% no c9p9assigned

$odule% rscp$i no%; line% *0load tried to find apool ta%le which doesnot exist in the ABAP;ictionary.

This error occurswhen the ConsistencyChec shows error

message type (0#llegal pool ta%levalues1 and reportU*IC76CIPEE?has not %een run.

8un report U*IC76CIPEE?page 6rror4 8eference sourcenot foundD.

6rror 8>load terminatesduring export ofsingle code "agesystem

8ead SAP &ote )+(>!' forcorrection instruction.

6rror (">P) "&&7&% ,obectna$e- $issing inDDNTT_C7N?_@C

8>load could not findthe Unicode nameta%for o%load notices if theUnicode nameta%shave %een created %ySPU* option$ %utnot the execution withS6>( and thereforetriggers a warning.

#gnore the message in case theUnicode nameta%s have %eencreated via report 8A;CUC&T inS6>(. Etherwise start theUnicode nameta% creation viaSPU* option
https://service.sap.com/~sapidb/012006153200000261572004E.ITFhttps://service.sap.com/~sapidb/012006153200000261572004E.ITFhttps://service.sap.com/~sapidb/012006153200000261572004E.ITF


31/38


32/38


33/38


password you have entered in thecorresponding SAPinst dialog$press 86T83 and enter your;;#C password once again.

3.+ ollo9,U" ctivities+. Perform the follow-up activites in the source system and in the target system as

descri%ed in the System Copy #uide for your release.

!. Afterwards perform the completion steps in the Unicode system listed in the followingchapter.

4. Unicode Conversion Com"letionP$aseThis section descri%es the steps which have to %e performed in the Unicode system after theconversion and import of the data%ase has %een successfully completed.

?og on to your Unicode system.

dditional Post Conversion Ste"s

*o to transaction S6>($ and execute report U*IA;;IPESTIST6P. This report consists ofseveral reports which were created for saving the conversion history @logs$ settings$ language

list$ etc. ad


34/38


U*IA;:USTI#+(&IS6TT#&*S

Update the #+(&System configuration46mpty ta%le TCP;Band ad'="=$ section 67'8 9uestionfordetails.

4. Country,S"eci&ic !evelo"ments Russia :uman Resources GII,CSC,RU,:RHA

Pro%lems with records with T866IT3P6X8U78X from ta%le ;66IT866I&E;6. 8unreport 78UUICE&H68TI#&IUCE;6 as descri%ed in SAP &ote (',("=.

#. :R master dataA Russia GP,P,RUHA

Pro%lems with 78-8U ta%les T)8U(P and T)8U'P.

8un report 78UUICE&H68TI#&IUCE;6 as descri%ed in SAP &ote +"+,(!.

'. :R master dataA Russia GP,P,RUHA

#n case of incorrect characters in SmartGorms$ refer to SAP &ote'(,"!"
http://www.service.sap.com/sap/support/notes/1128673http://www.service.sap.com/sap/support/notes/1132495http://www.service.sap.com/sap/support/notes/1112206http://www.service.sap.com/sap/support/notes/1128672http://www.service.sap.com/sap/support/notes/1293806http://www.service.sap.com/sap/support/notes/1288872https://service.sap.com/~sapidb/012006153200001638632004D.ITFhttp://service.sap.com/sap/support/notes/514967http://www.service.sap.com/sap/support/notes/539404https://websmp102.sap-ag.de/~sapidb/012003146900000604252005E.ITFhttps://service.sap.com/sap/support/notes/1015682http://www.service.sap.com/sap/support/notes/985020http://www.service.sap.com/sap/support/notes/985020http://www.service.sap.com/sap/support/notes/1128673http://www.service.sap.com/sap/support/notes/1132495http://www.service.sap.com/sap/support/notes/1112206http://www.service.sap.com/sap/support/notes/1128672http://www.service.sap.com/sap/support/notes/1293806http://www.service.sap.com/sap/support/notes/1288872https://service.sap.com/~sapidb/012006153200001638632004D.ITFhttp://service.sap.com/sap/support/notes/514967http://www.service.sap.com/sap/support/notes/539404https://websmp102.sap-ag.de/~sapidb/012003146900000604252005E.ITFhttps://service.sap.com/sap/support/notes/1015682http://www.service.sap.com/sap/support/notes/985020


35/38


7. :R master dataA Russia GP,P,RUHA

#n case of incorrect characters in other 8ussian 78 ta%les$ refer to SAP &ote +!),>+).

. /W system conversion onlyA

#n case of pro%lems during data load follow the correction description in SAP &ote ,+(=!.

5. CR- Server Unicode conversion onlyA

#n case of pro%lems with corrupt language-dependent data in o%ile Client Text Ta%les$ referto SAP &ote)'>,=.

10. m"ort Pro"osal Pool &rom non,Unicode systemA

3ou want to use the Proposal Pool created in the SAP translation environment @transactionS6> in the non-Unicode system. 3ou have exported the Proposal Pool %efore the Unicodeconversion @see chap. +.) Translation 6nvironment.

Gollow the instructions in SAP &ote+",,(!"$scenario >$ how to import the Proposal Poolinto the Unicode System.

11. da"t SP system "ro&ile "arameters.

Adapt 85> parameter settings according to SAP &ote )'""''.

#f you have pro%lems with generated o%


36/38


37/38


a small num%er of o%


38/38


have %een deletedO 8unthis report until message0Chec successful$ noaction necessary1 is

shownO

U*IA;;IPESTIST6P

@Additional PostConversion Steps

UnicodeConversionCom"letion P$ase

"nicode System

Transaction S6>(

This report must %e run inthe Unicode system rightafter the data%ase import.#t contains other reportswhich were created forad

UC_master_guide_SAP.doc

Documents

Transcript of UC_master_guide_SAP.doc