Monitoring and Debugging XML Messages in SAP SRM 7.

0 System

Applies to:
SAP SRM 7.0. For more information, visit the Supplier Relationship Management homepage.

Summary
The article describes the procedure to monitor as well as debug the failed XML messages in SAP SRM system. In this scenario, data migration is from SAP R/3 (ECC 6.0) to SAP SRM 7.0 via SAP XI. Author: Saba Sayed

Created on: 12 September 2009

Author Bio
Saba Sayed is a SAP certified NetWeaver ABAP Consultant. She has approximately four years of SAP experience and has worked extensively in ABAP, OO ABAP, Workflow and ALE/IDoc. She has worked on SAP R/3 as well as SAP SRM systems.

SAP COMMUNITY NETWORK © 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 1

.................................Monitoring and Debugging XML Messages in SAP SRM 7........... 3......com 2 .............. 4.................................................................................................................................... 5................ 4 Monitoring XML messages ............................................ 3 Transactions .......................................................................boc................................................................................................................................................................................................ 3 Issue ..............................sap...............................................................................................................1 6................................... 4 Step by step procedure.................................................... 4 Debugging failed XML messages ................................................. 12 SAP COMMUNITY NETWORK © 2009 SAP AG SDN ...................................com | BPX .............................. 3 Definition .......................................................................sdn..................................................sap...................2 Business Requirement................... 2.............bpx....................................................com | BOC ................................................... 6................................................sap..... 6........................0 system Table of Contents 1...................................... 6 Related Content ....................... 11 Disclaimer and Liability Notice .......... 3 Navigation ..........................................

com 3 . ii) Track and debug failed XML messages (Please note: In this case.boc. we will have to monitor and debug its cause in SRM system.sap.sap. For detailed information please check the below link: SAP Exchange Infrastructure 3. SAP R/3 is the sending system and SAP XI is a middleware that connects both the system. so.0 is the receiving system. Exchanging XML Messages The core of the SAP XI infrastructure is a message-oriented communication based on Hyper Text Transfer Protocol (HTTP). Definition SAP Exchange Infrastructure The SAP Exchange Infrastructure (SAP XI) is a middleware that enables you to connect SAP and non SAP systems with each other in a heterogeneous system landscape and transform message content between sender and receiver systems. for example between an SRM document and a Document Builder document.0 system 1.sdn. Navigation SAP NetWeaver > Process Integration > SAP Exchange Infrastructure > Runtime > Integration Engine > Monitoring > Monitor for Processed XML Messages. Business Requirement i) Monitor XML message flow between the sender and the receiver systems via SAP XI.com | BPX . Business content is transferred in the form of eXtensible Markup Language (XML) messages.bpx.sap. 4.) 2. The structure of a message is determined by the interface data structure that is used.SXMB_MONI ABAP Proxy generation – SPROXY SAP COMMUNITY NETWORK © 2009 SAP AG SDN . Both systems are connected to SAP XI by means of special classes called proxies.Monitoring and Debugging XML Messages in SAP SRM 7. Transactions Monitoring XML Messages . Failure is at receiving end.com | BOC . SAP SRM 7.

Red flag means there is an error in XML message.com 4 .com | BPX . It will navigate to the following screen: b.Monitoring and Debugging XML Messages in SAP SRM 7.sap.e. Click on execute button. 6.sap. Step by step procedure 6. SRM system.0 system 5.boc.1 Monitoring XML messages a. SAP COMMUNITY NETWORK © 2009 SAP AG SDN .com | BOC . Go to transaction ‘SXMB_MONI’ to monitor XML messages.sdn.sap. Issue Data migration failed at the receiving end.bpx. We will have to analyze the error and its cause by monitoring and then debugging the failed XML message at the receiving end i.

bpx.sdn.boc.sap. c. SAP COMMUNITY NETWORK © 2009 SAP AG SDN . Select ‘Trace’ (Call Inbound Proxy -> SOAP Header -> Trace) to check the error description on the right-hand side.0 system Select the message and click on ‘Error Information’ pushbutton (as shown in the above picture) to check the error message only. Following screen will appear: d. Now.sap.sap.com | BOC . to display the entire message in detail.com | BPX . either double click on the message or click on ‘Display’ pushbutton as shown below.com 5 .Monitoring and Debugging XML Messages in SAP SRM 7.

Go to transaction ‘SPROXY’ to check the service details. you will get the main record detail (i.sdn.e.Monitoring and Debugging XML Messages in SAP SRM 7. g. 6. f.com | BPX .bpx.sap. Select the respective node and interface (from 7. Get the Receiver namespace and interface details. posted from IDOC). You can reprocess the error message by clicking on ‘Restart’ button as shown in figure ‘e’.com | BOC .1 point ‘f’) on the left-hand side. SAP COMMUNITY NETWORK © 2009 SAP AG SDN . Under Payloads Main Document.com 6 .sap.boc.0 system e.sap.2 Debugging failed XML messages a.

On double clicking the method name (under ‘Methods’ tab).Monitoring and Debugging XML Messages in SAP SRM 7.com 7 . SAP COMMUNITY NETWORK © 2009 SAP AG SDN .com | BOC . you will get the executing code where you could place a breakpoint.boc.0 system On the right-hand side. c. in order to debug the message.sap. double click the Provider Class name.sap. You can debug the message from SPROXY transaction by clicking on ‘Test (F8)’ button on Application toolbar (first screen).sdn.bpx. It will navigate you to the class interface screen as seen below: b.com | BPX .sap.

bpx. Select the respective inputs and execute. Following dialog screen will appear: e.sap. SAP COMMUNITY NETWORK © 2009 SAP AG SDN .com | BOC . It will navigate you to the XML message screen.sdn.com 8 .boc.sap.0 system d.Monitoring and Debugging XML Messages in SAP SRM 7.com | BPX .sap.

following debugging screen will appear. Click on ‘XML Editor’ from application toolbar (4 button from left).) th g. SAP COMMUNITY NETWORK © 2009 SAP AG SDN .com | BOC .sap. Accordingly.sdn.bpx. Copy the message from ‘Main Document’ (SXMB_MONI transaction code) and paste it here. Now you can debug the code and analyze the error and its cause. (By copying the failed message directly in your editor.0 system f.sap. you can take necessary actions for its resolution.com 9 .com | BPX .boc. Save the data and then execute the record. This will save your time and efforts. Since you have set a breakpoint in the code (step ‘b’).sap. you are ready to debug that particular record.Monitoring and Debugging XML Messages in SAP SRM 7.

com | BPX .com 10 .Monitoring and Debugging XML Messages in SAP SRM 7.bpx.com | BOC .boc.sap.0 system SAP COMMUNITY NETWORK © 2009 SAP AG SDN .sap.sap.sdn.

bpx.com | BOC .sdn.sap.sap.sap.com | BPX .Monitoring and Debugging XML Messages in SAP SRM 7.0 system Related Content SAP Exchange Infrastructure Sending an IDoc through XI Failed Problem Description SAP Exchange Infrastructure SAP COMMUNITY NETWORK © 2009 SAP AG SDN .com 11 .boc.

sap. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample. SAP COMMUNITY NETWORK © 2009 SAP AG SDN .sap. including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. SAP will not be held liable for any damages caused by using or misusing the information. You agree that you will not hold.sap.bpx.boc. SAP responsible or liable with respect to the content of this document. code or methods suggested in this document. Changes made based on this information are not supported and can be overwritten during an upgrade.Monitoring and Debugging XML Messages in SAP SRM 7.com | BPX . and anyone using these methods does so at his/her own risk. or seek to hold.com 12 .com | BOC .sdn.0 system Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP.