Adaptive RFC Calls

Hi everybody,
From the tutorial I know how to populate a table from an RFC call by using 'create binding' from the context menu of the table. I want to know how I can output data from a RFC without having an input field and search button. So as soon as I launch the Dynpro app there is some data in the table from the backend.
Thanks.
MK

You would put your call to the BAPI in the  wdDoInit method of the controller.
Here is some code from an application I did where there is no input parameter and the data is displayed in the application right away.
  public void wdDoInit()
    //@@begin wdDoInit()
//       Bind to the context
          Z_Ep_Get_Ytd_Sales_Input input = new Z_Ep_Get_Ytd_Sales_Input();
          wdContext.nodeZ_EP_GET_YTD_SALES().bind(input);
          try {
//      calls remote function module Z_EP_GET_YTD_SALES
               wdContext
                    .currentZ_EP_GET_YTD_SALESElement()
                    .modelObject()
                    .execute();
          } catch (Exception ex) {
//       If an exception is thrown, then the stack trace will be printed  
               ex.printStackTrace();
          wdContext.nodeOutput().invalidate();
    //@@end
Regards,
Rich Heilman

Similar Messages

  • Looking for a beginner guide - Adaptive RFC  call BAPI  in Web Dynpro Java

    Hi,
    im new in SAP Developeing. I developed some basic web Dynpro applications (after some tutorials) and they are all working.
    Now i want to build an Web Dynpro application with an adaptive RFC Model.
    I already imported the adaptive RFC Modell with a function Model (BAPI Z_...) from the R3 System successfully.
    But if i deploy the application i will get following error:
    com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type extern:mypackages.com.types.BapiModel:mypackages.com.types.Zmbs_Bapi_Dispo_Orderdata could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:305)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:234)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:449)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:387)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:416)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:83)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:125)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:121)
         at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:215)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
         at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:377)
         at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:322)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:181)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getStructure(DdBroker.java:180)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:303)
         ... 49 more
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:152)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:178)
         at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:62)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
         ... 59 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load client to connect to SLD. Please check your SLD connection settings using the Visual Admin.
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory$1.run(SystemLandscapeFactory.java:754)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getClient(SystemLandscapeFactory.java:747)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.readJCODestinationFromSLD(JCOClientConnection.java:511)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:439)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:233)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:218)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150)
         ... 62 more
    Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Failed to create CIM client. Check via 'Visual Administrator' tool if the secure store is operational.
         at com.sap.sldserv.SldApplicationService.getCimClient(SldApplicationService.java:117)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory$1.run(SystemLandscapeFactory.java:751)
         ... 70 more
    Caused by: com.sap.lcr.api.cimclient.CIMClientException: java.net.MalformedURLException: URL must have a host part
         at com.sap.lcr.api.cimclient.ClientFactory.createConnection(ClientFactory.java:466)
         at com.sap.lcr.api.cimclient.ClientFactory.createClientImpl(ClientFactory.java:413)
         at com.sap.lcr.api.cimclient.ClientFactory.createClient(ClientFactory.java:363)
         at com.sap.sldserv.SldApplicationService.getCimClient(SldApplicationService.java:113)
         ... 71 more
    ........Looks like a have a Problem with JCO.
    Is there a good guide, which explains the Basic steps in developeing Web dynpro applications and BAPI ?!

    thank you guys for all the answers.I have to read all the documentations.
    to my szenario:
    I installed on my notebook the Trial Versions of:
    SAP NetWeaver Application Server 7.00/Java AS 7.00
    SAP NetWeaver Developer Studio Version: 7.0.14
    All my basic Web Dynpro Applications in Java are running (even with Adobe Interactive Forms) on the local NetWeaver Trail- Web AS Trail perfectly.
    Now i want to connect per RFC to another SAPERP Server, which is in the intranet.
    I did the whole RFC tutorial with the flights -
    http://help.sap.com/saphelp_nw04/helpdata/en/c3/76b45d9688e04abe1a1070410ddc1e/content.htm (also with the JCO codeing etc)
    so my web dynpro application should work.
    I think I have to configure - like ramesh said something on the NetWeaver Trail.
    So what do i need and configure excactly on my Netweaver Trial to work with RFC - to call the BAPIS in the other System?
    - SLD ? JCO ?
    If i over Web Dynpro - Content Administrator - >
    it says "Connection to System Landscape Directory (SLD) could not be opended successfully." and all the buttons
    create Jco destinations etc. are greyed out.
    I didn´t configured the SLD and JCO in the Netweaver yet.

  • SAP adapter giving the merged result set (First RFC call data + Second RFC call data) for second RFC call

    I have a WCF Adapter service to call a SAP RFC. When I call the RFC first time, it gives me correct no of result set but when I call this RFC second time immediately after first call, it gives me merged result set (First Result set + Second Result Set).
    e.g. We have a RFC which receives vendor number and blank object of result set as parameter and gives back the list of purchase orders as Response in object of result set for that vendor.
    Suppose, we have a vendor "a" and vendor "b". For vendor "a" there are 5 purchase orders and for vendor "b", we have 4 purchase orders in SAP. When I call the WCF adapter service for this RFC for vendor "a",
    it gives me 5 purchase orders. Immediately after first call, when I call WCF service for vendor "b", it gives me 9 (5+4) purchase order records which is wrong.
    In brief, one RFC call is affected by its previous call.
    For each new WCF request, a new object of result set is created, connection is opened, rfc is executed and connection is closed.
    Can anybody have any idea on this?
    Thanks.
    Thanks, Nishant Gupta

    Hi,
    Please refer to the document
    http://seroter.wordpress.com/biztalk-and-wcf-part-vii-about-the-biztalk-adapter-pack/

  • Why we call adaptive RFC in webdynpro java..

    Hi,
    I want to know why we call adaptive RFC connection in webdynpro java whenever we import new rfc in our  java web dynpro project.  why name  ADAPTIVE RFC  is used
    if we  make any structure changes in the model which we imported in web dynpro project , like adding a new field, or changing the length/datatype of the existing field, then we always have to reimport the model in our webdynpro project so why adaptive name used. wats especial in the word ADAPTIVE RFC

    Hi Rahul,
    please read the guide:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10465350-b4f5-2910-61ba-a58282b3b6df?quicklink=index&overridelayout=true
    Best Regards,
    Ervin

  • RFC calls with SAP JCO and IBM resource adapter for SAP - basic tuning

    Hi experts,
    we are working on a java portal connected to a backend system SAP by calling RFCs.
    On our first integration tests, it appears to be quite slow fetching data from SAP by calling the remote functions from the custom portal. We are using SAP JCo 3.0.6 and IBM resource adapter for SAP 7.0.0.3 to integrate SAP with our portal.
    Is there any basic tuning to achieve to improve performances or any hint of where to tune in SAP ?
    Any help would be greatly appreciated.
    Thanks a lot,
    Jamal

    Hi Jamal,
    I understand you have already checked performance issues in the SAP Server. We had some problems with certain RFC calls and it turned out to be a badly developed ABAP sentence.
    I'd recommend you to use httpwatch or another tool to check the response times from the browser, so you can point accurately where the is.
    Regards
    Francisco

  • Best approach for RFC call from Adapter module

    What is the best approach for making a RFC call from a <b>reciever</b> file adapter module?
    1. JCo
    2. Is it possible to make use of MappingLookupAPI classes to achieve this or those run in the mapping runtime environment only?
    3. Any other way?
    Has anybody ever tried this? Any pointers????
    Regards,
    Amol

    Hi ,
    The JCo lookup is internally the same as the Jco call. the only difference being you are not hardcoding the system related data in the code. So its easier to maintain during transportation.
    Also the JCO lookup code is more readable.
    Regards
    Vijaya

  • Adaptive RFC 2 gives error: com/sap/ide/jco/service/internal/R3Service

    Hi,
    I've run into the following problem about NWDS. This happens as I create a Model. It appears there is a new version of the Adaptive RFC Model, which is called Adaptive RFC 2 Model.
    1. Right click on Models, and select Create.
    2. Double Click on Adaptive RFC 2 Model
    3. The error pops up. It says "An error has occurred. See error log for more details. java.lang.NoClassDefFoundError". Then if you click details you get "An error has occurred. See error log for more details. com/sap/ide/jco/service/internal/R3Service "
    If you know which log to have a look, or what this error is about please let me know urgently. Any help if much appreciated.
    Thanks,
    Ogeday Isiklar

    Hi,
    I am also getting same problem. Waiting for solution
    Regards,
    Pradeep Kumar

  • Error while importing a Adaptive RFC Model

    Experts,
    I am trying to import an Adaptive RFC Model. Before importing I need to speciy the connection parameters in the import wizard. I am using the single server method to connect and have specified all the parameters correctly. I have not specified a SAP router as I am using a test system. when I click next on the Model import wizard I get an error.
    The trace shows-
    [code]ConnectionFailed Exception : com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
    Connect_PM  GWHOST=test833, GWSERV=sapgw00, ASHOST=test833, SYSNR=00
    LOCATION    CPIC (TCP/IP) on local host
    ERROR       partner not reached (host 10.3.82.177, service 3300)
    TIME        Fri Jun 29 08:54:18 2007
    RELEASE     640
    COMPONENT   NI (network interface)
    VERSION     37
    RC          -10
    MODULE      nixxi_r.cpp
    LINE        8715
    DETAIL      NiPConnect2
    SYSTEM CALL SiPeekPendConn
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUN
         at com.sap.ide.jcb.core.service.connection.internal.ConnectionManager.connect(ConnectionManager.java:220)
         at com.sap.ide.jcb.core.service.connection.internal.ConnectionManager.connectToSingleServer(ConnectionManager.java:206)
         at com.sap.ide.jcb.core.wizardpages.SAPLogonPage.internalConnectToServer(SAPLogonPage.java:1769)
         at com.sap.ide.jcb.core.wizardpages.SAPLogonPage.access$2300(SAPLogonPage.java:46)
         at com.sap.ide.jcb.core.wizardpages.SAPLogonPage$9.run(SAPLogonPage.java:1730)
         at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
         at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:98)
         at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:1999)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1733)
         at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:136)
         at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:261)
         at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
         at com.sap.ide.jcb.core.wizardpages.SAPLogonPage.connectToServer(SAPLogonPage.java:1699)
         at com.sap.ide.jcb.core.wizardpages.SAPLogonPage.performFinish(SAPLogonPage.java:1805)
         at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelWizard.initializeReimporter(ModelWizard.java:1410)
         at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelWizard.performPostSapLogonPageForReimport(ModelWizard.java:1433)
         at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelDialog.nextPressed(ModelDialog.java:85)
         at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:316)
         at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
         at org.eclipse.jface.window.Window.open(Window.java:563)
         at com.sap.ide.webdynpro.modeleditor.ModelEditorCallback.reimportModel(ModelEditorCallback.java:218)
         at com.sap.ide.webdynpro.service.modeleditor.ModelService.reImportModel(ModelService.java:207)
         at com.sap.ide.webdynpro.service.modeleditor.ServiceWithUI.reImportModel(ServiceWithUI.java:120)
         at com.sap.ide.webdynpro.tsmodel.application.actions.ReimportModelAction.run(ReimportModelAction.java:11)
         at com.sap.ide.webdynpro.projectbrowser.actions.PBReimportModelAction.run(PBReimportModelAction.java:77)
         at com.sap.ide.webdynpro.projectbrowser.actions.PBDevelopmentObjectAction.runInternal(PBDevelopmentObjectAction.java:80)
         at com.sap.ide.webdynpro.projectbrowser.actions.PBDevelopmentObjectAction.run(PBDevelopmentObjectAction.java:61)
         at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
         at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
         at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
         at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
         at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
         at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
         at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
         at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
    Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
    Connect_PM  GWHOST=test833, GWSERV=sapgw00, ASHOST=test833, SYSNR=00
    LOCATION    CPIC (TCP/IP) on local host
    ERROR       partner not reached (host 10.3.82.177, service 3300)
    TIME        Fri Jun 29 08:54:18 2007
    RELEASE     640
    COMPONENT   NI (network interface)
    VERSION     37
    RC          -10
    MODULE      nixxi_r.cpp
    LINE        8715
    DETAIL      NiPConnect2
    SYSTEM CALL SiPeekPendConn
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUN
         at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeConnect(Native Method)
         at com.sap.mw.jco.rfc.MiddlewareRFC$Client.connect(MiddlewareRFC.java:1125)
         at com.sap.mw.jco.JCO$Client.connect(JCO.java:3138)
         at com.sap.ide.jcb.core.service.connection.internal.ConnectionManager.connect(ConnectionManager.java:216)[/code]
    Can someone tell me problem..
    Thanks in advance,
    Vineeth

    In service file if entry is not there... give the enty like
    <b>sapgw<Inst.No>       33<Inst.No>/tcp
    sapgw<Inst.No>s      48<Inst.No>/tcp</b>
    where <Inst.No> = System Number of your R/3 system(00 or 01...)
    In host file....
    ip of the server                            name of the server....

  • Is there any way to limit the number of RFC calls from xMII to SAP R/3

    Hi All!
    I wanted to know whether the number of simultaneous RFC connections made from xMII to SAP R/3 system can be controlled in any way. Suppose we have a scenario wherein some million Sales Orders or Production Orders are to be updated in SAP R/3 from xMII in a short span of time. For all these updations to take place, multiple RFC calls will be established from xMII to SAP at the same time. This will increase the load on the SAP R/3 system and affect performance of the SAP R/3 system. Is there any check on xMII side to limit the number of RFC calls that can be made to SAP R/3 system?
    Regards
    Anupam

    Anupam,
    If you are using 11.5 just keep in mind that the JCO connection points to a single application server (based upon the SAP Server alias connection settings), but the traffic itself to make a BAPI request is effectively the same as any client user traffic.  There will obviously be limitations on performance and throughput, with network and server constraints added to the number and size of the R/3 requests, but there is no magic formula to plug-in because of all of these variables.
    If you are using 12.0 (or plan to migrate when it goes GA) then taking advantage of the JRA (java resource adapter) and the associated application server pooling that it offers on the NetWeaver side of things will greatly help you in the throughput capacity.
    If you have put some of your xMII application into either test or productive use and are running into issues then I would highly recommend entering the specifics into the customer / partner support portal so that they can help you through any associated problems.
    Regards,
    Jeremy Good

  • SAP R/3 RFC Call to XI

    Hallo,
    My scenario is as follows: when sending a RFC to XI via the RFC adapter, I get a short dump with the following error: "the error occurred in an RFC call to another system (XI).The termination occurred in the function "RfcExtendedReceive" of the SAP
    Basis System, specifically in line 392 of the module
    "//bas/640_REL/src/krn/rfc/abrfcrcv.c#2".
    The internal operation just processed is "FUNC".
    The internal session was started at 20060125163632".
    The RFC adapter has been configured as the Sender and all the parameters populated with the system details.
    Has someone seen this eror before?
    Please assist.
    Thanks,
    Catherine

    Maybe you're invoking RFC synchrounously from ABAP code and your receiving scenario is on Asynchrounous interfaces? What are you doing then in XI with data sent by the RFC?
    Message was edited by: Alessandro Guarneri

  • Message transfer between R/3 to XI By RFC call

    Hi all,
    I am trying to pass some parameters to XI by making an RFC call from R/3.In sm59 the connection is working fine with the RFC destination declared.I have created an RFC enabled function module and  it has   5 import parameters .The FM doesn't contain any query as i have queried in the calling program. The program as followes;
    DATA  : IT_ZXIRFC LIKE ZXIRFC.
    DATA: IS_BILL_NUM LIKE ZXIRFC-BILL_NUM,
          IS_BUYERVATNUM LIKE ZXIRFC-BUYERVATNUM,
          IS_BUYERACCNUM LIKE  ZXIRFC-BUYERACCNUM,
          IS_PRODUCTDES LIKE  ZXIRFC-PRODUCTDES,
          IS_BUYERNAME LIKE ZXIRFC-BUYERNAME.
    SELECT * FROM ZXIRFC INTO  IT_ZXIRFC
             WHERE BILL_NUM = 'ABC1234'
               AND BUYERVATNUM = 'CH456789'
               AND BUYERACCNUM = 'THE456789'.
    ENDSELECT.
           IS_BILL_NUM = IT_ZXIRFC-BILL_NUM .
           IS_BUYERVATNUM = IT_ZXIRFC-BUYERVATNUM.
           IS_BUYERACCNUM = IT_ZXIRFC-BUYERACCNUM.
           IS_PRODUCTDES = IT_ZXIRFC-PRODUCTDES.
           IS_BUYERNAME = IT_ZXIRFC-BUYERNAME.
    CALL FUNCTION 'ZRFC_XI_TEST1' IN BACKGROUND TASK  DESTINATION 'SAP_X3ATEST'
      EXPORTING
        I_BILL_NUM          =  IS_BILL_NUM
        I_BUYERVATNUM       =  IS_BUYERVATNUM
        I_BUYERACCNUM       =  IS_BUYERACCNUM
        I_PRODUCTDES        =  IS_PRODUCTDES
        I_BUYERNAME         =  IS_BUYERNAME
    COMMIT WORK.
    I am getting notthing in moniter of XI when i excecute this program.
    Please have a look at this and suggest me the solution.
    Thank you,
    Best regards,
    Priya parmeshwar.

    Hi,
    In SM59 my RFC destination is working fine.I have done the configuration according to Michal' blog
    https://weblogs.sdn.sap.com/pub/wlg/1438.The [original link is broken] [original link is broken] [original link is broken] [original link is broken] RFC  destination details as followes:
    RFC destination :  SAP_X3ATEST
    Gateway Host :   ld8022
    Gateway service: sapgw22
    Program Id : RFCTEST1
    and here i have checked the Registered server program.
    The same data has been updated in communication channel  with a sender RFC adapter type.
    Thankx,
    Priya

  • XI RFC call failing

    Hello,
       I am setting up a very simple scenario where I am making a sychronous RFC call to a BAPI in R/3 (Version 4.6c) from an XI Sandbox (Version 7.0).
       I have the RFC Communication channel properly configured, or so I think, and have verified everything else as well. I initiate the message from the Runtime Workbench and it shows with status "Successful" in the Message Monitoring section. However, when I look in SXMB_MONI transaction I am unable to find a response message from the BAPI coming back in the payload. I notice that even though the scenario is synchronous, the "Type" column in the SXMB_MONI transaction results shows it as "Asynchronous". Also, in the message details there is a Payload (which I am sending when I create and send the message from the RWB), in every step, until the Call Adapter step. After that there is no payload in the Call Adapter or the Response steps, just the SOAP Body with the Manifest.
       In the message details I see that the <SAP:Processing Mode> entry is set to "Asynchronous" rather than "Synchronous".
       Does anyone have any idea why this is so?
    Thanks,
    Murtaza.
    Message was edited by:
            Murtaza Madraswala

    Hi Amitabha,
       I looked in the location you suggested and got a list of "Success" messages. These are listed below for you to look at:
    Time Stamp Status Description
    2007-06-18 15:17:54 Success Message successfully received by messaging system. Profile: XI URL: http://camapox1:50100/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
    2007-06-18 15:17:54 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
    2007-06-18 15:17:54 Success Message successfully put into the queue.
    2007-06-18 15:17:54 Success The message was successfully retrieved from the receive queue.
    2007-06-18 15:17:54 Success The message status set to DLNG.
    2007-06-18 15:17:54 Success Delivering to channel: GeneratedReceiverChannel_RFC
    2007-06-18 15:17:54 Success MP: entering
    2007-06-18 15:17:54 Success MP: processing local module localejbs/RfcAFBean
    2007-06-18 15:17:54 Success RFC adapter received an asynchronous message. Attempting to send tRFC for Z_SD_RFC_ATP_WRAPPER with TID XIlc32S1tf4Togkm0mRWaHRG
    2007-06-18 15:17:55 Success MP: leaving
    2007-06-18 15:17:55 Success The message was successfully delivered to the application using connection RFC_http://sap.com/xi/XI/System.
    2007-06-18 15:17:55 Success The message status set to DLVD.
       The problem that I am seeing is that this is posted under the list of Asychronous Received Messages. Thats something I am just unable to understand. I have a Synchronous Outbound Interface defined and an RFC Communication Channel, which is Synchronous as far as I know. So why is the processing mode for the message being chosen as Asynch? Which config setting have I missed that is causing this problem? I am just unable to find the answer so far.
       I appreciate your help. Please let me know if you have any clues.
    Thanks,
    Murtaza.

  • Asyncronic JCO RFC call from JAVA to ABAP

    Hi,
    Please could you provide a sample java code to establish JCO RFC call to ABAP?
    Thanks.

    Hi Denis,
    Import the model In NWDS for ABAP for RFC.
    Please check here [Accessing ABAP Functions using the Adaptive RFC Model |http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a00f7103-6790-2a10-ac9c-fcac7c5b18a3?quicklink=index&overridelayout=true]
    [Web Dynpro Model: Backend Access|http://www.sdn.sap.com/irj/sdn/nw-wdjava?rid=/webcontent/uuid/403e6bf5-426e-2910-b0a8-a95548724af9#section10 [original link is broken]]
    Also check here /docs/DOC-8661#section10 [original link is broken]
    Hope it helps,
    Redards,
    Arun

  • Question on service userid - for RFC call

    Hi
       In XI 3.0 SP18 , we are making a RFC call from XI mapping runtime - to XI's ABAP stack - RFC function module . In the RFC receiver communication channel , I tried using service user XIISUSER , XIAPPLUSER for this RFC call - I got short dumps on XI ABAP stack mentioning that these two service users do not have authorization to make RFC calls -
    Does anybody out there know what service user on XI has RFC call authorization that can used to make RFC calls onto XI ABAP stack from its mapping runtime ?
    Correct answers will be rewarded rightaway. Thanks for your time in advance.

    Hi,
    u have to make entry in sld...
    Hi,,
    2 Introduction
    Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
    systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
    simple, are many times missed or mis-configured, causing the delivery of messages to fail.
    Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
    ABAP.
    Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
    SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
    backend SAP system.
    3 The Step By Step Solution
    The basic steps for the IDoc configuration are outline below:
    1. Configure SM59 on XI to communicate to SAP backend system.
    2. Configure port on XI for IDoc communication.
    3. Create or verify the Logical System Name on the SAP backend system.
    4. Create or verify business system in XI’s System Landscape Directory.
    5. Verify the Logical System Name of the business system.
    6. Verify or add the Logical System Name for the sender business system.
    7. Create/configure the Communication Channel for the IDoc receiver adapter
    3.1 Configure SM59 on XI to communicate to SAP backend system.
    1. Using transaction SM59, create an RFC destination with Connection Type = “3”.
    In this example, the RFC destination name is “NDVCLNT510”.
    2. Enter the logon information:
    3. Test the connection by clicking on “Testing connection” and “Remote logon”.
    Both must be successful.
    3.2 Configure port on XI for IDoc communication.
    4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is “SAPNDV”.
    • &#61472;The Port name must be in the form of “SAPxxx”, where xxx is the system ID of the backend SAP
    system.
    • The Client must be the client number of the backend SAP system.
    • Select the RFC Destination which was created in the previous step.
    3.3 Create or verify the Logical System Name on the SAP backend system.
    5. Enter transaction SALE on the SAP backend system.
    6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
    3.4 Create or verify business system in XI’s System Landscape Directory.
    The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
    7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
    3.5 Verify the Logical System Name of the business system.
    8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
    Navigate the menu:
    Service • Adapter Specific Identifiers.
    If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
    9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
    Landscape Directory.
    • &#61472;Double-click on the business system in the Integration Directory.
    • &#61472;Switch to Edit mode.
    • &#61472;Select menu: Service • Adapter-Specific Identifiers
    10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
    11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
    3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
    15. In the Integration Directory, create an IDoc receiver communication channel.
    • &#61472;The RFC Destination is from step 3.1.
    • &#61472;The Port is from step 3.2.
    NOTE:
    There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
    4 Appendix
    Transaction: IDX2
    There are a couple of situation where IDX2 can be useful on the XI system.
    1. When we want to test connection between the XI and SAP backend system.
    2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
    meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
    Go to transaction IDX2 and click on “Create”.
    Enter the IDoc Type and the Source Port as defined in step #2. Click “Continue”.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
    Reward points if find useful.

  • RFC Call error..

    Hi All XI Expert,
    I am facing an issue with regard to RFC call from an external system.Business flow is like, Purachase Requisition(PR) is created from Ariba system/application which is passed to SAP via TIBCO Adapter to create Purchase order(PO).As per my understanding the data flow is like this: Ariba PR data's are captured by Ariba Adater and are send to TIBCO ADAPTER.This TIBCO adapter will invoke request-response service from SAP Adapter for operation of SAP RFC calling.Now i am able to successfully create PR/PO from Ariba application with amount(more than $10mn with after decimal value as 00) say $12,000,000.00 / $15,000,000.00. But while creating PR/PO from Ariba application with amount (more than $10mn with after decimal value as other than 00 i.e .99, .78, .05 etc) say $12,000,000.99 / $15,000,000.08, it gives below error which are captured in Ariba side, hence unable to create PR/PO's more than $10mn, however for less than $10mn amount of PR/PO with after decimal value as other than 00 i.e .99, .78, .05 etc, it is successfully getting created.So the problem is amount with more than $10mn PO with after decimal value as other than 00 i.e .99, .78, .05 etc.
    Error found in Ariba side for above scenarion:
    " Thu Apr 09 12:21:49 EDT 2009 (integrationExternal:error:4745): Received a Tibco generated message: 2009 Apr 9 12:21:49:079 GMT -5 SAPAdapter.SAInboundRFC.psap1 Error Application AER3-000185 CallReceive failed for operation Z_ARIBA_PO_PUSH; exception : Unable to interpret 1.10000005E7 as a number., RFC error; Group/Key/Message: 104/CONVT_NO_NUMBER/Unable to interpret 1.10000005E7 as a number.
    Where could be the problem?Does it a TIBCO Adapter config/ SAP adapter Problem / SAP RFC code issue?
    FYI....SAP RFC that is getting called doesnot contain any code of "CONVT_NO_NUMBER" .
    Awaiting your reply guys

    The problem is that in case the value of the amount is greater than $10mn, then it is converting the numeric value into exponential number 1.10000005E7. This is a number but when RFC tries to treat it as a number, it is throwing the exception. At sender Ariba system, you may change some configuration to avoid changing of numeric field to exponential field and problem would get resolved.
    Regards,
    Prateek

Maybe you are looking for

  • My A1208 iMac will no longer power on

    I have a iMac core 2 duo model a1208 (late 2006) that has never had any problems whatsoever until last year, it had trouble powering on. It would not respond to the power button for extended periods of time, then would miraculously turn on one day. T

  • Turning Off Compatibility Mode

    Hello, Every time that I open iTunes for my PC (Vista operating system), I receive a dialog box that states: "iTunes.exe has been set to run in compatibility mode fore an older version of Windows. For best results, turn off compatibility mode for iTu

  • Total record display in resultlist (interaction history)

    Hi all, May I know how can I add the total search data so that it can display in the interaction history page to show the total record found? In most cases, like in Activity, it will show the total record found in resultlist. But not in interaction h

  • Stolen iPad

    Christmas day I stupidly left my iPad on AA#1381 going on to Acapulco. Once it left the country I could not track it. Also had some crazy password problem with MobileMe so I don't know whether the wipe feature ever worked. I have spoken to MobileMe a

  • Starting NWDS help!

    Hi All, I am stating with NWDS and I am getting this challange!! I was reading one thread that was saying "Next, we must to import the aii_map_api.jar library. The file aii_map_api.jar is located in j2ee\cluster\server0\apps\sap.com\com.sap.xi.servic