Nwapi-Payload missing

Hi Guys,
I have configured nwapi. When i monitor the messages on the integration engine, i dont see the payload for the asynchronus messages.
we are on PI 7.1 EHP1 SP3
anybody having the same problem? any help would be appreciated.
Thanks,
Reddy

Hello Reddy
Check the notes below:
1) 1515345 Non-supported monitoring tools described in documentation
2) 1446507 NWAPI link removed from PI start page
The nwapi is not supported for monitoring.
Regards
Mark

Similar Messages

Error during sync integrated configuration - incoming payload missed

Hi guys,
we are suing PI 7.11 and trying to use the new feature integrated configuration wherever possible.
Now I test a sync szeanrio where sender is SOAP and receiver is RFC.
The messages fails in SOAP Sender channel with the error that there is no suitable receiver found for this message.
During integrated configuration content based routing is used.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Receiver Determination failed for message e54dba61-9ded-11de-801a-020000000038(OUTBOUND)
But the message fails without persisting the payload, so I could check what value is missing in the receiver rules.
Furthermore the message is only displayed in the sender chanel and is not shown in rwb
While using the normal way of messsage processing where the integration server is involved, such errors are persisted and the payload is also available.
Is that the normal behaviour of integrated configurations.
Could the behaviour be parametrized?
Any help appreciated
Kind regards
Jochen

Hi,
thanks for helping.
Because of integrated configuration the integration server is passed and there is no entry in sxmb_moni.
I already tried this blog, but it doesn´t work for me.
I changed the parameter according to the blog.
But the message content of sync messages are stilled deleted.
Does the parameter changed requires restart of adapter engine or complete java stack?
There two templates one called 'Usage_Type_all_in_One' and above there is an node named equal to the server node name. The parameter of which template have to be changed.
I tried both with out success.
Hopefully you could help me using this feature
Kind regards
Jochen

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>

Response payload missing in SXMB_MONI

Dear All,
I have a query related to Response payload in SXMB_MONI.
I am using IDOC-XI-FILE & FILE-XI-IDOC asynchronous scenario . Output xml files and idocs are generated properly.
<b>In SXMB_MONI,when I click on successful processed message it is not showing me the Response payload-MainDocument(application/xml).</b>
<b>I was able to see response payload in my Development server but in production server I am not able to see the reponse payload.</b>
I am using SP15.
I tried to activate services also using t-code SICF but not able to solve the problem yet.
Can anybody suggest me solution to this problem.

Hi Prabhat,
we had the same problem when we upgraded to SP15, we consulted SAP and they came up with the answer that this is a known bug in SP15. This seems to have been fixed in SP16.
Regards,
Roberto
See Re: SXMB_MONI does not show payload after upgrade to SP15
Message was edited by: Roberto Viana

Payload missing in Soap document

We use XI 3.0, R3->XI->WebService scenario
From my SoapDocument, i don't see the payload being part of the <Body>.
Hence we get the "Object reference not set to an instance of an object" exception, from the WS
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Header xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:wsse="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
+ <SAP:Main versionMajor="3" versionMinor="0" SOAP:mustUnderstand="1" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>6c6d4f1d-922c-bb4c-a530-565d72af968a</SAP:MessageId>
<SAP:TimeSent>2010-07-09T23:27:07Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="" scheme="" />
<SAP:Service>IP_Centura</SAP:Service>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>Centura</SAP:Service>
</SAP:Receiver>
<SAP:Interface namespace="http://bancousa.com/sapr3/fi/transdata/Centura">MI_CenturaReq_Inbound</SAP:Interface>
</SAP:Main>
+ <SAP:ReliableMessaging SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
+ <SAP:Diagnostic SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:HopList SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2010-07-09T23:27:07Z" wasRead="false">
<SAP:Engine type="PE" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">PE</SAP:Adapter>
<SAP:MessageId>6c6d4f1d-922c-bb4c-a530-565d72af968a</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2010-07-09T23:27:08Z" wasRead="false">
<SAP:Engine type="IS">is.01.m2sapxqsc</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>6c6d4f1d-922c-bb4c-a530-565d72af968a</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2010-07-09T23:27:08Z" wasRead="false">
<SAP:Engine type="AE">af.xqs.m2sapxqsc</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>6c6d4f1d-922c-bb4c-a530-565d72af968a</SAP:MessageId>
</SAP:Hop>
</SAP:HopList>
</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>

