Payload missing in File-File scenario

Hi,
I have created a scenario which is a combination of File-IDoc and File-File scenario.
First scenario is working fine.IDoc is getting generated and posted to SAP R/3.
I could see messages for these two as child messages in sxmb_moni with same message ID.
But in the second message,payload is missing in Call Adapter block and Response block in sxmb_moni.
Also,output file is not getting generated though the message is successful in sxmb_moni.
Could anyone please let me know what could be the reason for this.
Thanks.
Best Regards,
Shweta

this is the full trace:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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>47A1A2FD-9F90-0066-E100-80028928A9DC</SAP:MessageId>
<SAP:TimeSent>2008-01-31T10:34:40Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">Logitec_Test</SAP:Party>
<SAP:Service>POS_MAIL</SAP:Service>
<SAP:Interface namespace="http://pan.eu/ORDERS/LOGITEC_ORDRS_09">MI_ORDERS_EDIFACT_D96A_AS_OB</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">Logitec_Test</SAP:Party>
<SAP:Service>BS_FILE_RECEIVER</SAP:Service>
<SAP:Interface namespace="http://pan.eu/ORDERS/LOGITEC_ORDRS_09">MI_ORDERS_EDIFACT_D96A_AS_IB</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>s0jXwORWMKCNyteX7/7ysA==</SAP:ObjectId>
<SAP:SWCV>ftfEkNt0EdqTpexmiSip3w==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="http://pan.eu/ORDERS/LOGITEC_ORDRS_09">MI_ORDERS_EDIFACT_D96A_AS_IB</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="2008-01-31T10:34:40Z" wasRead="false">
<SAP:Engine type="AE">af.pxe.pandpxe</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>2100B8D2-CFE8-11DC-CDAA-001125A5DEBE</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2008-01-31T10:34:40Z" wasRead="false">
<SAP:Engine type="IS">is.00.pandpxe</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>47A1A2FD-9F90-0066-E100-80028928A9DC</SAP:MessageId>
- <SAP:Branch>
<SAP:MessageId>47A1A2FC-9F90-0066-E100-80028928A9DC</SAP:MessageId>
<SAP:Service>PAECLNT020</SAP:Service>
</SAP:Branch>
- <SAP:Branch>
<SAP:MessageId>47A1A2FD-9F90-0066-E100-80028928A9DC</SAP:MessageId>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">Logitec_Test</SAP:Party>
<SAP:Service>BS_FILE_RECEIVER</SAP:Service>
</SAP:Branch>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20080131</SAP:Date>
<SAP:Time>113441</SAP:Time>
<SAP:Host>pandpxe</SAP:Host>
<SAP:SystemId>PXE</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>AIX</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>003</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>XIAFUSER</SAP:User>
<SAP:TraceLevel>3</SAP:TraceLevel>
<SAP:Logging>1</SAP:Logging>
<SAP:LogSeqNbr>004</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>XBTOW___0002</SAP:QIdInternal>
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:ParentId ChildNo="0" ChildTotal="0">2100B8D2CFE811DCCDAA001125A5DEBE</SAP:ParentId>
<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">8928A9DC00C947A1A441092F</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>4272</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>8041</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>4272</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>2874</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
<SAP:AdapterOutbound>AENGINE</SAP:AdapterOutbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>35</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Sender_Agreement_GUID>C14103EF96A93EF7A416B17522666D3A</SAP:Sender_Agreement_GUID>
<SAP:Receiver_Agreement_GUID>4E2837E24B083A33A77C5043CBB15379</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="pandpxe">20080131103440.920981</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="pandpxe">20080131103440.934955</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="pandpxe">20080131103440.935459</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="pandpxe">20080131103440.945085</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="pandpxe">20080131103440.945102</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="pandpxe">20080131103441.062247</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="pandpxe">20080131103441.064953</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="pandpxe">20080131103441.069988</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="pandpxe">20080131103441.096849</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="pandpxe">20080131103441.102084</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="pandpxe">20080131103441.11954</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="pandpxe">20080131103441.170827</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="pandpxe">20080131103441.170842</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="pandpxe">20080131103441.343581</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="pandpxe">20080131103441.346447</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="pandpxe">20080131103441.388572</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="pandpxe">20080131103441.414031</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="pandpxe">20080131103441.418165</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="pandpxe">20080131103441.447064</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="end" host="pandpxe">20080131103441.589866</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>4E2837E24B083A33A77C5043CBB15379</SAP:OutboundBindingObjectId>
<SAP:FromPartyName>Logitec_Test</SAP:FromPartyName>
<SAP:FromServiceName>POS_MAIL</SAP:FromServiceName>
<SAP:ToPartyName>Logitec_Test</SAP:ToPartyName>
<SAP:ToServiceName>BS_FILE_RECEIVER</SAP:ToServiceName>
<SAP:ToInterfaceName>MI_ORDERS_EDIFACT_D96A_AS_IB</SAP:ToInterfaceName>
<SAP:ToInterfaceNamespace>http://pan.eu/ORDERS/LOGITEC_ORDRS_09</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">Logitec_Test</SAP:PartyName>
<SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">BS_FILE_RECEIVER</SAP:ServiceName>
<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">CC_FILE_RECEIVER_EDIFACT_ORDERS</SAP:ChannelName>
<SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">File</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">3B787A8035C111D6BBE0EFE50A1145A5</SAP:AdapterSWCV>
<SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">AE</SAP:AdapterEngineType>
<SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">File</SAP:MessageProtocol>
<SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">3.0.0527</SAP:MessageProtocolVersion>
<SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">FTP</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">Seeburger</SAP:FromPartyAgency>
<SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30">AS2ID</SAP:FromPartySchema>
<SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30">AS2ID</SAP:ToPartySchema>
<SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30">Seeburger</SAP:ToPartyAgency>
- <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:ChannelAttributes>
</SAP:ChannelEntry>
</SAP:OutboundBindingEntry>
</SAP:OutboundBinding>
- <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 = Logitec_Test</Trace>
<Trace level="1" type="T">Sender party normalized = Logitec_Test</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="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = pandpxe.pan.eu:8000</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 137.40.169.220</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="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<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="3" type="T">system-ID = PXE</Trace>
<Trace level="3" type="T">client = 010</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-01-31T10:34:40Z 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 = 2100B8D2CFE811DCCDAA001125A5DEBE</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="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = 2100B8D2CFE811DCCDAA001125A5DEBE</Trace>
<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="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTI0008</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0008</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = 2100B8D2CFE811DCCDAA001125A5DEBE</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">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="3" type="T">Version number = 000</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<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="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = PXE</Trace>
<Trace level="3" type="T">client = 010</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z 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="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <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 level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: Logitec_Test - BS_FILE_RECEIVER</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 2</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - PAECLNT020</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:2</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <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 level="2" type="T">Check conditions for (Inb: Party Srvc If) PAECLNT020 ORDERS.ORDERS05</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: ORDERS.ORDERS05</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) Logitec_Test BS_FILE_RECEIVER MI_ORDERS_EDIFACT_D96A_AS_IB</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: MI_ORDERS_EDIFACT_D96A_AS_IB</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:2</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <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="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<Trace level="1" type="T">number of receivers: 2</Trace>
<Trace level="1" type="T">Multi-receiver split case</Trace>
<Trace level="1" type="T">Persisting initial (pre-split) message</Trace>
<Trace level="1" type="T">Persisting split messages (split kids)</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Splitting loop start</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Split kid MessageGuid: 47A1A2FC9F900066E10080028928A9DC</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO3___0001</Trace>
<Trace level="1" type="T">Persisting split kid = 47A1A2FC9F900066E10080028928A9DC</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="T">Split kid MessageGuid: 47A1A2FD9F900066E10080028928A9DC</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTOW___0002</Trace>
<Trace level="1" type="T">Persisting split kid = 47A1A2FD9F900066E10080028928A9DC</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<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="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = PXE</Trace>
<Trace level="3" type="T">client = 010</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z 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="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET Begin of pipeline processing PLSRVID = 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="Timestamp">2008-01-31T10:34:41Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <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="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping is already determined in the interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping B348D7C0E45630A08DCAD797EFFEF2B0</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping 7ED7C490DB7411DA93A5EC668928A9DF</Trace>
<Trace level="1" type="T">Interface Mapping http://pan.eu/ORDERS/LOGITEC_ORDRS_09 IM_ORDERS_EDIFACT_to_ORDERS_EDIFACT</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_.</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_ completed. (executeStep() of com.sap.xi.tf._MM_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <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 level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">Logitec_Test-POS_MAIL</Trace>
<Trace level="2" type="T">Logitec_Test-BS_FILE_RECEIVER</Trace>
<Trace level="2" type="T">http://pan.eu/ORDERS/LOGITEC_ORDRS_09.MI_ORDERS_EDIFACT_D96A_AS_IB</Trace>
<Trace level="2" type="T">Channel found: Logitec_Test - BS_FILE_RECEIVER - CC_FILE_RECEIVER_EDIFACT_ORDERS</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS =</Trace>
<Trace level="3" type="T">P_IFNAME =</Trace>
<Trace level="3" type="T">P_METHOD =</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Unknown channel type: File</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: File</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">return fresh values from cache</Trace>
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
<Trace level="3" type="T">URL = http://pandpxe:50000/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User = XIISUSER</Trace>
<Trace level="3" type="T">Cached = X</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 200</Trace>
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 003</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="T">Async processing: skip mapping of response</Trace>
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK.</Trace>
<Trace level="3" type="T">system-ID = PXE</Trace>
<Trace level="3" type="T">client = 010</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 003</Trace>
<Trace level="3" type="T">Message version 004</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</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" />
</SOAP:Body>
</SOAP:Envelope>

