IDOC not reaching target

Hi all,

I am doing IDOC to IDOC interface.IDOC is reaching XI but it showing red flag for the outbound side.i checked port and partner profiles everything looks fine.

But in RWB in component monitoring i couldnt able to see communication channel that i created in ID.

could any one tell me what could be the problrm.

Regards

Rao

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (2)

you will not c the idoc adapter in the runtime workbench CC monitoring......as it is in the ABAP stack....goto to the sm58 in the sender side and check itis going fine from sender side...and check the sxmb_moni in XI to check the status of the message on the reciver side check teh error status....

to check the idoc monitoring use idx5....

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Nisar,

I did checked in IDx5 it showis fine.Could u please tell me where exactly i can c the errror in the XML message.as outbound side showing Red flag..

Regards

Rao

double click the red flag in sxmb_moni and chceck the error description here and let me know

I duble clicked on the redflag but where i can c error info here.

when you dounle click the message in SXMBMONI...on the left hand side there will be some steps in which loook at the red color ( that will give you the error details)

Hi Nisar,

It showing the following message as i couldnt able to finmd out what is the error i am apsting whole msg i can c here.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Response

-->

- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">

- <SOAP:Header>

- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">

<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>

<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>

<SAP:MessageId>DC8303D9-F930-24F1-BCAC-001AA00BC352</SAP:MessageId>

<SAP:TimeSent>2007-10-25T14:09:27Z</SAP:TimeSent>

- <SAP:Sender>

<SAP:Service>MAG_PI_QB1_SAPR3</SAP:Service>

<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ORDERS.ORDERS04</SAP:Interface>

</SAP:Sender>

- <SAP:Receiver>

<SAP:Party agency="" scheme="" />

<SAP:Service>MAG_PI_QB1_SAPR3</SAP:Service>

<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ORDERS.ORDERS04</SAP:Interface>

<SAP:Mapping notRequired="X" />

</SAP:Receiver>

<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ORDERS.ORDERS04</SAP:Interface>

</SAP:Main>

- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SystemAckRequested="false" SystemErrorAckRequested="true" ApplicationAckRequested="true" ApplicationErrorAckRequested="true" SOAP:mustUnderstand="1">

<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>

</SAP:ReliableMessaging>

- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

- <SAP:Hop timeStamp="2007-10-25T14:09:28Z" wasRead="false">

<SAP:Engine type="IS" />

<SAP:Adapter namespace="http://sap.com/xi/XI/System">IDOC</SAP:Adapter>

<SAP:MessageId>DC8303D9-F930-24F1-BCAC-001AA00BC352</SAP:MessageId>

<SAP:Info>ORDERS.0000000005924024:20071025160912</SAP:Info>

</SAP:Hop>

- <SAP:Hop timeStamp="2007-10-25T14:09:29Z" wasRead="false">

<SAP:Engine type="IS">is.00.lbsv2k329</SAP:Engine>

<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>

<SAP:MessageId>DC8303D9-F930-24F1-BCAC-001AA00BC352</SAP:MessageId>

<SAP:Info>3.0</SAP:Info>

</SAP:Hop>

- <SAP:Hop timeStamp="2007-10-25T14:09:34Z" wasRead="false">

<SAP:Engine type="IS" />

<SAP:Adapter namespace="http://sap.com/xi/XI/System">IDOC</SAP:Adapter>

<SAP:MessageId>DC8303D9-F930-24F1-BCAC-001AA00BC352</SAP:MessageId>

<SAP:Info>0000000000000001;</SAP:Info>

</SAP:Hop>

</SAP:HopList>

- <SAP:IDocInbound xmlns:SAP="http://sap.com/xi/XI/Message/30">

<SAP:TABNAM>EDI_DC40</SAP:TABNAM>

<SAP:MANDT>010</SAP:MANDT>

<SAP:DOCREL>46C</SAP:DOCREL>

<SAP:DOCNUM>0000000005924024</SAP:DOCNUM>

<SAP:DIRECT>1</SAP:DIRECT>

<SAP:IDOCTYP>ORDERS04</SAP:IDOCTYP>

<SAP:CIMTYP />

<SAP:MESTYP>ORDERS</SAP:MESTYP>

<SAP:MESCOD />

<SAP:MESFCT />

<SAP:SNDPOR>SAPQB1</SAP:SNDPOR>

<SAP:SNDPRN>QB1_010</SAP:SNDPRN>

