cancel
Showing results for 
Search instead for 
Did you mean: 

SAP PI BPM (IP) question help please

Former Member
0 Kudos

I have a questions for SAP PI/XI experts, can you please give me advice.

Source system is JMS system.

Target System is FTP Server.

ECC has 3 different RFC's

where PI gets item_no, category_no, purchase_order, and other 10 more fields from JMS source system, there are 3 different RFC's (client does not want to combine these 3 RFC's in to one module/call, they clearly indicated that they need three different calls to ECC)

PI has to do is

1) take item_no send to ECC to get back the valid_id (1st interface/call - RFC-1)

2) take this valid_id and send to same ECC to get back the category_no(2nd interface/call- RFC-2) ,

2) send these valid_id, category_no to same ECC to get back the purchase_order after creating it(3rd interface/call ECC-RFC- RFC-3)

3) send all these item_no,valid_id,category_no,purchase_order and other 10 fields to Target System as a File.

1) JMS > PI (BPM)<> ECC

2) PI (BPM)--> FTP

Can is possible to achieve this by using BPM(IP) we using PI7.1

Accepted Solutions (0)

Answers (4)

Answers (4)

baskar_gopalakrishnan2
Active Contributor
0 Kudos

Hi,

Though it's our job to convince the client to go for better design, some work areas we are not able to make it due to some constraints. I agree with Stefan.

One more suggestion: PI 7.1 does support RFC Lookup. So you can use RFC Lookup in the message mapping to do RFC lookup for the values. And send those information to the target system in file output. This way you can achieve all in one interface and without BPM. I did one interface for one lookup for RFC during mapping and it works great.

Here is the link...

/people/jin.shin/blog/2008/02/15/sap-pi-71-mapping-enhancements-series-graphical-support-for-jdbc-and-rfc-lookups

Thanks

Baskar

stefan_grube
Active Contributor
0 Kudos

> (client does not want to combine these 3 RFC's in to one module/call, they clearly indicated that they need three different calls to ECC)

In my opinion it is the duty of a PI expert to convince the customer to go to a good interface design.

You are the expert, therefore the customer hired you.

Instead of using RFC, create an pair of async interfaces. You create an inbound proxy. Inside this inside proxy ABAP code, you call the three RFCs and call the outbound proxy.

With this approach you avoid BPM and reduce PI development and monitoring to minimum. The creation of ABAP code inside ECC it is much less work compared of creating a BPM.

Former Member
0 Kudos

Hi Vasu,

Can we think of without BPM...

1) take item_no send to ECC to get back the valid_id (1st interface/call - RFC-1)

2) take this valid_id and send to same ECC to get back the category_no(2nd interface/call- RFC-2) ,

2) send these valid_id, category_no to same ECC to get back the purchase_order after creating it(3rd interface/call ECC-RFC- RFC-3)

3) send all these item_no,valid_id,category_no,purchase_order and other 10 fields to Target System as a File.

You can go for RFC Lookups and get the date from ECC. U have this in 7.0 using UDF and in 7.1 using the inbuilt functions.

As Abhishek also mentioned instead of using 3 RFC Lookups we can go for a single RFC lookup and this RFC lookup will have the final output purchase_order required.

So write a RFC in ECC side import as item_no and export as purchase_order. The RFC will have logic to find purchase_order from a given item_no and valid_id.

Babu

former_member200962
Active Contributor
0 Kudos
client does not want to combine these 3 RFC's in to one module/call, they clearly indicated that they need three different 
calls to ECC

Looking at your requirement, ideally, the RFCs should have been combined. It hardly makes any sense to keep on calling the same ECC system multiple times for data which can be sent in one go.

Can is possible to achieve this by using BPM(IP) we using PI7.1

Yes. It can also be done by BPM of PI7.0 or Pi7.11

Regards,

Abhishek.