BPE_ADAPTER SYNCHONOUS_MESSAGE Error on sync RFC from BPE

[Former Member]

Hello, I'm frustating on an error which occurs in the BPE. I have a little ASYNC/SYNC Bridge that takes a Message from an Service asynchronly, does an transformation and should send it on an synchrone RFC module. The answer of the RFC is not needed.

SOAP --> XI/PI --> RFC

The hole process is shown here:

[Scenario(overview)|http://www.gothsite.de/sappi/Scenario1.jpg]

[ReceiveStep|http://www.gothsite.de/sappi/Scenario2.jpg]

[Transformation1|http://www.gothsite.de/sappi/Scenario3.jpg]

[SyncSendStep|http://www.gothsite.de/sappi/Scenario4.jpg]

[Tranformation2|http://www.gothsite.de/sappi/Scenario5.jpg]

[MessageOverview|http://www.gothsite.de/sappi/Scenario6.jpg]

[BPEL Szenario as ZIP|http://www.gothsite.de/sappi/BPEL-Szenario.zip]

Here the error thar occurs:

<!-- Call Adapter

-->

- <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>The process does not support the given synchronous interface or does not support synchronous messages Exception CX_WAPI_DEF_PROPERTY_NOT_FOUND occurred (program: SAPMHTTP, include: , line: 0).</SAP:Stack>

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

</SAP:Error>

In the Trace of the calling Message there is an entry, I don't know if it is relevant:

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

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

<Trace level="1" type="Timestamp">2009-02-24T09:10:03Z CET Starting Processing</Trace>

<Trace level="1" type="T">Pipeline Timeout: 24.02.2009 10:11:04 CET</Trace>

<Trace level="3" type="T">Calling BPE Adapter</Trace>

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

<Trace level="3" type="T">Processing mode is</Trace>

<Trace level="1" type="T">No mapping property with name sap.bc.bmt.wfm.xi.interface.synch.urn:claas:pi:csc:export:report:10:MI_AB_ASYNC_Report</Trace>

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

</Trace>

The system is an SAP PI 7.0 on SP 13.

The SOAP Adapter is on Best Efford, but I think it isn't used, because the service call comes directly to the Integration Engine.

Can anybody give me a hint, where my failure comes from?

[Former Member · Accepted solution]

Hi

Check the below

1) if your RFC CC is set correctly & working fine (for other simple scenarios atleast)

2) Check if this is used properly MI_AB_ASYNC_Report

3) check SXI_CACHE for your BPM

4) try to reactivate your settings once again (preferrably by re-importing BPM in ID)

Hope this helps

Regards

Vishnu

[Former Member · Accepted solution]

>

> Hi
> 
>   Check the below
> 
> 1) if your RFC CC is set correctly & working fine (for other simple scenarios atleast)
The RFC CC is working fine with other scenarios.
> 2) Check if this is used properly MI_AB_ASYNC_Report 
The MI_AB_ASYNC_Report  is used as message container for the receive step and than as inputmessage for the transformation step.
> 3) check SXI_CACHE for your BPM
in SXI_CACHE the BPM the return Code is "0", so it seems ok. 
> 4) try to reactivate your settings once again (preferrably by re-importing BPM in ID)
i tried to rebuild the complete process, but with no change in the result.
> 
> Hope this helps
> 
> Regards
> Vishnu

It seems that the process isn't starting. In the sxmb_moni_bpe I can't see it.

[Former Member · Accepted solution]

Hi

I did not imagine that you have put screen shots, but before diving into that

some points to be considered

1) you say Async call - but your soap is set as BE, for async soap call you need to explicitly set QOS as EO in the url (&QualityOfService=ExactlyOnce)

2) how are handling the response from the RFC??

Regards

Vishnu

[Former Member · Accepted solution]

Hello Vishnu Kanth V,

thank you for your response.

to 1) ok, I've forgotten this parameter. Now I'm on work, that this parameter is set in future.

to 2) The response is mapped to nothing end the process shouldn't work with the response. The mapping step is only there, because it was an hint of an other thread I've read.

[Former Member · Accepted solution]

Hi,

thank you for your help. The parameter you posted was the key:

1) you say Async call - but your soap is set as BE, for async soap call you need to explicitly set QOS as EO in the url (&QualityOfService=ExactlyOnce)

Now the scenario is alright. Thanks.

[Former Member]

If a SYNC Receive by SOAP is there, then you have to set the correlation.

Other wise how the adapter knows which message send back is the response.

[Former Member]

Dirk,

It seems that you have determined your messages as Abstract Async, but you use a sync call. This will not work.

For the sync call you need to have a Abstrac Sync Interface Mapping.

greets