RFC in a WebDynpro application

[Former Member]

We are currently implementing a project for a client that has the WAS 7.0 installed together with BW server, while having R/3 4.6C in another machine.

We faced difficulty when come to the data binding for Webdynpro application that the common HR tables such as PA0015, PA0001 are not available in the BW server.

I am sure this should be a common issue and we want to avoid create the messy customised table structure.

I did some readings on the service call function but by using the wizard to create it, it doesn't recognize the function module and destination. I have already created the connection between the two servers in t-code sm59.

Thus, Is it possible that we do RFC for the data binding of Webdynpro application? And what should we aware of if we decide to go with this solution?

Any feedback and comment will be greatly appreciate!

Message was edited by:

Jin Jin Ooi

[Former Member]

Hi Jin Jin ...

when creating a service call with the wizard RFC is not possible. So the wizard itself only knows FMs on the current machine.

In this case you have to write the RFC call by hand.

Your problem with the missing data structures on the machine with WD4A is

something we faced in the beginning of our project. We did not want to import all

missing structures to the WAS 7.0 so we decided to test WebService calls to the

BAPIs on the R/3. This was kind of easy because the proxy generation

automatcally creates all necessary structures. But anyway, you still loose

translations, search helps and other cool stuff which is available if your WD4A

application is on the same machine as all the FMs and data structures you want

to use.

So depending on the amaount of data structures and function modules you want to

use you could consider to import the data structures to the WAS and write

Wrapper FMs which call the R3 FMs via RFC or to use web service calls.

Cheers,

Sascha

[Former Member]

Hi Sascha,

Thanks for the advice.

A few more questions to your reply,

How did you import the data structures to WAS?

What do you mean by wrapper FM calling the R3 FM via RFC?

Is it done by this way,

CALL FUNCTION 'Z...' DESTINATION 'DEV22'

<parameter list>

Thanks again.

[Former Member]

Hi Jin Jin.

We did not import the structures, we just considered it. After some evaluation the

decission was made to hold everything on one server so we have all structures

available. But you can import the structures via transports I guess. I just mentioned

it cause if you only need few structures this might be worth a try. But you have to

consider that if something changes regarding the structures on the R/3 you have

to update the structures on the WAS too.

With a wrapper function module i mean a function module that resists on your WAS which itself perform the call to the function module on the R3 via RFC. This would let you use the wizard to create a service call if you absolutely want to use it.

It would be a really nice feature if the wizard was RFC enabled and would import or generate everything you need to call remote fucntion modules.

Cheers,

Sascha