<SAP:SNDPRT>LS</SAP:SNDPRT>

<SAP:SNDPFC />

<SAP:RCVPOR>SAPDX3</SAP:RCVPOR>

<SAP:RCVPRN>0006005454</SAP:RCVPRN>

<SAP:RCVPRT>LI</SAP:RCVPRT>

<SAP:RCVPFC>LF</SAP:RCVPFC>

<SAP:TEST />

<SAP:SERIAL>20071025160912</SAP:SERIAL>

<SAP:EXPRSS />

<SAP:STD />

<SAP:STDVRS />

<SAP:STATUS>30</SAP:STATUS>

<SAP:OUTMOD>2</SAP:OUTMOD>

<SAP:SNDSAD />

<SAP:SNDLAD />

<SAP:RCVSAD />

<SAP:RCVLAD />

<SAP:STDMES />

<SAP:REFINT />

<SAP:REFGRP />

<SAP:REFMES />

<SAP:CREDAT>2007-10-25</SAP:CREDAT>

<SAP:CRETIM>16:09:14</SAP:CRETIM>

<SAP:ARCKEY />

</SAP:IDocInbound>

- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">

<SAP:TABNAM>EDI_DC40</SAP:TABNAM>

<SAP:MANDT>010</SAP:MANDT>

<SAP:DOCREL>700</SAP:DOCREL>

<SAP:DOCNUM>0000000000000001</SAP:DOCNUM>

<SAP:DIRECT>2</SAP:DIRECT>

<SAP:IDOCTYP>ORDERS04</SAP:IDOCTYP>

<SAP:CIMTYP />

<SAP:MESTYP>ORDERS</SAP:MESTYP>

<SAP:MESCOD />

<SAP:MESFCT />

<SAP:SNDPOR>SAPDX3</SAP:SNDPOR>

<SAP:SNDPRN>QB1_010</SAP:SNDPRN>

<SAP:SNDPRT>LS</SAP:SNDPRT>

<SAP:SNDPFC />

<SAP:RCVPOR>SAPQB1</SAP:RCVPOR>

<SAP:RCVPRN>QB1_010</SAP:RCVPRN>

<SAP:RCVPRT>LS</SAP:RCVPRT>

<SAP:RCVPFC />

<SAP:TEST />

<SAP:SERIAL>20071025160912</SAP:SERIAL>

<SAP:EXPRSS />

<SAP:STD />

<SAP:STDVRS />

<SAP:STATUS>30</SAP:STATUS>

<SAP:OUTMOD>2</SAP:OUTMOD>

<SAP:SNDSAD />

<SAP:SNDLAD />

<SAP:RCVSAD />

<SAP:RCVLAD />

<SAP:STDMES />

<SAP:REFINT />

<SAP:REFGRP />

<SAP:REFMES />

<SAP:CREDAT>2007-10-25</SAP:CREDAT>

<SAP:CRETIM>16:09:14</SAP:CRETIM>

<SAP:ARCKEY>DC8303D9F93024F1BCAC001AA00BC352</SAP:ARCKEY>

</SAP:IDocOutbound>

- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SAP:Date>20071025</SAP:Date>

<SAP:Time>160934</SAP:Time>

<SAP:Host>lbsv2k329</SAP:Host>

<SAP:SystemId>DX3</SAP:SystemId>

<SAP:SystemNr>00</SAP:SystemNr>

<SAP:OS>Windows NT</SAP:OS>

<SAP:DB>ORACLE</SAP:DB>

<SAP:Language />

<SAP:ProcStatus>003</SAP:ProcStatus>

<SAP:AdapterStatus>007</SAP:AdapterStatus>

<SAP:User>PISUPER_TEST</SAP:User>

<SAP:TraceLevel>1</SAP:TraceLevel>

<SAP:LogSeqNbr>002</SAP:LogSeqNbr>

<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>

<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>

<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>

<SAP:PipelineElementId />

<SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>

<SAP:PipelineService />

<SAP:QIdInternal>XBTO0___0000</SAP:QIdInternal>

<SAP:CommitActor>A</SAP:CommitActor>

<SAP:SplitNumber>0</SAP:SplitNumber>

<SAP:NumberOfRetries>0</SAP:NumberOfRetries>

<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>

<SAP:TypeOfEngine client="010">CENTRAL</SAP:TypeOfEngine>

<SAP:PlsrvExceptionCode />

<SAP:EOReferenceRuntime type="TID">632180CC12404720A39E0025</SAP:EOReferenceRuntime>

