Best adapter inbound scenario to SAP ECC

[rhviana]

Hi guys,

I´ve been looking a lot of discussions about this theme into these links below:

http://scn.sap.com/message/9978635

http://simonlesflex.wordpress.com/2011/03/23/sap-pi-choose-the-right-adapter-to-integrate-with-sap-s...

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0e7ae66-be6d-2a10-d385-92e6e67de...

My current project, the Archtecture Team defines the SAP PI 7.1 for SOA Integrations, it´s means that I have adapters AAE - abap proxy and Idoc. In my case Idoc it´s out of process.

Thinking into steps RFC AAE (less saves into data base - Monitoring RWB) look like more better them proxy (More saves into data base monitoring RWB and IE)

Proxy steps:

1 ) Load

2 ) Transform

3 ) Delivery to BAPI

4 ) Execute bapi

6 ) Return data

RFC AAE (Expose BAPI from ECC into SAP PI)

1 ) Load

2 ) Execute bapi

3 ) Return data

The scenario are some interfaces to create vendor/material, update vendor/material , list vendor/material and others stuffs.

We are thinking only about RFC AAE and abap proxy. Which one it´s the best ?

I´d like to know the experts opnions.

Thanks

Kind regards,

[Former Member · Accepted solution]

Hi Ricardo,

I'm confused a little with why you are evaluating RFC vs Proxy for SOA. You mentioned:

My current project, the Archtecture Team defines the SAP PI 7.1 for SOA Integrations,

I think Proxies should be the first option when considering SOA. Have you perhaps investigated SAP Enterprise Services offerings for vendors & materials? I was just trying to understand what the architectural plan was to realize SOA if RFC's are used.

In your scenario, you could realize SOA with one Service Interface and multiple operations:

- e.g. Create, update, list, delete Vendors - or - Materials on one SI.

You could even use underlying (already shipped) SAP Enterprise Services so you don't need to write new code. You could just enhance the enterprise services if you have additional requirements.

Regards, Trevor

[rhviana · Accepted solution]

Trevor,

I said that because the landscape consist of with SAP PI 7.0 - for (NF-e - SOA Integration) especific for Brazil and other to integrations soa without NF-e.

That´s clear for me.

Thanks for all aswers.

Kind regards,

Ricardo Viana.

[rajasekhar_reddy14]

Hi ,

ABAP Proxy always right idea to implement in PI integration point of view, however RFC AAE also good idea to implement.

If you found standard function modules , then better to gor RFC AAE because it avoids lot of customization(proxy developments).

If your team going to develop customized BAPIs then for Proxy.

Both Proxy and RFC support sync communication but RFC monitoring at ECC side always requires skill.

[nabendu_sen]

Hi Ricardo,

If you are going to use Standard BAPI, go for RFC_AAE. If you are going to write custom BAPI with too many validations, go for direct Outbound processing, Proxy.

[rhviana]

Thanks for answer until now.

I found a bapi BAPI_MATERIAL_SAVEDATA for create/edit - Probably will develop that with RFC AAE.

But for Vendor Master I didn´t find BAPI, maybe I will go for abap proxy.

Just aditional information a full interface scenario are Inbound Syncrono.

Let see if someone else has more option abou theme.

See ya

[former_member201264]

Hi Ricardo,

I aggree with Raja and Sen, in addition to that you performance(when you process huge volume of data) wise Proxy is better than RFC and you can use attachments also with proxy.

Regards,

Sreeni.