Syndicating with a non unicode environment

When MDM is used as the central data manager what are the known issues when the data is syndicated to a non Unicode environment?

Similar Messages

Mixing Unicode with non-unicode

Hi, Wwe have ECC 6.0 and BI 7.0 running on Windows 2003 and Oracle 10.2.0.4 all on non-unicode
We are about to install another BI 7.0 landscape.
If I install this new BI 7.0 on unicode, should I expect issues when communicating between systems such as BI loads?
Thanks.

BI-Java are in the works for 2009, so, I will need to convert my first BW instance to unicode... ouch, that part was not planned. so, I guess I will have a lot of work in 2009.
Technically it might work with a non-Unicode backend but you never know...
If your BI system is a single codepage system the UC conversion is not that big. The tools are meanwhile so good you shouldn´t have any big issues. Make sure you are on the latest BASIS support package, this will help a lot.
so, I will install the new BI landscape using unicode, that will save me from converting this system later.
yes - definitely.
And if the connected ERP (or CRM or whatever) backend is only single codepaged there won´t be any problems when you exchange data.
Markus

Create PDF with CONVERT_OTF in Unicode system

Hi,
I try to create a PDF file from OTF input with function module CONVERT_OTF.
It worked in a non-unicode environment with problems.
If I use the same coding in a unicode system (6.0) and OTF input
contains real doublebyte unicode characters like arabian/greek characters,
the PDF file shows wrong characters like "ÔÑÙàÜÐÕÞÙ Ôâé" instead of
"רבדל הצור %לועה" or "ЉЊЋЌЎЏАБВГόψχΩΨΧ".
I enable the developer trace for CONVERT_OTF, but the trace also
shows the correct unicode characters.
If I create a PDF file with PDF Creater with the same input on my computer,
PDF file looks fine. SAP PDF file uses Font enconding 'Windows', PDF Creator
uses a 'Custom' font encoding.
Any idea, that's going wrong here?
I install TrueType fonts like described in SAP note 999712 with no success,
but this note refers to SAP_BASIS 011, which is not yet available on SAP Marketplace
(latest is 010 today).
Is there any other configuration to enable PDF unicode support?
Print preview from other SAP transactions looks fine with unicode characters.
thanks for help
/Tibor

>
Juraj Danko wrote:
> Hi,
> I have similar problem than you ... how have you solved it?
> thanks
> Juraj
I found a solution, but I am not sure, if it was for this problem or
output problem with for example PL in non-unicode systems.
I created the input for CONVERT_OTF with CALL FUNCTION 'PRINT_TEXT'.
PRINT_TEXT has to be called with DEVICE = 'PRINTER',
DEVICE = 'ABAP' uses internally the wrong code page.
You have also to set otf_options-tdprinter to a valid printer,
if it is empty, the default printer from user settings is used.
You can use code example from SAP note 413295.
Before you call CONVERT_OTF, you can also check entries with 'FC' in OTF input.
The font (see description of OTF format in SAP help) must be set like described in SAP note 144718.
/Tibor
Edited by: Tibor Gerke on Jan 13, 2011 10:29 AM

Non-Unicode Support Post NetWeaver 2004s

Hi everyone,
Our site runs an existing non-unicode environment, and are aware that we can definetly upgrade our existing environments to NetWeaver 2004s (Basis 7.0).
However will SAP provide future upgrade kits for later releases of SAP (eg Basis 8.x and higher) for non-unicode environments.
Cheers
Shaun

Thanks Matt and Eddy for your replies.
I had already read the "blog" Matt, and Eddy I have spent a heap of time in the service market place reading everything thats available on unicode including oss notes.
However here is a snippit from the blog the Matt directed me too:
========================================================
2. This change only really effects NEW installations of SAP NetWeaver and SAP applications based on SAP NetWeaver that were previously available with non-Unicode installation options.
3. Existing installations of SAP NetWeaver and SAP applications based on SAP NetWeaver that were based on single code pages can be upgraded to the new releases WITHOUT having to convert to Unicode. This is really cool as it protects your existing investments and you can live in the non Unicode world for a <b>little longer</b>.
========================================================
Note on "3." that is says at the end there "for a little longer". ... how long? too what release?
From what I have read so far it sounds like anything above NetWeaver Application Server 7.0 will require a unicode conversion.
Any comments??
Ideally I would like someone to just give me a yes/no answer.
Cheers
Shaun

IChat, ICQ and non-unicode ICQ clients (cyrillic=latin accented letters)

I would like to use iChat to connect to my ICQ account
If somebody with an older ICQ client sends me cyrillic I get garbage (latin accented letters).
If they're using newer ICQ clients I'm getting the message in correct cyrillic.
This imho has something to do with using non-unicode encoding for the messages.
In other ICQ clients (e.g. Adium) I've used there was a setting specifying the encoding to use when there's no explicit encoding. Setting this to windows-1251 was solving the problem for me.
But I see no similar setting for iChat.
Can this be handled somehow ? Is there some preference somewhere ?