Similar Messages

PI 7.1 EHP1 - Unable to find missing file (File to Proxy) - AAE

Hi Friends,
We have one File to Proxy scenario which is configured using ICO (Integration Configuration) - AAE. In this, the MDM system places every day n number of files at 9:30 PM IST in FTP server. (No of file ex: 16180, 12500, 6000) like this. It is a one time process everyday. Our PI file channel is shceduled at 10:30 PM ISTto pick and process those files. Once all files are picked, those moved to archive directory.
Then problem is It is difference between files in archive directory and processed messages in PI. Ex:
Sep 30 --> Files --> 16179 (Archive) --> 16178 (Processed in PI), Oct 2 --> Files -->12492 (Archive) --> 12490 (PI).
Everyday 1 or 2 files are missing in PI. We set the polling interval as 2 hrs and keep the channel active for 8 hrs.
1) The file names are unique.
2) Though payload are same in some of the files, the file is processed.
The MDM log says 16179 files were exported successfully.
Is AAE miss any one file / two files ? Really it is confusing for us how to compare this and find the missing one.
Friends, could you please clarify from your experience how to solve this.
Thanking you.
Kind regards,
Jegathees P.

Hello,
Please check at PI side how much messages get processsed that day..is there any error in RWB.
Messages count in pi and MDM should match if files are processed succesfully from MDM side.
Regards
Monica
Edited by: monica bhosale on Oct 4, 2011 12:32 PM

