Document created by tommy_conway636242 Employee on Aug 17, 2017
Version 1Show Document
  • View in full screen mode


While sending an IDOC to SAP, you may encounter an error similar to the one below that shows up in the container logs for the atom.


(7) IDOC_ERROR_PARSE_FAILURE: The metadata for the parsed IDoc was not available. See cause exception for details. : 
state=READING_ENDTAG, charPosition=0, lineNumber=0, columnNumber=0; Caused by: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ORDERS11" with extension "ABCDE123" is unavailable





Please check login credentials. If they are correct, please check the roles for the user used to access SAP, or that you are using the correct user for the connection.


For the error above, a user, who had full access to all RFC calls and IDOC objects, had their role reduced to only one RFC call and one IDOC. This user was then used for the connection in other processes that used different RFC calls and a different IDOC. Changing the user to one who had the correct roles resolved the issue.