BW Unicode & Versioning

Hi,
We are in the process of starting our Global BW project. Initially we thought of using 3.1 Unicode system by upgrading our 3.1 Non-unicode system. But I believe SAP are not going to support 3.1 Unicode from 2006 and asking all customer to go for the new installation of BW 3.5 or higher.
Now about some points which I would like to have help,
1. Our go-live time will be sometimes around 2007. In that case, what is your recommendations for the BW version ? Should we go for 3.5 or something higher. Like if we go live on 2007 March and then start our upgradation project to 4.0 - really we should then implement 4.0 now.
2. We are using R/3 4.7 Unicode as our source system. So if we go for BW 3.5 Unicode or higher version, do we need to tweak our R/3 source system a lot ? Like we are not willing to change a lot in R/3. Now we are using the R/3 system with our present Non-unicode BW 3.1 system.
3. Are there any different system as 3.5 Unicode and 3.5 Non-unicode or all the BW 3.5 is Unicode system.
Thanks for your time and appreciate your help and guidance.
Good Day !
Regards,
Arpan

Hi Arpan,
I'll try an address all the questions you entered!
1. SAP BW on unicode is only available as of SAP NetWeaver '04 (SAP BW 3.5). SAP NetWeaver '04 (SAP BW 3.5) is supported until March 2013. As SAP NetWeaver '04 is the latest release and it is <b>available now</b> for customers. I would suggest that you start with this release.
Note: SAP BW 3.1 Content on unicode is <b>not</b> available. You can't order SAP BW 3.1 Content on unicode.
2. I would recommend that you start with SAP BW on unicode.
- If you went with a non-unicode SAP BW there is only minimal impact (non on SAP R/3 Enterprise). The minor impact is ensuring you only extract language texts that you support on your SAP BW system.
It would be simplier to have a unicode SAP BW system to start with because I expect at some time in the future someone will want BW developments to cover language in mulitple code-page.
3. The major difference between a unicode and a non-unicode is that you hvae a fully unicode database and the underlying SAP Web AS kernel can communicate with the unicode database.
- From a SAP BW functionality perspective they are the same.
I hope this helps,
Mike.