File-to-File/RFC scenario with reading filename

Hi,
i have a File-to-File/RFC scenario which causes some problems in desining it correctly. Maybe some of you has an idea how to do this.
Scenario:
- A file is picked up by a File-Adapter. The files are different: pdf, doc, tiff, jpg, txt, ...
- The file must now go through a business process (not necessary the file, but i need the filename in the business process).
- The process has to contact several backend systems (SAP R/3) to collect some data. To achieve this the filename has to be send to this systems.
- The collected data are send via SOAP to a receiver system
- The file itself has to be stored in a directory via File-Adapter.
Here's my problem:
- Is it possible to transport the binary file content within a message which contains other elements (e.g. filename)?
- Is it possible to do graphical mappings with such a payload (only 1 to 1)? Or must i use Java Mappings only?
- How to generate a Message from the sender File Adapter which contains binary file content AND filename? Is this possible with a Module?
- Is it better to create 2 messages with an adapter module? One with the image the other with the filename. Or is it better to split them later in a Mapping?
Thanks in advance,
ms

If all that you need is the file name, use adapter specific settings in the sender file adapter. Then you can access the file name in mapping runtime in UDFs. If you want to have content of the pdf, jpg etc images, i do not think there are ready modules available except for reading pdfs ( you might have to research on this).
For look ups etc with R3 systems, you can use the file name that you got from the adapter and store it in mapping fields.
VJ

Records are missing in the File which XI has placed in Target FTP server

Hi All,
I have a scenario where in XI is transfering the files from ECC to Target System . No transformation required here . I am using AAE to run this scenario.
Issue i am facing here is that i can see few records missing in the File which XI had placed in the Target system FTP server . Same file if i check it in archive folder of ECC (which XI has archived after picking the file), complete set of records are present for the same file.
Need your inputs please....
Note : XI is using AAE to transfer the files and no mapping . Also i tried to check out the audit logs in the channel monitoring . Unforutanely i was not able to see the logs to check the bytes that was transferred while readng and writing the file . Sometimes i have faced audit logs issue in PI 7.1
Regards
Vinay P.

