Following interfaces in SUS will use the FEH, if activated and configured: This is possible only for non ESOA type XML interfaces that are not using the Forward Error Handling (FEH). In case of SUS application errors there will be a section called containing the error message encountered during application processing of the XML message. Otherwise you will find more information on the kind of error in the Trace section, which can be accessed from the left side navigation tree. To identify an error in the processed message in many cases you can refer to the content of ’Window 2’ after opening the XML message. To view the details of a specific message, please select it and use the ’Details’ button, or double click on an XML message. You can change the layout and specify the displayed fields and sort order as it is common for an ALV list. The found XML message will be displayed in an ALV result list. Please make sure to set the ’Length of Output List’ parameter depending on your search criteria Displaying results As of SRM 7.0 you can use the report /SAPSRM/PUR_SELECT_MESSAGES in SE38 for finding XML messages for a specific purchase order.If you already know the XML message ID of a particular XML message please select the ’Advanced Selection Criteria’ tab and specify the ID in the field ’Message ID’.In case you are only looking for XML message that are in error status, you can use the selection criteria for ’Status Group’ and specify the value ’Errors’ here.This will give you a list of all XML messages corresponding to the search criteria regardless of what status the message is in.
0 Comments
Leave a Reply. |