Symptom
You have a Java only (AEX) system that is using the IDoc_AAE Adapter transfer between a backend and PI environment. When you try to execute the LUW or restart its status, you face an IDoc exception:
(3) IDOC_ERROR_METADATA_UNAVAILABLE: The data for the IDoc type "??????????????????????????? ?" with extension " SAPRPL RP0CL
Also, from the default trace (SAP Note 1514898) a stacktrace similar to the one below can be seen:
com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ä´€ä„€åŒ€å €â€€â€€â€€â€€â€€â€€â€€ä´€ä„€å€ä´€ä„€åŒ€â€€â€€â€€â€€â€€â€€â€€â€€â€€â€ †" with extension " xxxx xxxx    " is unavailable. (raised by system [<server name>|<RFC destination name>])436)…
…return code: RFC_FAILURE (1)
error group: 104
key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:4396)…
…Caused by: RfcException raised by system
Read more...
Environment
- SAP NetWeaver
- SAP Process Integration
Product
Keywords
idoc, xi, pi, po, sm59, unicode, Process Integration, Process Orchestration, PI, PO, NetWeaver, XI, AEX, Idoc_aee , KBA , BC-XI-CON-IDO , Idoc Adapter J2EE , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview