Changes in Unicode

Hi,
Does anyone have a list the FMs and the statements that we need to change in Unicode system?
regards,

Hi
See the links related to Unicode
The Link will be helpful to you.
Re: Upgrade 4.6 to ECC - What are the responsibilites
regarding Unicode influence in Standard programs
Very good document:
http://www.doag.org/pub/docs/sig/sap/2004-03/Buhlinger_Maxi_Version.pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d37d1ad9-0b01-0010-ed9f-bc3222312dd8
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/589d18d9-0b01-0010-ac8a-8a22852061a2
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f8e316d9-0b01-0010-8e95-829a58c1511a
Reward points for useful Answers
Regards
Anji

Similar Messages

When ERP change into Unicode base, what should I do?

Hello,
I'm using R/3 4.6C and BI 7.0.
I plan to upgrade ERP and change UNICODE base.
If ERP was changed to Unicode base, what would I have to do for BI, what would happen without doing anything?
Best regards,
Koji
Edited by: Koji Nagai on Sep 11, 2008 10:40 PM

Hi Koji,
Both ERP and BI 7.0 systems should be in UNICODE system
then only data loading from ERP to BI 7.0 will be without data problems.
if systems are of different UNICODE system, data will not load properly into BW / BI system.
Regards
Daya Sagar

Change of Unicode attribute in a custom made class

Hi,
In relation to a Unicode conversion, I have a program that calls a Class ZHRxxx.
After I have changed the attribute to Unicode check, I get a new error in the method Constructor:
Class ZHRCLPA001,Method CONSTRUCTOR
In the constructor method, you can only access instance attributes,instance methods, or "ME" after calling the constructor of the
superclass . . . . . .
The code is one line:
method CONSTRUCTOR.
Assign pernr to class attribute
a_pernr = i_pernr.
endmethod.
Any ideas ?
Thanks

