Portal language not getting passed to SAP R3 via RFC destination

[Amey-Mogare]

Hello,

I am facing exact same issue as described in

There was no useful reply to above thread so posting it with more info specific to my problem.

I am using CE7.3 EHP1 SPS9 Portal and have a WD Java application calling a Function module in SAP R/3 via RFC destinations (ARFC2 model).

Even though Portal language is DE, RFC returns results in EN only.

I checked following: -

1. In NWA > Modeldata & Metadata RFC destinations > Logon data tab > Language field = blank

2. Logged into SAP GUI with language as DE and executed RFC via SE37 and noticed that result text is in DE.

Any ideas on this? Please help.

Thanks & Regards,

Amey

[hemanth2]

Hi Amey,

Hope you are doing good.

From the WD content admin you can figure out the URL of the application. Inorder to amend the sap-locale parameter, in the standalone webdynpro link, please add: ?sap-locale=en_GB

For example:

http://<server>:<port>/webdynpro/dispatcher/sap.com/tc~sec~ume~wd~umeadmin/UmeAdminApp?sap-locale=DE

is this working?

The following is the heirarchy that determines what language is used in the portal:

   1. Component (iview) language (defined in the portalapp.xml)

   2. Portal Mandatory language (defined in the prtDefault.properties)

   3. User language (defined in the user#s profile).

   4. Request language (defined by the browser).

   5. Portal Default language (defined in the prtDefault.properties)

   6. System Default language (default locale defined by the OS).

For more information check:

#947081 - Locales, languages, date and time formats in Web Dynpro

and

Lookup of Resource Bundle - Portal - SAP Library

____________
Kind Regards,
Hemanth
SAP AGS
 

[Amey-Mogare]

Hello Hemanth,

Thanks for reply. Nice to hear from you too.

Thanks for information regarding hierarchy of logon languages.

But here, issue is different.

WD application's labels etc changes when user changes portal language. But it is not being sent I think to SAP R/3 when RFC call is made.

Is the situation clear?

Thanks & Regards,

Amey

[Amey-Mogare]

Hello Hemanth,

Could you please share your comments on my reply below?

Thanks & Regards,

Amey

[hemanth2]

Hi Amey,

I think we will need to check httpwatch and other traces. The best option would be that you create a OSS incident and we can check this further.

Regards,
hemanth

[Amey-Mogare]

Hello Hemanth,

Yes, I have already raised an OSS message. But replies from SAP on this topic isnt much useful.

51129 / 2015

Thanks & Regards,

Amey

[Amey-Mogare]

Hello Hemanth,

I got below reply from SAP on OSS message that I posted: -

"portal language cannot be sent through JCo connection in ARFC2 anymore.

You have to use the ABAP language setting for the SSO user."

I cannot set any fixed language for SSO user in ABAP profile as it would not serve the purpose.

I need below scenario to work: -

1. Portal language is FR.

2. MODELDATA RFC destination is Current User (Assertion Ticket) and

Logon language field is blank.

3. In SAP R/3, SU01, logon language for this user profile is 'DE' or blank or any other lang..

In above scenario, when RFC is called from Web Dynpro application, the lang that gets passed to R/3 is FR.

Is there any sort of API which I can used in my Web Dynpro Component Controller to 'set' the language in RFC destination?

Thanks & Regards,

Amey

[Former Member]

Amey Mogare,

Have you found a solution to your problem?

Aviad

[Amey-Mogare]

No, Aviad.

[JPReyes]

Hi Amey,

In both JCO's and RFC's you can specify the logon language, I think you might have an incorrect entry, check the logon data.

Regards, Juan

[Amey-Mogare]

Hello Juan,

Thanks for reply.

The requirement is to send Portal language to R/3.

If I mention some language code in Logon Data of destination, it will be 'fixed' setting.

If user switches his portal language from DE to EN, RFC will still show data in DE, which is not what is needed.

Thanks & Regards,

Amey