BPM : Message interface is not used by this process

[Former Member]

Hi,

In BPM : to pass the message facing error as below.

Messages not reflecting in BPM monitor.

I have configured Recveiver - transformation - sender in BPM.

In recvier in BPM is configured with Abstract Type as same in the message mapping.

Is there any thing i am missing?

<?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>

I have refered links but not able to get the clue for this error as its from the Call adapter.

Regards,

[Former Member]

Hi,

Thanks for the input.

I using PI 7.01.

ID reported and checked still the same.

I create new setup and tested but no improvement.

IP no syntax error.

How to check ESR in PI 7.0?

Regards,

[baskar_gopalakrishnan2]

ESR is available in PI 7.1 and above. There is only IR in 7.0. Dont worry about it.

You specified invalid message type at the receiver side. This must match with the one specified in interface mapping defined within integration directory.

[Former Member]

Hi,

Interface mapping and messages are same, find the design below.

Is it ok?

Message Interface :

1. MIIASY - Recevier(MTR_recevier)

2. MIOASY_Sender - Sender (MTS_sender)

3. MIAASY - Abstract (MTS_sender)

Message mapping :

1. MM_S_ABS - Sender to Abstract

2. MM_ABS_ABS - Abstract to Abstract

Interface mapping :

1. IM_Sender - (MM_S_ABS)

2. IM_ABS - (MM_ABS_ABS)

Integration Process :

Container:

rec Abstract Interface MIAASY

send Abstract Interface MIAASY

Receiver (send)  Transformation (IM_ABS)  sender (rec)

Regards,

[Former Member]

Hi,

Receiver (send)  Transformation (IM_ABS)  sender (rec)

your esr and IP design looks like worng in some steps.

please go through below steps , you can achieve you requirement

Message Interface :

1. MIIASY - Recevier(MTR_recevier)

2. MIOASY_Sender - Sender (MTS_sender)

3. MIAASY - Abstract (MTS_sender)

4. MIIASY - Abstract (MTR_recevier)

Message mapping :

1. MM : (MTS_sender and MTR_recevier)

Interface mapping :

1. IM : MIAASY - Abstract (MTS_sender)

MIIASY - Abstract (MTR_recevier)

Container:

rec -- MIAASY - Abstract

send-- MIIASY - Abstract

Receiver (rec)  Transformation (IM)  sender (send)

regards,

ganesh.

[Former Member]

Hi,

Thanks for the reply,

Receiver (send)  Transformation (IM_ABS)  sender (rec)

send and rec are naming conversion of the same message interface.

I tested even chaning them still its same

Regards,

[Former Member]

Hi,

Receiver (send)  Transformation (IM_ABS)  sender (rec)

send and rec are naming conversion of the same message interface.

in receive step you have to specify in service interface abstarct _source (that is which was you created service interface with message type of source).

In transformation you have to specify the interface mapping (sorce and target message types also)

in send step you have to specify in service interface abstarct _target (that is which was you created service interface with message type of target).

i think you have source and target message type, that are specified in service interfaces (Outbound for source and Inbound for target). same as you have create service interface Abstract also. that abstract service interfaces provided inti interface mapping.

recive(rec) > Transformation(IM)> Send(send)

also check in sxi_cache your IP inital value is 0 or not.

regards,

ganesh.

[Former Member]

Hi,

I just saw your IP design and from this I can see that you have message mapping between Sender(as in Outbound interface MIOASY) and abstract interface (as in MIAASY) and then in that you have used transformation step to utilise Interface mapping which is between same abstract interface which is not required at all as message type for both the interfaces is same. For me, what your configuration would be is

1. Sender agreement to fetch the message from outbound interface(MIOASY) utilising communication channel with whatever adapter you have used

2. Receiver Determination with Sender and sender interface as MIOASY while receiver as IP(Integration process)

3. Interface determination between

a. Sender and Outbound interface and Abstract interface with interface mapping IM_Sender

b. IP as sender with abstract interface MIAASY and receiver interface MIIASY with no interface mapping being used as it must be of same type as receiver interface is

4. Receiver agreement with MIIASY being used as receiver interface and communication channel utlililsed to convert it into receiver format.

If I am assuming it correct then if you see then inside BPM we are not using receiver interface MIIASY which is why I feel this error is coming.

However, if you design it something like this then I feel the error would get resolved

Design

1. Make one abstract interface (MIAASY_Sen) of same type as sender, and create another abstract interface (MIAASY_Rec) of same type as your receiver message type

2. Create message mapping between sender message type and receiver message type, Interface mapping IM_ABS - (MM_ABS_ABS) between sender abstract interface (MIAASY_Sen) and receiver abstract interface (MIAASY_Rec)

3. BPM should be something like this

• Container:*

rec Abstract Interface MIAASY_Sen

send Abstract Interface MIAASY_Rec

Receiver (rec) - Transformation (IM_ABS) - sender (send)

Configuration

1. Sender agreement to fetch the message from outbound interface(MIOASY) utilising communication channel with whatever adapter you have used

2. Receiver Determination with Sender and sender interface as MIOASY while receiver as IP(Integration process)

3. Interface determination between

a. Sender,Outbound interface MIOASY and Abstract interface MIAASY_Sen with no interface mapping

b. IP as sender with abstract interface MIAASY_Rec and receiver interface MIIASY with no interface mapping being used as it is of same type as receiver interface is

4. Receiver agreement with MIIASY being used as receiver interface and communication channel utlililsed to convert it into receiver format.

Let me know if it works.

Regards,

Amit

[Former Member]

HI ,

check your cofiguration whatever you created in esr and id.

Please refer this below blog :

thanks,

[Former Member]

Hi,

In ID Delete the old IP and activate it. Then reimport and try again in the ID.

Hope in the IP, there is no syntax error (F7 Check).

check in sxi_cache your IP inital value is 0 or not.

regards,

ganesh.