Unicode in Bex

Hi all
Like mentioned in SAP Note 588480, there are some Unicode restrictions in the BEx front end.
I suppose it has sth to do with the OLE DB which does not support Unicode ?
Does somebody knows the real reason(s) for it; and how to solve this problem ?
Thx in advance!
Filip

Hi,
Can you give me any more details regarding when the redesign to analyser will be available?
We are currently on v3.1 and planning to upgrade early 2005. One of our projects requires BW to report using Cyrillic characters and I understand that the current requirement is to upgrade to v3.5. Will there be additional support to Unicode avalable in v7 that are not available in v3.5?
Any help will be welcomed.
Kind regards,
Roger

Similar Messages

Unicode output in BEx

I am not able to see the report in multi language ( unicode ) in the Bex analyser, I am able to see the multi langauge in Web as well as when I download the report to excel.
Please let us know what setting needs to be changed in order to make sure I see the report in multilanguage in my BEx Reporting.
thanks
Bwinfo

Thanks...
HAs anyone treied to intervene the VB in excel to display Unicode.
As we know during download into excel it workd perfectly fine, can we do any macros on top of excel to ensure it displays int Unicode.
thanks
harish

Assignment of BEx 7 connection parameters in unicode system

Hi, experts!
We faced the following problem:
There is a BEx 7 workbook on BI-server. We use this WB to save data in DSO with remote function module. To call the this FM, in VBA-function we create an object r3 like u201CSAP.Functionsu201D.This object gets BEx Analyzeru2019s current connection parameters. At that moment the following error raises: u201CRun-time error u201861704u2019: Internal application erroru201D.
Our BI-system is Unicode system. In all Non-unicode BI-systems, that we tested, connection parameters are sending successfully. However, if we create "SAP.Functions.Unicode" object, then there is another error: "Run-time error '-2147352568 (80020008)': Bad variant type".
When we use the similar functions in BEx 3.5, assignment of connection parameters is fine with "SAP.Functions" object both in Unicode and non-unicode systems... Using "SAP.Functions.Unicode" does not lead to error, but the connection is not happening in this case.
Could you advice what settings should be done in BI-system or how can we adjust our function to solve connection problen
Functions we use to assign connection in BEx7:
Sub testconnection()      u2018non-unicode
Dim r3, MyFunc As Object
Dim RES_DATA_TBL As Object
Dim ConnObject As Object
Set ConnObject = Run("BEXAnalyzer.XLA!sapBEXgetConnection")
Set r3 = CreateObject("SAP.Functions")
r3.Connection = ConnObject '        here this error raises: "Run-time error '61704': u2018Internal application error".
Set MyFunc = r3.Add("Z_UD_DATA_ODS")
Set RES_DATA_TBL = MyFunc.Tables("RES_DATA")
Result = MyFunc.Call
End Sub
Sub testconnection_UC()      u2018unicode
Dim r3, MyFunc As Object
Dim RES_DATA_TBL As Object
Dim ConnObject As Object
Set ConnObject = Run("BEXAnalyzer.XLA!sapBEXgetConnection")
Set r3 = CreateObject("SAP.Functions.Unicode")
r3.Connection = ConnObject '        here this error raises: "Run-time error '- 2147352568 (80020008)': Bad variant type"
Set MyFunc = r3.Add("Z_UD_DATA_ODS")
Set RES_DATA_TBL = MyFunc.Tables("RES_DATA")
Result = MyFunc.Call
End Sub
Thanks for your replies,
Best wishes,
Sergey Musatov.
Edited by: Sergey Musatov on Nov 23, 2011 7:05 AM

Hi, gurus!
Don't you have any ideas on this problem? It is not solved yet...
We'll be grateful if you care.
Thanks in advance.
Best wishes,
Sergey Musatov.

Bex Analyzer not showing unicode data correctly

Hi all,
we are currently testing unicode data with BW.
when desplaying the data in BEx Analyzer 3.5 there is some data that sows as #. not all.
The connection from BW tosource is unicode and the other side around.
The data is stored as unicode in BW - checking the infoobject masterdata, data displays correctly.
RSRT displays the data correctly - all unicode characters display correctly.
we also made a analyzer 7.0 query which also displays the data correctly.
BEx web also returns the 3.5 query correctly.
Does anyone encountered this in the past or knows why this is happening? the problem is clearly only with bex analyzer 3.5
i am using gui 7.20 with SAP BW 3.5 AddOn Patch 5 for GUI 7.20 patch.

Jason-
We had exactly the same issue. The problem is not in the SAP system, it's in the MS Excel language system. Microsoft does not like to be set up for more than one language. Most users set up their computer for one language. So set up your test computer for... for example, Chinese. Allow English. Log in to Bex in Chinese, and execute your report. You should see Chinese characters, and you may also see English characters as well.
Please note also that if the characteristic text is not maintained in more than one language, you will see the key value instead of the text value. this can become an annoying issue.. for example, we had to write an exit in the datasource so that the customer name (in the communication language) was returned in every single installed langauge to the master data text.
Good luck !

Using three Unicode-enabled languages in BEx at the same time

Hi Guys,
Has anyone been using BEx reports with three or more Unicode-enabled languages at the same time?
Currently we are using English and Korean (Unicode-enabled) in BW 3.1C. Next month we will be in BW 3.5 and we are planning to add two more Unicode-enabled characters (Chinese and Japanese) into BW.
Just wondering if this is possible or not?
Any comments would be appreciated.

Dear Julius Shen ,
Have U able to work on the same.
Is ur issue resolved.
Kindly revert.
Regards,
Shaibaz

Problem when trying to publish Query through BeX in Portal as iView

Hi ,
We are trying to publish BW 3.5 query in EP 6.0.
when we are trying to publish the query as iView in portal, it gives the error message 'System Error'. The J2EE Error Log contains the following error :
#1.5#001321FC0EDF001D0000000100000AF800042349427FEAFD#1164697462095#com.sap.security.core.server.jaas##com.sap.security.core.server.jaas#J2EE_GUEST#2##BID#AMARNATH_RR                     #6AA3FE0EADF14B2593F0019B1DB52607#SAPEngine_Application_Thread[impl:3]_17##0#0#Error##Java###Authentication stack: [].
[EXCEPTION]
#2#evaluate_assertion_ticket#javax.security.auth.callback.UnsupportedCallbackException: Unsupported callback!
     at com.sap.engine.services.rfcengine.security.impl.RFCCallbackHandlerImpl.handle(RFCCallbackHandlerImpl.java:49)
     at javax.security.auth.login.LoginContext$5.run(LoginContext.java:812)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.login.LoginContext$SecureCallbackHandler.handle(LoginContext.java:808)
     at com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule.removeSSOHeader(EvaluateAssertionTicketLoginModule.java:736)
     at com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule.login(EvaluateAssertionTicketLoginModule.java:390)
     at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:69)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:154)
     at com.sap.engine.system.SystemLoginModule.login(SystemLoginModule.java:90)
     at sun.reflect.GeneratedMethodAccessor206.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at javax.security.auth.login.LoginContext.invoke(LoginContext.java:675)
     at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129)
     at javax.security.auth.login.LoginContext$4.run(LoginContext.java:610)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:607)
     at javax.security.auth.login.LoginContext.login(LoginContext.java:534)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:60)
     at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
     at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#001321FC0EDF00140000000600000AF800042349427FF32E#1164697462095#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal()####BID#AMARNATH_RR                     #6AA3FE0EADF14B2593F0019B1DB52607#Thread[JCO.ServerThread-8,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Plain###java.lang.RuntimeException: com.sap.engine.services.rfcengine.RFCException: Incoming call is not authorized#
#1.5#001321FC0EDF00140000000700000AF800042349427FF40A#1164697462111#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal()####BID#AMARNATH_RR                     #6AA3FE0EADF14B2593F0019B1DB52607#Thread[JCO.ServerThread-8,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Plain###java.lang.RuntimeException: com.sap.engine.services.rfcengine.RFCException: Incoming call is not authorized
     at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:188)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Landscape:We have both BW 3.5 and EP 6.0, SP 16 on the same instance in