Tom Gewecke wrote:
Can this be handled somehow ?
PS There is one thing you could try, namely setting the font used by iChat to one encoded as Win-1251. You can get some here, for example:
http://web.ku.edu/~herron/fonts/download_fonts.html
Whether having these on your system will mess up anything else I don't know.
This didn't worked unfortunately. I'm still getting the text as accented latin letters. Apparently the network layer of iChat is translating them to unicode somehow.
And no : having these fonts installed haven't affected anything else on my system from what I can tell.

Unicode or non-unicode RFCSDK

Has someone experience with connecting an unicode SAP-system with a non-unicode subsystem? Which version of the rfcsdk do I need to compile the subsystem, unicode or non-unicode?

Even though this post is really old, I thought I'd reply for the benefit of others.
Your best bet is to use the unicode version of RFC SDK. Then, irrespective of whether the SAP system is unicode or non-unicode, you only need to send unicode bytes. the SDK will take care of the conversion to the code page of the SAP system.

How to start 1 JCO-unicode-Server and 1 JCO-none-unicode-Server

It is possible to start one JCo-Server that is unicode-able and another one JCo-Server that is not unicode-able in one program?
I want to share one service that my Java-Program is providing for 2 SAP-Systems. But one SAP-System is a Unicode-System and the other a None-unicode-System.
I've implemented the tip of the following site for my Unicode-System, but anyhow it does not function:
http://help.sap.com/saphelp_nw04/helpdata/de/87/b55a4201301453e10000000a155106/content.htm
If I start the JCo-Server for my Unicode-System first, then the communication for this system will work, but for the other, none-unicode system not.
If I start the JCo-Server for my None-unicode-System first, then only the communication for the none-unicode system will work.
Any Ideas??
Or another question: How can I make the Unicode-System communicate-able with a none-unicode JCo-Server?
Thanks for reply.

Hi,
i've solved my problem: I changed all my JCo-Objects in my program from from version 2.1.8 to 3.0.2.
After that I don't needed to input information wether it's a unicode-connection or not.

Unicode Non Unicode

Hi Experts
I have installaed a ECC 6.0 ABAP+ JAVA unicode system. Now for soem reason my management wants to move to a Non-Unicode version.
Is there any way we can make unicode to Non-Unicode conversion or I have to go for a fresh install and start all work fron scratch.

Hello Raj,
As you can see above there is no method to move your system to a Non Unicode System from a Unicode system.
In addition to this, i would point out that even with a non unicode system your java stack will always have to
be unicode even your your abap stack is not.
Kind Regards,
David

RFC destination definition with non-unicode external program

Hello All,
we have one issue with our RFID system connecting to WM system (SWD).
For most functions, external RFID server/middleware makes RFC call to SAP system. Means, from outside system to inside SAP. This seems to be working fine.
But in one case, SAP needs to print label to RFID printer. In this case, SAP is calling external RFID server/middleware using RFC destination. Means, from inside SAP to outside system. This is failing.
We think this has something to do with ECC60 being unicode system, and the RFC destination setup. We define rfc destination "ZRFID_SSI" in SM59. We define it same way as in as-is SSI 4.6B production system. But in SWD ECC60 system, SM59 has more options. We define as 'non-unicode' because target RFID server/middleware is non-unicode Windows server. RFC destination is actually working ok.
To send label to printer, SWD calls function ZFSSIRF202 with remote destination ZRFID_SSI. Listener on RFID server/middleware will respond to function call. This also seems to be working. But then, RFID server/middleware cannot process the data from ZFSSIRF202, log says that data is "0". (Actually, the first time SWD calls, log says 0 data, the 2nd time there is connection failure, the 3rd time it is 0 data, 4th time connection failure, etc, etc.)
Compared with production environment, everything is the same, except that SAP is unicode system. So, our suspicion is, that when ECC60 system sends data, it is encoded somewhat a little different than when SAP 46B system sends data. I have similar experience with our other interface (XSI), also involving RFC desintion, but XML file exchange. Here, ECC60 is encoding XML file with UTF-16, but SAP46B was encoding with UTF-8.
Anyone know how to help ?

Hi Jeongbae,
as of NW 7.0 EhP2, it is possible to directly set the code page in SM59.
In earlier releases, this is not possible.
In general, SAP systems use the logon language (SY-LANGU) to determine the code page, if this is available.
Please check SAP note 788239.
Please also have a look at SAP note 991572 for possible alternative settings, if SY-LANGU is not available.
In addition I would recommend to have a look at SAP note 1021459.
However in order to analyze the problem properly, you need to know the exact short dump text (via rfc trace).
For XML processing, please read SAP note 1017101. UTF-16 should NOT be used in an XML file !
Best regards,
Nils Buerckel
SAP AG

