This is the xml which you copied from SXMB_MONI i think.
This xml actually shows the different steps that XI performs in a particular order inorder to process an incoming msg.
The XI pipeline steps for every msg are in this order
1) receiver determination--> 2) interface determination -->3) message split(incase of multiple mappings) ->4) message mapping ->5)technical routing ->6) adapter call.
Once a message is received in XI it will perform the above steps and after completion of each step it will add the relevant information to this XML.
for example in your case:
<?xml version="1.0" encoding="UTF-8" ?>
- <GeneratorLog Version="2">
<DirectoryNode name="Plan_Driven_Procurement_SupplierEnablement" generated="nareshbabu1" datetime="2007-08-22, 15:40:13" description="" />
- <ScenarioNode name="Plan_Driven_Procurement_SupplierEnablement" namespace="http://sap.com/xi/SRM/Basis/Global" description="Plan Driven Procurement with SupplierEnablement" swcv="SAP SRM SERVER 5.0">
- <IntegrationViewNode alias="Plan Driven Procurement with SupplierEnablement">
- <ConnectionNode Status="2" fromRole="MM" fromComponent="SAP R/3" fromAction="Send Z_CREMAS_SUSMM" fromInterface="Z_CREMAS_SUSMM.CREMAS03" toRole="SUS" toComponent="SAP SRM (WITH SAP EBP)" toAction="Business Partner empfangen" toInterface="SupplierPortalTradingPartner_CreateOrChange_In" communicationType="A2A, Asynchronous" mapping="MM2SUSSupplier">
- <b><ReceiverDeterminationNode</b> Status="2" fromParty="" fromService="ECC6_BS" outboundInterface="Z_CREMAS_SUSMM.CREMAS03" toParty="" toService="">
- <p1:ref xmlns:p1="XiReference">
- <p1:vc vcType="D">
<p1:clCxt consider="A" />
</p1:vc>
- <p1:key typeID="RoutingRelation">
<p1:elem />
<p1:elem>ECC6_BS</p1:elem>
<p1:elem>urn:sap-com:document:sap:idoc:messages</p1:elem>
<p1:elem>Z_CREMAS_SUSMM.CREMAS03</p1:elem>
<p1:elem>*</p1:elem>
<p1:elem>*</p1:elem>
</p1:key>
</p1:ref>
<LogMessage type="1" severity="0" message="Required sender service: | ECC6_BS" />
<LogMessage type="1" severity="0" message="Required receiver service: | <b>SRM_BS"</b> />
<LogMessage type="1" severity="0" message="No receiver determination exists for the connection" />
<LogMessage type="2" severity="1" message="A new receiver determination was created" />
<LogMessage type="2" severity="1" message="The new or reused receiver determination was inserted into the configuration scenario and can be processed further independently of the generation step" />
<LogMessage type="2" severity="1" message="Added receiver service: SRM_BS" />
<LogMessage type="3" severity="1" message="Check the conditions for all receivers of the receiver determination. The default result value for the generated condition is: TRUE" />
<b></ReceiverDeterminationNode></b>
The above xml describes the receiver determination details for a msg coming from the the sender service - "ECC6_BS" and outbound interface "Z_CREMAS_SUSMM.CREMAS03" the receiver determined for this is "SRM_BS".
next is the interface determination
<InterfaceDeterminationNode Status="1" fromParty="" fromService="ECC6_BS" outboundInterface="Z_CREMAS_SUSMM.CREMAS03" toParty="" toService="SRM_BS">
- <p2:ref xmlns:p2="XiReference">
- <p2:vc vcType="D">
<p2:clCxt consider="A" />
</p2:vc>
- <p2:key typeID="MappingRelation">
<p2:elem>urn:sap-com:document:sap:idoc:messages</p2:elem>
<p2:elem>Z_CREMAS_SUSMM.CREMAS03</p2:elem>
<p2:elem />
<p2:elem>ECC6_BS</p2:elem>
<p2:elem />
<p2:elem>SRM_BS</p2:elem>
</p2:key>
</p2:ref>
<LogMessage type="1" severity="0" message="Required sender/receiver service: | ECC6_BS / | SRM_BS" />
<LogMessage type="1" severity="0" message="No interface determination exists for the connection" />
<LogMessage type="2" severity="1" message="A new interface determination was created" />
<LogMessage type="2" severity="1" message="The new or reused interface determination was inserted into the configuration scenario and can be processed further independently of the generation step" />
</InterfaceDeterminationNode>
- <OutboundBindingNode Status="2" fromParty="" fromService="ECC6_BS" <b>inboundInterface="SupplierPortalTradingPartner_CreateOrChange_In" toParty="" toService="SRM_BS"></b>- <p3:ref xmlns:p3="XiReference">
- <p3:vc vcType="D">
<p3:clCxt consider="A" />
</p3:vc>
- <p3:key typeID="OutboundBinding">
<p3:elem />
<p3:elem>SRM_BS</p3:elem>
<p3:elem>http://sap.com/xi/SRM/SupplierEnablement</p3:elem>
<p3:elem><b>SupplierPortalTradingPartner_CreateOrChange_In</</b>p3:elem>
<p3:elem />
<p3:elem>ECC6_BS</p3:elem>
<p3:elem>O</p3:elem>
</p3:key>
</p3:ref>
<LogMessage type="1" severity="0" message="Required communication channel: GeneratedReceiverChannel_HTTP" />
<LogMessage type="1" severity="0" message="No receiver agreement exists for the connection" />
<LogMessage type="2" severity="0" message="A new receiver agreement was created" />
<LogMessage type="2" severity="0" message="The new or reused receiver agreement was inserted into the configuration scenario and can be processed further independently of the generation step" />
</OutboundBindingNode>
for the sender ECC6BS and receiver SRM_BS the inbound receiver that is identified is ---"inboundInterface="SupplierPortalTradingPartner_CreateOrChange_In" toParty="" toService="SRM_BS">
The process goes on like like this and XML will get appended after each step. you can use this to figure out in the case of error in your scenario where what is going wrong.
Cheer's
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.