same physical machine. EP 6.0 works on J2EE engine as an add-in installtion.
Steps we followed for the integration of EP with BW:
1)Create RFC Destination in J2EE Engine:
Parameters:
Program ID: xyz
Gateway host: abc.ad.company.com
Gateway service: sapgw00
Application server host:abc.ad.company.com
System number: 00
Client: BID
Language: EN
User: sapjsf
Password: ********
2)Maintain RFC Destination for SAP EP 6.0
Parameters:
RFC destination: SAP_EP
Connection type: T for TCP/IP connection
Description: SAP EP RFC Destination
Technical Settings:
- Type of activation: Registered server program
- Program ID: xyz
- Gateway host: abc.ad.company.com
- Gateway service: sapgw00
Logon/Security:
- Send SAP Logon Ticket: Activated
Special Options:
Unicode
3)Maintain Portal Server Settings for SAP EP 6.0 in table RSPOR_T_PORTAL
in BW 3.5
RFC destination: SAP_EP
System name: BIDEV
Default: Checked
Portal URL prefix: http://abc.ad.company.com:50000
RM prefix for BW metadata: <empty>
KM service URL: <empty>
P.S.:We have maintained one more dummy entry as per the SAP Note 815044
in the table RSPOR_T_PORTAL.
4)Maintain Single Sign-On in SAP BW
In transaction RZ10, We have maintained following settings:
login/create_sso2_ticket=2
login/accept_sso2_ticket=1
5)Export BW Certificate to SAP BW and
6)Import BW Certificate to SAP EP 6.0
We have followed the above mentioned two steps.
7)Create BW System in SAP EP 6.0
Parameters:
Log on methods: SAPLOGONTICKET
We have created the BW system and the Connection test in WAS Connection
is working fine.
8)Configure User Management in SAP EP 6.0
This step is not maintained as our scenario does not demand it.
9)Export Portal Certificate to SAP EP 6.0 and
10)Import Portal Certificate to SAP BW
This step is also maintained as per Performance Assistant guidelines in
SPRO.
The user that we are trying to log into BeX Web Query Analyzer is
Amarnath_rr who has 'SAP ALL' rights and the same user in EP is assigned'Super Admin' as well as 'Content Admin' role.
Can anyone throw any light on wat the error might be??

Ricky,
a couple of clarifications :
1. Does the report execute independently on the web - when you execute in Query view over IE or through a web template
2. Check if SSO is properly configured - you can check if SSO is enabled by using TCode STRUST in BW. - the status of PSE should be Green.
Arun
Assign points if useful

Corrputed loaded text from an Export Datasource with Unicode

Hi Experts
I am new with BW and this forum helped me a lot in the past year.
I am loading texts to an InfoObject using a Master Data (texts) Export DataSource from another InfoObject. The system is NetWeaver 2004s (BW 3.5) with Unicode.
The InfoObject's Text MD is Language Dependent but users enter the system only with EN language.
For some reason the loaded texts are corrupted.
For example: The original InfoObject has Hebrew texts (that were loaded perfectly from the source system which is also Unicode), but the text in the PSA table and in the text table of the target InfoObject will be: ###########
Can anyone help?

Hi Niraj
Thanks for your answers
Let me explain:
Currently, we load texts with Hebrew chars from the SAP ECC6 system and everything is good (we see Hebrew chars in SAPGUI/BEx/WAD etc.)
The problem occurs when we load these texts from one InfoObject to another, via Export DataSource.
To do that, We generated an Export DataSource for the original InfoObject and assigned it to the target InfoSource of the other InfoObject. After running an InfoPackage for this DataSource, the texts that were loaded to the PSA (and hence, to the target InfoObject texts table) were corrupted - which means that they appeared: ##########
Thanks,
Yaniv

Bex reports in non english language

What setting required to get the Bex reports in Japanese language. Provide more inputs..

Hi,
Regarding to the Japanese Displaying issue, it depends on what Bex version are you using to display the BEx report and please refer to thefollowing information:
1. If you are using BEx3.5 tool    It is necessary to set all the regioan and language settings in
   control panel of the issued machine to "Japan" and "Japanese",
   inculding the "format" "unicode" "keyborad and     languages"       and
   "location" tabs. For more details, please refer to the attached
   "region and language settings.jpg" file.
   After set the language to Japanese, you need to restart your
   PC and then you can verify if the Japanese Characters can be
   displayed correctly in BEx3.5 report.
   Note:Users are supposed to understand Japanese if they need to
   display and read Japanese reports, so all the settings are required
   to set to Japanese, if users need to have PC with English menu
   displayed but with report in Japanese, they can leave "display
   language part" as "English" so the OS system menus will still be in
   English.
2. If you are using BEx7.0 tool
   Basically you don't have to set anything specially on the client
   machine as Bex7.0 is a multiple language supported version, meaning
   with all Engish settings on local machine, once you logon Bex in
   JA, Japanese Characters can also be displayed correctly in the
   Bex reports. Just make sure that the relevatn reports data have
   JA maintained in BW backend system and JA language is installed
   correctly.
Thanks,
Venkat

Error when trying to generate a report using BEX Quesry in Crystal Reoprts

HI Experts,
As per the SAP NOTE we did FP 2.6 Unicode Transports and then SP3 transports. Transports are imported with min Errors.
Now *when am trying to generate a report using BEX Quesry in Crystal Reoprts* am getting error
"Database Connector Error: BAPI Error #:0
Error occurred when starting the parser: timeout during allocate /CPIC-CALL: 'ThSAPCMRCV' "
*When trying to Generate using OLAP CUBE Report Wizard. AM getting Error*
" READING OLAP META DATA FAILED."
Thanks,
Bharath

This is not really the correct forum to be posting Reports issues. However, if I were to guess, your issue is likely related to the known issues related to installing FMw11R1 on machines which had IPv6 enabled. In most cases, disabling IPv6 would correct the problem, however some issues were not resolved even after disabling IPv6 post-install. I would recommend patching to WLS 10.3.6 and FMw 11.1.1.6 as these versions include fixes for all of those issues as far as I recall.
Consider referring to this MyOracleSupport document if you have access:
Steps to Maintain Oracle Fusion Middleware 11g Release 1 (11.1.1) (Doc ID 1073776.1)

EURO sign not displayed correctly after unicode migration

All,
Don't know where exactly to post this, in BI forum or Netweaver Platform.
But here is my question:
We have migrated our SAP BW 3.5 (NW04, SP20) system from codepage 1100 (using general fallback codepage 1160) to unicode UTF-8. After the conversion graphic reports (using internet explorer) do not show the euro sign correctly in the unicode system. In stead of the euro sign a # is shown in the internet explorer window. When looking at the source of the same web page however the euro sign is showed correctly.
When looking at the encoding of the web page it is mentioned that utf-8 is used...
Any ideas...?
Thanks,
Regards, Bart

Hi Manoj,
It is with displaying of graphical data that the error occurs. Text data (tables) on the same web page are shown normally, with the correct euro sign.
When I look at the source of the web page it looks that for the graphic a java script is being called:
/sap/bw/Mime/BEx/JavaScript/JSBW_C_Std.js
Withing the coding I see the euro sign normally, however in the graphical display this is converted to #.
I have run the suggested query. The database nls_characterset is set to UTF8.
Thanks,
Regards,
Bart

Customer names with cyrylic characters are wrongly shown in Bex Analyser

Customer names with Cyrillic characters are wrongly shown in Bex Analyser. The master data is correctly maintained and extracted\loaded by BW for these customer (Master Data object is correct). This might be a Bex Designer issue.
Furthermore, it has nothing to do with the local settings, when copying the name of the customer to Bey Analyzer the name is correctly shown.