Please use temporary name scheme
http://help.sap.com/saphelp_nwpi711/helpdata/en/44/6830e67f2a6d12e10000000a1553f6/content.htm
hope this helps
regards
Ninad

ATTRIBUTE_IDOC_RUNTIME error in File-IDOC Scenario

Hi,
I got this error in FIle-IDOC scenario.
ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPMMX, client , RFC destination contain errors
There are many threads on same issue. Almost in all threads, the suggestion given was, we need to check the Channel Definition(Port should be SAP<SYSID> and not SAP<SYSID>_<CLIENT>)
I have given the proper values for RFC desitnation and port. Even then, I m getting this error.
Is there any other suggestions?

Hi aarthi,
I suggest u chk all d settings dat u hav done..
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Step 6)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 7)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
reward points if helpful...
MenoN

File - File integration scenario in SAP XI 3.0

I am trying a simple file <-> file scenario in XI 3.0 . I am reading file content from an FTP server , having a simple mapping program in XI and then writing it to another foler on the FTP server.
I am completely new to XI , however worked on TIBCO EAI extensively.
I have created the following DESIGN TIME Objects and NOTHING ELSE
1) Two DataTypes , Two Message Types & Two Message Interfaces
2) An interface mapping & a message mapping object( mapping program) to convert b/w the above two message types
I have created the following CONFIGURATION TIME objects and NOTHING ELSE
1) Two Business Services ( Under Service without Party ) , and ve created a communication channel ( adapter type FILE ) under each business service
I am trying to use the Configuration Assistant under Tools menu , the doc says , i just need to select the message types & the rest will be genrated by the wizard. I choose the Business Service , but then what is the "INTERFACE" i have to choose , since nothin appears in the drop down. I tried "Internal Communication" & "Partner Communication" options but got stuck in both when choosing the "interface" object. Ideally i think i need to choose the "internal communication".
Any pointers to what am i missing will be helpful . What are the objects i need to create at Design Time & Config time to achieve the above scenario.

The Configuration Assistant does not work for business services without party. Go to the SLD and create one or two Business Systems and add them to the Integration Directory, then it should work.
Regards
Stefan

Error message: Missing PDF maker files in Word 2007

OK, I am beyond frustrated. I have had nothing but trouble with Windows Vista and Adobe Acrobat. Please help!!!
What happens: first, the pdf addin for Word 2007 suddenly becomes disabled, for no apparent reason. Forget about trying to re-enable it through the Add-Ins menu, because Word tells me that the "connected state of Office Add-Ins registered in the HKEY_LOCAL_MACHINE cannot be changed". This is a problem for me, because I use a special font (Vietnamese) that sometimes gets corrupted when running pdf maker. The only consistent way I have found to avoid this problem is to run the pdf maker as "Quick PDF" and as far as I can see that option is only available through the pdf addin in Word, I have never been able to find it when I open the Acrobat program and create a pdf from there.
Second problem: shortly after the pdf addin becomes disabled, my Acrobat program loses the ability to create pdfs altogether. I get the error message "Missing PDF maker files". Yes, I have tried repairing the installation and re-starting my computer per the instructions given. It doesn't fix the problem. I also tried looking in the Knowledge Database on this website, but it appears that the instructions they have to fix the problem there are for earlier versions of Word, not 2007, because my version of word does not look like the version of Word in their little videos.
This is the second time this has happened. The first time I resolved the problem by a) re-installing Acrobat, which is a pain because it involves calling Adobe and wading through their customer service to get a new installation number, and b) paying a computer repair service to dig deep into the guts of my computer and convince it to change the Office Add-ins to allow the pdf addin again. It worked for about 6 months, and now I have the same problem again. For some reason Vista is spontaneously disabling Acrobat.
I simply cannot deal with this every few months. We all know that Vista is a crappy program, but I run a business and I need a program that works with whatever crappy program Microsoft puts out. Please, can anyone give me suggestions about how to re-enable these functions when Vista disables them?
Thanks in advance!
Alycia

for Office 2007, see if this Microsoft product will work for you
http://www.microsoft.com/downloads/details.aspx?FamilyId=4D951911-3E7E-4AE6-B059-A2E79ED87 041&displaylang=en

In firefox 4 RC, some addons installed suddenly disappear, but checking the profile, some of the missing addons related files are still here, how to make the addons back?

