Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Inbound RFC into ECC6.0

Former Member

‎2008 Aug 21 4:20 PM

0 Likes
366

Hi All,

We have an inbound RFC from a C++ application into R/3. Up until we upgraded our R/3 system to ECC6.0 the application was working fine. After we upgraded to ECC6.0 we keep getting UserID/password incorrect. I do understand the case-sensitiveness of the password in ECC6.0. The issue I have is if the password on the R/3 system is changed to uppercase, the application is working fine. However, if the password on the R/3 side is lower case, the application fails. When I debug the code, the password is lowercase up until the RFC call. I am not sure if we have to upgrade the RFC library or something.

Albert

Hi All,

We have an inbound RFC from a C++ application into R/3. Up until we upgraded our R/3 system to ECC6.0 the application was working fine. After we upgraded to ECC6.0 we keep getting UserID/password incorrect. I do understand the case-sensitiveness of the password in ECC6.0. The issue I have is if the password on the R/3 system is changed to uppercase, the application is working fine. However, if the password on the R/3 side is lower case, the application fails. When I debug the code, the password is lowercase up until the RFC call. I am not sure if we have to upgrade the RFC library or something.

Albert

Reply
1 REPLY 1
Read only

Former Member

‎2008 Aug 21 4:25 PM

0 Likes
350

Is this RFC custom or standard?

You should make sure that the domain behind that password field should allow lower case letters.

Double click on the field it will take you to the data element , double click on the data element it will take you to the domain.

Check the attribute "Lowercase'. Unless this is checked, the field will always be treated as uppercase.

If this field is a standard field, try to create you own field as changing standard filed domains is not advisable.