cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Inbound error

Former Member
0 Kudos

Hi,

I am doing file to IDOC. The message is showing Successful but it is was going to R/3. I am giving there that xml message which generated in SXMB_MONI.

-


<?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>70C7D170-4D1F-11DB-C92E-000D60E1FBDF</SAP:MessageId>

<SAP:TimeSent>2006-09-26T05:25:36Z</SAP:TimeSent>

- <SAP:Sender>

<SAP:Service>BS_KAREEM_3RDPARTY</SAP:Service>

<SAP:Interface namespace="http://file2ZIDOC_Kareem">MI_FILE2IDOC_KAREEM</SAP:Interface>

</SAP:Sender>

- <SAP:Receiver>

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

<SAP:Service>BS_R3_SYSTEM</SAP:Service>

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

- <SAP:Mapping notRequired="M">

<SAP:ObjectId>Mrkk5K/IO/2cNNOwFbUlQg==</SAP:ObjectId>

<SAP:SWCV>/fKMsErhEduTP/v6CjIBJA==</SAP:SWCV>

<SAP:SP>-1</SAP:SP>

</SAP:Mapping>

</SAP:Receiver>

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

</SAP:Main>

- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" 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="2006-09-26T05:25:36Z" wasRead="false">

<SAP:Engine type="AE">af.x11.apollo</SAP:Engine>

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

<SAP:MessageId>70C7D170-4D1F-11DB-C92E-000D60E1FBDF</SAP:MessageId>

<SAP:Info />

</SAP:Hop>

- <SAP:Hop timeStamp="2006-09-26T05:25:37Z" wasRead="false">

<SAP:Engine type="IS">is.01.apollo</SAP:Engine>

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

<SAP:MessageId>70C7D170-4D1F-11DB-C92E-000D60E1FBDF</SAP:MessageId>

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

</SAP:Hop>

- <SAP:Hop timeStamp="2006-09-26T05:25:37Z" wasRead="false">

<SAP:Engine type="IS" />

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

<SAP:MessageId>70C7D170-4D1F-11DB-C92E-000D60E1FBDF</SAP:MessageId>

<SAP:Info>0000000000004003;</SAP:Info>

</SAP:Hop>

</SAP:HopList>

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

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

<SAP:MANDT>001</SAP:MANDT>

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

<SAP:DOCNUM>0000000000004003</SAP:DOCNUM>

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

<SAP:IDOCTYP>ZIDOCIN</SAP:IDOCTYP>

<SAP:CIMTYP />

<SAP:MESTYP>ZMTIDOCIN</SAP:MESTYP>

<SAP:MESCOD />

<SAP:MESFCT />

<SAP:SNDPOR>SAPX11</SAP:SNDPOR>

<SAP:SNDPRN>C11CLNT001</SAP:SNDPRN>

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

<SAP:SNDPFC />

<SAP:RCVPOR>SAPA11</SAP:RCVPOR>

<SAP:RCVPRN>A11CLNT200</SAP:RCVPRN>

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

<SAP:RCVPFC />

<SAP:TEST />

<SAP:SERIAL />

<SAP:EXPRSS />

<SAP:STD />

<SAP:STDVRS />

<SAP:STATUS />

<SAP:OUTMOD />

<SAP:SNDSAD />

<SAP:SNDLAD />

<SAP:RCVSAD />

<SAP:RCVLAD />

<SAP:STDMES />

<SAP:REFINT />

<SAP:REFGRP />

<SAP:REFMES />

<SAP:CREDAT>0000-00-00</SAP:CREDAT>

<SAP:CRETIM>00:00:00</SAP:CRETIM>

<SAP:ARCKEY>70C7D1704D1F11DBC92E000D60E1FBDF</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>20060926</SAP:Date>

<SAP:Time>105537</SAP:Time>

<SAP:Host>apollo</SAP:Host>

<SAP:SystemId>X11</SAP:SystemId>

<SAP:SystemNr>01</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>PIAFUSER</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>XBTO2___0002</SAP:QIdInternal>

<SAP:CommitActor>X</SAP:CommitActor>

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

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

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

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

<SAP:PlsrvExceptionCode />

<SAP:EOReferenceRuntime type="TID">0A32012412084518B9D10012</SAP:EOReferenceRuntime>

<SAP:EOReferenceInbound type="TID" />

<SAP:EOReferenceOutbound type="TID">0A32012412084518B9D10013</SAP:EOReferenceOutbound>

