Error in JCO trace log for custom IDOC

[Former Member]

I am working with a custom IDOC (ZPROCREL) that worked just fine 3 times a few days ago. Now, all other transmissions result in this error in the JCO Trace files:

JCO.ServerThread-3 [22:35:30:307]: [JNI-LAYER] RFC.incomingRequestHandler(): catch an application exception The meta data for the IDoc type "ZPROCREL" is unavailable.

I'm not sure what has changed to cause this error.

The IDOCs are being created, I can see them in WE02 (IDOC Lists) and they all have a status of "03" for successful.

[Former Member · Accepted solution]

Generally this means the client level handshake between the IDOC listerner and R/3 was unsuccessful. One possibility is that the userid or password in the client properties is incorrect or that userid has been locked out and the listener cannot login into R/3 to complete the handshake.

[Former Member · Accepted solution]

Whew, thanks for pointing where to look. Somehow, someway, someone, changed the credentials on the Client Properties tab in the IDOC Listener to use the xMII server login credentials, not the R/3 login credentials.