BI-IP with non SAP environment

Hi,
How is BI-IP suitable for Planning , Budgeting and Forecasting with non-SAP environment?
Regards,
UR

Hi UR,
BI-IP works on top of BI (datawarehouse). If you mean load data from non sap into BI and then plan with IP, it can be a good solution, if you mean plan data outside BI it is not possible.
br
Michele

Unicode Errors - Interface with non-Unicode 3rd party system

Does anyone have an experience working with an interface between a Unicode SAP system and a non-Unicode 3rd party system? Would appreciate your input on existing data declaration and logic (prior to SAP Unicode conversion), if changes need to be made to the character types and upload/download functions.
We are doing our testing in a newly converted Unicode system which has interface sending files through SAP Business Connector, and uses TDAccess/COMM-PRESS to encrypt the payment file.
We are getting an COMM-PRESS error that it's not able to get the private key
ERR=>RC=107#Error building signature segment (S1A/S2A) ERR=>#Error getting private key: #PUBLIC KEY FINGERPRINT = , rc = 524
The issue seems to be that the passphrase is not received correctly in COMM-PRESS (codepage 1100) from Unicode SAP (codepage 4102). The passphrase is uploaded from a text file (codepage 1100?) to T_PPLOC and then to W_PPLOC.
TYPES: BEGIN OF T_PPLOC,
         FLINE(64) TYPE C,
       END OF T_PPLOC.
DATA: W_PPLOC(64) TYPE C
CALL FUNCTION 'GUI_UPLOAD'
      EXPORTING
        FILENAME                = W_FILENAME
        FILETYPE                = 'BIN'
      TABLES
        DATA_TAB                = T_PPLOC
    LOOP AT T_PPLOC.
      IF W_PPLOC IS INITIAL.
        MOVE T_PPLOC-FLINE TO W_PPLOC.
      ELSE.
        CONCATENATE W_PPLOC T_PPLOC-FLINE INTO W_PPLOC.
      ENDIF.
    ENDLOOP.
Comparing the results between a Unicode and non-Unicode system, the uploaded passphrase is different because of the codepage. But even if I convert the passphrase first from 1100 to 4102 codepage, it still fails.

Hi,
Try this by sending value to the CODEPAGE parameter of the function module GUI_UPLOAD.
aRs

How to use non-Unicode mode in VB6 with ADO.