<SAP:EOReferenceInbound type="TID">632180BA0DEC4720A38A019A</SAP:EOReferenceInbound>

<SAP:EOReferenceOutbound type="TID">632180CC12404720A39F0026</SAP:EOReferenceOutbound>

<SAP:MessageSizePayload>49197</SAP:MessageSizePayload>

<SAP:MessageSizeTotal>66965</SAP:MessageSizeTotal>

<SAP:PayloadSizeRequest>49197</SAP:PayloadSizeRequest>

<SAP:PayloadSizeRequestMap>49197</SAP:PayloadSizeRequestMap>

<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>

<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>

<SAP:Reorganization>INI</SAP:Reorganization>

<SAP:AdapterInbound>IDOC</SAP:AdapterInbound>

<SAP:AdapterOutbound>IDOC</SAP:AdapterOutbound>

<SAP:InterfaceAction>DEL</SAP:InterfaceAction>

<SAP:RandomNumber>57</SAP:RandomNumber>

<SAP:AckStatus>071</SAP:AckStatus>

<SAP:SkipReceiverDetermination />

<SAP:Receiver_Agreement_GUID>5B66CB1D3BCC3EE0B9F8D8FBFF85ED15</SAP:Receiver_Agreement_GUID>

<SAP:Serialize_Children>X</SAP:Serialize_Children>

</SAP:RunTime>

- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">

- <SAP:RunTimeItem>

<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>

<SAP:Timestamp type="begin" host="lbsv2k329">20071025140928.657</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>

<SAP:Timestamp type="end" host="lbsv2k329">20071025140929.72</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>

<SAP:Timestamp type="begin" host="lbsv2k329">20071025140929.72</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>

<SAP:Timestamp type="end" host="lbsv2k329">20071025140933.407</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>

<SAP:Timestamp type="begin" host="lbsv2k329">20071025140933.704</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>

<SAP:Timestamp type="end" host="lbsv2k329">20071025140933.923</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>

<SAP:Timestamp type="begin" host="lbsv2k329">20071025140933.923</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>

<SAP:Timestamp type="end" host="lbsv2k329">20071025140934.048</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>

<SAP:Timestamp type="begin" host="lbsv2k329">20071025140934.048</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>

<SAP:Timestamp type="end" host="lbsv2k329">20071025140934.454</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>

<SAP:Timestamp type="begin" host="lbsv2k329">20071025140934.454</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>

<SAP:Timestamp type="end" host="lbsv2k329">20071025140934.689</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>

<SAP:Timestamp type="begin" host="lbsv2k329">20071025140934.689</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>

<SAP:Timestamp type="end" host="lbsv2k329">20071025140934.829</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>

<SAP:Timestamp type="begin" host="lbsv2k329">20071025140934.829</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>

<SAP:Timestamp type="end" host="lbsv2k329">20071025140934.954</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>

<SAP:Timestamp type="begin" host="lbsv2k329">20071025140934.954</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>

<SAP:Timestamp type="end" host="lbsv2k329">20071025140935.439</SAP:Timestamp>

</SAP:RunTimeItem>

</SAP:PerformanceHeader>

- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:TraceLevel>Information</SAP:TraceLevel>

<SAP:Logging>Off</SAP:Logging>

</SAP:Diagnostic>

- <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

- <SAP:OutboundBindingEntry version="30">

<SAP:OutboundBindingObjectId>5B66CB1D3BCC3EE0B9F8D8FBFF85ED15</SAP:OutboundBindingObjectId>

<SAP:FromPartyName />

<SAP:FromServiceName>MAG_PI_QB1_SAPR3</SAP:FromServiceName>

<SAP:ToPartyName />

<SAP:ToServiceName>MAG_PI_QB1_SAPR3</SAP:ToServiceName>

<SAP:ToInterfaceName>ORDERS.ORDERS04</SAP:ToInterfaceName>

<SAP:ToInterfaceNamespace>urn:sap-com:document:sap:idoc:messages</SAP:ToInterfaceNamespace>

- <SAP:OutboundBindingAttributes>

<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />

</SAP:OutboundBindingAttributes>

- <SAP:HeaderMapping>

<SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />

</SAP:HeaderMapping>

- <SAP:ChannelEntry version="30">

<SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />

<SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">MAG_PI_QB1_SAPR3</SAP:ServiceName>