I use firefox 4 form beta 9 to RC (zh) now and there are also firefox 3.6 installed in computer. One day when I open Fx 4 RC, some (actually a lot but not all) of the adoons just disappear. When I check on about:addons page, some addons installed do not appear in the list.
The addons '''REMAINED''' including:
* addons I already used in Fx 3.6 (like webmail notifie , xmarks)
* ''addons only can use in Fx 4'' (like Open Web Apps for Firefox).
The addons '''DISAPPEARED''' including:
* addons I already used in Fx 3.6 (like yoono)
* '' addons installed when using Fx 4'' (like updatescanner, Thumbnail Zoom).
But when I check the profile(by Help > Troubleshooting Information>Open Containing Folder) , some (not sure is it all) of the missing addons related files are still here [lucky], so any one know how to make the missing addons back?
Some more details:
* This happened when i use RC for already a few days and keep on even i restart Fx and windows.
* The bookmarks, history, search engine and even themes and icon setting are still here. [ I only sync bookmarks but not history for both xmarks and firefox sync.]
* This addons are really '''disappeared''' but not disable only!
* This number of addons missed, as i remember, at least 30, should be more than that number bacause some of them are installed but in disable mode.
* I try to install back one of the addons - Stylish, the installed code are still here.
* It is nearly an impossible mission to install every missing addons again, as it really kill my time.

Delete the files extensions.* (extensions.rdf, extensions.cache, extensions.ini, extensions.sqlite) and compatibility.ini in the Firefox [[Profiles|profile folder]] to reset the extensions registry. New files will be created when required.
See "Corrupt extension files": http://kb.mozillazine.org/Unable_to_install_themes_or_extensions
If you see disabled, not compatible, extensions in "Tools > Add-ons > Extensions" then click the Tools button at the left side of the Search Bar to do a compatibility check.

I am running InDesign CS5.5 and trying to open an In Design File but getting an error message. " Cannot open the file "PDavidLCover.indd". Adobe InDesign may not support the file format, a plug-in that supports the file format may be missing, or the file

I am running InDesign CS5.5 and trying to open an In Design File but getting an error message. " Cannot open the file "PDavidLCover.indd". Adobe InDesign may not support the file format, a plug-in that supports the file format may be missing, or the file me be open in another application."Please help I really need to get this file open.

Since you've shown us the folder contents it's a good bet it isn't in use (no lock file). And it doesn't look like the file is mis-named as there doesn't seem to be anything else there that would be the .indd file (but just in case, open it in TextEdit and paste the first few lines here so we can see what the file header says), so the most likely case is the file is damaged. Is that on a removable device of some sort?
You can try the tool at Repair corrupt InDesign Adobe files on Mac OS X or send me a link to the file by private message and I'll try the recovery tool I have for Windows.

Has anyone found a quick, permanent solution to the missing iTunes.msi file. It's very frustrating that I can't uninstall or reinstall. I have a new iphone and I'm dead in the water:)

Has anyone found a quick, permanent solution to the missing iTunes.msi File? I have tried many times to upgrade both itune and quicktime and get the same old error notice. Surely, by now, someone has found out how to get around this mess. Please....