@ VJ,
In PI RWB, you would not see the payload along with the main document. If you are finding the payload in SXMB_MONI, it is good.
Are you sure about this? I don't think this is correct.
-- Abhi

ISM-SRE-300-K9 Failed

Hello
Im installing a CUCME + CUE, after the instalation of the ISM-SRE-300-K9 in 2921
i configure the module but in show commands it appears as failed, and i cannot access the service module.
IOS : c2900-universalk9-mz.SPA.151-4.M2
CUCME: 8.6
CUE Module: ISM-SRE-300-K9
This message appears on the console:
%SRE_SM-6-STATE_CHANGE: ISM0/0 changing state from SERVICE_MODULE_STATE_SHDN to SERVICE_MODULE_STATE_FAIL
CUE Config on CUCME
interface ISM0/0
ip unnumbered G0/0
service-module ip address 176.16.1.7 255.255.255.0
service-module ip default-gateway 176.16.1.1
no keepalive
ip route 176.16.1.7 255.255.255.255 ISM0/0
dial-peer voice 8100 voip
mailbox-selection orig-called-num
description ------------------------------[CUE]
destination-pattern 80..
session protocol sipv2
session target ipv4:176.16.1.7
dtmf-relay sip-notify
codec g711ulaw
no vad
telephony-service
voicemail 8000
Logs:
%SRE_SM-6-STATE_CHANGE: ISM0/0 changing state from SERVICE_MODULE_STATE_SHDN to SERVICE_MODULE_STATE_FAIL
GW01#service-module iSM 0/0 status
Service Module is Cisco ISM0/0
Service Module supports session via TTY line 131
Service Module is failed
Service Module heartbeat-reset is enabled
Service Module is in fail open
Service Module status is not available
No install/uninstall in progress
Local Partition Info
=====================
Please reset module to retrieve
partition information if needed
Somebody can help me?
Thanks

Did u eventually got this running, I too have the same problem.
I am unable to configure the SRE-300-K9, always i have to reset and go to the int ism0/0 and give no shut to bring it up but it comes up in boot loader configuration.
I tried to install using the guide but after all installation and language selection it keeps saying as payload missing and curl code error 19 and sometimes curl code error 78.
If u already found some solutions pls share it.

SM-SRE-710-K9 CUE module crashed after uploading mailbox license files

Kindly find the attached file for the error I am getting after reloading the CUE module.

Did u eventually got this running, I too have the same problem.
I am unable to configure the SRE-300-K9, always i have to reset and go to the int ism0/0 and give no shut to bring it up but it comes up in boot loader configuration.
I tried to install using the guide but after all installation and language selection it keeps saying as payload missing and curl code error 19 and sometimes curl code error 78.
If u already found some solutions pls share it.

Sender RFC Scenario Error:Payload Is Missing

I am facing an issue in 'RFC2JDBC' scenario which is mentioned below:
here our scenario is 'RFC2JDBC'.here our 'RFC' is having 2 fields in tables parameter
i.e. empno & empname.
the results of the 'RFC' is coming as:
Personnel Number Employee Name
00000100                 Rasmiraj
00000200                 Tanmay
00000300                 Kanhu
00000400                Debabrata
00000500                shantanu
i am triggering the 'rtfc' through a program.
when i am triggering the 'RFC',in monitor of PI it's coming as sucessful.however in the payload one of the field value is missing i.e. employee name.(same also updating in the legacy database)
in the payload it's appearing as:
[ <?xml version="1.0" encoding="UTF-8" ?>
- <rfc:ZSAM_SEND_RFC_PI xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <EMP_DTLS>
- <item>
<EMPNO>00000100</EMPNO>
<EMPNAME />
</item>
- <item>
<EMPNO>00000200</EMPNO>
<EMPNAME />
</item>
- <item>
<EMPNO>00000300</EMPNO>
<EMPNAME />
</item>
- <item>
<EMPNO>00000400</EMPNO>
<EMPNAME>a</EMPNAME>
</item>
- <item>
<EMPNO>00000500</EMPNO>
<EMPNAME />
</item>
</EMP_DTLS>
</rfc:ZSAM_SEND_RFC_PI> ]
please,suggest.(here,we are using sender 'RFC' communication channel & an 'RFC'destination of type 'T'(with parameter registered server program,gateway host,gateway service)

Hi rasmiraj tripathy,
I am also facing the same problem (Sender or Payload is missing) while integrating R3 to B1 using IDOC. When I resend IDOC, it capture by B1iSN but doesn't work, it gives me error. When I look into xml document, it is found that there is no receiver payload.
My R3 system is non-unicode and it is difficult to change it to unicode as it requires updation.
Can you please confirm that this error is coming due to Non-Unicode, and can be resolved by setting it to Unicode.
Note: There is no double definition of any object.

Payload is missing in XI adaptor

HI
My scenario is file->XI->Proxy.
Message is showing sucessful in SXMB_MONI,but the output message in payload of XI adaptor is not comming.Under the SOAP Ody only maifest exists,ut no payload can be seen.Also in proxy input structure data is not comming(initial).What can be done??
Thanks
Debraj

Hi debraj,
Is your XI patched upto SP15?
if so then, the payload doesnt appear in the SXMB_MONI transaction code. There was no clue to this behaviour. There are also some threads that discussed this.
Go thro these threads,
SXMB_MONI does not show payload after upgrade to SP15
Response payload in SXMB_MONI is missing
regards,
P.Venkat

Missing response payload in IE

Hi,
System:
PI 2004s SP 23
Problem:
Integration engine does not receive payload from adapter engine.
Scenario:
Synchronous scenario
proxy -> xi -> soap
Description:
This is an old scenario that have been working fine for years but after upgrade from SP 14 to SP 23 it no longer works.
The service is still being called fine. In the AE i can see the response payload being returned to PI.
When i look in IE however i can no longer see the response payload, only the manifest. Further response processing thus causes an error due to the missing payload.
For the record it should be stated that im using 'nosoap' in the receiver SOAP adapter.
This is not an issue related to logging. Logging is fine, but the response payload really is non-existent when entering the IE.
Apart from this there is no special configuration involved.
Thanks in advance,
Daniel

Hi Daniel,
Thanks for your response.
We are 711 SP 6 both on ABAP and Java stacks. This SAP Note# 1522630 alone resolved the problem for you ? What was the parsing issue about ? The only issue I have currently is I could not see the response payload from Receiver SOAP adapter in IE which is causing mapping issues since payload is missing.
Please let me know.
Shany

SOAP Adapter missing payload on receiving web service

Hi there,
I'm having a problem with a File to (asynchronous) SOAP Adapter scenario that is currently baffling me.
I wonder if anyone out there has any troubleshooting ideas for this one?
The source message is being picked up OK and I can see from Communication Channel Monitoring on the Runtime Workbench that it is allegedly being delivered to the Web Service OK.
All the entries in the audit log point to a successful scenario and I can view the payload in the Message Content "payload" area.
However on the web service / server side the message is completely blank. Somewhere along the line the payload has gone missing.
I can copy and paste the payload manually into the web service test area and this is fine.
Any ideas/suggestions as to what could be happening with this or how I might go about troubleshooting it?
Many thanks
Ian

Thanks Bruno,
It looks like you were right...
In the end we used Wireshark - a packet sniffing application - to check what was actually hitting the destination server. We found that the content was arriving at the server but the web service wasn't accepting the format. The creators of the web service are now investigating why and will hopefully will advide me of the format error in the message. But at least I was able to prove that the message was getting there which was the focus of this query.
Regards
Ian

Sender SysId, Sender ObjectType or Sender payload is missing.

Hello Experts,
i'm currently trying to learn about B1i.
I installed the current version of B1i (Version B1iSN2007.P11.3.46 ) and started with the B12B1 example, presented here.
I managed to follow the instructions without too much problems, but I'm actually stuck at monitoring the results.
When I submit a PO, i get the following error in the logs: Sender SysId, Sender ObjectType or Sender payload is missing.
I checked the forums on this issue, but haven't found an answer. I actually followed the instructions in the blog very closely.
I also seem not to have a Receiver Type 2007_SO, which is why i wrote the needed parts myself.
If someone could help me continue, i would be really thankful!
Sincerely,
Florian

Hi Florien,
Last week I had the same error during a demo :o(
I find out the problem after the demo but the demo was already registered with all the steps showing how to try to find a problem in B1iSN...
In my case it was due to a double definition of the same B1 object in B1iSN.
There is a limitation in B1iSN for B1 objects. You can only define 1 custom B1 object per each type of B1 object. So you can have only for example one custom definition of the B1 PO object apart from the B1iSN default definition for the PO.
Hope it works also for you
Regards
Trinidad.

Namespace missing in the payload

Hi ,
I doing a JDBC to IDoc scenario.I am using a JDBC sender Adapter to get data using a select query from DB Table ,every thing works fine.The Structure get filled up ,but the namescape is missing in the source payload (SXMB_MONI).Anyone knows why this is happening.
Thanks,
Venu

Hi Venu,
looks like you are missing namespace in the JDBC data, you should mention the docNamespace in the JDBC sender adapter.
Copy your payload and paste this in your mapping test tab. How ? After copying the payload go to Message mapping, there is Tab for Test right next to the Design. click on that and then click on the SRC button in the source message and paste your XML and do a test. Then you will know whats going wrong.
One other precaution is, you can fill the fields in the test tab then click on SRC button to look at what the source XML should look like.
hope you understand, if not post the question again.
Thanks.

DBout segment missing in receiver payload

Hello,
We have a problem with a scenario at our customer.
We created a B1if File to B1 scenario.
For some files we get a failure message in the message log saying:
"DBout segment missing in receiver payload (handover to database not possible) "
When we do a retry with restart in-process (biu processing and outbound) it works.
Sometimes a second retry is needed.
Any ideas?
Best regards,
Steven

Hi Mark,
Thank you very much for the explenation!
I will try this and let you know if I got it to work
I'm very new to B1i as you can see.
I found the solution to our problem.
The processing of the B1if File to B1 scenario is devided into 3 scenario's.
First scenario: a timer checks every minute for files in a certain directory 'IN'. 1 file is copied into another directory 'PROCESSING' and called ORDER.csv. The original file is being cut and paste into directory 'SAVED'.
Second scenario: check if file ORDER.csv exist in directory 'PROCESSING'. Some checks and some processing are done on the file.
Last scenario: every minute this is run with a timer. Some checks are done and the objects are created in B1.
The processing of 1 file takes about 1 minute to 1 minute and a half!
The problem was that a timer was set to check every minute if there was a file. (first scenario).. offcourse when the processing is still busy this will fail and I believe that is why a file was almost always skipped.
I changed the timer to every 2 minutes and now everything works like a sharm!
Problem is that it takes offcourse twice the time as before.
Do you or anybody else knows a possibility to speed this up?
Is it possible to create the scenario in 1 scenario instead of 3? or maybe 2?
Kind regards,
Steven

Content missing in payload

Hi ,
I am using FCC.communication channel is running fine.
But , content is missing in payload.
Even i cant see fiield tags in MONI.
What could have been the probelm.
Regards
--Pradeep

Hi,
My FCC parameters are,
Emp_header.fieldSeparator     ' '
Emp_header.endSeperator     'nl'
Emp_header.fieldNames     key,empid,empname
Emp_header.keyFieldValue     1
Emp_header.keyFieldInStructure     ignore
Emp_week_det.fieldSeparator     ' '
Emp_week_det.endSeperator     'nl'
Emp_week_det.fieldNames     key,week,weekhours,wage
Emp_week_det.keyFieldValue     2
Emp_week_det.keyFieldInStructure     ignore
Emp_summary.fieldSeparator     ' '
Emp_summary.endSeperator     'nl'
Emp_summary.fieldNames     key,Tot_hrs,Tot_wage
Emp_summary.keyFieldValue     3
Emp_summary.keyFieldInStructure     ignore
Regards
--Pradeep

Nwapi-Payload missing

Similar Messages

Maybe you are looking for