JCO - BAPI_REQUISITION_CHANGE -  TEXTs

Hello,
I try to update a requisition item with the corresponding texts
( Item text, Item note, delivery text, PO text) via JCO.
Changing of the texts works, as well as appending texts, but DELETING
of the texts is not working....
To delete the texts I iterate through the REQUISITION_TEXT_NEW table and delete the rows with a certain TEXT_ID (e.g. B01).... but unfortunately that does not work.
I would appreciate any hint!! Thanks in advance!!!
Warm Regards,
Christian

Hi Thomas,
I'm calling BAPI_REQUISITION_CHANGE (standard sap BAPI). I' don't know if this BAPI has an implicit COMMIT WORK inside....
What I can tell you is:
- Changing texts works fine
- Adding new text also
- DELETING texts works not correct
What I do is:
- get the OLDtable:
function.getTableParameterList().getTable("REQUISITION_TEXT_OLD")
- copy values from the OLD table to the NEW
- delete the rows which are not needed anymore:
function.getTableParameterList().getTable("REQUISITION_TEXT_NEW").deleteRow()
Then the BAPI_REQUISITION_CHANGE and BAPI_TRANSACTION_COMMIT is called:
JCO.Function commit = getBapiFunction("BAPI_TRANSACTION_COMMIT");
commit.getImportParameterList().setValue("X", "WAIT");
client.execute(commit);
What am I doing wrong? Why the texts can not be deleted??
Thanks for any advice!!!!
Best regards,
Christian

Similar Messages

  • JCo method to find CCMS Text Attribute/Object Description attributes value

    Is there any function available in SAP JCo / XAL ( External Interface for Alert Management ) to find the current values for CCMS Text Attribute or Object Description attributes and CCMS Heartbeat attributes from a Java Program. It seems XAL only has functions to find the current values of performance, status and log attributes.

    hi arun,
    refer this link
    http://help.sap.com/saphelp_nw04/helpdata/en/6a/82343ecc7f892ee10000000a114084/content.htm
    https://dsd.esco-salt.com/StartPage/documents/admin/30.html
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/548da290-0201-0010-0299-f037dd7eeb36
    check for the api for jmomapi.jar
    Alert status definitions
    ther u have code and example also
    bvr
    Edited by: bvr on Apr 27, 2009 12:18 PM
    Edited by: bvr on Apr 27, 2009 12:53 PM
    Edited by: bvr on Apr 27, 2009 12:55 PM

  • Getting JCO version as text output

    Hi,
    I'm using JCo 3.0.5 as a connector between SAP and an application that I write.
    I am looking for a way to verify that the JCo JAR that I use is the correct one.
    When I run the command "java -jar sapjco3.jar" I get the JAR information in a window.
    In order to verify the version I need the output as text to stdout so I can parse it.
    Is there a way to accomplish that or this information is only available in a GUI window?
    Thanks!

    A quick look in the API documentation would've given you for example the following static method:
    com.sap.conn.jco.JCo.getVersion()
    Note that also the About class used when running the jar can provide the information as text output, e.g. you can use
    java -jar sapjco3.jar -stdout
    or alternatively from Java code
    com.sap.conn.jco.About.getFullVersion()

  • SSO between EP and ECC-- JCo RFC Provider- Error-- JCO_ERROR_SERVER_STARTUP

    Hello Everyone
    I am setting Up SSO between my EP 7.0 and my ECC 6.0 system. During the phase JCO RFC PRovider i am giving the following values:
    The following was done;
    1. start Visual Administrator -> Service : Choose JCo RFC Provider
    2. Created JCo RFC provider:
    Program ID: SAPJ2EE_Port
    Gateway host: EPDEV ( host of my EP System)
    Gateway service: sapgw00
    Server Count 5
    Application Server Host: ERP6 ( Host of my ECC System)
    System Number: 00
    Client: 000
    Language: EN
    User: SAPJSF
    Password: ..
    When i click on SET i am getting the error " ERROR When ADDING TO BUNDLE" Check LOG FOR DETAILS".
    I checked the DEFAULTTRACE.TRC and get the following MEssage :
    Date , Time , Message , Severity , Category , Location , Application , User
    03/01/2011 , 3:33:30:101 , Error changing bundle SAPJ2EE_PORT , Error , /System/Server , com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.addBundle(BundleConfiguration conf) ,  , Administrator
    03/01/2011 , 3:33:30:085 , com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Mar 01 03:33:30 PST 2011.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 1 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=SAPJ2EE_PORT GWHOST=EPDEV GWSERV=sapgw00
    ERROR       partner 'EPDEV:sapgw00' not reached
    TIME        Tue Mar 01 03:33:30 2011
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2823
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUNTER     1
    I have configured my SLD as well. Any suggestions. Please Advise.

    Hi Ahmed,
    Please do check the validity of the certificate.
    Please do cross check these steps again.
    1.     Transaction u2013 STRUSTSSO2 (Trust Manager for Logon Ticket)
    2.     Double Click Owner certificate. It gets reflected under the certificate tab.
    3.                  Choose Format Binary
    4.                  Choose File Path.
    5.                  Enter the File Name
    6.                 saved in local drive.
    You can import into portal as x.509 certificate.
    check this thread -
    Certificate no longer has signature (use restriction)
    Renew certificate via SAP MarketPlace, and install from tcode slicense.  If you are working on a trial version, there is a SAP license request application form. Fill the form with the hardware key. you will get the new license via email. Install using slicense. Then try exporting the certificate.
    Thanks,
    Divya
    Edited by: Divya V on Mar 10, 2011 11:25 AM

  • Problem with SLD and Creation of JCo

    Hello everyone!
    I have a problem with the SLD and the Creation of JCo on the Portal, in trying to create the JCo always tells me that the name used there in the SLD, being that the facility is new.
    Who performs the installation, set in the SLD the ECC 6 PRD, delete it to see if I could create a JCo but still the error again when creating the ECC 6 PRD in the SLD I said that already exists and can not create it.
    I found a forum which recommended re-import the cimsap .... .... zip and zip CR_Content which would clean everything, I managed to import the zip cimsap ... but in trying to raise CR_Content gives me the following message "All incremental updates of the selected aggregate import for export SAP_CR line have already been loaded before. You require a newer import to update your current content SAP_CR version 4.11." .
    I recommend, do the installation again, reload the cimsap.zip and CR_Content.zip a copy homogeneous.
    from already thank you very much
    Text of error to create JCo destination
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
        at at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
        at at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionGoForward(ButtonBar.java:505)
        at at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:280)
        at at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
        ... 28 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; InfoPath.1)
    Version null
    DOM version null
    Client Type msie7
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0017.20081210091801.0000 (release=NW04S_17_REL, buildtime=2009-01-12:09:43:27[UTC], changelist=52884, host=pwdfm114), build date: Tue Apr 28 19:28:39 CLT 2009
    J2EE Engine 7.00 patchlevel 48199.450
    Java VM IBM J9SE VM, version:2.2, vendor: IBM Corporation
    Operating system Linux, version: 2.6.18-92.el5, architecture: amd64
    Session & Other
    Session Locale en
    Time of Failure Fri Aug 28 11:43:53 CLT 2009 (Java Time: 1251474233677)
    Web Dynpro Code Generation Infos
    sap.com/tcwdtools
    No information available null
    sap.com/tcwddispwda
    No information available null
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
         at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionGoForward(ButtonBar.java:505)
         at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:280)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         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.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         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(AccessController.java:207)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

    Hello!!
    The "SLD" with which I am working up to Portal, the "ECC" installs itself as "ABAP.
    Who did the installation and initial configuration, do not leave any documentation about it.
    Now I need to create the systems and "JCo" necessary to enable them to implement the "ESS", but errors are presented above.
    Some days ago I managed to update the CR_Content, which allowed me to create the "JCo" but at the time of the test, says' com.sap.mw.jco.JCO $ Exception: (103) RFC_ERROR_LOGON_FAILURE "name or password incorrect .
    I managed to also create the portal systems, "System Administration -> System Configuration -> Content Portal" and to test it fails on "Test Connection with Connector", which as noted is associated with the connectors "JCo".
    For the creation of the system, I think I should create something in the Visual Administrator ", but within the documentation that I do not see anything about it.
    thanks for your help!

  • Error when editing a JCO

    hello everyone!
    delivery to acknowledge the help I can get.
    I tell them my problem, I have a BI Server (ABAP + JAVA), which is trying to configure the JCO, but there is a problem when trying to create a new or an existing deal.
    starting to enter the "Web Dynpro Content Administrator" presents the message "java.lang.NullPointerException"
    to try to Edit or Create a JCO, gives the following error:
    500   Internal Server Error
      SAP NetWeaver Application Server 7.00/Java AS 7.00 
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:286)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:251)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:158)
        ... 45 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; MEGAUPLOAD 1.0)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0020.20090723111631.0000 (release=NW04S_20_REL, buildtime=2009-08-14:13:18:26[UTC], changelist=65312, host=pwdfm114), build date: Wed Nov 11 21:35:52 AST 2009
    J2EE Engine 7.00 PatchLevel 65302.450
    Java VM IBM J9 VM, version:2.3, vendor: IBM Corporation
    Operating system AIX, version: 5.3, architecture: ppc64
    Session & Other
    Session Locale es_CL
    Time of Failure Sat Apr 03 16:06:33 AST 2010 (Java Time: 1270325193642)
    Web Dynpro Code Generation Infos
    sap.com/tcwdtools
    No information available null
    sap.com/tcwddispwda
    No information available null
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:286)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:251)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:158)
         at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         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.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         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.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         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(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

    Probably you might need to stop and start the service/application in VM(under deploy) or from NWA.
    The webdynpro application name should cover in sap.com/tcwd* (* means all followers).
    Let us know the outcome.

  • ERROR WHEN I CREATE A JCo DESTINATIONS

    Hi to all
    I have the SLD running. I want create two JCo destinatios. I want create a Web Dynpro application with adaptive RFC Model.
    But, I login to http:///webdynpro/dispatcher/sap.com/tcwdtools/Explorer
    and when I attempt create a JCo destinations, appear the following error:
    500   Internal Server Error
      Web Dynpro Container/SAP J2EE Engine/6.40 
    Failed to process request. Please contact your system administrator.
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:985)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
        ... 45 more
    Can someone say me, why occurs this error ? I have reviewed all my configuration, but I haven´t found nothing.
    Thank you very much.
    Regards
    Dario Rodriguez

    I think while creating the JCOs you must hav left some field with a NULL  value.Try to check out that all the connection properties hav been specified correctly also make sure that the connection pooling has a small range.

  • Error while obtaining JCO connection.

    Hi I'm trying to put in place since BW-SEM RSPLAN the transaction, I'm pointing at my portal from the transaction RSPLSA
    But when it signs the user gets the message Error while obtaining JCO connection.
    I was reviewing my WebDynpro on my site by following these steps:
    1 I will http://portal:port
    2 I clicked Webdynpro
    3 I click on Content Administrator
    I clicked on 4 Maintain JCO destinations
    and then I log shows the following:
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:485)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:480)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:699)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:663)
        ... 39 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type     HTML Client
    User agent     Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
    Version     null
    DOM version     null
    Client Type     ns7
    Client Type Profile     nn7
    ActiveX     disabled
    Cookies     enabled
    Frames     enabled
    Java Applets     enabled
    JavaScript     enabled
    Tables     enabled
    VB Script     enabled
    Server
    Web Dynpro Runtime     Vendor: SAP, build ID: 7.0014.20071210061512.0000 (release=645_VAL_REL, buildtime=2007-12-10:05:23:29[UTC], changelist=470565, host=pwdfm101), build date: Wed Oct 01 12:15:02 CDT 2008
    J2EE Engine     7.00 patchlevel 109886.44
    Java VM     IBM J9 VM, version:2.3, vendor: IBM Corporation
    Operating system     AIX, version: 5.3, architecture: ppc64
    Session & Other
    Session Locale     en_US
    Time of Failure     Thu Nov 06 16:00:23 CST 2008 (Java Time: 1226008823202)
    Web Dynpro Code Generation Infos
    sap.com/tcwdtools
    No information available     null
    sap.com/tcwddispwda
    No information available     null
    sap.com/tcwdcorecomp
    No information available     null
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:485)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:480)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:699)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:663)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.wdDoInit(JCOConnectionsDetails.java:121)
         at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdDoInit(InternalJCOConnectionsDetails.java:262)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
         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.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         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(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    What should I do??

    Hi Antonio,
    Follow the below note for Jco related troubleshooting.
    https://service.sap.com/sap/support/notes/919850
    Are you able to see the 4 Jco connections green?
    Regards,
    Debasis.

  • Error while obtaing JCO connection

    In Bussiness planning in portal. When i click Planning tab in Enterprise portal, its throwing an error that "error while obtaining JCO connection". I cant proceed furtherI
    I am working in my own system.
    I have checked many posts and i have done some JCO destinations as per the instructions but it's vain.
    The detailed error is as follows;
    500   Internal Server Error
    Web Dynpro Container/SAP J2EE Engine/6.40
    Failed to process request. Please contact your system administrator.
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(CharRelInst): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
    at com.sap.ip.bi.plan.workbench.wdp.InternalInfoprovController.wdGetCharRelInstInterface(InternalInfoprovController.java:296)
    at com.sap.ip.bi.plan.workbench.InfoprovController.checkSavable(InfoprovController.java:254)
        ... 48 more
    please give some pointers like what needs to be done JCO settings in Backend.
    Thanks in advance.

    Niranjan,
    3 causes and many more....
    First and most probable cause is that your CR content in SLD is old....
    FIX - to fix this download latest cimsap and crcontent from service.sap.com and implement in SLD.
    Second cause user is locked
    FIX - unlock in R/3
    Third cause could be that the connection pool in JCO is exhausted.
    FIX - increase connection pool in JCO.
    More causes.
    With this new version it appears that any error before connection is created ends up showing this, so I would really go into default trace and look there for original errors, that is the way I found JCO pool was exhausted, that error was not being forwarded and instead it was showing this error...
    reward points if helpful

  • Error in while creating JCo's

    HI all,
    I am getting a error while creating a JCO's .When i am going to web dynpro content administrator and clicking on maintain JCo connections and then click on the create button in the JCo I am getting a exception.Below is the error what i am getting .Please somebody help us.
    500   Internal Server Error
      Web Dynpro Container/SAP J2EE Engine/6.40 
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
        ... 45 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.2)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:41:58[UTC], changelist=413534, host=pwdfm101), build date: Thu Mar 19 12:14:50 IST 2009
    J2EE Engine 7.00 patchlevel
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_19-rev-b07, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: amd64
    Session & Other
    Session Locale en
    Time of Failure Thu May 14 16:58:44 IST 2009 (Java Time: 1242300524924)
    Web Dynpro Code Generation Infos
    sap.com/tcwdtools
    No information available null
    sap.com/tcwddispwda
    No information available null
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
         at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         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.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    Hi Ambarish,
    Yes, it seems to be NW 7.0. Please upgrade Java(NW 7.0) to SP 12 or higher. I guess latest is 17.
    Before upgrading Java, better if you un-install all VIRSA components, and re-install it after applying Java patch. ALso make sure Kernel version is upgraded before applying Java patch.
    Take this sequence-
    1. Un-install VIRSA components
    2. Update Kernel
    3. Update Java patch
    4. Install VIRSA components.
    5. Apply latest patch of VIRSA components.
    6. Apply latest RTA patches in backend system.
    Regards,
    Sabita

  • Error in JCo Connection creation

    Hi All,
    When I create a JCo connection on my local J2EE it fails with the error enclosed as below:
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM  TYPE=B MSHOST=frces4066 GROUP=PUBLIC R3NAME=AM1 MSSERV=sapmsAM1 PCS=1 ERROR       partner not reached (host frces4066, service sapmsAM1) TIME        Mon Apr 03 18:44:33 2006 RELEASE     640 COMPONENT   NI (network interface) VERSION     37 RC          -10 MODULE      nixxi_r.cpp LINE        8596 DETAIL      NiPConnect2 SYSTEM CALL SiPeekPendConn ERRNO       10061 ERRNO TEXT  WSAECONNREFUSED: Connection refused COUNTER     1 
    When I try and ping the JCo the error is as enclosed below:
    Failed to ping JCo destination WD_COMMITMENT_MODELDATA_DEST
    I have maintained the enteries in hosts file as well as the services file and when I telnet the server on port 36XX where XX is the system number of the system I create the JCo for it connects successfully.
    When I test the CIM test for the SLD that connects successfully.
    Where and why is the JCo failing after creation?
    Can someone throw some light on this error.
    Thanks in advance for all your help.
    Best regards,
    Divya

    Hi All,
    Anyone can help? I got the same problem. It seems that the PUBLIC group in NSP ABAP system can't not be accessed.
    Here is my system landscape:
    - I have installed the Java and ABAP in the same host
    - My ABAP system is NW2004sSneakPreviewABAP, Java is SAPNetWeaver04_SP16Preview
    1) I set up SLD successfully (import CIM, run <b>RZ70</b>, the ABAP system shown up in the Technical Landscape in SLD
    2) I created JCO destination with Load Balancing but it failed to ping and to test
    3) I already define the group 'PUBLIC' in tx <b>SMLG</b> but from SAPGUI I can't add the group. I got the error message "<b>Message Sever could not find any group</b>".
    4) The PUBLIC group does not show if I run the program <b>'lgtst'</b>.
    Test lgtst:
    ===========
    c:\usr\sap\NSP\SYS\exe\nuc\NTI386><b>lgtst.exe -H hpxp2 -S sapmsNSP</b>using trcfile: dev_lg
    list of reachable application servers
    <b>[hpxp2_NSP_00] [hpxp2] [10.10.0.10] [sapdp00] [3200] [DIA UPD ENQ BTC SPO ICM ]</b>
    c:\usr\sap\NSP\SYS\exe\nuc\NTI386>lgtst.exe -H hpxp2 -S 3600
    using trcfile: dev_lg
    list of reachable application servers
    [hpxp2_NSP_00] [hpxp2] [10.10.0.10] [sapdp00] [3200] [DIA UPD ENQ BTC SPO ICM ]
    James

  • Help needed in jco programming

    hi friends
    when i try to connect with SAP server using jco i have some probem.
    Connection with jco program is working fine. I make it ajava file and run separately).
    Now i want do that with jsp.
    I am getting error of
    Exception report
    message
    description The server encountered an internal error () that prevented it from fulfilling this request.
    exception
    javax.servlet.ServletException
    org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:848)
    org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:781)
    org.apache.jsp.barcodeMainP_jsp._jspService(org.apache.jsp.barcodeMainP_jsp:124)
    org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    root cause
    java.lang.NoClassDefFoundError
    mySAP.JcoTest.createConnection(JcoTest.java:78)
    mySAP.JcoTest.<init>(JcoTest.java:8)
    org.apache.jsp.barcodeMainP_jsp._jspService(org.apache.jsp.barcodeMainP_jsp:74)
    org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    note The full stack trace of the root cause is available in the Apache Tomcat/5.5.9 logs.
    My Program is
    My java program
    package mySAP;
    import com.sap.mw.jco.*;
    public class JcoTest {
         public JcoTest() {
              createConnection();
              retrieveRepository();
              closeConnection();
         public StringBuffer fetchData(String Dofrom, String Doto) {
              StringBuffer stringbuffer = new StringBuffer();
              try {
                   com.sap.mw.jco.JCO.Function function = getFunction("Z_BC_LABEL");
                   System.out.println("SUCC YOU GOT CONN");
                   com.sap.mw.jco.JCO.ParameterList listParams = function
                             .getImportParameterList();
                   System.out.println(listParams);
                   listParams.setValue(Dofrom, "DO_FROM");
                   listParams.setValue(Doto, "DO_TO");
                   theConnection.execute(function);
                   System.out.println("SUCC function executed success");
                   com.sap.mw.jco.JCO.Table tableList = function
                             .getTableParameterList().getTable("ZBAR");
                   String s3 = "\t";
                   stringbuffer.append("vbeln" + s3);
                   stringbuffer.append("uecha" + s3);
                   stringbuffer.append("kdmat" + s3);
                   stringbuffer.append("lifmg" + s3);
                   stringbuffer.append("bstkd" + s3);
                   stringbuffer.append("groes" + s3);
                   stringbuffer.append("name1" + s3);
                   stringbuffer.append("lfdat" + s3);
                   stringbuffer.append("posnr" + s3);
                   stringbuffer.append("lifmg  bstkd " + "\n");
                   // stringbuffer.append("\t");
                   if (tableList.getNumRows() > 0)
                        do {
                             com.sap.mw.jco.JCO.Field tabField;
                             for (com.sap.mw.jco.JCO.FieldIterator fI = tableList
                                       .fields(); fI.hasMoreElements();
                             stringbuffer.append(tabField.getString() + s3)) {
                                  tabField = fI.nextField();
                             stringbuffer.append("\n");
                        } while (tableList.nextRow());
                   else
                        System.out.println("sorry no records...better luck next time");
              } catch (Exception ex) {
                   ex.printStackTrace();
              return stringbuffer;
         private static void createConnection() {
              try {
                   theConnection = JCO.createClient("080", "xxxx", "xxxx", "EN",
                             "xxx.xxx.xx.xx", "00");
                   theConnection.connect();
              } catch (Exception ex) {
                   System.out.println("Failed to connect to SAP system");
         private static void closeConnection() {
              try {
                   theConnection.disconnect();
              } catch (Exception ex) {
                   System.out.println("Failed to connect to SAP system");
         private static void retrieveRepository() {
              try {
                   theRepository = new com.sap.mw.jco.JCO.Repository("saprep",
                             theConnection);
              } catch (Exception ex) {
                   System.out.println("failed to retrieve repository");
         public static com.sap.mw.jco.JCO.Function getFunction(String name) {
              return theRepository.getFunctionTemplate(name.toUpperCase())
                        .getFunction();
         private static com.sap.mw.jco.JCO.Client theConnection;
         private static IRepository theRepository;
    My JSP calling Program
    <%@page language="java"
         import="java.sql.*,java.io.*,mySAP.*,java.net.URL;"%>
    <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
    <title>Insert title here</title>
    </head>
    <body>
    <%!StringBuffer stringbuffer = new StringBuffer();
         int testemp;%>
    <%
         String dofrom;
         String doto;
         String s;
         String s1;
         dofrom = request.getParameter("DOFrom");
         doto = request.getParameter("DOTo");
         ResultSet resultset;
         String flag = request.getParameter("dall");
         mySAP.JcoTest obj = new mySAP.JcoTest();
         StringBuffer sb = obj.fetchData("one", "two");
         out.println(sb);
         try {
              StringBuffer stringbuffer = new StringBuffer();
              String separator = System.getProperty("file.separator");
              String path = System.getProperty("user.dir") + separator;
         } catch (Exception e) {
              out.println("error%%%%%%%%%" + e);
    %>
    </body>
    </html>

    NoClassDefFoundError always means Class Path problem. The classpath of the Servlet is not the same as a normal Java Application. Move any of the necessary dependencies to the Servlet Context's class path (jars in the WEB-INF/lib/ or classes in WEB-INF/classes/).

  • Java JCo SAP XI RFC SAP R/3 6.C ... Unicode issue

    Hello,
    My scenario is very simple. I'd like to connect a Java program to a SAP R/3 (MDMP) for RFC calls (in both direction), using SAP XI (some of the RFC calls will redirected to some other systems). I use SAP JCo v2.1.8 and tried with Java 1.4.2_09 and Java 6.0.
    It works well when the Java program is calling a function module, but when SAP R/3 is doing it, the returned texts looks like: S#A#P# #J#C#o# #v#2#.#1#.#8# #(#2#0#0#6#-#1#2#-#1#1#)# (the text should be SAP JCo v2.1.8).
    It looks like an issue with Unicode. Although I didn't check the Unicode checkbox in the RFC sender adapter (the RFC receiver one doesn't offer the possibility to specify unicode or not).
    Do anyone have a solution ? Is it a code in the Java program or something to set in SAP XI / SAP R/3 ?
    Thanks in advance for your help.

    This is a workaround solution. In the case of this prototype it is ok, but the final plan is to migrate a web based application. It was directly connected to one SAP R/3, but now we would like to connect it to SAP XI because a few RFC calls will be re-directed to some other systems, but the majority of them will we'll still be sent to the SAP R/3. We don't want to make development on this part for cost reason (and time). Plus on some text there are the "#" character that is legitimate.

  • PI 7.31 (single stack) posting to RFC configuration gives this error: om.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: String index out of range: 0 (raised by system extern ...

    Getting cryptic error while trying to post to a custom RFC from PI 7.31 single stack.
    com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: String index out of range: 0 (raised by system <extern>|pidevhost)
    Does anyone recognize this error and/or know of detailed instructions for registering custom RFCs in PI 7.31. I could possibly have configured the target wrong but no error says so.
    This is a File-->PI-->RFC scenario. The file processing is super simple and a configuration I have used successfully before. I would assume I'd get a different error if it couldn't parse the file.
    Jody

    Not shure if you already did but try getting some details with XPI Inspector. Also increasing log level for this category might help. You also may wanna check authorization (even if this should show with a different error text) in ECC using ST01.
    My guts feeling is that there is something wrong with payload / signature of RFC.
    Cheers
    Jens

  • Can't create JCO connection in Portal7 for ESS1.0

    Hi,
    I am in the Process of setting up ESS/MSS Rel 1.0 in Portal 7. The Portal is a WebAS ABAP+JAVA system.
    First step after installing Portal, I configured the SLD and created the Technical systems.  The sld is running and I have tested the sld from the Content Administrator->WebDynpro-> check SLD. It results sld successfully tested and I am able to start the sld also.
    After that I deployed the Business packages for ESS/MSS and selfservices via SDM.
    Now I am trying to create the JCO connection in the Content Administrator->WebDynpro->create/maintain JCO Connections, it throws the following error
    500   Internal Server Error
      Web Dynpro Container/SAP J2EE Engine/6.40 
    Failed to process request. Please contact your system administrator.
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
        ... 45 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:41:58[UTC], changelist=413534, host=pwdfm101), build date: Fri Aug 31 20:55:03 GMT+08:00 2007
    J2EE Engine 7.00 patchlevel
    Java VM Java HotSpot(TM) Server VM, version:1.4.2_15-b02, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: x86
    Session & Other
    Session Locale en_US
    Time of Failure Tue Sep 11 17:54:15 GMT+08:00 2007 (Java Time: 1189504455341)
    Web Dynpro Code Generation Infos
    sap.com/tcwdtools
    No information available null
    sap.com/tcwddispwda
    No information available null
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
         at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         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.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    This is very urgent, can any one of u help me on this....
    Thanks

    Hi,
    I am running Netweaver 7 and ERP2005.
    J2EE support pack is 9. The sap note that you mentioned is for NW2004 and our system is running on NW2004s.
    Now I am trying to reconfigure the sld. In case if you can suggest me another solution, I will be very happy to try that out...
    Thanks for your reply
    Edited by: Rakesh Bothra on Apr 20, 2011 4:23 AM

Maybe you are looking for

  • More records in Purchasing Cube than in PSA.

    Dear Folks, Right now i'm working on 0PUR_C01 Cube.In Quality server, i checked the data in Cube after executing the DTP and found that records are getting increased.Records in PSA(2152),but in Cube(2359),there are some routines in the Transformation

  • Ipod nano displays apple icon and doesn't work

    I bought this nano as a gift (I already have an identical one). There were no problems syncing the content and registering the device, but once it is disconnected from the system, if you navigate to a song on the device and hit "[play", the screen go

  • Script to add markers to text by paragraph format

    With previous versions of Framemaker, I had a FrameScript which would loop through my document and add a marker to text based on the paragraph format applied. The marker text would be the selected paragraph.  I am now trying to recreate this in Exten

  • Problems with getting waveform using tektronix tds 6604

    hello, i'm using the scope tds 6604 with tektronix lv-driver (TKTDS6K) under lv 6.0.2. I always want to read the displayed waveform via GPIB. This is not a problem. The waveform and the scales are correct. BUT if I stop the aquisition on the scope Ru

  • Links on some websites

    On some websites I go to the links do not work.  Is there a setting in my BB I need to change or is it just something about the website? Thanks Solved! Go to Solution.