Error in BPM

[Former Member]

Hi,

i send a soap message to xi(thru soap adapter) with a async. message interface, this message is then send to BPM thru an abstract interface. I always get the following error:

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

<SAP:Category>XIAdapter</SAP:Category>

<SAP:Code area="BPE_ADAPTER">SYNCHONOUS_MESSAGE</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>This process does not support the specified synchronous interface or does not support any synchronous messages The exception occurred (program: SAPMHTTP, include , line: 0)</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

Please, give your advice on this.

thanks in advance,

Peter Ha

[Former Member]

Hi Peter,

could you pls explain your scenario...like whts on the other end....file or db??

regards

Priyanka

[Former Member]

Scenario:

1) a Webdynpro sends a soap message to XI(XI webservice)

2) a soap adapter receives the message with an async interface(comm. channel = Exact Once)

3) send message to BPM with a async abstract interface

4) send message to R3 (async)

It is a very simple scenario.

[Former Member]

Hi,

Is it an idoc or an rfc on the r/3 side??

If rfcn then response needs to be mapped.Chk whether ur rfc has a return parameter or not.

Regards

Priyanka

[Former Member]

Hi,

i send message to R3 thru with a rfc, it is called async from the BPM. I check that all interface are async.

[Former Member]

hi,

Is the rfc working fine?? chk in SE37....whetehr you are able to push values into tables.

Regards

priyanka

[Former Member]

RFC works with a scenario without BPM,

when i try a sync scenario, everything works.

[Former Member]

what are all the steps in ur bpm

Could you pls mention tht too

Regards

Priyanka

[Former Member]

Hi Peter,

Looks like you have a problem in your business process.. Check all the send recieve n transformation steps.

>>>when i try a sync scenario, everything works.

i suggest instead of changing ur sync scenario to async, try doing it as a separate scenario.

Regards,

Divya

[Former Member]

BPEL:

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

<process name="CreateOrder_BPM" targetNamespace="http://com.unisys.esa/demo" xsi:schemalocation="BPEL4WS.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:tns="http://com.unisys.esa/demo" xmlns:sapxi="http://www.sap.com/xi/">

<variables>

<variable name="CreateOrder_REQ" messageType="http://com.unisys.esa/demo:MT_Order" />

</variables>

<sequence>

<receive name="ReceiveOrder" sap-extn:mode="async" variable="CreateOrder_REQ" createInstance="yes" xmlns:sap-extn="http://www.sap.com/xi/extensions" />

<invoke name="SendToR3" sap-extn:context="" sap-extn:mode="async" inputVariable="CreateOrder_REQ" portType="http://com.unisys.esa/demo:MI_Order_Out_Abstract" operation="MI_Order_Out_Abstract" xmlns:sap-extn="http://www.sap.com/xi/extensions" />

</sequence>

</process>

This is the trace:

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

- <!-- Call Adapter

-->

- <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>synchronous</SAP:ProcessingMode>

<SAP:MessageId>4D4C9016-83CF-6947-8843-A424BDF7D016</SAP:MessageId>

<SAP:TimeSent>2005-08-10T08:57:19Z</SAP:TimeSent>

- <SAP:Sender>

<SAP:Service>SOAP_SENDER</SAP:Service>

<SAP:Interface namespace="http://com.unisys.esa/demo">MI_Order_Out_async</SAP:Interface>

</SAP:Sender>

- <SAP:Receiver>

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

<SAP:Service>CreateOrder_BPM_Service</SAP:Service>

<SAP:Interface namespace="http://com.unisys.esa/demo">MI_Order_Out_Abstract</SAP:Interface>

</SAP:Receiver>

<SAP:Interface namespace="http://com.unisys.esa/demo">MI_Order_Out_Abstract</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>BestEffort</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="2005-08-10T08:57:19Z" wasRead="false">

<SAP:Engine type="IS">is.15.bekon-es7ksap</SAP:Engine>

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

<SAP:MessageId>4D4C9016-83CF-6947-8843-A424BDF7D016</SAP:MessageId>

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

</SAP:Hop>

- <SAP:Hop timeStamp="2005-08-10T08:57:20Z" wasRead="false">

<SAP:Engine type="PE" />

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

<SAP:MessageId>4D4C9016-83CF-6947-8843-A424BDF7D016</SAP:MessageId>

<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>20050810</SAP:Date>

<SAP:Time>095719</SAP:Time>

<SAP:Host>bekon-es7ksap</SAP:Host>

<SAP:SystemId>FXI</SAP:SystemId>

<SAP:SystemNr>15</SAP:SystemNr>

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

<SAP:DB>MSSQL</SAP:DB>

<SAP:Language />

<SAP:ProcStatus>023</SAP:ProcStatus>

<SAP:AdapterStatus>000</SAP:AdapterStatus>

<SAP:User>HATP</SAP:User>

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

<SAP:LogSeqNbr>000</SAP:LogSeqNbr>

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

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

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

<SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>

<SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>

<SAP:QIdInternal />

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

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

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

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

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

<SAP:PlsrvExceptionCode />

<SAP:EOReferenceRuntime type="TID" />

<SAP:EOReferenceInbound type="TID" />

<SAP:EOReferenceOutbound type="TID" />

<SAP:MessageSizePayload>327</SAP:MessageSizePayload>

<SAP:MessageSizeTotal>609</SAP:MessageSizeTotal>

<SAP:PayloadSizeRequest>327</SAP:PayloadSizeRequest>

<SAP:PayloadSizeRequestMap>206</SAP:PayloadSizeRequestMap>

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

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

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

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