<SAP:MessageSizePayload>1004</SAP:MessageSizePayload>

<SAP:MessageSizeTotal>3457</SAP:MessageSizeTotal>

<SAP:PayloadSizeRequest>1004</SAP:PayloadSizeRequest>

<SAP:PayloadSizeRequestMap>650</SAP:PayloadSizeRequestMap>

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

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

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

<SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>

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

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

<SAP:RandomNumber>13</SAP:RandomNumber>

<SAP:AckStatus>000</SAP:AckStatus>

<SAP:SkipReceiverDetermination />

<SAP:Receiver_Agreement_GUID>773C6AD79B4C3C31ACD5CE98876A9904</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="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>

<SAP:Timestamp type="begin" host="apollo">20060926052536.997</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>

<SAP:Timestamp type="end" host="apollo">20060926052537.013</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="apollo">20060926052537.013</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="apollo">20060926052537.028</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="apollo">20060926052537.028</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="apollo">20060926052537.216</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="apollo">20060926052537.216</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="apollo">20060926052537.216</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="apollo">20060926052537.216</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="apollo">20060926052537.232</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="apollo">20060926052537.232</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="apollo">20060926052537.232</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="apollo">20060926052537.232</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="apollo">20060926052537.325</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="apollo">20060926052537.325</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="apollo">20060926052537.419</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="apollo">20060926052537.419</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="apollo">20060926052537.45</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="apollo">20060926052537.45</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="apollo">20060926052537.466</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>773C6AD79B4C3C31ACD5CE98876A9904</SAP:OutboundBindingObjectId>

<SAP:FromPartyName />

<SAP:FromServiceName>BS_KAREEM_3RDPARTY</SAP:FromServiceName>

<SAP:ToPartyName />

<SAP:ToServiceName>BS_R3_SYSTEM</SAP:ToServiceName>

<SAP:ToInterfaceName>ZMTIDOCIN.ZIDOCIN</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:Field>

<SAP:Name>ReceiverService</SAP:Name>

<SAP:ExtractorId>604DD4C04D1F11DB98B1000E7FF4C3A7</SAP:ExtractorId>

</SAP:Field>

- <SAP:Field>

<SAP:Name>SenderService</SAP:Name>

<SAP:ExtractorId>5D504C304D1F11DBB7BD000E7FF4C3A7</SAP:ExtractorId>

</SAP:Field>

</SAP:FieldMapping>

</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">BS_R3_SYSTEM</SAP:ServiceName>

<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">CC_File2ZIdoc_Receiver_kareem</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>SAPA11</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>RFC_ZEUS_ABAP</SAP:Value>

</SAP:Attribute>

- <SAP:Attribute>

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

<SAP:Value>700</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:System 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/Message/30/general" name="senderAgreementGUID">def5775cf87c3aee8e94b2e814a8791b</SAP:Record>

</SAP:System>

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

<Trace level="1" type="T">Party normalization: sender</Trace>

<Trace level="1" type="T">Sender scheme external = XIParty</Trace>

<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>;

<Trace level="1" type="T">Sender party external =</Trace>

<Trace level="1" type="T">Sender party normalized =</Trace>

<Trace level="1" type="T">Party normalization: receiver</Trace>

<Trace level="1" type="T">Receiver scheme external =</Trace>

<Trace level="1" type="T">Receiver agency external =</Trace>

<Trace level="1" type="T">Receiver party external =</Trace>

<Trace level="1" type="T">Receiver party normalized =</Trace>

<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />

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

-->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>

<Trace level="1" type="T">COMMIT is done by XMB !</Trace>

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

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

-->

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

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

-->

<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />

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

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

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

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

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

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

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

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

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

<Trace level="1" type="Timestamp">2006-09-26T05:25:37Z CET</Trace>

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

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

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

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

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

-->

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

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

<Trace level="1" type="T">QOS = EO</Trace>

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

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

-->

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

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

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

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

<Trace level="1" type="T">Generated prefixed queue name = XBTI0006</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="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

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

-->

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

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

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

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

-->

<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 = X11</Trace>

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

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

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

<Trace level="1" type="Timestamp">2006-09-26T05:25:37Z CET</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="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<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">R E C E I V E R - D E T E R M I N A T I O N</Trace>

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

</Trace>

</Trace>

</Trace>

</Trace>

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

