BAPI Synchronous Config

[Former Member]

when setting up the config for an RFC BAPI synchronous call, it appears that i must have a BAPI on my client side so i can configure the distribution model (BD64) and BAPI destination (BD97) accordingly. Now here's the odd thing. the whole point of this is to call a remote BAPI synchronously. But to set up the config, i must have the BAPI setup on the client, from which i would never call it. ok, the BAPI's method can be any old function module, but is this really how it is done? or am i missing something obvious?

thanks

[christian_wohlfahrt]

Hi Glen,

to be able to understand your problem:

In which way do you want to call the BAPI?

I would expect:

You have a Z-report, there you implement BAPI call with destination [like defined in BD97].

There is no distribution model.

If you have a distribution model, I expect to distribute IDOCs, which are booked locally (e.g. with BAPI).

Maybe I don't know all possibilities of different distribution models, but please explain your situation more detailed.

Regards,

Christian

[Former Member]

i will call the remote bapi's methods (implemented by the RFC FM on the target system - server) in a bespoke porgram.

in the source system - client, i will use the function module ALE_SYNC_BAPI_GET_RECEIVER to return the rfc destination from BD97 and pass over eg. CALL FUNCTION ZBAPI_MYFUNCTION destination l_var_dest...

should i wish to, i could also call ALE_BAPI_GET_FILTEROBJECTS to interogate the dist mod - BD64, for any filters.

however, i think ... to enter the object and method in either BD64 or BD97, i must have to create the object's method's bapi in my source system - client. to do this, i have to actually create a function module, release it, create the method for my object, use the function module i have just created, make it an API type in the method, then release it in the method.

this is all well and good it you want to use any functionality implemented by a BAPI on the system the BAPI is created on, however, i am trying to call a remote BAPI.

the BAPI implementation on the client, has nothing to do with the BAPI call on the server. it does not even have to be called the same, nor require the same interface. it purely exists for the population of BD64 and BD97.

i hope what i have written is getting nearer to the point.

cheers christian

glen