Skip to Content
author's profile photo Former Member
Former Member

WDTypeNotFoundException for Adaptive RFC model


after successful implementation and test of the Flight Tutorial for Adaptive RFC, I performed the very same steps for a self made function module on the same RFC system.

However I get the TypeNotFound exception for one of the model class types although I can see the type in the generated dictionary and did an import of the class in the Custom Controller java code.

(The JCO connection is also setup correctly.)

What else can be wrong?

I would appreciate any ideas on what to check next.



Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jul 08, 2004 at 12:21 PM

    Hi Patricia,

    please post the exception here, otherwise it's difficult to give you any advise.



    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Alexandre,

      the cause of your problem is possibly based on the incompatibility of the version of JCO included with your Engine installation to the changes done in the ABAP system you are trying to access. It is not relevant, what kind of connection you use.

      This is an issue in the current implementation of jRFC/JCO in combination with a change done in the ABAP system you're using.

      <i>This issue will be fixed in Stack 11 of NetWeaver 04.</i>

      Regards, Bertram

  • author's profile photo Former Member
    Former Member
    Posted on Jan 13, 2005 at 01:56 PM

    Hi Patrica

    I suppose you need to Check your SLD JCO Connection

    are your Logical systems correctly Mapped to the Server,

    COz that gives u problem of such kind

    Ur WD_ModelData_Dest and WD_RFC_MetaData_Dest are to be cofigured correctly, check and let me know

    With Wishes

    Krishna Kanth

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      Some insight to the WDTypeNotFound Exception

      The error only occured because I wasn't connected properly to the SAP system via JCO. I verified this by taking a different FM available in a live system (where loadbalancing is used). Because the metadata JCO was properly configured to the MSG server (not the workaround I mentioned above), the exception did not occur.

      So the only question that remains is how to connect to the msg.server of a development machine where load balancing isn't set up. the port should be 36XX, where XX = system number, but what about the GROUP? At least for me the default "PUBLIC" didn't work. SID??



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.