- <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">I N T E R F A C E - D E T E R M I N A T I O N</Trace>

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

</Trace>

</Trace>

</Trace>

</Trace>

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

<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />

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

-->

- <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_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />

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

-->

<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 = XBTO2___0002</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" />

<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="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

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

-->

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

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

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

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

-->

<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 = X11</Trace>

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

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

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

<Trace level="1" type="Timestamp">2006-09-26T05:25:37Z CET</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="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<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">Interface Mapping http://file2ZIDOC_Kareem MI_FILE2IDOC_KAREEM</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

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

- <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 level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />

</Trace>

</Trace>

</Trace>

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

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

<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">----


</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 BS_KAREEM_3RDPARTY</Trace>

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

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

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

<Trace level="1" type="T">Parse XML-BODY</Trace>

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

<Trace level="1" type="T">Convert one IDoc</Trace>

<Trace level="1" type="T">Warning: IDoc does not contain control-record</Trace>

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

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

</Trace>

<Trace level="1" type="T">Call Outbound IDoc-Adapter</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= RFC_ZEUS_ABAP</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

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

</Trace>

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


</Trace>

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

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

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

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

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

<Trace level="1" type="Timestamp">2006-09-26T05:25:37Z CET</Trace>

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


</Trace>

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

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

-->

</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-70cefd614d1f11dbb943000d60e1fbdf@sap.com">

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

<SAP:Description />

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

</SAP:Payload>

</SAP:Manifest>

</SOAP:Body>

</SOAP:Envelope>

-


THX.

Accepted Solutions (1)

Accepted Solutions (1)

bhavesh_kantilal
Active Contributor
0 Kudos

Ansar,

Check the TRFC status in SM58 in XI and see if there is any entry in it.

If the IDOC has not reached the R3 system, and is succesful in MONI ( both inbound and outbound side ) check TRFC SM58 in XI.

Regards,

Bhavesh

Former Member
0 Kudos

Hi Bhavesh,

Thx a lot. The Problem is "PIAFUSER Does not have

authorization to send IDOC". Now What TCodes I should

take authorization to solve this problem?

thx and Regars,

Ansar.

Shabarish_Nair
Active Contributor
0 Kudos

for authorizations ref. the following;

bhavesh_kantilal
Active Contributor
0 Kudos

Ansar,

The note : 837595 would give the list of authorizations.

<i>************************************************************************************************************

Summary

Symptom

Loading the IDoc metadata from the reference system terminates with the following error message:

"Metadata EDISDEF for port, IDoc type and CIM type not maintained".

Other terms

IDoc adapter, metadata, EDISDEF, IDX2, authorization, Release 4.6C

Reason and Prerequisites

You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.

This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.

Solution

In transaction PFCG, extend the role of the logon user by adding the following authorizations:

Authorization object S_RFC

Field name RFC_TYPE value FUGR

Field name RFC_NAME value EDIMEXT, SDTX

Field name ACTVT value 16

Authorization object S_IDOCDEFT

Field name ACTVT value 03

Field name EDI_CIM value ' '

Field name EDI_DOC value TXTRAW01

Field name EDI_TCD value WE30

Authorization object S_CTS_ADMI

Field name CTS_ADMFCT value TABL

Authorization object S_TABU_DIS

Field name ACTVT value 03

Field name DICBERCLS value

Note: You can activate the display of the technical names of objects and fields in authorizations maintenance by choosing the 'Technical Names' function from the 'Utilities' menu.

Then save and execute the 'Generate' function. Then choose 'Back' to return to role maintenance and switch to the 'Users' tab. Press the 'User comparison' button to execute this function.

************************************************************************************************************</i>

Regards,

Bhavesh

Former Member
0 Kudos

Thx a lot ... Problem solved. I given authorization to PIAFUSER...

thx and regards,

Ansar.

Answers (1)

Answers (1)

Shabarish_Nair
Active Contributor
0 Kudos

only thing noticable in the trace is

<Trace level="1" type="T">Parse XML-BODY</Trace>

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

<Trace level="1" type="T">Convert one IDoc</Trace>

<b><Trace level="1" type="T">Warning: IDoc does not contain control-record</Trace></b>

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

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

You mentioned that your message shows a success status.

Check for the following,

1. In R3 in we02 check if you have any entry for you inbound IDOC

2. in XI, ixdx5 check monitor your IDOC.

3. do a trace in SM58 (R3)