I'm using ADO on top of OraOLEDB to connect to Oracle 9.2. The database characterset is AL32UTF8. Since my client can't handle Unicode characters, I need a character conversion. However, arcording to the OraOLEDB document( which can be obtained here http://download-west.oracle.com/docs/cd/B10501_01/win.920/a95498/using.htm#1010255):
"How Oracle Unicode Support Works
OraOLEDB works in two modes, Unicode mode and non-Unicode mode. When the client character set is not a superset of
the server character set, OraOLEDB automatically enables the Unicode mode. In this mode, OraOLEDB stores the data in its cache in the UCS2 encoding scheme. The user should ensure that the database's character set is UTF8 in order to prevent any data loss.
If the client character set is a superset of the server's, the provider operates in the non-Unicode mode. This mode provides slightly better performance as it does not have to deal with larger character buffers required by the UCS2 encoding."
My client can only use NLS_LANG VN8VN3, which is NOT a superset of AL32UTF8, so "OraOLEDB automatically enables the Unicode mode". So if I code like this:
Text1.Font="Some Vietnamese Font"
Text1.Text= rs1.Fields("Name").Value
the display is bad ('?' all over the place). This is because rs1.Fields("Name").Type is adVarWChar, so rs1.Fields("Name").Value is encoded in UCS2. What I need is to make rs1.Fields("Name").Type is adVarChar, but it seems to be impossible since Field.Type is readonly.
When I use MS provider for Oracle, I found out that rs1.Fields("Name").Type is adVarChar, so Oracle do the conversion from/to AL32UTF8 (database character set) and VN8VN3(NLS_LANG) for me.
Since I use LOB and things that MS does not support, I want to use OraOLEDB, so anyone can help me out? It's ugent.
I can see that some 3rd program like SQLNavigator4.3 work well with NLS_LANG = VN3VN8 and DATABASE_CHARACTERSET=AL32UTF8 (i.e the program convert between the 2 characterset).
Please correct me if I misunderstood anything.
I need this ugently. Any help would be appreciated. If I don't make myself clear enough, please let me know.
Thanks in advance.

Thank you for your reply. I started to think that everybody is out on holidays...
The Oracle9i Client version is 9.2.0.1.0
Oracle Provider for OLEDB version is 9.2.0.4.0
Oracle Net version is 9.2.0.1.0, in case you need it.
The Oracle9i Database version is 9.2.0.1.0
But I don't think it is a version problem, is it?

Text Mining with Trex 6.1 in non-portal environment

Hello,
I am using a 46C system with Kpro connected to a Trex 6.10 for indexing DMS-documents. The fulltext search works fine, however I cannot get the text-mining functions to work.
In the Trex 6.10 administration looking at the index parameters i see the text-mining-flag is NOT set.
How can I set the text-mining flag of an index?
Since i have only a 46c system I create the index-category in transaction SKPR07 - but i cannot enable text-mining there (?).
To wrap it up: I want to get not only fulltext-search results but also document features and (maybe) similar documents from trex. How can i achieve this in a non-portal environment?
Any help from you experts would be highly appreciated!
best regards,
Johannes
ps: i posted this here in the EP forum because this seems to be where the trex knowledge is.

Hi Karsten
Problem was that when i create the index from SKPR07 it is always without text-mining flag. But a small modification solved the problem, and now I can use textmining also in the 46C system.
here is how-to:
added 2 new import parameters in the function (on 46c)
FUNCTION SRET_INDEX_STORAGE_CREATE.
""Lokale Schnittstelle:
*" IMPORTING
*"     VALUE(SEARCHENG) LIKE SRETGSTRUC-XSENG
*"     VALUE(CODEPAGE) LIKE SRETRCP-CODEPAGE
*"     VALUE(XUSECLASS) LIKE SRETGSTRUC-XUSECLASS OPTIONAL
-->added     VALUE(FILTER_FLAG) LIKE SRETGSTRUC-X2FLAG OPTIONAL
-->added     VALUE(TEXTMINING_FLAG) LIKE SRETGSTRUC-X2FLAG OPTIONAL
*" EXPORTING
*"     VALUE(RCODE) LIKE SRETGSTRUC-RCODE
*" TABLES
*"      IDXSTORAGETAB STRUCTURE SRETIDSTID
*"      TECHNICALATTR STRUCTURE SRETXTECAT
*"      DOCATTRTAB STRUCTURE SRETDOCATR
*" EXCEPTIONS
*"      CREATION_NOT_POS
set textmining flag to '1' and so now a newly created index has the textmining flag on the trex.
now i can use function (on any webas>6.10)
SRET_C_GET_DOCUMENT_FEATURES to get the document keywords. Great! Now I can (finally) implement the "google-like" document search in the old 46c system.
thank you for your help! your fast replies are very much appreciated!
Johannes

Unicode vs. Non-Unicode with MI

Hi all,
We are looking at doing an installation of MI. We are currently Non-Unicode on our ERP system, although a Unicode conversion project is not too far away.
According to the document: "How To Design a SAP NetWeaver Based System Landscape" (NW 7.0, ver 1, March 2008) on pg 15, it says:
"It is required that an MI system with AS ABAP has the same Unicode type as the MI back-end system: If your MI back-end system is a Unicode system, also install a Unicode MI system (that is, both AS ABAP and AS Java on Unicode); if your MI back-end system is non-Unicode, install an MI system with non-Unicode AS ABAP (that is, AS Java on Unicode and AS ABAP on non-Unicode).
Recommendation
For new installations, it is recommended to install a Unicode based system for all SAP applications and SAP NetWeaver deployments that require an AS ABAP usage type based system (AS JAVA is only available in Unicode). In future all new installations from SAP will be Unicode only."
This is clearly conflicting...We are an English-only shop, we have a Unicode conversion imminent, and SAP's direction is clearly Unicode.
Should we even consider a Non-Unicode install?
Thanks,
Troy

Hi,
install a unicode middleware system for the following reasons:
- Soon the BE will be unicode enabled.
- The MI client is anyway unicode enabled, this means the end users can enter unicode characters anyway. After Unicode conversion of the backend your MI server would be the only non unicode component.
- having the mw as unicode does not harm, even if the BE is non unicode (apart from the bigger DB size due to the code page)
Best Regards,THomas

Can we UseECC6 non Unicode with SRM7.0 Unicode system

Hi SRM Gurus,
Can we use ECC6.0 non unicode system with SRM7.0 Unicode system as a backend?
I am searching for the information regarding the compatability and connectivity between Unicode and nonunicode systems.
Can some please do let me know the web links related to my post or Please do let me know the Possibility for using ECC6.0 Non-Unicode with the SRM7.0 Unicode.
Regards,
Srini

Hi,
RFC communication takes care Unicode conversion. Question is how many languages are used in ERP 6.0. Non-Unicode -> Unicode should not be a problem but Unicode -> Non-Unicode is question.
Is it single codepage system or old MDMP system?
Regards,
Masa

Syndicating with a non unicode environment

Similar Messages

Maybe you are looking for