<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">CC_QB1_To_QB1</SAP:ChannelName>

<SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:AdapterName>

<SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>

<SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">B38BCD00E47111D7AFACDE420A1145A5</SAP:AdapterSWCV>

<SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>

<SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />

<SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:MessageProtocol>

<SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />

<SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:TransportProtocol>

<SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />

<SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>

<SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />

<SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />

<SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />

<SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />

- <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">

- <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">

- <SAP:Attribute>

<SAP:Name>interfaceVersion</SAP:Name>

<SAP:Value>3</SAP:Value>

</SAP:Attribute>

- <SAP:Attribute>

<SAP:Name>passControlSetValues</SAP:Name>

<SAP:Value>1</SAP:Value>

</SAP:Attribute>

- <SAP:Attribute>

<SAP:Name>passReceiverValue</SAP:Name>

<SAP:Value>0</SAP:Value>

</SAP:Attribute>

- <SAP:Attribute>

<SAP:Name>passSenderValue</SAP:Name>

<SAP:Value>0</SAP:Value>

</SAP:Attribute>

- <SAP:Attribute>

<SAP:Name>port</SAP:Name>

<SAP:Value>SAPQB1</SAP:Value>

</SAP:Attribute>

- <SAP:Attribute>

<SAP:Name>queueing</SAP:Name>

<SAP:Value>0</SAP:Value>

</SAP:Attribute>

- <SAP:Attribute>

<SAP:Name>restoreOriginalParty</SAP:Name>

<SAP:Value>0</SAP:Value>

</SAP:Attribute>

- <SAP:Attribute>

<SAP:Name>rfcDestination</SAP:Name>

<SAP:Value>QB1CLNT010</SAP:Value>

</SAP:Attribute>

- <SAP:Attribute>

<SAP:Name>sapRelease</SAP:Name>

<SAP:Value>470</SAP:Value>

</SAP:Attribute>

- <SAP:Attribute>

<SAP:Name>segmentVersion</SAP:Name>

<SAP:Value />

</SAP:Attribute>

</SAP:AdapterTypeData>

</SAP:ChannelAttributes>

</SAP:ChannelEntry>

</SAP:OutboundBindingEntry>

</SAP:OutboundBinding>

- <SAP:DynamicConfiguration xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPOR">SAPQB1</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRN">QB1_010</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRT">LS</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPOR">SAPDX3</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRN">0006005454</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRT">LI</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPFC">LF</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="MESTYP">ORDERS</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="IDOCTYP">ORDERS04</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="CIMTYP" />

</SAP:DynamicConfiguration>

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

- <!-- ************************************

-->

<Trace level="1" type="T">User: PISUPER_TEST</Trace>

<Trace level="1" type="T">Language: E</Trace>

<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>

<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>

<Trace level="1" type="T">Syntax-Check-Flag X</Trace>

<Trace level="1" type="T">IDoc-Tunnel-Flag X</Trace>

<Trace level="1" type="T">Queueid</Trace>

- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">

<Trace level="1" type="T">Get the Metadata for port SAPQB1</Trace>

<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>

<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>

</Trace>

<Trace level="1" type="T">party normalization error: scheme = ALE#LI#LF</Trace>

<Trace level="1" type="T">Set Receiver Routing-object</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>

- <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA">

</Trace>

<Trace level="1" type="T">COMMIT is expected by application !</Trace>

- <!-- ************************************

-->

- <!-- ************************************

-->

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="1" type="T">system-ID = DX3</Trace>

<Trace level="1" type="T">client = 010</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PISUPER_TEST</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Message-GUID = DC8303D9F93024F1BCAC001AA00BC352</Trace>

<Trace level="1" type="T">PLNAME = CENTRAL</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>

<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>

<Trace level="1" type="T">Queue name : XBTI0000</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTI0000</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Going to persist message</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">--start sender interface action determination</Trace>

<Trace level="1" type="T">select interface ORDERS.ORDERS04*</Trace>

<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>

<Trace level="1" type="T">no interface found</Trace>

<Trace level="1" type="T">--start receiver interface action determination</Trace>

<Trace level="1" type="T">select interface *</Trace>

<Trace level="1" type="T">select interface namespace</Trace>

<Trace level="1" type="T">no interface found</Trace>

<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>

<Trace level="1" type="T">Hence set action to DEL</Trace>

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = DX3</Trace>

<Trace level="1" type="T">client = 010</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PISUPER_TEST</Trace>

