BPE_ADAPTER error

[Former Member]

Kindly help in this regards.. its a file to file Bpm collect message scenario

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

- <!-- Call Adapter

-->

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

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

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

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Message interface is not used by this process</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

[Former Member · Accepted solution]

Hi,

This is because of mismatch the message interface.Check the all Interface determination for Sender to BPM,Abstract message interfaces are added.

Regards,

Prakasu

[Former Member · Accepted solution]

can any one help me out wat the error is... i cross checked my

message interfaces and recevr and interface determination all are mentioned rite... could u please help out...

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

<SAP:MessageId>66CF66D6-077B-4ED2-0AC9-D44FEB6F67E9</SAP:MessageId>

<SAP:TimeSent>2009-03-12T11:55:35Z</SAP:TimeSent>

- <SAP:Sender>

<SAP:Service>BS_Bpm_file</SAP:Service>

<SAP:Interface namespace="http://capgemini/mumbai/upgrade">BpmPatternCollectIfToBeCollected</SAP:Interface>

</SAP:Sender>

- <SAP:Receiver>

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

<SAP:Service>BPMPatternCollectMessage</SAP:Service>

<SAP:Interface namespace="http://capgemini/mumbai/upgrade">BpmPatternCollectIfCollected</SAP:Interface>

<SAP:Mapping notRequired="X" />

</SAP:Receiver>

<SAP:Interface namespace="http://capgemini/mumbai/upgrade">BpmPatternCollectIfCollected</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:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

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

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

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Message interface is not used by this process</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

- <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="2009-03-12T11:55:35Z" wasRead="false">

<SAP:Engine type="AE">af.xi1.inbomsap11</SAP:Engine>

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

<SAP:MessageId>66CF66D6-077B-4ED2-0AC9-D44FEB6F67E9</SAP:MessageId>

<SAP:Info />

</SAP:Hop>

- <SAP:Hop timeStamp="2009-03-12T11:55:36Z" wasRead="false">

<SAP:Engine type="IS">is.00.inbomsap11</SAP:Engine>

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

<SAP:MessageId>66CF66D6-077B-4ED2-0AC9-D44FEB6F67E9</SAP:MessageId>

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

</SAP:Hop>

- <SAP:Hop timeStamp="2009-03-12T11:55:37Z" wasRead="false">

<SAP:Engine type="PE" />

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

<SAP:MessageId>66CF66D6-077B-4ED2-0AC9-D44FEB6F67E9</SAP:MessageId>

<SAP:Info />

</SAP:Hop>

</SAP:HopList>

[former_member200962 · Accepted solution]

Hi,

check the return code of your BPM in SXI_CACHE....it should be 0.

Also check for any error instances of your BPM in transaction SWWL....if there are any unwanted instances then Delete them.

Regards,

Abhishek.

[Former Member · Accepted solution]

Hi,

One more doubt when i delete the error workflow number and trigger my scenario will it be a new workflow number ...

and also at present there is a status message sent but when I send a stop message the status throws an error flag ... any solution

[Former Member]

Hi Robin

In integration Directory check your message interface is there in the receiver interfaces of your integration process.

Check return code for your BPM in transaction SXI_CACHE. If it is not '0' , Re-Activate your Integration process.

Hope it helps..

Thanks,

Kumar.

[Former Member]

Hi,

doubt when i delete the error workflow number in SWWL transaction and trigger my scenario will it be a new workflow number ...

[former_member200962]

Hi,

This error is due to the mismatch between the Interfaces used in design (BPM) and in Configuration (ID)

Make sure that you are using the required Message Interface at the desired place (receiver determination, interface determination etc)...

The message that the BPM is receiving is not configured for use in the BPM....

Also check the return code of your BPM in SXI_CACHE....it should be 0.

Regards,

Abhishek.