Skip to Content
avatar image
Former Member

Upgrading from 4.6 to ECC 6, issues with NCO

We are performing some testing for a planned upgrade of our systems from 4.6D to ECC 6. We have an application that uses the .NET Connector v2.0 to call an RFC for creating warranty claims.

This application works perfectly fine in 4.6, however, when we run the same code against ECC 6 none of the data is being received by the RFC and an empty claim is created. The only difference we've made to the application is the connection string. Instead of connecting through the old RFC method we're now connecting by the SOAP methodology.

Does ECC 6 handle RFCs differently or does anyone have any idea why data suddenly doesn't get passed through?

Just as an additional note, as well, we've run a network sniffer to watch the connection and we can see that the data IS being passed to SAP. Thoughts?

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Apr 04, 2009 at 10:45 AM

    As per my understanding you are using enterprise services for the operation,

    in that case please use test facility in service repository of SAP to test the service.

    Add comment
    10|10000 characters needed characters exceeded