Hello Peter
Alexander gave you already the answer. However, based on the naming of your z-class I assume that you are trying to read or access infotype tables. Are you aware of class CL_PT_EMPLOYEE? This class provides you with a simple acccess to any infotypes you need.
[code&----
*& Report ZUS_SDN_CL_PT_EMPLOYEE
REPORT zus_sdn_cl_pt_employee.
DATA:
go_employee TYPE REF TO cl_pt_employee.
PARAMETERS:
p_pernr TYPE pernr_d,
p_begda TYPE begda,
p_endda TYPE endda.
START-OF-SELECTION.
go_employee ?= cl_pt_employee=>get_employee( p_pernr ).
CALL METHOD go_employee->get_master_data
 EXPORTING
 im_begda = p_begda
 im_endda = p_endda
 IMPORTING
 EX_I0000 = " infotype 0000
 EX_I0001 = " infotype 0001
 EX_I0002 = " infotype 0002
 EX_I0007 =
 EX_I0008 =
Using this method you can access any infotype(s)
CALL METHOD go_employee->if_pt_employee~get_infotypes
 EXPORTING
 i_itlist =
 I_FROMDATE =
 I_TODATE =
 I_FILTER =
 I_NOAUTHCHECK =
 IMPORTING
 E_RESULT =
 E_RETCD =
END-OF-SELECTION.[/code]
The class is final. However, if you need a class hierarchy simply define your z-classes having CL_PT_EMPLOYEE as instance attribute.
Regards
Uwe

Data errors/changes in unicode database Once all code is unicode compliant

Hi All,
This is regarding unicode project.
We have currently made all the programs unicode complaint
and the database we are using is not unicode database.
We are moving now the entire code to the Unicode database system.
1>Could anyone tell what kind of data errors that might be encountered due to this new database system.
2>What kind of data changes regarding the format/data we might observe in the output files generated.
Any expertise and experiences in the similar upgradation will be very helpful..
Thank you all in advance

Hi Kumar,
each code page encodes characters into a binary representation. ASCII is may be the best known. It encode 128 characters with seven bits. The first 32 characters are control characters for printers and terminals like carriage return and bell. Then there are some special characters like Space and Comma followed by digits and the characters of the roman alphabet in upper case and lower case representation. Unicode is another code page which is defined in unicode standard documentation. Because unicode characters are wider than one byte (the current standard contains almost 100.000 characters) there are different encoding used in applications. The most used encoding is probably UTF-8 which is used by DB2 and Oracle. MaxDB uses UTF-16 which uses much more space for most used characters. Languages use characters from a code page to build words. You may have multiple code pages in one system (MDMP) or a unicode system which supports all languages on a single code page.
I hope this help you to understand the difference between a code page and a language. May be you check out the links [http://www.asciitable.com|http://www.asciitable.com] and [http://unicode.org|http://unicode.org].
Best regards
Ralph

Changes to Unicode support in LabVIEW 8.6

There seems to have been a change in the way LabVIEW handles alternative text input between 8.5.1 and 8.6.
In 8.6, if I try to use type something in Hebrew (alt+shift in Windows changes the input language), the words come out in the wrong order (the first word appears on the left instead of on the right). The actual order of the letters in the word appears correctly (right to left), although sometimes the first letter in the text gets stuck on the left size.
If I try to use Hebrew in a label, I get a message telling me that I can't type a Unicode string into labels and enums.
In all of these cases, copying a string from Notepad and pasting it into LabVIEW displays it correctly (including in labels).
I have tried doing this with UseUnicode INI key set both to T and to F and it happens in both cases.
This SUCKS. Big time. Really.
I know that LabVIEW doesn't officially have support for right to left languages, but at least in previous versions it would sort of behave. I'm pretty sure this isn't what people who were expecting more Unicode support were thinking about.
Does anyone have any idea for a workaround? The only two I can currently think of is copying and pasting or writing a small VI which will reverse the text on demand, both of which are bad solutions.
If there's a patch planned, fixing this will definitely get my vote as something that deserves going in there.
P.S. I'm not sure why the Hebrew input is treated as Unicode. If I'm not mistaken, changing the input language in Windows should still result in ASCII characters and in previous versions it does (the Hebrew chars in the code page LabVIEW uses in 7.0 start at ASCII E0 and in 8.6 it starts at D005 with the next letter being D105).
P.P.S Did I mention this sucks?
Try to take over the world!

I'm going to suggest something really strange as a workaround, but, trust me, I have historical precedent for suggesting this...
Try editing the keyboard shortcuts for LabVIEW and change Quick Drop to be something other than ctrl+spacebar.
Why might this help the problem? When I developed the alignment grid, I thought that ctrl+# was a very intuitive shortcut key for toggling the grid on and off (since the hash symbol looks like a grid). What we found was that when the OS language was set to French, users could no longer type many of the extended grammer characters. The reason was that a critical scan code for the extended character sets overlapped with the scancode for ctrl+shift+3. In LV 8.6, we added ctrl+space, which is the first non-alphabetic shortcut key we've added since the ctrl+#. It might be that whatever keyboard scancode is used for Hebrew happens to overlap, and the code is being translated into a shortcut key for LV instead of a typed character.
I have no evidence that this is what is happening, but it is the only analagous situation that I know of, so I suggest it as something to try.

Extended ASCII changing to UNICODE in Oracle9i?

Hello,
We're just getting to verifying support for our applications against Oracle9i database. Historically, we've been supporting Oracle8 and Oracle8i, and they work just peachy.
On some of our tables, we have a varchar column that is 255 characters long. We often import data that is exactly 255 chars in length. With 9i, if the data is 255 chars long, and contains any extended ASCII chars (such as degree symbol or plus/minus symbol, both of which we use), that row will fail to be imported. My personal impression is that it is being converted to UNICODE, which of course means that it becomes a two-byte character, and that means that this 255 char string is now 256 chars (bytes, actually, but you know what I mean), and can't be loaded into a varchar(255).
We are willing to change our schema, but cannot do so until our next release. We need to get this release working on 9i, without changing the schema.
Is it possible to import (using sqlldr) extended ASCII characters without changing them into Unicode characters?
I have tried changing my NLS_LANG settings to US7ASCII (which is definitely wrong, it changes the extended chars into zeros) and I have tried WE8MSWIN1252, which does preserve the symbols, but does not preserve the ASCII encoding...
I have tested the application against a changed schema ( just extended the varchar(255) to varchar(265)), so I know it works, but we've alreacy frozen this release, so I can't include the new schema...
I am totally open to any suggestion that does not involve schema changes...
Thank you,
William

My previous post is not really relevant to your problem.
What character sets are you using in Oracle 8, Oracle 8i
and Oracle 9i?
For example:
SQL> select * from nls_database_parameters
2 where parameter = any('NLS_CHARACTERSET','NLS_NCHAR_CHARACTERSET');
PARAMETER VALUE
NLS_CHARACTERSET WE8ISO8859P15
NLS_NCHAR_CHARACTERSET AL16UTF16
According to Oracle's documentation,
up to three character set conversions may be required for data definition language
(DDL) during an export/import operation:
1. Export writes export files using the character set specified in the NLS_LANG
environment variable for the user session. A character set conversion is
performed if the value of NLS_LANG differs from the database character set.
2. If the export file's character set is different than the import user session
character set, then Import converts the character set to its user session character
set. Import can only perform this conversion for single-byte character sets. This
means that for multibyte character sets, the import file's character set must be
identical to the export file's character set.
3. A final character set conversion may be performed if the target database's
character set is different from the character set used by the import user session.
To minimize data loss due to character set conversions, ensure that the export
database, the export user session, the import user session, and the import database
all use the same character set.

OS 10.7, SMB Connection, Change to Unicode with Extended Security on Windows Server 2008 Standard

Hi All, I've searched Google, and I've also contacted Apple Support with no luck: I want to implement unicode with extended security on Windows Server 2008 Standard server shared folders so that Lion can connect normally (i.e. Finder->Go->Connect to Server->IP Address or server name) to SMB shares and access files. I'm lacking information; has anyone actually implemented unicode with extended security? If so, how?
Thanks in advance.
Tom

Thanks for the reply aorlich. Do you mean enable file sharing on my Mac? With file sharing enabled, I still cannot get to my Windows 7 shares, although the files on my Mac do become available to Windows. Thanks again.

How to change unicode of a variable in PowerShell

Hi
I am trying to store a value of a git command into a variable. The command results in a name that contains a Danish Alphabet character. When I give that git command only, on the prompt I get the correct result. As shown below:
PS C:\WINDOWS\system32> git config user.nameJohn Møller
but when I store the result of this command into a variable and then display that variable I get different result. what wrong am i doing? Is it something to do with unicode utf8? can I use get-content -encoding utf8 to change the unicode setting of a variable.
I know get-content work with files.
PS C:\WINDOWS\system32> $nameingit = git config user.name
PS C:\WINDOWS\system32> $nameingit
John M├©ller
Any help will be appreciated.
Regrds

This is my code which I am trying to run i PowerShell. I am simply comparing two values. One is coming from a command "$nameingit = git config user.name" and other from $name which full user name of the current user on the machine. next, i first
check if there is any special character in the $name or $nameingit. if it is there then i try to use get-content command to change the unicode to utf8. But it does not work for me. All the links talk about sending out put to file in utf8 but I want to change
the unicode of variable itself so that it can read danish alphabets.
$nameingit = git config user.name
$dom = $env:userdomain
$usr = $env:username
$name=([adsi]"WinNT://$dom/$usr,user").fullname
if ($name -match '[^a-zA-Z0-9 ]')
$name = Get-Content -Encoding UTF8 $name
if ($nameingit -match '[^a-zA-Z0-9 ]')
$nameingit = Get-Content -Encoding UTF8 $nameingit
if ($nameingit.trim() -eq "$name".Trim())
$usrchk = "PASS"
else
$usrchk = "Failed"

Unicode changes for hex values

HI,
We are working on upgrade to ECC 6. 0 and we have the following program which we need to make unicode compatible.
In this program there is a structure which is declared as follows
data:    begin of trans occurs 0,
           x     type x value '00',
           c_00 type c value ' ',
           soh   type x value '01',
           c_01 type c value ' ',
           stx   type x value '02',
           c_02 type c value ' ',
           etx   type x value '03',
           c_03 type c value ' ',
           eot   type x value '04',
           c_04 type c value ' ',
           enq   type x value '05',
           c_05 type c value ' ',
           ack   type x value '06',
           c_06 type c value ' ',
           bel   type x value '07',
           c_07 type c value ' ',
           bs    type x value '08',
           c_08 type c value ' ',
           ht    type x value '09',
           c_09 type c value ' ',
           lf    type x value '0A',
           c_0a type c value ' ',
           vt    type x value '0B',
           c_0b type c value ' ',
           ff    type x value '0C',
           c_0c type c value ' ',
           cr    type x value '0D',
           c_0d type c value ' ',
           so    type x value '0E',
           c_0e type c value ' ',
           si    type x value '0F',
           c_0f type c value ' ',
           dle   type x value '10',
           c_10 type c value ' ',
           dc1   type x value '11',
           c_11 type c value ' ',
           dc2   type x value '12',
           c_12 type c value ' ',
           dc3   type x value '13',
           c_13 type c value ' ',
           dc4   type x value '14',
           c_14 type c value ' ',
           nak   type x value '15',
           c_15 type c value ' ',
           syn   type x value '16',
           c_16 type c value ' ',
           etb   type x value '17',
           c_17 type c value ' ',
           can   type x value '18',
           c_18 type c value ' ',
           em    type x value '19',
           c_19 type c value ' ',
           sub   type x value '1A',
           c_1a type c value ' ',
           esc   type x value '1B',
           c_1b type c value ' ',
           fs    type x value '1C',
           c_1c type c value ' ',
           gs    type x value '1D',
           c_1d type c value ' ',
           rs    type x value '1E',
           c_1e type c value ' ',
           us    type x value '1F',
           c_1f type c value ' ',
         end of trans.
Now in order to make it unicode compatible we have to replace all the declarations involving 'type x'
into respective character equivalents. This is usually done using the class 'cl_abap_char_utilities'
But this can be used only for a few attributes like horizontal_tab, vertical_tab,linefeed,form feed
etc. apart from these things the structure also has many declarations which are not maintained in the
above mentioned class.
For example
type x value '1D' group separator
Type x value '1E' record separator
Type x value '1F' unit separator
Type x value '11' etc are not maintained in the attributes of the class.
Do you know which class to use for these values of hex.
Assured Points for useful answers.
Thanks,
Shobana

Hi,
I got the same problem, while changing to unicode system.
Here is an example for the '1D' group separator:
data: x_1D type x value 29,           " Hex 1D = Dec 29
         x_char.
CALL FUNCTION 'SCMS_BIN_TO_TEXT'
EXPORTING
     BIN_LINE        = x_1D
IMPORTING
     TEXT_LINE       = x_char
EXCEPTIONS
     FAILED          = 1
     OTHERS          = 2.
This works quite fine for visible and unvisible characters.
Hope I can help anyone,
ms

CRVS2010 Beta - Cannot export report to PDF with unicode characters

My report has some unicode data (Chinese), it can be previewed properly in the windows form report viewer. However, if I export the report document to PDF file, the unicode characters in exported file are all displayed as a square.
In the version of Crystal Report 2008 R2, it can export the Chinese characters to PDF when I select a Chinese font in report. But VS2010 beta cannot export the Chinese characters even a Chinese font is selected.

Barry, what is the specific font you are using?
The below is a reformatted response from Program Management:
Using non-Chinese font with Unicode characters (Chinese) the issue is reproducible when using Arial font in Unicode characters field. After changing the Unicode character to Simsun (A Chinese font named 宋体 in report), the problem is solved in Cortez and CR both.
Ludek

Unicode issue with Boot Camp XP

My Boot Camp XP is running perfectly fine. However, I have a piece of software that has a process which involves renaming files, and this renaming now results in some weird file names (the software does not do this when running a "regular" Win XP). The support for the software told me to try changing the unicode setting (to UTF-8) - how do I go about this? Thanks!

Actually, you must have Windows finish its installation before installing the Bootcamp Drivers. When you get in your desktop for the first time, go to: Start> My Computer> Select your Mac's DVD Drive. Look for an "eject" button in the Windows Explorer window.
You may also want to check the Bootcamp Installation guide for Mac OS X Snow Leopard (10.6), it comes handy in these situations:
http://manuals.info.apple.com/en_US/Boot_Camp_Install-Setup_10.6.pdf
This is the one for Mac OS X Lion (10.7):
http://manuals.info.apple.com/en_US/boot_camp_install-setup_10.7.pdf
EDIT:
Added a video tutorial from CNET, but follow the Apple Provided installation guide:
http://www.youtube.com/watch?v=9dLcJmDIccc
This video is more up to date:
http://www.youtube.com/watch?v=X-CXTovYk3A&feature=related
Note that the tutorial says that Windows 7 is not compatible, this not longer the case after the release of Bootcamp 3.1.
Message was edited by: vea1083

Error in unicode export...

Hi,
We are doing an inplace conversion of an ERP2005SR2 system. We have just upgraded the system from 4.6C yesterday and are now performing an unicode conversion.
Unfortunately we have an error in the unicode export... See below:
From the SAPINST_DEV.LOG file:
ERROR      2007-08-25 17:08:03 [iaxxbdbld.cpp:1001]
           CR3ldStep::startR3ldProcesses lib=iamodload module=CR3ldStep
MSC-01015 Process finished with error(s), check log file G:\usr\sap\SAPinst\CPC\EXP/SAPSDIC.log
From the SAPSDIC.LOG file:
/sapmnt/BNP/exe/R3load: START OF LOG: 20070825202939
/sapmnt/BNP/exe/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
/sapmnt/BNP/exe/R3load: version R7.00/V1.4
Compiled Aug 8 2007 00:22:00
/sapmnt/BNP/exe/R3load -datacodepage 4102 -e /usr/sap/SAPinst/CPC/EXP/SAPSDIC.cmd -l /usr/sap/SAPinst/CPC/EXP/SAPSDIC.log -inplace
DbSl Trace: CPFB755 occured. Refer to job log.
(DB) INFO: connected to DB
(EXP) INFO: check NameTab widths: Result=0.
(RC) WARNING: unexpected "ext:" entry at line 6 in file /usr/sap/SAPinst/CPC/EXP/SAPSDIC.cmd,
            entry will be ignored
(RSCP) WARN: UMGCOMCHAR read check, skip: no data found; probably old SPUMG.
(RSCP) INFO: "/usr/sap/SAPinst/CPC/EXP/SAPSDIC004.xml" created.
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(RSCP) INFO: UMGSETTINGS nametab creation: ok.
(RSCP) INFO: Global fallback code page = 1100
(RSCP) INFO: Common character set is not 7-bit-ASCII
(RSCP) INFO: Collision resolution method is 'fine'
(RSCP) INFO: R3trans code pages = Normal
(RSCP) INFO: EXPORT TO ... code pages = Normal
(RSCP) INFO: Check for invalid language keys: active, by default
(RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
(RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
(RSCP) INFO: I18N_NAMETAB_ALT_ALLOW = 10000
(RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
(RSCP) INFO: I18N_NAMETAB_OLD_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
(GSI) INFO: dbname   = "BNPSAP001                                                                                "
(GSI) INFO: vname    = "DB400                           "
(GSI) INFO: hostname = "SAP001                                                          "
(GSI) INFO: sysname = "OS400"
(GSI) INFO: nodename = "SAP001"
(GSI) INFO: release = "3"
(GSI) INFO: version = "5"
(GSI) INFO: machine = "006500039C6C"
(GSI) INFO: instno   = "0020141614"
(EXP) INFO: starting NameTab check. Allow 999999999 misses in DDNTT, 10000 misses in DDNTT_CONV_UC, 0 outdated alternate NameTab entries according to CRTIMESTMP.
(EXP) INFO: /SSF/DHEAD                        missing in DDNTT_CONV_UC
(EXP) INFO: /SSF/DTAB                         missing in DDNTT_CONV_UC
(EXP) INFO: /SSF/PTAB                         missing in DDNTT_CONV_UC
(EXP) INFO: TIBAN_ACTIVE                      missing in DDNTT_CONV_UC
(EXP) ERROR: entry for COPABBSEG                         in DDNTT is newer than in DDNTT_CONV_UC: 20070825073714 > 20070825073318
(EXP) ERROR: entry for COPABBSEG_GLX                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073756 > 20070825073318
(EXP) ERROR: entry for COPACRIT                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073801 > 20070825073318
(EXP) ERROR: entry for COPAOBJ                           in DDNTT is newer than in DDNTT_CONV_UC: 20070825073804 > 20070825073318
(EXP) ERROR: entry for EE72_COPAKEY                      in DDNTT is newer than in DDNTT_CONV_UC: 20070825073756 > 20070825072528
(EXP) ERROR: entry for JBDCHARDERI                       in DDNTT is newer than in DDNTT_CONV_UC: 20070825073804 > 20070825071134
(EXP) ERROR: entry for JBDCHARPAFO                       in DDNTT is newer than in DDNTT_CONV_UC: 20070825073805 > 20070825071134
(EXP) ERROR: entry for JBD_STR_FO_PA_CHAROBJ             in DDNTT is newer than in DDNTT_CONV_UC: 20070825073805 > 20070825071127
(EXP) ERROR: entry for JHF11_KOMP_STR                    in DDNTT is newer than in DDNTT_CONV_UC: 20070825073820 > 20070825071037
(EXP) ERROR: entry for JVKOMP                            in DDNTT is newer than in DDNTT_CONV_UC: 20070825073822 > 20070825070937
(EXP) ERROR: entry for KOMG                              in DDNTT is newer than in DDNTT_CONV_UC: 20070825073808 > 20070825070802
(EXP) ERROR: entry for KOMGF                             in DDNTT is newer than in DDNTT_CONV_UC: 20070825073823 > 20070825070802
(EXP) ERROR: entry for KOMGFNEW                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073836 > 20070825070802
(EXP) ERROR: entry for KOMGFOLD                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073838 > 20070825070802
(EXP) ERROR: entry for KOMP                              in DDNTT is newer than in DDNTT_CONV_UC: 20070825073814 > 20070825070755
(EXP) ERROR: entry for KOMPAKE                           in DDNTT is newer than in DDNTT_CONV_UC: 20070825073805 > 20070825070755
(EXP) ERROR: entry for OICIL                             in DDNTT is newer than in DDNTT_CONV_UC: 20070825073825 > 20070825070219
(EXP) ERROR: entry for OIRCPMITEM                        in DDNTT is newer than in DDNTT_CONV_UC: 20070825073826 > 20070825070148
(EXP) ERROR: entry for STR_KOMG                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073828 > 20070825063750
(EXP) ERROR: entry for SVVSC_COPA                        in DDNTT is newer than in DDNTT_CONV_UC: 20070825073757 > 20070825063738
(EXP) ERROR: entry for TRCON_CONTRACT_DATA               in DDNTT is newer than in DDNTT_CONV_UC: 20070825073846 > 20070825053905
(EXP) ERROR: entry for TRCON_CONTRACT_DATA_MM            in DDNTT is newer than in DDNTT_CONV_UC: 20070825073847 > 20070825053905
(EXP) ERROR: entry for TRCON_CONTRACT_DATA_SD            in DDNTT is newer than in DDNTT_CONV_UC: 20070825073848 > 20070825053905
(EXP) ERROR: entry for TRCON_IT_KOMP                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073830 > 20070825062450
(EXP) ERROR: entry for TRCON_OUTP_DBDATA                 in DDNTT is newer than in DDNTT_CONV_UC: 20070825073848 > 20070825053905
(EXP) ERROR: entry for WB2_EKOMP                         in DDNTT is newer than in DDNTT_CONV_UC: 20070825073831 > 20070825060540
(EXP) ERROR: entry for WCB_COND_DATA                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073848 > 20070825053905
(EXP) ERROR: entry for WCB_COND_DISP                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073839 > 20070825053905
(EXP) ERROR: entry for WCB_KEY_CHANGE                    in DDNTT is newer than in DDNTT_CONV_UC: 20070825073843 > 20070825053905
(EXP) ERROR: entry for WCB_KOMG                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073832 > 20070825053905
(EXP) ERROR: entry for WCB_KOMG_HELP                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073834 > 20070825060526
(EXP) ERROR: entry for WRF_POHF_KOMP_STY                 in DDNTT is newer than in DDNTT_CONV_UC: 20070825073844 > 20070825060357
(EXP) INFO: NameTab check finished. Result=2 #20070825203013
(EXP) INFO: check for inactive NameTab entries: Result=0.
(DB) INFO: disconnected from DB
/sapmnt/BNP/exe/R3load: job finished with 1 error(s)
/sapmnt/BNP/exe/R3load: END OF LOG: 20070825203013
I have an OSS message on "very-high" on this error, but they are not helping very much! SAP has proposed note 738858 were we set two environment variables. We have done this and that did not help.
We have upgraded and unicode converted two test systems and one development system in the last 2 months without this error.
Do you have any ideas?
Best regards
Henrik Hviid

Hello!!:
I'm doing a CU&UC (as say the CU&UC Guide), and now i'm in the phase of upgrade from 46C MDMP to ECC6.0 no unicode (later in other phase i've to change to unicode). I've generated all the SCAN's, and launch the SAPup (Upgrade Process). The phase UPGRADE/SHADOW: START OF PHASE RUN_RADCUCNT_ALL of the SAPup has created the job RADCUCNTUPG, and has been running during 20 hours. It's possible to do this phase quickly??.
Otherwise, in the chapter 3.2.2 Phase RUN_RAD_CUCNT_NEW is going to regenerated the DDIC Objects. So in the Additional Preparation Steps in SAP NW7.0 nonUC (chapter 4.1. of the guide) will be neccesary to launch again the program RADCUCNT with the variant UNICODE-02??? or we've only to do the seven steps that appears in the Guide???.
I've seen the Note 932779, 837173, about this, but i don't see the solution. In the page 7 and 8 of the Note OSS 932779, say that:
- during CU&UC nametab is touched twice, once for upgrade and once for unicode conversion (in phase RADCUCNT_ALL and in phase RADCUCNT_NEW).
- later appears that during unicode conversion preparation (SPUM4/SPUMG) RADCUCNT runs again twice.
So in the chapter 4.1 about additional preparation steps in NW7.0 non UC there is not this step (only appears7 steps). It's really neccesary in the CU&UC in this moment?
Thanks!.
Alfredo.

RFC Problems with VB and Unicode.

Hi all,
i've a VB application wich connects via RFC to an ERP 5.0 Systems and calls BAPI_DOCUMENT_CHANGE2 to checkin a document to a content server.
For non unicode this works fine.
For a unicode system there will be the following errors:
ERROR file opened at , SAP-REL 710,0,0 RFC-VER 3 880476 MT-SL
T:2368 Error in program 'doc2bapi': *>RfcInstallUnicodeStrucure: field 11 (ROW, t:8, l:4) offset 502 too small
(at least 504 expected in sizeofR(SAP_UC) == 1 environment)
ERROR file opened at 20070723 084619 Westeuropäisch, SAP-REL 640,0,113 RFC-VER 3 810862 MT-SL
T:1104 <* RfcDispatch : returns 1:RFC_FAILURE
ERROR file opened at 20070723 084622 Westeuropäisch, SAP-REL 640,0,113 RFC-VER 3 810862 MT-SL
T:2372 <* RfcDispatch : returns 1:RFC_FAILURE
What is wrong and what is to do ?
Regards
Reinhold

Hi Reinhold,
how are you doing ?
thank you for the helpful answer reward points.
what version of VB and connector are you using to connect ?
with NCo ( SAP .NET Connector) every rfc has a different proxy, when the system changes from unicode to non unicode, the proxy in only certain cases needs to be regeneerated ( when unicode chars are part of the i/p output structures)
if you are using the DCOM connector or connecting with your own connector, you will need to follow the same methodology, which in this case will be to point out the unicode character structure, and accomodate it's length.
alternatively you could write a wrapper eliminating the unicode char from the input / output structure, again for this you will need to know the structure
with respect,
amit

Unicode check in 4.6C

Hi All ,
Is there any way to have the unicode check feature i.e.UCCHECK in R/3 4.6C environment ? please let me know if anyone has any clue.
Regards
Yogesh

Hello Yogesh
The report Peter mentioned is RSUNISCAN. The output of the report looks like this:
ABAP Unicode Scan
This program finds coding that does not yet correspond to the restrictive Unicode syntax
(Based on the ABAP Unicode design of June 1999) It finds most of the affected coding, but not all of it.
The main aim of the program is to give you an idea of the kinds of coding that need to be changed for Unicode.
It generates error messages for code that will have to be changed later, and for which there are means in 4.6B for doing so
It generates warnings for cases that will have to be changed later, but where the required statements will
not be avilable until Release 5.0. ...
Regards
Uwe

How to convert Unicode-8 to GB2132

Hello All,
I am using DMEE Engine to download Payment details using T-Code - F110 / Program - SAPFPAYM.
When I download the XML file , it has the Unicode-8.
I want to change the Unicode-8 to GB2132.
I have done the configuration part for GB2132(8400).Bui it will download into Unicode-8.
I also try to use copy the FM-FI_PAYMEDIUM_DMEE_30 ,it will not work here also.
but I dont know how to write the code and how to change the format.
Please suggest me how to change the format.

Hi,
please have a look at SAP notes 969775 and 911190.
Best regards,
Nils Buerckel

Changes in Unicode

Similar Messages

Maybe you are looking for