SAP Inbound error

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:[email protected]">
  <SAP:Name>MainDocument</SAP:Name>
  <SAP:Description />
  <SAP:Type>Application</SAP:Type>
  </SAP:Payload>
  </SAP:Manifest>
  </SOAP:Body>
  </SOAP:Envelope>
THX.

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

Similar Messages

  • How to catch SAP application errors in BPM.

    Hi,
    I have a IDOC to Soap Sync Scenario where I send the message to a Webservice. I have used a BPM since we need to catch the resposne of this message and map it to a RFC. For ex if I get a success resposne I need to map success if not than I need to catch the error and map it to the RFC. Now here in some cases like if the target system (webservice) is down than XI raises a sap application error:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Connection refused (errno:239)</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Normally XI stops the process in these cases and does not proceed to the next step but I need to catch this message and map the content in the AdditionalText to the target RFC. Can anyone let me know how to catch this SAP Application Error in BPM and map it to the RFC.
    Thanks,
    Bhargav

    Hi Gaurav,
    As I have mentioned I need to catch the application error in the BPM. If you see the discussion that is mentioned after the blog you have mentioned it is stated that the fault messages or the application error cannot be caught in BPM.
    In the blog that you stated we can catch the fault message and map it to a message structure but only to that extent after that it would stop the BPM process at that step but would not proceed further as shown in the screenshot given in the blog it would fail as "application error restart not possible".
    I need to proceed further and capture this error to an RFC Structure and call a proxy.
    Here after the error it does not proceed to the next step.
    Thanks,
    Bhargav

  • Sap Payroll error log report

    Hi All,
    We are developing Report on SAP Payroll log with the error message . Is any table exist in SAP where we can get the standard error message repositery and then convert it in the User freindly error message ?
    Thanks
    H

    Hello hg,
    Before developing report on SAP Payroll error log I suggest taking a look at below blog. There is a new functionality from SAP to improve payroll data validation and they are calling it "Control Center Add-On".
    This is going to be a free add on for anyone who is on EHP7 and NetWeaver on 7.4 release. The general availability is June 2nd 2014.
    Improve payroll data validation with SAP Payroll control center add-on
    Hope this helps.
    Thanks,
    Hemanth Jamithi.

  • Error while printing (SAP spool error)

    Hi,
    I have configured a printer of type 'C : Direct Operating System Call'. On printing a page, an error occurs with the following log entries
    SAP spool error log
    =====================
    Print request processing log
    The host spool is reporting errors
    Windows/NT error 1775: "A null context handle was passed from the client to the host during a remote procedure call."
    Errors occurred processing this print request
    Error during print request output. l_rc = 1
    There may be no printout
    Please. can someone help me out here.
    Thanks!
    Regards,
    Angad

    Ok I am upgrading from R/3 46C to ECC 6.0, on the 46c system the printers are configured as follow:
    Device type          HPLJ4    : HP Laserjet 4 series
    Spool server          sapprod1_PRD_00       sapprod1
    Device class          Standard printer
    Host spool access method C: Direct operating system call
    Host printer          
    srtroot03.startek.com\srt-dc-c4-sharp
    Host name          sapprod1
    On the ECC 6.0 system the printers are configured as follows:
    Device Type          HPLJ4    : HP Laserjet 4 series
    Spool Server          srtsapeccdev1_DEV_00
    Server Description
    Host               srtsapeccdev1
    Device Class          Standard printer
    Host Spool Access Method C: Direct operating system call
    Host printer          
    srtroot03.startek.co\srt-dc-c4-sharp
    HostName          srtsapeccdev1
    The 46c system prints just fine, on the ECC 6.0 systems; I can not get the printers to work.  I have made sure that the hosts file on the ECC server has the printer host address, and I get the following error back:
    SAP spool error log
    =====================                                                     
    Print request processing log
    The host spool is reporting errors
    Windows/NT error 5 [
    srtroot03.startek.com\srt-dc-c4-sharp]: "Access is denied."
    Errors occurred processing this print request
    Error during print request output. l_rc = 1
    There may be no printout
    The access to the Printer Host is wide open, what do I need to do to resolve this issue.

  • Sap-plugin error when deploying a par file

    Hi,
    We are getting sap-plugin error when ever we are trying to deploy the application to the portal.Even after restarting the server the problem is not getting solved.
    The application we are trying to deploy is perfectly alright as we tested the same earlier.
    Can any one provide some inputs to solve this issue.
    To add some more points
    In brief ,we are not able to deploy our Portal applications . It is giving us error like this
    NFO: Detected Portal Archive File: com.abc.par
    INFO: Deployment failed - exception caught: Application upload failed: com.abc.par - more detail at: /usr/sap/POD/JC30/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/deployment/pcd/com.abc.par.log…
    We got this error many times , but after some time , when we restart the portal it works,
    this time it is not working even after I restarted the server many times

    hi all, i have same problem with upload of .par file, it doesn't work both from the portal and from the NWDS,
    here i post first part of log file:
    this is   sap-plugin.log :
    [16.05.07 / 13:05] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > Upload Response: <?xml version="1.0" encoding="utf-8"?>
    <query-result><info><type>1</type><message>Detected Portal Archive File: test.par</message></info><info><type>1</type><message>Deployment failed - exception caught: Application upload failed: test.par - more detail at: C:\usr\sap\SWB\DVEBMGS02\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd\test.par.log</message></info></query-result>
    this is  test.par.log :
    2007-05-16_12-03-10
    Application upload failed: test.par
    com.sapportals.portal.prt.runtime.PortalException: [ApplicationRepositoryService.putArchive] archive: test.par
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:328)
         at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:813)
         at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(DeploymentManager.java:474)
         at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(DeploymentManager.java:319)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doUpload(ArchiveUploader.java:116)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(AbstractPortalComponent.java:700)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:412)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:707)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.pcd.pl.PlRuntimeException: unexpected SQLException
    Cannot assign a zero-length byte array to host variable 18.
         at com.sapportals.portal.pcd.pl.PlFactory.handleUnexpectedSQLError(PlFactory.java:2490)
         at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:652)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildOnPersistence(XfsContext.java:1360)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildAndNotify(XfsContext.java:1118)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChild(XfsContext.java:1076)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.createSubcontext(XfsContext.java:846)
         at com.sapportals.portal.pcd.gl.xfs.BasicContext.createBasicSubcontext(BasicContext.java:185)
         at com.sapportals.portal.pcd.gl.PcdPersContext.createSubcontext(PcdPersContext.java:188)
         at com.sapportals.portal.pcd.gl.PcdFilterContext.filterCreateSubcontext(PcdFilterContext.java:244)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.createSubcontext(PcdProxyContext.java:133)
         at com.sapportals.portal.pcd.gl.PcdGlContext.createSubcontext(PcdGlContext.java:500)
         at com.sapportals.portal.pcd.gl.PcdGlContext.bind(PcdGlContext.java:425)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.bind(PcdProxyContext.java:426)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.rebindInt(PcdProxyContext.java:446)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:460)
         at com.sapportals.portal.pcd.gl.PcdGlContext.rebind(PcdGlContext.java:1317)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:501)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:663)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:668)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.updateObject(ApplicationRepositoryService.java:717)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.storeApplication(ApplicationRepositoryService.java:389)
         at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:306)
         ... 34 more
    Caused by: com.sap.sql.log.OpenSQLException: Cannot assign a zero-length byte array to host variable 18.
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)
         at com.sap.sql.jdbc.common.dispatch.BlobHostVariable.setBinaryStream(BlobHostVariable.java:143)
         at com.sap.sql.jdbc.common.CommonPreparedStatement.setBinaryStream(CommonPreparedStatement.java:776)
         at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setBinaryStream(PreparedStatementWrapper.java:401)
         at com.sapportals.portal.pcd.pl.AttributeHeadersTable.storeAttribute(AttributeHeadersTable.java:431)
         at com.sapportals.portal.pcd.pl.AttributeHeadersTable.insert(AttributeHeadersTable.java:248)
         at com.sapportals.portal.pcd.pl.PlObject.save(PlObject.java:541)
         at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:616)
         at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:640)
         ... 54 more

  • Inbound Error message in SMQ2

    Dear All Experts,
    1 ) I am facing one error in SMQ2 of SRM sytem that XI restart in qRFC not allowed. I am having the scenario ECC->XI->SRM. The messages are getting stuck in both XI system and SRM system. The contents of the errored message in SRM is provided below.
    <SAP:Category>Application</SAP:Category>
      <SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="http://sap.com/xi/SRM/SE/Global">ExchangeFaultData</SAP:ApplicationFaultMessage>
      <SAP:Stack>Application has thrown an exception</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    The error message I am getting in SMQ2 of XI sytem is XI Error CLIENT_RECEIVE_FAILED.INTERNAL: Queue stopped. The contents of the message in XI is given below.
    <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>400</SAP:P1>
      <SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
    <SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)</SAP:Stack>
    Has anybody gone through this kind of message ? Experts help on this will be great !
    Regards,
    Siji.

    Hi,
    It seems like huge messages problem. 
    Have a look into SAP Notes: 824554, 906435, 783515, 910649, 706563.
    If it is because of Queue problems have a look into SMQ2 and then go thru this blog-How to Re-Process failed XI Messages Automatically .  See the below link.
    http://www.saptechies.com/xi-timeouts-timeouts-timeouts/
    /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    Regards,
    Rajesh

  • SAP query error - 1). [Microsoft][SQL Server Native Client 10.0][SQL Server]Conversion failed when converting date and/or time from character string.  'Received Alerts' (OAIB)

    SAP query error - 1). [Microsoft][SQL Server Native Client 10.0][SQL Server]Conversion failed when converting date and/or time from character string.  'Received Alerts' (OAIB)
    SELECT    
    CASE WHEN T0.DocStatus = 'O' THEN 'OPEN'
    WHEN T0.DocStatus = 'C' THEN 'CLOSED'  END  AS 'Document Status',
    T0.DocDate AS 'Posting Date',
    T0.DocNum AS 'Doc.No',
    T0.NumAtCard,
    T0.TransId AS 'Trans. No.',
    T0.Comments AS 'Remarks',
    T0.CardCode AS 'Offset Acct',
    T0.CardName AS 'Offset Acct Name',
    sum(T0.DocTotal) + (T0.WTSum) as 'DocTotal',
    T3.DueDate AS 'Cheque Date',
    T3.CheckSum AS 'Amount'
    FROM         ODPO AS T0 LEFT OUTER JOIN
                          VPM2 AS T1 ON T0.ObjType = T1.InvType AND T0.DocEntry = T1.DocEntry LEFT OUTER JOIN
         OVPM AS T2 ON T2.DocEntry = T1.DocNum LEFT OUTER JOIN
                          VPM1 AS T3 ON T2.DocEntry = T3.DocNum
    where T0.DocDate>='[%0]' and T0.DocDate<='[%1]'

    Hi,
    Try this:
    SELECT   
    CASE WHEN T0.DocStatus = 'O' THEN 'OPEN'
    WHEN T0.DocStatus = 'C' THEN 'CLOSED'  END  AS 'Document Status',
    T0.DocDate AS 'Posting Date',
    T0.DocNum AS 'Doc.No',
    T0.NumAtCard,
    T0.TransId AS 'Trans. No.',
    T0.Comments AS 'Remarks',
    T0.CardCode AS 'Offset Acct',
    T0.CardName AS 'Offset Acct Name',
    sum(T0.DocTotal) + (T0.WTSum) as 'DocTotal',
    T3.DueDate AS 'Cheque Date',
    T3.CheckSum AS 'Amount'
    FROM         ODPO  T0 LEFT OUTER JOIN
                          VPM2  T1 ON T0.ObjType = T1.InvType AND T0.DocEntry = T1.DocEntry
    LEFT OUTER JOIN
         OVPM  T2 ON T2.DocEntry = T1.DocNum LEFT OUTER JOIN
                          VPM1  T3 ON T2.DocEntry = T3.DocNum
    where T0.DocDate >= '[%0]' and T0.DocDate <='[%1]'
    group by T0.DocStatus,T0.DocDate ,
    T0.DocNum ,
    T0.NumAtCard,
    T0.TransId ,
    T0.Comments ,
    T0.CardCode,
    T0.CardName ,
    T0.WTSum ,
    T3.DueDate ,
    T3.CheckSum
    Thanks & Regards,
    Nagarajan

  • Enable SAP Inbound email through IMAP, POP3 & MAPI instead of SMTP

    Hi,
    I am trying to configure SAP Inbound email in CRM 6.0 and would like to know if I can use IMAP, POP3 or MAPI instead of SMTP due to our company's legal policies and maintenance purposes.
    If there is a way, please let me know how to?
    I have checked other options but none of them talk about IMAP, POP3 or MAPI
    *) ICI (Integrated Communication Interface)
    *) Agent Inox based on SAP Connect Interface via SAP Business WorkflowCheck
    http://help.sap.com/saphelp_crm60/helpdata/en/46/23e545c17b5872e10000000a11466f/content.htm
    PI Mail Adapter  - http://help.sap.com/saphelp_nw04/helpdata/en/ad/bf93409c663228e10000000a1550b0/frameset.htm
    Configuring the Sender Mail Adapter - http://help.sap.com/saphelp_nw04/helpdata/en/ad/bf93409c663228e10000000a1550b0/frameset.htm
    Configuring the Receiver Mail Adapter  - http://help.sap.com/saphelp_nw04/helpdata/en/ad/bf93409c663228e10000000a1550b0/frameset.htm
    Thanks in advance

    Hello,
    As far as I am aware, SMTP is now the only supported option for configuring inbound emails through the SAPConnect interface into the Interaction Center agent inbox.
    [SAP Note 455140|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=455140]
    [SAP Note 1236270|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1236270}
    Best regards,
    John

  • B2B Inbound Error : Need Clarification

    Hi All,
    I would like to illustrate a particular use case for B2B Inbound Errors and if there is any workaround available to get over the problem. We are using B2B version 10.1.2
    Use Case Details</strong1. Consider the scenario wherein we have a Inbound EDI File which has 100 transactions in it. B2B reads the file and automatically debatches into individual transactions and processes them separately.
    2. Out of the 100 transactions in the input file, if say 5 transactions are error transactions, we have observed that all the 100 transactions error out in B2B.
    3. The 95 correct transactions fail with the error "General Validation Error" and the 5 error transactions have the exact error details in the B2B Message Reports.
    4. Ideally, B2B should error out only the 5 error transactions and process rest of the 95 transactions without allowing them to fail with "General Validation Error".
    I am sure that most of us must have faced this error. Could someone please let me know the folllowing:
    1. Is there any setting in B2B by which we can enable it to error out only the transactions which have valid errors in a single file
    2. Is there any other workaround that we can take to avoid this issue.
    The reason we need to have a solution for this is because in our Production B2B environment we receive inbound files from Trading Partners which have hundreds of transactions in each file.
    If, even a single transaction has error, then the whole file errors out and it is quite cumbersome to browse through the B2B Message Reports to get the exact error transaction because all the correct transactions would failed with error "General Validation Error".
    Please let me know the inputs.
    Thanks,
    Dibya

    Hi Ramesh,
    Thanks for the clarification and information. We have already set the parameter OneErrorAllError = true and my understanding was that if we set this parameter to TRUE, it means that if one transaction in the OUTBOUND batch errors out then the whole batch will error out.
    I was not aware that it also holds true for INBOUND. Is there any other way that we can set this parameter based on direction (INBOUND or OUTBOUND).
    We would like to have this parameter set for OUTBOUND and disabled for INBOUND Transactions.
    Please let me know. Thanks Again.
    Regards,
    Dibya

  • SAP XI error: 401 Unauthorized (When calling from Enterprise Portal)

    Hello Friends
    I am trying to access an SAP table from IVIEW of portal via XI. Using the latest and greatest version of all SAP Components. (We just installed couple of weeks back).
    I keep getting the following error message when I try to access data from IVIEW of portal.  
    "SAP XI error: 401 Unauthorized"
    What may be the reason? If some one can help me, I would really appreciate it.
    Thanks
    Ram

    Thanks Srinivas for your help.
    I tried accessing the URL directly and got the error message
    "User Credentials not passed via Enterprise Portal. Please contact your Administrator"
    Any more suggestions?
    Thanks again
    Ram

  • SAP inbound/outbound data traffic measure

    Hi all.
    I am looking to find out the way to measure the SAP inbound/outbound data traffic loads.
    In transaction OS06 shows the hourly measure of received/sent packets, but I need to know the traffic load in bits.
    Is it possible to know that the traffic load from SAP?
    Thank you.

    I was hoping this was an easy answer for the experienced one. Should this post be moved some other place or is it the right place to ask for such question ?

  • SAP Inbound Proxy Error

    Hi Experts,
    I am facing an issue when executing inbound proxy message. After the message completed, the message status end up with Error. The error says below details.
    "Information about the method parameters is missing
    for the interface INTERFACE_NAME
    (ABAP interface, request message MT_Fault, request
    message namespace....)"
    I am also raising Fault messages from ABAP Proxy message programming. In SXMB_MONI while expanding all the messages I can able to see the application message but also i am seeing the above mention errors.
    Any Idea why this error appears?
    Thank you
    Magesh.

    Hi Diptendu - I don't think it's an issue with URL.
    Did  you register the service?
    http://<host>:<port>/ProxyServer/register?ns=http://sap.com/xi/XI/System&interface=ValueMappingReplicati
    onOutSynchronous&bean=localejbs/sap.com/com.sap.xi.services/ValueMappingApplicationSynchronous&m
    ethod=ValueMappingReplicationOutSynchronous
    Reference :
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e07dd2ae-f783-2c10-9aa6-ca69f67dd20f?QuickLink=index&…
    what is your receiver channel?

  • HTTP Inbound error - 500 SOAP PARSING HEADER

    I am working with receiving inbound acknowledgement a text file from the customer to FTP through XI, the URL I supplied to the customer is in the form.
    http://<url address linked to XI server:port>/sap/xi/engine?namespace=<namespace>&
    interface=<sender interface>&
    service=<Sender Service>&
    party=&agency=&scheme=&
    QOS=EO&sap-user=&sap-password=&sap-client=005&sap-language=EN
    Customer is receiving the error message and I don't see any trace of them contacting our XI. When I tried testing usign SAP pI 7 client test tool with out providing /SAP/XI/engine? it doesn't throw any error and no xml payload file generated in FTP though no error seen.
    Any one have any idea what this probelm could be?
    Thanks,
    Menaga

    Hi,
    you can do this
    1. start ICF trace  form transaction SICF in order to log the message which is being send by your partner
    this way if anything is reaching XI you will see it in the log
    http://help.sap.com/saphelp_nw04/Helpdata/EN/80/b2dd3a6dac703be10000000a11405a/content.htm
    Regards,
    Michal Krawczyk

  • 997 inbound error in AK404

    Hi All,
    Attached 997(acknowledgement coming inbound from customer to SAP) is failing with error in parsing at AK404 (index out of bounds exception)
    Any idea why?
    thx
    mike

    Did you try converting the raw file into XML using B2B toolkit? There should be a checkbox for enabling "Log converting" which should log all the steps..
    In addition, Compare the file with any other successful 997 and see if you can find any difference..

  • BD87 idoc inbound error for message type HRMD_A

    Hello there,
    I am getting below error  while fetching Inbound idoc in tcode BD87, see log below from ST22
    Short text
        An SQL error occurred when executing Native SQL.
    What happened?
        The error "-10328" occurred in the current database connection "LCA".
    What can you do?
        Note down which actions and inputs caused the error.
        To process the problem further, contact you SAP system
        administrator.
        Using Transaction ST22 for ABAP Dump Analysis, you can look
        at and manage termination messages, and you can also
        keep them for a long time.
    How to correct the error
        Database error text........: "Mismatch of number of stream members for
         parameter (3) (application 6, database 9)."
        Database error code........: "-10328"
        Triggering SQL statement...: "EXECUTE PROCEDURE "SIM_SIMSESSION_CONTROL""
        Internal call code.........: "[DBDS/NEW DSQL]"
        Please check the entries in the system log (Transaction SM21).
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
        "/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU07"
        "SIMSCTRL_EXEC_COM"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
        1. The description of the current problem (short dump)
           To save the description, choose "System->List->Save->Local File
        (Unconverted)".
        2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "SIMSCTRL_EXEC_COM" "(FORM)", or its possible occurrence must be declared in
    the
    Do we need SAP_APO in order to install LiveCache?
    We have below landsacpe
    - SAP ECC 6 EHP4 with SQL server 2005 S BACKEND
    -LCAPPS Component release 2005_700 with SP
    SAPKIBHD05.
    - We dont have SAP_APO component
    -SAP LiveCache system have MAXDB 7.7.04.29 as backend.
    - Live cache client is installed on same SAP ECC system where we have SAP ECC EHP4 system.
    any suggestion how to resolve it?
    Mani

    >
    Mani wrote:
    > I installed a standalone server and i need it only for SAP HR (specifically Idoc processing in SAP HR Human capital management module). But i am getting error while running ibound idoc process.
    > So Do i still need SAP_APO component?
    I never heard of this specific scenario for liveCache usage in the past 7 years working in SAP support on the liveCache component.
    Might be useful if you provide some more details (documentation, notes, links) that describe this usage scenario.
    In any case you will need to have a liveCache version that is compatible to your application ABAP coding.
    The error message you posted indicates that your liveCache version does not fit your application version (or vice versa).
    > I installed SAP MAxDB and LiveCache buid using Installation master DVD for SAP ERP. So i think i followed the right method as specified in installation guide.
    Be precise, please. Which installation guide? There are hundreds of them - not THE installation guide.
    > Secondly can you help me something specific to my problem in coding form?
    Already did.
    > i tried in LC10, using LCA monitoring i am not able to run SQLDBC trace under
    > LCA >> LiveCache Monitoring >> Tools
    > but i am not able to execute the same, is it a error or we need to configure something?
    Well, the liveCache needs to be integrated into the LC10. You'd do this in transaction SM59 - but as you've followed an installation guide, this would have been covered in it...
    > Operational status is active green light, below is file status.
    >
    >
    KNLMSG     KnlMsg     1.098.697     28.01.2011     06:59:55     Database Messages     ASCII
    > KNLMSGARC     KnlMsgArchive     8.192     28.01.2011     06:59:50     Database Errors     ASCII
    > KNLMSGOLD     KnlMsg.old     342.663     28.01.2011     06:59:50     Database Messages (OLD)     ASCII
    > KNLTRC     knltrace     6.209.536     28.01.2011     06:59:56     Database Trace (Raw/Binary)     BINARY
    > BACKHIST     dbm.knl     570     10.01.2011     06:18:41     Backup History     ASCII
    > DBMPRT     dbm.prt     133.843     29.01.2011     11:41:27     Database Manager Log File     ASCII
    > DBMPAHI     L00.pah     214.225     10.01.2011     06:18:16     Database Parameter History     ASCII
    > LCINIT     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Initialisation     ASCII
    > LCINITCMD     lcinit.bat     3.047     28.10.2008     14:45:51     LiveCache Initialisation Script     ASCII
    > LCINITHIS     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Initialisation History     ASCII
    > INSTPRT     dbm.ins     863.981     10.01.2011     06:18:47     Installation Log File     ASCII
    > DIAGDIR     File     0     10.01.2011     06:18:18     Diagnose History     DIRECTORY
    > ANALYZER     analyzer     0     29.01.2011     00:00:36     DB Analyzer File     DIRECTORY
    > LCTRC#init.his     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
    > LCTRC#init.log     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
    > LCTRC#_apo_version.txt     lc_apo_version.txt     164     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
    >
    > any clue whats wrong?
    > Mani
    The only thing this tells us is: the liveCache instance itself apparently comes up and writes out the standard log files.
    That's it.
    As I already tried to explain, the problem seems to be the dependence between your application and the liveCache version.
    Usually I'd recommend to open a support message for this, but the colleagues would (hopefully) ask the same questions as I did.
    regards,
    Lars

Maybe you are looking for

  • How to install Mountain Lion on my macbook pro MB990LL/A 2009?

    Hi, I have a big problem here.. I saw on internet that many people have installed on they're macbook pro MB990LL/A an OS like Snow Leopard, Lion, Mountain Lion. This weekend, I've tried to install Snow Leopard, and when I've inserted the disc in my m

  • Safari 2.0.4  IS this BETA?

    Safari 2.0.4 It constantly locks up (not responding) I'd like to give it a response! It quits while deleting email repeatedly. I'd like to delete IT! If this is BETA is there a higher one I can download and how and do I need to get rid of the 2.0.4?

  • How do I make fonts larger i photoshop?

    how can I make my fonts larger in photoshop?

  • Windows reconfigures iTunes every time its launched

    Today I finally upgraded to iTunes 9. After about 2 hours of fooling around with it because of missing registry stuff, I download new drivers and reinstalled iTunes. It works and I can download and transfer songs. But heres the problem and yes I know

  • BW query as datasource for segmentation

    Hi, At help.sap.com the following is posted: "Only use queries that are based on InfoCubes. Queries that are based on ODS objects and BI InfoSets are only partially supported." (http://help.sap.com/saphelp_crm50/helpdata/en/af/d0efa709f811d4b2d70050d