Skip to Content

RFC target sys

Hi WD gurus,

Does anybody know how we specify an RFC target sys?

since it's not an import or export parameter neither

a table, How we reference this after importing the model through RFC adaptive model?

many thanks for your time and patience.


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Posted on Feb 02, 2005 at 11:35 PM

    Hi Raju,

    many thanks for your response.

    May I elaborate a little more about my real problem:

    I am working on a WD front end for a transaction for the media market.

    This particular transaction is called, passing a string to the RFC Target Sys

    (if you go to transaction SE37, enter a bapi/rfc and execute it, you'll see

    that I can either specify a logical system or an application (this is the case).

    Actually this string is used to identify a machine in the intranet where an

    client app. will be started.

    Or when I write an ABAP code it would look like this


    a little different from WSD (an usual R/3 logical system)

    If you go to the content admin and try to create a new JCO destination, you'll see

    that I will have to opt between creating a modeldata destination or a metadata


    let's say for example "PC2020.SAPCLNT" (I created as a modeldata destination), if

    you try to create the metadata destination, using the same name, you'll get

    Please choose another name for the new JCo destination. The defined name

    'PC2020.SAPCLNT' is used in the SLD.

    So, I can't create a destination when the target sys is an application.

    Now hopefully, has anyone went through this situation?



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      From my understanding, you are calling a BAPI which in turn talks to an external system. Are you planning to get the output of the external application within WD app? Is the external application returns the output to BAPI?

      I never worked in such a scenario, but I assume there are the following possibilities.

      1) Either you are talking to an R/3 system through BAPI or directly to the application.

      2) If you are talking through a BAPI, then you may want to write a wrapper RFC to get the required results from the external application and passing the output to WD application.

      3) You may want to write a web service to talk to the external application and get the required results.

      4) Also, if you know what information is passed through BAPI to external application, is it possible to get those output parameters to WD application by wrapping the BAPI and WD application directly calls the application .

      I assume in your case, last point may work as you can get the string(ouput) from BAPI into a WD app and then you want to write some methods or calling a web service you will fire the actions to call the external application and get the results.

      Regarding model data and meta data destinations, use prefixes to distinguish both differently so you that you would not get the errors as all JCo destinations needs to be unique




  • author's profile photo Former Member
    Former Member
    Posted on Feb 02, 2005 at 08:13 AM


    The target systems are maintained through JCo.

    1) Go to http://<server>:50000/index.html and click on Web Dynpro

    2) From there click on content administrator.

    3) From local -> click on the deployed applicaion . On right side you will see Jco connections and click on Create and maintain the parameters including which client you want to talk to.

    There is a document which explains how to set SLD and maintain JCO. Have a search on this forum / SAP help.

    If you could not get it , let us know.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 03, 2005 at 01:54 PM

    Raju and Pran,

    many thanks for your helpful insights.

    My first attempt in solving this problem was using a wrapper RFM that has a parameter that

    receives what would be passed in SE37 as the RFC target sys, but this solution worked out partially,

    the DLL in the client machine (specified in the RFC target sys) acknowledges

    that it should start up the advertisement editor (ad maker),

    and the original bapi (inside the wrapper bapi) ceases working

    (it sort of work asynchronously).

    Actually what happens when you execute the original bapi using se37 is that,

    the client machine starts up the ad maker, and when user closes it, it generates

    the ad, and returns a ad number back to the bapi. The bapi in this case works synchronously,

    waiting for the ad number.

    I'm actually developing a simple app, using jco, to see if I can call directly the

    original bapi, passing the rfc target sys as a property or an attribute of the connection.

    Unfortunately, couldn't find any sample using a target sys that isn't an usual

    logical system.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Kentaro

      Since you face the problem even if you execute from SE37, I suggest you look into how the internal BAPI is called , maybe you are not passing the right data from outer to inner which will probably cause your remote program to respond but not necessarily with the right return results or maybe also causing some abort which results in the call being terminated.(This might be giving you the asynchronous effect)

      Would like to know how you solved it ,when you will have solved it.



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.