cancel
Showing results for 
Search instead for 
Did you mean: 

NCO 2.0 and UNICODE compatibility

rcvt
Explorer

Hi all

We are still running ECC 6 EHP 7 non-UNICODE and busy with HANA readiness exercise and thus UNICODE conversion. During testing it came to light that a critical app that integrates with SAP via NCO 2.0 is not working. 

I am unable to locate any documentation for NCO 2.0 and opened a ticket to request the same (hopefully answered as it is already out of support). 

In general is NCO 2.0 UNCODE aware/enabled? When I check I can only see librfc32.dll present in the application install folder. When the app is doing the RFC call to SAP, the call makes it to SAP, but it seems like the service is then failing when SAP returns the requested information.

I have tried some of the 3.0 UNICODE parameters (e.g. PCS) in the app.config, but no luck thus far. Alternative seems to have the app rewritten to use 3.0 which is a huge task. 

Any help or guidance would be appreciated.

View Entire Topic
rcvt
Explorer
0 Kudos

Hi all

Just in case it may help anyone in the future - what we did as a workaround, in this case, is redirect the non-compliant NCO application to a non-UNICODE SAP system to act as a proxy to the UNICODE system.

Hence we adapted the RFC calls on the proxy system to just be wrappers calling the needed target RFCs on the UNICODE system.

We had to revert to this temporary workaround as the rewrite of the non-compliant NCO application did not fit into you needed UNICODE project timeline. 

Ulrich_Schmidt
Product and Topic Expert
Product and Topic Expert
0 Kudos

Actually, that's a brilliant idea... But it is a bit "shooting sparrows with cannons", isn't it... 🙂
Maintaining an entire R/3 system just to use it as a "call forwarder"...

MarkusTolksdorf
Product and Topic Expert
Product and Topic Expert
0 Kudos

Actually, I don't think that this is a good idea. You should plan for an upgrade of the application to the latest NCo version (3.1) to get rid of outdated and unsecure old .NET framework and NCo versions.

Best regards,
Markus