<Trace level="1" type="T">----

</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

- <!-- ************************************

-->

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <!-- ************************************

-->

<Trace level="1" type="T">number of receivers: 1</Trace>

<Trace level="1" type="T">Single-receiver split case</Trace>

<Trace level="1" type="T">Post-split internal queue name = XBTO0___0000</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Persisting single message for post-split handling</Trace>

<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = DX3</Trace>

<Trace level="1" type="T">client = 010</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PISUPER_TEST</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>

- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">

<Trace level="1" type="T">No mapping required</Trace>

</Trace>

- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

</Trace>

- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">

- <!-- ************************************

-->

- <!-- ************************************

-->

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">---- Outbound IDoc-Adapter -

</Trace>

<Trace level="1" type="T">----

</Trace>

- <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">

<Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>

<Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>

<Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>

<Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>

<Trace level="1" type="T">Sender service MAG_PI_QB1_SAPR3</Trace>

<Trace level="1" type="T">Receiver service MAG_PI_QB1_SAPR3</Trace>

<Trace level="1" type="T">Get IDoc-XML from the Resource Objekt</Trace>

<Trace level="1" type="T">----

</Trace>

- <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GET_IDOC">

- <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-FILTER_SEGMENTS">

<Trace level="1" type="T">Convert Segment-Definitions to Seg-Types</Trace>

<Trace level="1" type="T">Filter out unknown segments</Trace>

</Trace>

<Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>

- <Trace level="1" type="B" name="IDX_OUTBOUND_XMB">

<Trace level="1" type="T">FM IDOC_INBOUND_ASYNCHRONOUS with RFCDEST= QB1CLNT010</Trace>

</Trace>

</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Async processing completed OK.</Trace>

<Trace level="1" type="T">system-ID = DX3</Trace>

<Trace level="1" type="T">client = 010</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PISUPER_TEST</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

</SAP:Trace>

</SOAP:Header>

- <SOAP:Body>

- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">

- <SAP:Payload xlink:href="cid:payload-DC8303E54E9BA9F1BCAC001AA00BC352@sap.com">

<SAP:Name>MainDocument</SAP:Name>

<SAP:Description />

<SAP:Type>Application</SAP:Type>

</SAP:Payload>

</SAP:Manifest>

</SOAP:Body>

</SOAP:Envelope>

Regards

Rao

the IDOC is entering the Xi but on the inbound side it is thoring error.....can you just check in the sxmb_moni on the red color message move the bottom scroll bar toward right at the end there will be error mesage filed let me know that mean whil i will look ino the log you have sent....

IDX5 in XI is sucessfull...on the reciever side have you maintained the Partner profile and all required configratuion ar doneright?

Hi ,

One more thing in the reciever determination reciver side service and party it is showing Asteric symbol instaed of namer of the business system..

regrads

Rao

Hi Nisar,

after the reflag it is showing some queid and there is no original message id and request id...start time and end time ..it showing all these no error message showing..

Regards

Rao

In the receiver determintion side serive it might show the * if you arfe derteming the recievr at runtime.....

check the following steps...

1. your SA is correct

2. RD you have BS there if youa re not detemring at runtime.

3. Interface determintaion...

5. In RA you have BS and IDOC receiver adapter.

In the reciever determination i configured reciever BS but it is not showing .it is showing star there.

Regrads

Rao

can you reconfigre the ID steps where ever the thigns are missing

1.RD

2. ID

3.RA

then retrigger the IDOC from sender side

Hi Nisar,

I created RA,RD and ID again,but in RD * is still showing..what could be the problem...

Regrads

Rao

when you goto the RD...on the BS selection tab if yu click to open the BS are you able to see the BS lists,,,if yes select that and save it first then activate.....it cannot come as * if you have given teh BS name saved and activated...

rewaed points if helpfull

Hi Nisar,

If i select sender use virtual recievers it is showing business system name. can i use like this..

Regards

Rao

check this blog for ID configurtion

/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2

under this the receiver determination step:

under service select the BS there.. elect which your receiver system and select accordingly.....

reward points if usefull

I did same as u said but this problem is still there....

it is giving error code <b> DC83A27815E929F1BCAC001AA00BC352</b>

can u send me the picture of the error to my e-mailid

nisarkhan_n@hotmail.com

i will check and reply...

Could any one help me out in this issue .here in this error log i cant c error message what could be the problem..

Hi Rao