<SAP:AdapterOutbound>SA_COMM</SAP:AdapterOutbound>

<SAP:RandomNumber>53</SAP:RandomNumber>

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

<SAP:SkipReceiverDetermination />

</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="bekon-es7ksap">20050810085719.921</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="bekon-es7ksap">20050810085719.953</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="bekon-es7ksap">20050810085719.953</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="bekon-es7ksap">20050810085719.953</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="bekon-es7ksap">20050810085719.953</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="bekon-es7ksap">20050810085719.984</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="bekon-es7ksap">20050810085719.984</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="bekon-es7ksap">20050810085719.984</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="bekon-es7ksap">20050810085719.984</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="bekon-es7ksap">20050810085719.984</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="bekon-es7ksap">20050810085719.984</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="bekon-es7ksap">20050810085720.062</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="bekon-es7ksap">20050810085720.062</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="bekon-es7ksap">20050810085720.078</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="bekon-es7ksap">20050810085720.078</SAP:Timestamp>

</SAP:RunTimeItem>

</SAP:PerformanceHeader>

- <sapsess:Session xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema">

<enableSession>true</enableSession>

</sapsess:Session>

- <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>04101B30D1B4AE48A2F3920E8BBBB705</SAP:OutboundBindingObjectId>

<SAP:FromPartyName />

<SAP:FromServiceName />

<SAP:ToPartyName />

<SAP:ToServiceName />

<SAP:ToInterfaceName />

<SAP:ToInterfaceNamespace />

- <SAP:OutboundBindingAttributes>

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

</SAP:OutboundBindingAttributes>

- <SAP:HeaderMapping>

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

</SAP:HeaderMapping>

- <SAP:ChannelEntry version="30">

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

</SAP: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 =</Trace>

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

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

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

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

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

-->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry&version=3.0&Sender.Service=SOAP_SENDER&Interface=http%3A%2F%2Fcom.unisys.esa%2Fdemo%5EMI_Order_Out_async</Trace>

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

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

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

-->

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

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

-->

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

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

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

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

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

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

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

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

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

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

<Trace level="1" type="Timestamp">2005-08-10T08:57:19Z 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 = 4D4C901683CF69478843A424BDF7D016</Trace>

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

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

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

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

-->

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

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

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

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

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

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

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

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

<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>

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

</Trace>

</Trace>

</Trace>

</Trace>

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

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

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

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

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

<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>

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

</Trace>

</Trace>

</Trace>

</Trace>

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

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

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

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

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

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

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

</Trace>

</Trace>

</Trace>

</Trace>

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

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

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

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

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

<Trace level="1" type="T">Interface Mapping http://com.unisys.esa/demo IM_Order_Out_to_Order_Out_Abstract</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

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

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

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

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

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

<Trace level="1" type="T">processing the outbound binding</Trace>

<Trace level="1" type="T">search outbound bindings</Trace>

<Trace level="1" type="T">outbound bindings found</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

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

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

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

-->

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

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

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

-->

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

<Trace level="1" type="T">Start Sync/Async Communication</Trace>

<Trace level="1" type="Timestamp">2005-08-10T08:57:20Z CET Starting Processing</Trace>

<Trace level="1" type="T">Pipeline Timeout: 10.08.2005 10:58:20 CET</Trace>

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

<Trace level="1" type="T">No mapping property with name sap.bc.bmt.wfm.xi.interface.synch.http://com.unisys.esa/demo:MI_Order_Out_Abstract</Trace>

<Trace level="1" type="T">MI_Order_Out_Abstract really used in process?</Trace>

</Trace>

</Trace>

</Trace>

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

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

-->

</SAP:Trace>

</SOAP:Header>

- <SOAP:Body>

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

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

<SAP:Name>maindocument</SAP:Name>

<SAP:Description />

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

</SAP:Payload>

</SAP:Manifest>

</SOAP:Body>

</SOAP:Envelope>

[Former Member]

Hi Divya Vidyanandan Prabhu

it is a totally new scenario, with new interface, only the message type, data type, RFC... are the same.

The message interface are new for this scenario. Like for a sync message interface(MI), i created a new async MI

[Former Member]

Hi peter,

how abt the communication channels?

Regards,

Divya

[Former Member]

Hi Divya Vidyanandan Prabhu

soap channel: SOAP adapter, QoS= EO

rfc channel: usual stuff

[Former Member]

Also, i see non message in the BPE monitoring, does this means that it never arrive in the BPE?

[Former Member]

Hi peter,

I suggest u make slight changes in ur communication channels say in the description and activate it again.. Try the same with your business Process as well..Hope this tip works

Cheers,

Divya

[Former Member]

Hi Peter,

Just check in the integration process, the process log by pressing F7......see for any errors in it.

Regards

Priyanka

Message was edited by: Priyanka Balagangadharan

[former_member187339]

Hi Peter,

What i have found out from your post

<i><Trace level="1" type="T">No mapping property with name sap.bc.bmt.wfm.xi.interface.synch.http://com.unisys.esa/demo:<b>MI_Order_Out_Abstract</b></Trace>

<Trace level="1" type="T"><b>MI_Order_Out_Abstract really used in process?</b></Trace></i>

Check whether you have created container variable CreateOrder_REQ of type Abstract Interface???

Regards

Suraj

[former_member187339]

Hi Peter,

Check your Quality of service in your Sender Channel, it should be either Exactly Once or EOIO.

Can you describe your scenario, so that I can help you in a better way.

Regards

Suraj