Calling RFC placed in PI from Portal

[Former Member]

Dear All,

We have a scenario where we have RFCs in ECC and it has to be called from Portal through PI.

Please suggest the possible and easiest ways.

Please note these RFC are already being called from Portal to ECC directly. So we need to change it be called from PI.

with regards,

Ravi Siddam

[Former Member]

It is not answered but i want to close this question.

[Former Member]

Hi Ravi,

You can do it in either any one of the below ways.

Use PI Http Url to push the data to PI and from there you can call RFC.

Plz check below link:

Or you can use Web sevice to push the data to PI and then you call RFC.

Plz check below link on Web service scenario:/people/shabarish.vijayakumar/blog/2007/11/07/walkthrough--soap-xi-rfcbapi

But before going for above solutions. Please have a looku2026 on below info and decide whether to go for it or not.

SAP NetWeaver PI 7.1 Usage Scenarios: When NOT to use SAP PI

User Interface Integration scenario: This is a common scenario faced by the development team u2013 the Webdynpro application is developed on the SAP J2EE application server integrated with the portal. The business data has to be fetched from the SAP ECC backend.

The User Interface would demand a quick response from the backend for fetching data and conducting the transaction. This is a synchronous scenario, and it would also be conducted with high usage every day. Hence, it is recommended to have a direct integration between the source application (WebDynpro application) and the target application (SAP ECC6) without using SAP PI. It is also recommended to expose the backend functionality as standard services.

For example, integration between SAP Portals (containing SAP BPM, SAP CAF, SAP WebDynpro) and SAP Suite (SAP ECC, SAP CRM, SAP SCM, SAP SRM etc.) should be conducted without the usage of SAP PI; the services should be exposed from the SAP suite as standards-compliant enterprise services.

Web Service interface of backend application: Many times, the target application in SAP/Microsoft/Java/Legacy is available as a standard web service. In such cases, the web service interface can be easily consumed in the source application. In such scenarios, SAP PI adds no value for transformation or backend integration.

In conclusion, SAP PI usage is usually not recommended for User facing applications where the backend application is available as a standard web service. SAP PI is almost always suitable for integration between backend applications not requiring human intervention.

[prateek]

Please note these RFC are already being called from Portal to ECC directly.

Then why are you including PI in between?

Regards,

Prateek

[Former Member]

Hello,

We have some restrictions relates to licensing/security of directly making calls to ECC because of this it is decided to call through PI.

Can we make RFC call from Portal (web Dynpro Java) to PI using RFC Sender CC etc, is there any way .....

regards,

Ravi Siddam

[abhay_rajhans2]

Hi Ravi,

One way is you can create a scenario in which do a soap scenario. Send soap request with the required data to PI from PI call the RFC and pass the required data to RFC. This way your RFC will be called in ECC.

[stefan_grube]

> Please note these RFC are already being called from Portal to ECC directly. So we need to change it be called from PI.

You should not change it. Portal shall always use direct calls without PI. Otherwise you might run in performance issues.