sorry for the delay just few mintues back i checked my mail...it's strange your SXMB_MONI says sucessfull but some error sexists there......

can you check the call adapter step in the SXMBMONI and check theresult there? if it is sucessull then IDOC went to R/3 at the reciver side then we can check the error code

How do i check call adapter step...could you please guide me there

I checked with outbound channel monitoring there it is giving a message No authorization to send IDOC with status 0...

what exactlky this means..

regards

Rao

call adapter step: when you goto SXMB_MONI~~double click on the mesage left handseide you c the piplelline steps in the technical routing step~~calladapter check there

Hi Nisar,

here i cant c any technical routing.\

i can c Inbound message,Receiver grouping,responce thses there i can c here.

in these no where error log is showing..

No technical routing....

regards

Rao

you cannot c that beacuse of the Trace_level value is low...you can change that to 3 in SXMB_ADM~~>IE COnfiguration~~>change specific configuration....

Rao...

List down the steops yuo have done inXI for this interface as well as in R/3 side?

Hi Nisar,

Xi side:

I created a product,SWCV,TS and BS for R3(sender aswell receiver)

IR:imported IDOC from R3

ID:assigned BS

created CC

configured RA,RD and ID.

SM59 for R3 and created port(IDX1) and IDX2

R3 side:

SM59

WE21

WE20( for outbound and inbound as same system acting as a sender and receiver)

this steps i have done..

one more thing in SXMB_ADM~~>IE COnfiguration~~>change specific configuration....what i have to do next... to c technical routing..

Thnaks for your time

regards

Rao

Firstly you can use the standard function i R/3 to define taht in SLD

goto Rz70 in r/3 and enter the detail there the TS will be created automatically.....then you careate only the BS for that.....

for webasABAP it is good to taht this way...now coming into IR

IR:imported IDOC from R3 you dnt have any mapping program right? then IR is fine

ID:assigned BS , created CC, configured RA,RD and ID.

this is ok but it will not allow to uise the same BS in both Sender and receiver..... you said you have created the R/3 TS for R/3 in SLD for both sende and receiver which i doubt will work out...

on r/3 side the configuration looks fine..have you created the aprtner profile for the Receving the IDOC from XI?

SXMB_ADM~~>IE COnfiguration~~>change specific configuration....what i have to do next... to c technical routing.. to do this check this blog

Have a look at this michal's blog:

/people/michal.krawczyk2/blog/2005/05/10/xi-i-cannot-see-some-of-my-messages-in-the-sxmbmoni

I am using same BS as sender and reciver as i am using same R3 for both the cases.from XI to R3 i created in IDX2 is this ok..

regards

Rao

yes that's perfectly fine...but i think usually XI will not allow samw BS to act he sender and reciver system...but it will allow the Busines service as both....

Hey

>>but i think usually XI will not allow samw BS to act he sender and reciver system

not true,you can use same business system for both sender and receiver

Thanx

Aamir

Nisar how can i overcome this problem..and how can i use business scenarios ...

thanks

Rao

he problem i see is the Business system....try to create a dummy BS ( 3rd party) use that in teh Business serivece tab in teh ID this only for receiver system....

or goto the business serivcce in ID...assign the Business system you created for the receiver adn try to do teh cionfig steps and check......

1 Important thing is till now we are not able to figure out the error message ateast some meaning full error message in SXMB_MONI....becasue IDX5 entry is coming...

my suggestion is beofre we look into the BS issue, need to figure out the Error message in SXMB_MONI.....( like receiver not found ) etc/....

also you have not replied on the partner profile for Recievr side...is your partner type LS? have you maintained the partner profile inreceiver?

gotrough these blogs and checkyour settings accordingly

for idocs scenario have a look to this how to guide:

https://websmp203.sap-ag.de/~sapdownload/011000358700003604082004E/HowTo_IDOC_XI_Scenarios.pdf

/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit

/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems

reward points if usefull

Hi Nisar,

I did configured partner profiles on receiver side it is of LS type.

Regards

Rao

Hi Nisar,

In IDX5 when i clicked on Transaction id it showing in text message <b>NO Authorization to send IDOC with status 0</b>

and could you please some idea while we creating partner profiles.

i am doing from and to to same R3 system. which partner number i have to mention in inbound poartner profiles ..

regards

Rao

Can u please check the cache under it might be obsolete. Can u perform the CPA and complete cache refresh.

Thanks

Abhishek Mahajan

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Ask a Question

Top Q&A Solution Author

User

Count