2 systems sending data to one system

[Former Member]

Hi,

i have the following scenario:

sending R3 (i will call it A)

sending R3 (i will call it B)

recieving R3 (i will call it C)

now a job triggers an RFC in sys A to XI ,

then i need to call RFC in sys B map it together and send it to sys C

any suggestions? will the call to sys B needs to be Synch call? or a synch? thanks

[bhavesh_kantilal · Accepted solution]

Hi Udi,

On an afterthought, I would also suggest that you go through these links on SAP help for any info on how to configure your BPM,

http://help.sap.com/saphelp_nw04/helpdata/en/43/65d4dab39b0398e10000000a1553f6/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/62/dcef46dae42142911c8f14ca7a7c39/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/83/d2a84028c9e469e10000000a1550b0/content.htm

Regards,

Bhavesh

[Former Member · Accepted solution]

i am usin RFC for system A + B.

do i have to define them as Abstract ?

In the container only the Asynch interface opens for me

Why don't i get the synch interface also?

[Former Member · Accepted solution]

Udi,

BPM never deals with Synchronous interfaces. Although you might have a Synch interface, you will have to define a Abstract Asynch interface and use the same in your BPM.

Regards,

Ravi

[bhavesh_kantilal · Accepted solution]

Hi Udi,

Your BPM can interact only with abstract interfaces and so, you will have to define abstarct interfaces.

Regards,

Bhavesh

Message was edited by: Bhavesh Kantilal

[Former Member · Accepted solution]

I have defined a reciever step - Asynch

I have defined a send step - synch.

In the configuration of the send step i have defind the synch abs interface

in the target and source i ahve defined the abstract asynch req + res

but i get an error:

Message to be sent Req and synchronous interface CUSTOMERS_TO_XI_abs are not of the same type

why ?

[former_member187339 · Accepted solution]

Hi Udi,

In the sync send step:

Synchronous interface : Abstract Sync interface for RFC to B.

Source : input to RFC (on B)

Target : output from RFC (on B)

Let SYNC_RFC be the Abstract Sync interface. Check the Output Message is having the same MT as that given in the Source(given above) and the Input Message is having the same MT as that in Target (above).

Hope you got it...

Else:

Can you give the name of the value given in these fields.

Synchronous interface ?

Source ?

Target ?

& Output Message & Input Message for the above Abstarct Sync Interface.

Regards

Suraj

[Former Member · Accepted solution]

Thanks S.R

Can anyone tell me how do i build the configuration scenario ?

I get an error when trying to do the send step - system error

[bhavesh_kantilal · Accepted solution]

Hi Udi,

What adpater are you sing to send this information. Can you check the staus of your error in the RWB under Adapter Monitoring?

Regards,

Bhavesh

[Former Member · Accepted solution]

using RFC

In BPM monitoring it says:

An empty container element was specified when sending

[former_member187339 · Accepted solution]

Hi Udi,

Hope you are using these steps in your BPM.

1) Receive (from A)

2) Sync send to B.

3) send to C

Now in which step the BPM fails? You can go to the graphical log (SXMB_MONI--> PE --> Graphics) and see that step.

Regards

Suraj

[Former Member · Accepted solution]

Hi S.R,

I have a reciever step - Asynch then

Send step - Synch.

It fails in the send step

the message i see in the BPE is :

An empty container element was specified when send

do i have to use the optoin vitual sender in the sender agreement?

can you tell me which steps i need to do in the configuration?

[former_member187339 · Accepted solution]

Hi Udi,

>>do i have to use the optoin vitual sender in the sender agreement

No.

1)Create a sender agreement (Source service A, Message Interface RFC of A).

2)Receiver Determination

a) From A to BPM

b) From BPM to B

c) From BPM to C

& corresponding Interface Determination...

3) Receiver Agreement

a) From BPM to RFC B (receiver communication channel for triggering the Idoc in B).

b) From BPM to RFC C (receiver communication channel for triggering the Idoc in C).

Regards

Suraj

[Former Member · Accepted solution]

did this and still the same error...

prehaps something is wrong in my BPM configuration?

what do i need to provide in the recieve asynch and send sync properties?

[former_member187339 · Accepted solution]

Lets go step by step..

<b>RFC A</b>

Request = A

Response = A.response

<b>RFC B</b>

Request = B

Response = B.response

<b>RFC C</b>

Request = C

Response = C.response

1) Receive Step

Message = Abstract Message Interface containing A as MT

2) Sync Send

Synchronous interface = Abstract Message Interface containing A as input and B.response as output

Request Message = A (I think it should be equal to B)

Response Message = Abstract Message Interface containing B.response as MT

3) Transform

A, B.response ===> C

3) Async Send step

Message = Abstract Message Interface containing C.

Regards

Suraj

[Former Member · Accepted solution]

Thanks a lot !!!

i finally solved it!!!

[former_member187339]

Hi,

Use BPM.

1) RFC from A will trigger the BPM.

2) Receive step

3) Send step(sync) to call RFC in B

4) Transform step map response from B and A's data to C

5) Send step send the output to C.

Hope this will be clear.

Regards

Suraj

[Former Member]

Thanks you both!

Thing is i am some errors while trying to implement it with BPM

any example availabale for the BPM configuration?

[bhavesh_kantilal]

Hi Udi,

Think these 2 blogs can help you to configure a BPM using RFC synchronous call.

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

https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]

Regards,

Bhavesh

[udo_martens]

Hi Udi,

i see two possibilities:

with BPM:

A->asynchr->BP

BP<->synchr<->B

BP->asynchr->C

or without BPM:

A<->synchr<->B

A->asynchr->C

(The triggert programm calls first B synchr and next asynchron C)

If you are on WAS >= 6.20 proxy communication would be an alternative with an inbound (server) proxy on B which is calling system C.

Regards,

Udo