Similar Messages

  • Windows API ANSI version and UNICODE version

    Windows API have two version:
    ANSI version and UNICODE.
    I want to display chinese, so i use the UNICODE version. but i find it's some mistake.
    and later,  i change to ANSI version, it's correct.
    why the ANSI version can display chinese, and UNICODE can't.
    i use the api function
    FindWindowA
    GetWindowTextA
    who can tell me?

    I understand Vista is a 32 bit.
    IE 8 is what I have but I would consider IE 9 if that would be necessary.
    Just a bit more update. I just tried to download Adobe FP 10 again with the following results, again:
    The Adobe Download Manager windows shows:
    FP 10.3 Status as 100% "Installation Pending".
    FP 10.2 Status as 100% " Instatlling Application"
    and that will go one forever but never really actually installs anything and just keeps cycling through the "Add to Download" e.g. "Fanbase", "Times Reader"
    and "Adobe Air" (none of which I want added to the download), and the download and installation shows as 100%.
    Go figure!

  • Unicode version 3.2

    Does Java support Unicode version 3.2? How to specify the unicode value of 5 digit long e.g. "\u29C73"? I have tried this but Java interpret is as "\u29C7" + "3".
    Or what version of unicode Java supports?
    Thanks!

    See: http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Character.html
    Java 1.5 supports Unicode Standard 4.0 through the Charactor class.

  • Regd:UTF 8 Unicode Version

    Hi Gurus,
    How to find UTF-8 Version In Database? I need whether it is using version 1.0 or 2.0 like that.
    Regards,
    Simma...

    jeneesh wrote:
    Efficientoracle wrote:
    hi,
    s i need unicode version. How to find it in our database. Am using 11.2.0.3.
    Regards,
    Simma..It cannot change across databases.. As the documentation says, for 11g, it uses unicode version 3.0Oracle Database 11g, Release 1: 5.0
    Cheers,
    Manik.

  • My ERP 2005 - Is it only UNICODE version ???

    I heard that my ERP 2005 which is based on successor version of NW 04 and which is scheduled to release in Oct 2005 only supports Unicode installations ? I can't find any information on this on SAP website or SAP service market place to validate ? Only thing I know is that SAP will no longer support MDMP installations with mySAP ERP 2005.
    Can someone from SAP answer this for us. If we have French, Spanish and English language used which are code page 1100, are we force to convert to unicode if we have to upgrade to mySAP ERP 2005.
    Thanks,
    Raja

    Hi Max,
    The growth varies based on the DB used. Oracle is based on UTF-8 so it has a variable length for fields. As the field length is variable the size of the DB depends on the characters stored.
    Will you have a large numbers of data using exotic characters (like master data) or will you have minimal use of exotic characters and use more ASCII 7 characters? This has a different impact on DB size.
    This is different for each customer so it hard to give an exact answer. The numbers you see from SAP about DB size are conservative estimates.
    With regard to the size of your DB directly after the conversion.
    The conversion process does a full DB reorg so the actual size maybe reduced. If you have a fully reorged DB before the conversion, then expect the DB growth mentioned in the presentations you have mentioned.
    With regard to runtime of the conversion, there are a number of options available to you to speed the conversion. They are wholly dependent on your downtime needs and the hardware you have available. The optimization options are all based on optimizing data I/O and processing speed. 
    For the latest info, check out the TechEd 2005 presentations on the SAP service marketplace (http://service.sap.com/unicode@SAP).
    I hope this helps,
    Mike.

  • When i try to run Firefox i get a error message "cannot run unicode version of ATL80.dll install ANSI" this only happens with firefox,internet explorer, Opera and everything else run fine, have re-installed firefox but still the same. run fine.

    unicode ATL80.dll error message when trying to run firefox
    == This happened ==
    Every time Firefox opened
    == User Agent ==
    Opera/9.80 (Windows NT 5.1; U; en) Presto/2.6.30 Version/10.60

    I had this problem as well. I found that somehow the firefox.exe file had been set to run in compatibility mode for Windows 95.
    To check this on your system Browse to the firefox folder (C:\Program Files\Mozilla Firefox\) and right click on the file "firefox.exe".
    Select "Properties" and then the "Compatibility" tab. Make sure the option "Run this program in compatibility mode for" is UNCHECKED.
    Then try running Firefox as normal. Worked for me.
    Best of Luck.

  • UNICODE version of BDB API

    Hi
    I wonder why Oracle does not give UINICODE version of BDB APIs.
    Regards
    Nisam

    How do you mean? The BDB API is not aware of the encoding of the data it is storing. It returns exactly what you put in. The only times you need to worry about text encodings are with older code that assumes the most significant bit of each byte is unused for text (rare these days) or with code that does locale-aware text processing, such as collation or letter ranges (in regexps) and the like. BDB does none of that.
    So as long as you know what text encoding you put in (UTF-8, -16) you shouldn't have to worry about Unicode. You can safely assume that BDB will not mangle your text. However, if you expect the btree access method to sort your Unicode keys (or duplicate values) according to a language-specific collation, then you'll need to write your own comparison function based on one of the collation algorithms available on unicode.org.
    Hope this helps!
    Dan

  • Poratl Unicode version

    Hi All,
    Is there any way to check whether portal version i have is unicode or Non-unicode.
    Poratl version : Ep6.0 with support-stack 18.
    How to convert Ep 6.0 to unicode enabled.
    Any suggestions plz..
    Thanks in advance.
    Subhash.G

    Just an idea, do a view source on a portal page anywhere.  Do a search in the HTML file for "charset=utf-8" .  If you find that as a meta tag, then you know the portal is producing pages that are trying to tell the browser to interprete the page as unicode.
    I thought SAP were trying to make all installations unicode going forward?  Did they even release a non-unicode SP18 ?

  • Error in installing SAP Web AS ABAP (Unicode Version)

    I have SAP Web AS Java in my machine already, but in order to install XI, I need to install also ABAP unicode. During the installation, I got the following error. I can't interpret it what it is or what I have done wrong. Can anybody give me a hand?
    Here is the error message:
    ERROR 2005-12-16 01:51:17
    MOS-01082  File system node E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE with type NODE does not exist.
    ERROR 2005-12-16 01:51:17
    MOS-01105  Processing of one or more file system node operations of table   Content of table: t_SAPComponent_Filesystem_Action_SHARED with condition WHERE WapsSystemName='J2E' AND WapsInstanceName='DVEBMGS00' AND WapsInstanceHost='vm-w3k-pck' AND OpMode NOT IN('CHECKFREESPACE', 'CHECKIF')  Row[0]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/prfclog" FollowLinks="TRUE" NodeName="C:\usr\sap/prfclog" NodeType="DIRECTORY" OpMode="CREATE"   Row[1]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E" NodeType="DIRECTORY" OpMode="CREATE"   Row[2]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00" NodeType="DIRECTORY" OpMode="CREATE"   Row[3]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/data" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/data" NodeType="DIRECTORY" OpMode="CREATE"   Row[4]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/data/cache" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/data/cache" NodeType="DIRECTORY" OpMode="CREATE"   Row[5]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/exe" NodeType="DIRECTORY" OpMode="CREATE"   Row[6]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/log" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/log" NodeType="DIRECTORY" OpMode="CREATE"   Row[7]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/sec" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/sec" NodeType="DIRECTORY" OpMode="CREATE"   Row[8]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/DVEBMGS00/work" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/DVEBMGS00/work" NodeType="DIRECTORY" OpMode="CREATE"   Row[9]    WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS" NodeType="DIRECTORY" OpMode="CREATE"   Row[10]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe" NodeType="DIRECTORY" OpMode="CREATE"   Row[11]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe/opt" NodeType="DIRECTORY" OpMode="CREATE"   Row[12]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe/dbg" NodeType="DIRECTORY" OpMode="CREATE"   Row[13]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/exe/run" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/exe/run" NodeType="DIRECTORY" OpMode="CREATE"   Row[14]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/gen" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/gen" NodeType="DIRECTORY" OpMode="CREATE"   Row[15]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/gen/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/gen/dbg" NodeType="DIRECTORY" OpMode="CREATE"   Row[16]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/gen/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/gen/opt" NodeType="DIRECTORY" OpMode="CREATE"   Row[17]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/global" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/global" NodeType="DIRECTORY" OpMode="CREATE"   Row[18]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/profile" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/profile" NodeType="DIRECTORY" OpMode="CREATE"   Row[19]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/J2E/SYS/src" FollowLinks="TRUE" NodeName="C:\usr\sap/J2E/SYS/src" NodeType="DIRECTORY" OpMode="CREATE"   Row[20]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap/tmp" NodeType="DIRECTORY" OpMode="CREATE"   Row[21]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans" FollowLinks="TRUE" NodeName="C:\usr\sap\trans" NodeType="DIRECTORY" OpMode="CREATE"   Row[22]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/tmp" NodeType="DIRECTORY" OpMode="CREATE"   Row[23]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS" NodeType="DIRECTORY" OpMode="CREATE"   Row[24]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/in" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/in" NodeType="DIRECTORY" OpMode="CREATE"   Row[25]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/out" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/out" NodeType="DIRECTORY" OpMode="CREATE"   Row[26]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/log" NodeType="DIRECTORY" OpMode="CREATE"   Row[27]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/bin" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/bin" NodeType="DIRECTORY" OpMode="CREATE"   Row[28]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/buffer" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/buffer" NodeType="DIRECTORY" OpMode="CREATE"   Row[29]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/cofiles" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/cofiles" NodeType="DIRECTORY" OpMode="CREATE"   Row[30]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/data" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/data" NodeType="DIRECTORY" OpMode="CREATE"   Row[31]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/etc" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/etc" NodeType="DIRECTORY" OpMode="CREATE"   Row[32]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/log" NodeType="DIRECTORY" OpMode="CREATE"   Row[33]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/sapnames" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/sapnames" NodeType="DIRECTORY" OpMode="CREATE"   Row[34]   WapsSystemName="J2E" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="WAPS_COPY_E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE_C:\usr\sap\J2E\SYS\exe\run\..\UNINSTSAP.EXE" NodeName="E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE" NodeTarget="C:\usr\sap\J2E\SYS\exe\run\..\UNINSTSAP.EXE" OpMode="COPY"  failed.

    Still have the same error message.
    When I look at the log, it fails at some step that tried to copy UNINSAP.EXE to my local drive. It is looking at directory IM01_NT_I386/SAPINST/NT/I386/UNISAP.EXE. This is a path in the "Installation Master" DVD. However, during the intsallation, the installation wizard asked me to insert the RDBMS DVD.  I don't know exactly what it means. Anyway, following is a stack trace. See the last line:
    MOS-01105  Processing of one or more file system node operations of table
      Content of table: t_SAPComponent_Filesystem_Action_SHARED with condition WHERE WapsSystemName='ABP' AND WapsInstanceName='DVEBMGS00' AND WapsInstanceHost='vm-w3k-pck' AND OpMode NOT IN('CHECKFREESPACE', 'CHECKIF')
      Row[0]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/prfclog" FollowLinks="TRUE" NodeName="C:\usr\sap/prfclog" NodeType="DIRECTORY" OpMode="CREATE"
      Row[1]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP" NodeType="DIRECTORY" OpMode="CREATE"
      Row[2]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00" NodeType="DIRECTORY" OpMode="CREATE"
      Row[3]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/data" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/data" NodeType="DIRECTORY" OpMode="CREATE"
      Row[4]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/data/cache" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/data/cache" NodeType="DIRECTORY" OpMode="CREATE"
      Row[5]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/exe" NodeType="DIRECTORY" OpMode="CREATE"
      Row[6]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/log" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/log" NodeType="DIRECTORY" OpMode="CREATE"
      Row[7]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/sec" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/sec" NodeType="DIRECTORY" OpMode="CREATE"
      Row[8]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/DVEBMGS00/work" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/DVEBMGS00/work" NodeType="DIRECTORY" OpMode="CREATE"
      Row[9]    WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS" NodeType="DIRECTORY" OpMode="CREATE"
      Row[10]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe" NodeType="DIRECTORY" OpMode="CREATE"
      Row[11]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe/opt" NodeType="DIRECTORY" OpMode="CREATE"
      Row[12]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe/dbg" NodeType="DIRECTORY" OpMode="CREATE"
      Row[13]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/exe/run" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/exe/run" NodeType="DIRECTORY" OpMode="CREATE"
      Row[14]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/gen" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/gen" NodeType="DIRECTORY" OpMode="CREATE"
      Row[15]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/gen/dbg" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/gen/dbg" NodeType="DIRECTORY" OpMode="CREATE"
      Row[16]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/gen/opt" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/gen/opt" NodeType="DIRECTORY" OpMode="CREATE"
      Row[17]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/global" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/global" NodeType="DIRECTORY" OpMode="CREATE"
      Row[18]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/profile" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/profile" NodeType="DIRECTORY" OpMode="CREATE"
      Row[19]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/ABP/SYS/src" FollowLinks="TRUE" NodeName="C:\usr\sap/ABP/SYS/src" NodeType="DIRECTORY" OpMode="CREATE"
      Row[20]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap/tmp" NodeType="DIRECTORY" OpMode="CREATE"
      Row[21]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans" FollowLinks="TRUE" NodeName="C:\usr\sap\trans" NodeType="DIRECTORY" OpMode="CREATE"
      Row[22]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/tmp" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/tmp" NodeType="DIRECTORY" OpMode="CREATE"
      Row[23]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS" NodeType="DIRECTORY" OpMode="CREATE"
      Row[24]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/in" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/in" NodeType="DIRECTORY" OpMode="CREATE"
      Row[25]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/out" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/out" NodeType="DIRECTORY" OpMode="CREATE"
      Row[26]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/EPS/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/EPS/log" NodeType="DIRECTORY" OpMode="CREATE"
      Row[27]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/bin" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/bin" NodeType="DIRECTORY" OpMode="CREATE"
      Row[28]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/buffer" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/buffer" NodeType="DIRECTORY" OpMode="CREATE"
      Row[29]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/cofiles" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/cofiles" NodeType="DIRECTORY" OpMode="CREATE"
      Row[30]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/data" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/data" NodeType="DIRECTORY" OpMode="CREATE"
      Row[31]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/etc" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/etc" NodeType="DIRECTORY" OpMode="CREATE"
      Row[32]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/log" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/log" NodeType="DIRECTORY" OpMode="CREATE"
      Row[33]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="C:\usr\sap\trans/sapnames" FollowLinks="TRUE" NodeName="C:\usr\sap\trans/sapnames" NodeType="DIRECTORY" OpMode="CREATE"
      Row[34]   WapsSystemName="ABP" WapsInstanceName="DVEBMGS00" WapsInstanceHost="vm-w3k-pck" Key="WAPS_COPY_E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE_C:\usr\sap\ABP\SYS\exe\run\..\UNINSTSAP.EXE" NodeName="E:/IM01_NT_I386\SAPINST\NT\I386\UNINSAP.EXE" NodeTarget="C:\usr\sap\ABP\SYS\exe\run\..\UNINSTSAP.EXE" OpMode="COPY"
    failed.

  • Version of Unicode supported by Java 1.3.1 and 1.4

    Does anyone know exactly which versions of Unicode are supported and NOT supported by Java 1.3.1 and 1.4? My understanding is that v2 and v3.00 are supported in 1.3.1, but not sure about v1.x. Java 1.4.0 supports v3.0x (not 3.1), but what about Unicode v2.x or v1.x? Is there a list somewhere?

    J2RE 1.3.1 provides Unicode 2.1 support. J2RE 1.4 now supports Unicode 3.0. By "support" I mean that:
    1. Unicode character properties are available.
    2. Collation and break iterators should work.
    3. Case map operations should work.
    It would be nice if Character provided an API like getUnicodeVersion(). The javadoc for Character does tell what Unicode version is supported...at least in 1.4.
    J2RE 1.4 does not support Unicode 3.1 or 3.2 because the Unicode specs were not stable at the time the J2RE 1.4 specs were solidified. The Java I18N team is committed to tracking the evolving Unicode standard. The next major release of the Java platform will most likely support the existing version of Unicode at that time.
    Regards,
    John O'Conner

  • Unicode Portal version?

    Hi everyone,
    I'm trying to find information about EP unicode version?  Any clue about it ?  
    Right now, i dont know if there exists one unicode version.. =(
    Thanks for your help !,
    Diego

    hi
    Enterpise portal installer is now unicode compliant only thing is that while u are using any db such as MS sql server apply proper collation  which comes along with the standard installation package to it to make it unicode compliant.
    With regards
    Subrato kundu
    IBM
    SAP Enterprise Portal Technology consultant

  • BSI Tax Factory on ECC 6.0 Unicode

    I'm looking for some help with using BSI Tax Factory on an ECC 6.0 Unicode System.  Does anyone have any experience with using BSI Tax Factory on the Unicode version of ECC 6.0? Were there any special steps that were taken in order to make it work? I spoke with someone at BSI and they told me that Tax Factory was not Unicode compliant and that I should talk to someone at SAP to find out what steps needed to be done to make the system work.  While I inquire further with both SAP and BSI I thought I would post something here as well to see if anyone could offer any assistance.
    Thanks in Advance!
    -Nick

    Hi Nick,
    BSI TaxFactory is not unicode complaint. But in the past we have had customers who converted from non-unicode to unicode and had no problems with BSI TaxFactory.
    Export the BSI related data from the DB and import it back after the unicode conversion. And everything works fine!
    Regards,
    Tarun
    SAP ERP HCM

  • Problem with version 8 and Vista 64 bit?

    Hi. I have just bought a new PC and seem to be having a problem. When I start iTunes I get this message
    "Warning. The registry settings used by iTunes drivers for importing and burning CDs and DVDs are missing. This can happen as a result of installing other CD burning software. Please reinstall iTunes"
    I have not installed any other burning software and have tried to re install iTunes but still get the same message. Any ideas? Software currently installed is:2007 Microsoft Office system Version 12.0.6331.5000 *
    Acrobat.com *
    Adobe Acrobat Version 9.0.0.2008061200 *
    Adobe AIR 1.5 Version 1.5 *
    Adobe Reader Version 9.0.0.2008061200 *
    Agatha Christie - Death on the Nile Version 1.1.0.22 *
    Apple Inc. - Bonjour Version 1,0,5,11 *
    Apple Inc. - iTunes Version 8.0.2.20 *
    Apple Inc. - QuickTime QuickTime 7.6 (1292) *
    Apple Mobile Device Service Version 2.12.33.0 *
    Apple Software Update Version 2.1.1.116 *
    ArcSoft, Inc. - PhotoStudio Version 5.5.0.93 *
    Belarc, Inc. - Advisor Version 7.2x *
    Canon IJ Driver Uninstaller Version 1.4 *
    Canon IJ Utility Uninstaller Version 1, 4, 0, 0 *
    CANON INC. - CNSLMAIN.EXE Version 1, 2, 0, 0 *
    CANON INC. - Easy Guide Viewer Version 1.0.1.0 *
    CANON INC. - MP Navigator EX Version 2, 0, 0, 0 *
    CyberLink - DZM Version 2.00.0222 *
    CyberLink - PowerStarter Version 6.00.2111 *
    CyberLink Corp. - HP DVDSmart Version 2.0.1.2213 *
    CyberLink Corp. - HP DVDSmart Version 5, 0, 0, 0 *
    CyberLink Corp. - HP MediaSmart Music Version 2.0.1.2217 *
    CyberLink Corp. - HP MediaSmart Photo Version 2.0.1.2217 *
    CyberLink Corp. - HP MediaSmart Video Version 2.0.1.2217 *
    CyberLink Corp. - LabelPrint Version 2.5.0.0904 *
    CyberLink Corp. - Power2Go Version 6.0.0.2112 *
    CyberLink Corp. - PowerDirector Version 7.00.2202 *
    CyberLink Corp. - StartMen Application Version 1.00.0613 *
    CyberLink MediaLibray Service Version 2, 3, 2203, 0 *
    CyberLink PowerCinema Version 2.0.1.2217 *
    EasyBits Software AS - Magic Desktop Version 1.0.0.0 *
    Enable HP Product Improvement Data Collection *
    HelpLaunch Version 1.0.0.0 *
    Hewlett-Packard - HP Health Check Scheduler Version 3.1.9.1 *
    Hewlett-Packard - HP Health Check Service Version 3.1.9.1 *
    Hewlett-Packard - HP Installer Version 8,5,0,70 *
    Hewlett-Packard - HP MediaSmart Version 2.0.1.7 *
    Hewlett-Packard - HP Software Update Client Version 4, 0, 12, 1 *
    Hewlett-Packard - HP Total Care Advisor Version 2.4.5106.2815 *
    Hewlett-Packard Co. - hp digital imaging - hp all-in-one series Version 082.000.188.000 *
    Hewlett-Packard Co. - hp digital imaging - hp all-in-one series Version 111.000.006.000 *
    Hewlett-Packard Company - HP Solution Center Version 074.000.017.000 *
    Hewlett-Packard Company - HPEasyBackup Version 1.0.0.1 *
    Hewlett-Packard Company - hpsysdrv Application Version 2.00.00 *
    Hewlett-Packard Company - LightScribe Version 1.14.25.1 *
    Hewlett-Packard Development Company, L.P. - HPSysInfo Application Version 9.5.1.0 *
    Hewlett-Packard, Co. - HP PhotoSmart Essential Version 1.12.0.46 *
    HP Color LaserJet 2600n Version 1, 0, 0, 1 *
    HP Easy Backup Button Service *
    Intel Corporation - RAID Event Monitor Version 8.6.1.1002 *
    Intel Corporation - RAID Monitor Version 8.6.1.1002 *
    Intel(R) Matrix Storage Console Version 8.6.1.1002 *
    Macrovision Corporation - InstallShield (R) Version 10.50 * Macrovision Corporation - Software Manager Version 6, 0 *
    Microsoft (R) Windows Script Host Version 5.7.0.6000 *
    Microsoft - Kbd Stub Version 1.0.9.1 *
    Microsoft Application Error Reporting Version 12.0.6211.1000 *
    Microsoft AutoRoute 2004 Version 11.00.18.1900 *
    Microsoft Clip Organizer Version 11.0.8164 *
    Microsoft Corporation - digital locker assistant Version 1.6.5 *
    Microsoft Corporation - Internet Explorer Version 7.00.6000.16386 *
    Microsoft Corporation - Office Diagnostics Service Version 12.0.6211.1000 *
    Microsoft Corporation - Office Diagnostics Version 12.0.6211.1000 *
    Microsoft Corporation - Office Source Engine Version 12.0.4518.1014 *
    Microsoft Corporation - SelfCert Version 11.0.8164 *
    Microsoft Corporation - Windows Defender Version 1.1.1600.0 *
    Microsoft Corporation - Windows Installer - Unicode Version 4.0.6000.16386 *
    Microsoft Corporation - Windows Version 1.0.0.1 *
    Microsoft Office 2003 Version 11.0.8164 *
    Microsoft Office Document Imaging Version 11.0.8166.2 *
    Microsoft Office InfoPath Version 11.0.8161 *
    Microsoft Office Isolated Converter Environment Version 12.0.6211.1000 *
    Microsoft Office OneNote Version 12.0.6316.5000 *
    Microsoft Office Outlook Version 11.0.8217 *
    Microsoft Office Picture Manager Version 11.0.8161 *
    Microsoft Office Save My Settings/Profile Wizard Version 11.0.8161 *
    Microsoft Open XML Converter Version 12.0.6211.1000 *
    Microsoft Visio Version 11.0 *
    Microsoft® .NET Framework Version 2.0.50727.1434 *
    Microsoft® .NET Framework Version 3.0.4506.648 *
    Microsoft® Works 9 Version 9.07.0613.0 *
    muveeReveal Version 7.0 *
    NOS Microsystems Ltd. - getPlus(R) Helper Version 1.2.0.7 *
    NVIDIA Driver Helper Service, Version 175.78 Version 7.15.11.7578 *
    OsdMaestro Version 1, 0, 0, 5 *
    PC-Doctor, Inc. - Hardware Diagnostic Tools Version 5.1.0.0 *
    PhotoSuite Version 9.4.3.0 *
    Quick Tour *
    Recovery Manager Version 7, 0, 91, 13 *
    Research In Motion Limited - Desktop Tools for RIM Handhelds Version 4.7.0.32 (Release build by unknown) *
    Research In Motion Limited - RIM Handheld Communications Manager Version 4.3.1.15 (Release build by unknown) *
    Shop for HP Supplies Version 2.1.3.0000 *
    SoftThinks - Application CD Creator Version 7, 0, 91, 61 *
    Sonic Solutions - CommonSDK Version 9.0.0.93 *
    Sonic Solutions - CommonSDK Version 9.4.4.1 *
    Sonic Solutions - MediaCapture Version 9.4.3.0 *
    Sun Microsystems, Inc. - Java(TM) Platform SE 6 U7 Version 6.0.70.11 *
    Symantec Core Component Version 1.9.2.84 *
    Symantec Corporation - Firewall Component Version 3.0 *
    Symantec Corporation - LiveUpdate Notice Version 1.5 *
    Symantec Corporation - LiveUpdate Version 3.4.1.234 *
    Symantec Corporation - Norton 360 Version 2.0 *
    Symantec Corporation - Norton Protection Center Version 2008.8.00 *
    Symantec Security Technologies Version 107.0.6.4 *
    WildTangent, Inc. - GameConsole Version 1.0.0.1 *
    WizLink Application Version 1, 0, 0, 1 *

    Did you download the 64 bit version of iTunes? It should download automatically, but it might not.
    If you have the right version of the installer you should have 64 in the name IIRC it is called iTunes64setup.exe.
    This the same as 32 bit iTunes but it includes the 64 bit drivers for burning and the iphone.
    If you got the wrong installer, there is a link to the 64 bit installer on the download page but it is not obvious. The link is in the box lower left under "Windows software"
    http://www.apple.com/itunes/download/

  • SAP WEB AS 6.20 unicode installation question

    I am trying to install SAP WEB AS 6.2 unicode version on SAPDB 7.3 on windows 2000 . I get the following error when i try to install the database instance after the succesfully installing the Central instance.
    INFO 2004-10-11 22:22:50
    'C:\51018821/NT/I386/sdbinst.exe  -I C:\sapdb\data -i C:\sapdb\programs -d C:\sapdb\<SID>\DB -b' returned with '0'.
    ERROR 2004-10-11 22:22:51
    MOS-01082  File system node C:\sapdb\programs\pgm\sapni.dll with type NODE does not exist.
    ERROR 2004-10-11 22:22:51
    MOS-01105  Processing of one or more file system node operations of table   Content of table: tADA_Files  Row[0]    NodeName="C:\sapdb\programs\pgm\sapni.dll" NodeTarget="C:\SAPinst12\sapni.dll" OpMode="COPY"  failed.
    ERROR 2004-10-11 22:22:52
    FJS-00012  Error when executing script.
    When I checked, there is no directory 'C:\sapdb\programs\' created at all.
    The XMOD.log file says
    Execute Command : c:\sapdb\indep_prog/pgm/dbmcli.exe -d <SID> dbm_version INSTROOT
    Execute Session Command : exit
    Error! Connection failed to node (local) for database <SID>: dbmsrv not found
    What does this mean and what do I have to do to correct it ?

    Hello Venkatesh,
    could you please tell me which exact SAP DB version you want to install? That's important in this case, because within version 7.3 there's a switch (from a certain Build level) of the SAP DB Installer (used by the sdbinst program).
    Additionally, please send me installation protocol of sdbinst, located in the directory C:\sapdb\data\wrk. The name of the file will look something like this:
    SAPDB<Installationtype>-<Date>-Time.log
    Kind regards,
    Roland

  • JCo - Unicode issue

    Hi,
      Recently, we migrated SAP to unicode version. Due to this, we are getting the below error when we try to connect from SapJCo to SAP. The version of JCo used is 2.1.6. SAP is hosted on Unix and Java applications are hosted on Windows. We tried with jco.client.codepage= 4103; we are getting different error(RFC_ERROR_LOGON_FAILURE: >> unknown RFC error, no error log found <<) when we give the codepage property.
    Please let us know how to resolve the below issue:
    Exception in thread "main" com.sap.aii.proxy.framework.core.BaseProxyException: Conversion error between two character sets., error key: RFC_ERROR_SYSTEM_FAILURE
          at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
    At the SAP side, we are getting the below errors
    Error analysis
    The error probably occurred when installing the
    R/3 system.
    The termination was triggered in function "RfcExtendedReceive"
    of the SAP kernel, in line 301 of the module
    "//bas/700_REL/src/krn/rfc/abrfcrcv.c#5".
    The internal operation just processed is "FUNC".
    Internal mode was started at 20101124144800.
      CLUDE INCL_INSTALLATION_ERROR
    Edited by: manohar mirle on Nov 26, 2010 2:03 PM

    This got resolved.
    We had to make changes to the XML which is embedded in the java code of R3Connector classes. Changed the encoding type and data types in the XML. It went through.

Maybe you are looking for