File to File BPM scenario

[Former Member]

Hi Experts,

I am getting the below error for File to File BPM scenario.

<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 is not used by any processes</SAP:Stack>

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

</SAP:Error>

Could you please tell me, why I am getting this error.

Regards

Sara

[Former Member · Accepted solution]

Hi,

In MONI click on PE (you will find this when you scroll towards right). Now navigate like this Goto ---> Graphical workflow log. Check in which step there is a error (it will be in red colour lines).

Regards,

Sarvesh

[Former Member · Accepted solution]

Hi Vasanth,

The return code is 0 in SXI_CACHE.

Edited by: Sara D on Mar 19, 2008 1:03 PM

[Former Member · Accepted solution]

Hi Sara,

Have you checked your BPM in IR -> IP using F7..

Check the configuration in ID once again..

Thanks,

vasanth.

[Former Member · Accepted solution]

Please find the below IR objects which I hv created for File to File scenario

IR Objects:

-

---

Data Type

1. DT_File (FName, LName)

Message Type

1. MT_File

Message Interface

1. MI_Outbound_Async (MT_File, Outbound,Async)

2. MI_Inbound_Async (MT_File, Ibound,Async)

3. MI_Abs_Async (MT_File, Abstract,Async)

Message Mapping

1. MM_File (MT_File to MT_File)

Interface Mapping

1. Soruce Interface : MI_Outbound_Async

2. Target Interface : MI_Abs_Async

3. Mapping: MM_File

[Former Member · Accepted solution]

Hi Sara,

just explain your scenario what you are trying to do.........i think you just want to take a source file in BPM and output it by BPM.. if this is the case, then why are you using BPM for it because then there is no need for BPM for it.........

explain your bpm steps of your integration process...........then i may be able to help you in your this scenario.........

Regards,

Rajeev Gupta

[Former Member · Accepted solution]

Hi Sara,

Refer this blog

/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm

Hope it helps..

Thanks,

vasanth

[Former Member · Accepted solution]

IR IP

-

---

FileTOFile_BPM

1. Receive Step (Used MI_Abs_Async)

2. Send Step (Used MI_Abs_Async)

Please find the below configurations which I hv done in ID

IP in ID

BPM_FileToFile

Business Service & CC

1. SENDER_SERVICE

CC: File_Sender_BPM

2. RECEIVER_SERVICE

CC:File_Receiver_BPM

3. Receiver Determination:

a) Sender Service : SENDER_SERVICE

Sender Interface : MI_Outbound_Async

Receiver Service : BPM_FileToFile

Receiver Interface : MI_Abs_Async

Mapping : IM_File

b) Sender Service : BPM_FileToFile

Sender Interface : MI_Abs_Async

Receiver Service : RECEIVER_SERVICE

Receiver Interface : MI_Inbound_Async

Receiver Agreement : File_receiver_BPM

[Former Member · Accepted solution]

Hi

Please refer to this link and do the scenario in this way.

i think this will solve your problem.

please let me know if u face any problem.

/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit

Thanks

Rinku

[Former Member · Accepted solution]

Hi Sara,

ok now tell me when you run your scenario, then are getting the above error in the first msg or second msg..........go to PE icon, click it and see in graphical workflow log what happened..............run SXI_CACHE and do a complete cache refresh........re-run your scenario and let me know what happens.

Regards,

Rajeev Gupta

[justin_santhanam]

Sara,

Can u check whether the interface used in Sender agreement is the same as the interface used in Receiver Determination, whose receiver is BPM?

raj.

[Former Member]

Yes, Raj. Both are same.

[Former Member]

Hi SARA,

Go to Transaction: SXI_CACHE and check the return code for your intergration process, it must be 0.

Might solve your issue

Thanks,

vasanth.

Edited by: Vasanth Kumar.S on Mar 19, 2008 5:21 PM