Adapter for SAP 10.1 | webMethods Adapter for SAP Documentation | webMethods Adapter for SAP Installation and User’s Guide Documentation | Using IFR-XML Format with Adapter for SAP | Overview | Common Error Handling Concepts
 
Common Error Handling Concepts
The different error handling concepts of BAPIs and RFCs are presented at the XML level in a uniform way.
Generally, exception business documents are structured as serialized ABAP OOExceptions which are passed within the root element (InterfaceName.Exception) of the exception document. These serialized exceptions are flexible enough to contain different kinds of error information. Consequently, both BAPI return parameters and function module exceptions are mapped to the representation of serialized exception objects.
The serialized ABAP-OO exception consists of the following XML elements:
XML Element
Description
<Name>
Identifies the exception. Normally a global name.
<Message> (optional) sub-elements:
  <ID>
  <Number>
  <Text> (optional)
The <Message> element references an SAP message that describes the error situation.
Message class
Message number
Error description
<Attributes> (optional) sub-elements:
  <Collection> (optional)


<AttributenameX>
(multiplicity: 0..*)
The <Attributes> element contains additional application specific information.
Table with serialized exceptions that represent single error messages, if error collections have to be returned. Each serialized exception within the <Collection> element has the same structure as the wrapper exception.
Named attributes (AttributenameX = Name of Attribute) in which additional application specific information can be returned.
More detailed information about the XML format defined in the Interface Repository can be found at http://ifr.sap.com.