Win-GUI character encoding different from Logon-Pad-SAP-GUI codepage?

[#1]

Hello,

we use the SAP transaction IView in NetWeaver-Portal 7.0 SPS 18 to provide SSO to our SAP backend ERP system. The IView is set to "Win-GUI" and "using shortcut file". We allready set the "Workplace" parameter to "false" in the "SSFCommandTemplate" inside the "WinGuiRenderLayer.properties" file to ensure that the SAP GUI behaves the same as starting it from the SAP logon pad.

But now we noticed some differences when using a csv export function. Special characters like german "Umlaute" are exported in two different ways. I assume the problem resides in the codepage setting of the SAP GUI. In SAP logon pad we set the option "Coding: Default ANSI for Unicode-Systems". In the "WinGuiRenderLayer.properties" file the option "CharacterEncoding.default" is set to "ISO-8859-1". Does anyone the correct codepage settings? Or maybe the problem lies elsewhere?

Regards,

Marc

[Former Member]

The problem lies in the template for the shortcut file tx.sap. The solution comes with note "1073779 - setting the Frontend Up-/Download Codepage". You already modified the file WinGuiRenderLayer.properties which includes a template for the shortcut file. I appended the parameter /UPDOWNLOAD_CP=1160 to the raw starting with "GuiParm":

Before: GuiParm= /UPDOWNLOAD_CP=1160

That worked.

More usefull notes:

631198 - Verhalten des SAP GUI for Windows im SAP Workplace/Portal (english version is not up to date)

1258154 - EP 7.0: Different behavior for SAP WinGUI in the portal

Günter

[UlfZeisberger]

Hello Gents,

I came across a similar issue.

A FM GUI_DOWNLOAD  with file type 'DAT' put a txt file  names as

abcd.xls to the local disk, with Codepage 4110 it stated in the SAP GUI status bar.. The text file contained German Umlauts when viewed with UltraEdit.

When starting the SAP GUI via SAP Portal, the codepage was 4110 and excel could not display the Umlaut contained in it.

When starting the SAP GUI without Portal, just from the SAP logon pad, the codepage was 1160 and Excel could display the Umlaut.

In the back of my mind I had that there was some iview property with code page.

I found  parameter "Transaction supports unicode" was ticked in my transaction iView.

After I unticked it and tested again, the codepage now also was 1160.

Let's hope this proves to be the solution.

UPDATE:
SAP Note 1889855  tells the use of this option is not supported anymore.

And one should rather add set the codepage one requires in the iview property  "Additional parameters to start SAP GUI"

So I set that parameter to   UPDOWNLOAD_CP=1160

Ulf