(1) Download the Windows Installer CleanUp utility installer file (msicuu2.exe) from the following Major Geeks page (use one of the links under the "DOWNLOAD LOCATIONS" thingy on the Major Geeks page):
http://majorgeeks.com/download.php?det=4459
(2) Doubleclick the msicuu2.exe file and follow the prompts to install the Windows Installer CleanUp utility. (If you're on a Windows Vista or Windows 7 system and you get a Code 800A0046 error message when doubleclicking the msicuu2.exe file, try instead right-clicking on the msicuu2.exe file and selecting "Run as administrator".)
(3) In your Start menu click All Programs and then click Windows Install Clean Up. The Windows Installer CleanUp utility window appears, listing software that is currently installed on your computer.
(4) In the list of programs that appears in CleanUp, select any iTunes entries and click "Remove", as per the following screenshot:
(5) Quit out of CleanUp, restart the PC and try another iTunes install. Does it go through properly this time?

PI 7.1 scenario -- File to File , File to IDOC and IDoc to File Scenario

Hi All,
*I have PI 7.0 . I have in that File to File , File to IDOC and IDoc to File Scenarios*
File to File -- This scenario is working fine.
File to IDOC -- Setting done in PI 7.0 like SM59, IDXI, IDX2 and in R/3 like SALE (logical system)--- This scenario is working fine.
IDoc to File -- Seeting done in R/3 like SALE (Logical system, Distrubtion Model (Port, Partner Profile)) -- This scenario is working fine.
Now I need to move to PI 7.1 -- for File to File , File to IDOC and IDoc to File Scenarios.
Please let me know do I require to make any changes in Design and Configuration and settings in PI 7.1 and R/3 for above scenarios or it will work fine as it is already working for PI 7.0
If changes are required please let me know what changes to do for each scaenario and pls also send blogs for that.
Regards

>
Rickkk wrote:
> Hi,
>
> Idoc metadeta is updated through idx2?
>
> Regards
If there is no metadata maintained for an idoc type, the metadata for that idoc type gets loaded when an idoc of that type is received by PI for the first time. If you are looking at loading metadata of all idoc types before the first run, its really not required. Just make sure that the port is configured properly. Although, there is no harm in preloading the metadata using IDX2.
You need to use IDX2 mandatorily when the the metadata changes and the metadata in ECC and PI is different. In that case, you need to delete metadata for the changed IDoc type and then either you can update the metada through IDX2 or let the system take care of.

Error in file-file scenario: HTTP response contains status code 503

Hi folks,
I've encountered the foll error in file-file scenario:
Testing file-file scenario (followed the blog: https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/flatFILETOFLATFILE&)
Initially i was hving problems with recvr comm channel, which are now resolved. File is sent successfully but not recvd. I tried to modify the scenario above and change the file type to 'Text' but still got the same error.
I've checked SICF -->default_host/xi/engine , we dont maintain logon data there. when i test the default_host/xi/engine service, it resolves into an ip addr as follows:
http://<hostname>.<domain.com>:8001/sap/xi/engine?sap-client=<clientNo>
(Also, we hv a BW system running on the same server ,which uses a fully qualified domain, while we dont which is why we get the above domain. Im not sure if there are any issues with that.)
and we get the foll error:
Error Code 10060: Connection timeout
If i remove the domain manually, im prompted for userid/pwd and get the foll result:
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header />
- <SOAP:Body>
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Client</faultcode>
<faultstring>Pipeline specified in URL attribute (type) not existing</faultstring>
<faultactor>http://sap.com/xi/XI/Message/30</faultactor>
- <detail>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">URL_PIPELINE_NOT_FOUND</SAP:Code>
<SAP:P1>/sap/xi/engine?sap-client=<clientNo></SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Pipeline ID , which is expected as value of attribute "type" in the URL, does not exist in the Integration Engine (URL = /sap/xi/engine?sap-client=811)</SAP:Stack>
</SAP:Error>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
also, we dont hv any overload issues as this is dev env and not many of us are using the xi server. Would really appreciate if any of you can share your inputs on how to resolve this. Thanks!!
cheers
Prachi

Hi ,
Look in to this for all errors
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
Refer SAP Note 803145,807000,791655
<b>Award Points if found usefull.</b>

N:1 file merging scenario in bpm

Hi friends,
Can anybody send me link of blog for file merging scenario in BPM. i hav two files and i hav to merge it into one single file. I am new to XI, plz help me.
Thanks in advance,
Shweta

Hi,
Check this blogs...
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/narendra.jain/blog/2005/12/30/various-multi-mappings-and-optimizing-their-implementation-in-integration-processes-bpm-in-xi
http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
Merging using corelation -
/people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
Example using correlation:
http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
Please reward points if it helps
Thanks
Vikranth

XI is not able to archive file in file-idoc scenario

Hello friends,
I have an issue in my file->idoc scenario. When a file is placed to XI's filesystem using FTP, it is placed under xiftpuser user. Owner of all directories in this structure wher the file is placed is xiftpuser. XI is not able to archive the file because of the permissions on the archive directory. But the problem is, permissions on this directory are 775 and xiftpuser and xipadm user are in the same group. So this should work. But it doesn't. When I change permissions to 777 everything works fine.
Do you have any idea what could be wrong?
Does it matter, that xipadm user has been added to the common group with xiftpuser "later", when XI was up a long time before? Do we need to restart j2ee to take these new permissions into account?
Thank you,
Olian
Edited by: Olian Saludew on Sep 23, 2008 11:46 AM

Hi,
If archive directory Path is d:\archive
Put a '\' after it.
e.g. "D:\archive\"
It will work.
Regards,
Akshay.

Why is the import tab missing under the file tab?

Why is import missing under the file tab? I want to import bookmarks etc. from Safari into Firefox.

You can find the Import menu entry in the Bookmarks Manager (Library)
*Bookmarks > Show All Bookmarks > Import & Backup > Import Data from Another Browser
*http://kb.mozillazine.org/Import_bookmarks

Payload missing in File-File scenario

Similar Messages

Maybe you are looking for