Skip to Content
avatar image
Former Member

One adaptive RFC Model and Multi Backend System.

Hi All,

I am trying to fetch data from multi backend system by using an adaptive RFC model.

It is not tidy to create multi model for a RFC function to fetch data from multi SAP system, because we have dozens of SAP systems.(over 40)

So, I would like to switch to multiple SAP systems with an adaptive RFC model at runtime.

1 model(Same Function) -


> System A

-


> System B

-


> System C

Is there any sample or tutorial about this sort of senario?

Thanks in advance.

Message was edited by: JeongEog IM

Message was edited by: JeongEog IM

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    May 16, 2006 at 11:48 PM

    Hi Jeong,

    Its not possible to create one RFC model to different SAP backend systems, you can only connect one back end system for one rfc model.

    /Raj.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      In case of multiple R3 back end systems, you should not use adaptive RFC model. Instead you can go for SAP Enterprise Connectivity project and Java Bean model for the same.

      It gives you flexibility of model and lets you choose your R3 system in run time. SAP Connectivity creates the classes and interfaces of back end RFC/BAPIs and bypasses JCO destination. So you can provide your own R3 credentials in runtime.

      Please go through the tutorials in Help regarding SAP connectivity and Java Bean Model and try to bridge them.

      Abhijeet

      P.S. Reward points for useful answers!

  • avatar image
    Former Member
    May 17, 2006 at 04:48 AM
  • avatar image
    Former Member
    Jun 26, 2006 at 06:28 AM

    I would avoid using the Java connector in your Web Dynpro project if possible because you lose the benefits of creating model nodes and binding them directly to your UI elements.

    There is a nifty way of switching the backend system at runtime which doesn't require any special coding techniques, just the use of URL parameters. It also means you can maintain your backend system credentials in the content administrator where it should be maintained. Basically create a jCO destination in the Web Dynpro Content Administrator for each backend system where the name is the same as your default one, except add a 3 char ID suffix to the end which might represent the backend sys id. You can then pass this ID in as a URL parameter to use that particular back end system.

    Please visit this page for more information:

    http://help.sap.com/saphelp_nw2004s/helpdata/en/82/76a2406546ba15e10000000a1550b0/frameset.htm

    Cheers,

    Nick

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi, Nick

      Please tell me your knowledge.

      For example, there are two JCo destination named TESTMETA and TESTDATA.

      TESTMETA and TESTDATA are connected to the client 100 of backend ERP.

      WD4J application is made as the prerequisite with above JCo destinations.

      When I want to connect the client 200 of backend ERP,

      May I set up the JCo destination named TESTMETA200 and TESTDATA200, and enter the URL "http://<hostname>/<application name>?sap-wd-arfc-useSys=TESTDATA:200&sap-wd-arfc-useSys=TESTMETA:200"?

      Best Regards,

      Masahide Yano

  • avatar image
    Former Member
    Jul 17, 2009 at 06:40 AM

    Hi,

    U use SAP Enterprise Connectivity project and Java Bean model.

    Refer these links,

    Step by step procedure is there.

    http://help.sap.com/erp2005_ehp_04/helpdata/EN/18/13dfb557d33a4b99019667362c7233/frameset.htm

    http://help.sap.com/erp2005_ehp_04/helpdata/DE/c3/321b410210ef6fe10000000a1550b0/frameset.htm

    Regards,

    Sunaina Reddy t

    Add comment
    10|10000 characters needed characters exceeded