Hi,
We are facing the same problem with the turkish characters, Our system is BW 3.10 (3.30 Cont) and ECC 6.0. The turkish characters are displaying correctly at the table level, but not at the RSRT or the Bex level.
The turkish characters are displaying correctly at the table, RSRT and Bex level if we load the same record from the Non-unicode Prod system to the Non-unicode BW Dev system, but if we load from the unicode QA system the same record is not displaying correctly.
Has anybody got a solution for this issue
thanks
Kalyan

Reg: Turkish characters issue on BW 3.10 Bex level and RSRT

Hi,
We are facing the same problem with the turkish characters, Our system is BW 3.10 (3.30 Cont) and ECC 6.0. The turkish characters are displaying correctly at the table level, but not at the RSRT or the Bex level.
The turkish characters are displaying correctly at the table, RSRT and Bex level if we load the same record from the Non-unicode Prod system to the Non-unicode BW Dev system, but if we load from the unicode QA system the same record is not displaying correctly.
Has anybody got a solution for this issue
thanks
Kalyan

Hi,
Yes, we installed transport request, which came with Integration Kit in our BW System.
We are also facing another issue,
ISSUE 2:
We have another publication with oracle DataSource , where we need to publish report(personalized) for 200 users.
Even we configured dedicated processing server for that publication and setting maximum no of connection to 250, it is throwing error like maximum no of concurrent connection reached.
Previously it was working with just 50 connections.
Now we are running this report by setting max no of connection to 500, and doing service restart after each publication.
Otherwise next publication will throw same error again.
Guide me on this also.
Regards
Baby

BI Unicode Conversion impact on Microsft office tools

Hello Friends,
The BI version is BI 7.0, but we are using both Bex 3.x and Bex 7.0.BI 7.0 is being Unicode converted.
Questions
Does Unicode conversion have any impact on running the new/existing reports in 3.x and 7.x
Does Unicode conversion have any impact on running the new/existing WAD reports.
Does Unicode conversion have any impact on any of the Microsoft office products used by BI.
Thanks!

Since Excel is the starting point for BEx Analyzer, Excel 2007 would need to be tested. In BEx Web, if you have Excel as a save as option for queries, you will need to test that too. It also requires that the .NET Framework 3.0 be on the end user machine.
See [OSS Note 1013201|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1013201]

Junk characters displayed when viewing BEx query through WAD

Hello,
I am trying to display the results of a web report containing a BEx query through the "Execute in the Browser" option in WAD. But, junk Chinese characters keep showing up in the display. Also, if I try the same with one of the older web reports, they display fine. But, the moment I make a copy of these and execute without any modifications, the junk characters show up again.
I tried executing through RSRT and there my report works perfectly. So, what could be going wrong or am I missing something?
Thanks in advance!
Menaz

Thanks Emma.
We figured it was related to the Unicode charset while I was going through the source code. I don't think there is any permanent fix yet. But, I followed the posting below and am trying to temporarily fix the error:
Web Application Designer Appearing in Unicode (UTF-8)
Thank you!

Source system Error of BI- Incorrect Unicode Settings

Hi gurus,
We are facing problems in the source system of BI 7.0,after
installation it self .
As we Click on Check for the source systen of BI it is throwing an
information .
"The unicode settings for destination BD1CLNT300 do not match the source
system."
This is leading to failure of Export Datasource creation for BI system.
and even BEx Personalisation for History.
Please Help.
Our system is having following components:
SAPABA -700-18-SAPKA70018
SAPBASIS-700-18-SAPKB70018
PI_BASIS -2005_1_700-18-SAPKIPYJ7I
SAP_BW-700-0020- SAPKW70020
BI_CONT -703-14-SAPKIBIIQ4
Please suggest the correction as per the patch Level.
Regards,
Deepak kansal

Hi Deepak
Please check below link, let me know if this doesnt help you
[https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/6038903c-3c32-2c10-2c8b-c5bb71baab67]
-DU

Unicode in Bex

Similar Messages

Maybe you are looking for