Error in BPM: FIle to RFC

[Former Member]

Hi friends,

I am working on File --> RFC ---> File Scenario using BPM ...

Here I am getting system error in BPM and showing broken red brick in workflow at sender1 ...

I have given like this...

Start --> Receiver ->sender1>Sender2 ---> Stop.

I have given properties... for each

C2 = Abstractinterface FIleResponse_Abs

Recevier

_______

1)Step Name = Receiver

Message = C1 (I defiend in container Category =Abstact interface type = FileRequest_Abs)

Start process = (Selected)

Mode = Asynchronous

2)Sender1

Step name = Sender1

Mode =Synchronous

Synchronous Interface = FileRequest_AI

Request Message= C1

Response Message=C2

3)Sender2

Step Name =Send2

Mode = Asynchronous

Message = C2

After Configartion,I have placed the sender sample XML in Server ...it is picking up properly.But

it showing error while it was executing in the BPM. Please suggest me what i have to do.

If you didnt understand I ll give some more details.

Pls help me in this regard.

With Regards,

Raju.

[Shabarish_Nair]

Ref: that

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

the configuration steps will be;

1. 1 Sender agreement - Sender File CC

2. 2 Receiver Agreements - Recv. RFC CC and Recv. File CC

3. 3 Receiver Determination - File o/b -> BPM, BPM -> R3 (RFC) and BPM -> File (I/b)

4. Corresponding Interf. Detr. for the above Recv. determinations

Is this of help ?

[Former Member]

Hi Raju,

check if you are getting response back from the system where you are making the RFC call.

Regards

Pushkar

[Former Member]

FileRFC_Send2 Sender Adapter v2630 for Party '', Service 'sap1user13':

Configured at 2007-06-19 13:25:11 EDT

History:

- 2007-06-20 08:36:00 EDT: Retry interval started. Length: 20.000 s

- 2007-06-20 08:36:00 EDT: Error: No suitable sender agreement found

- 2007-06-20 08:35:40 EDT: Error: No suitable sender agreement found

- 2007-06-20 08:35:20 EDT: Error: No suitable sender agreement found

- 2007-06-20 08:35:00 EDT: Error: No suitable sender agreement found

[Shabarish_Nair]

<i>No suitable sender agreement found</i>

>>

note that you will need 2 Sender Agreements.

1. For File - Sender File CC and Outbound Interface for File

2. For the RFC call - Sender RFC CC and imported RFC as the interface

[Former Member]

Hi shabarish ,

WEhy we have to use two sender Agreements here.Could you pls tell me ...

As there is only one Physical System as sender.

[justin_santhanam]

Raju,

First sender agreement is for File to BPM. The second sender agreement is for BPM to R/3 (For RFC request).

Best regards,

raj

[Shabarish_Nair]

Sorry correction !!!!

well in the sync. send step for the RFC, you need a communication channel to call the R3. In that case you will need to have a Receiver RFC CC.

So that means 2 Receiver agreement.. sorry for the confusion !!!!

Message was edited by:

Shabarish Vijayakumar

[Former Member]

Hi Pushkar Anand,

Could you tell me how to check whether we are getting back response when we make a call to RFC.

[justin_santhanam]

Raju,

Can u tell what the error description u get. Coz it could be easy to analyze and suggest further.

Best regards,

raj.

[Former Member]

I am getting error in Integration Engine.....

Attribute Value

Engine Integration Engine

Status System Error

Repeatable No

Cancelable No

Start 20.06.2007 06:25:22

End 20.06.2007 06:25:22

Sender Party

Sender Service BPM_FILE_RFC_SAGAR

Sender Interface http://File2RFC_Syn

FileRequest_AI

Receiver Party

Receiver Service ECCIDOC800

Receiver Interface urn:sap-com:document:sap:rfc:functions

BAPI_SALESORDER_GETLIST

Quality of Service Best Effort

Error Category

Error Code

Message 9BA7365DDBC0FE49B9F512F7308DDA53

Reference

[Shabarish_Nair]

/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit - base that as a reference.

I think this is exactly what you are trying to do.

[Former Member]

Hi ,

Me too followed the same blog...

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

could you please give me details how to design the BPM and give their properties.