Spool List not available

I am not able to see the spool when i run my program in background.
I run it by executing the program in se38 choosing the option as execute in background. I am of the idea that SAP creates a spool on its own when i run any program that has a list output without me having to code anythin explicitly for it.
please suggest me some ways of checking why is it happening !! this is urgent !!
Thanks.
Shiv

You could write a wrapper program that does a submit.
Do F1 help to see the extensions of this statement,  you can set the print parameters there.
SUBMIT <program> to SAP-SPOOL.
You can also set these parameters if you were to schedule this in a job via SM36.
You can also set these defaults in your user profile, but this would make it so for ALL reports that you run.  Maybe not such a good idea.
Also you must verify that you are actually generating ouput.  Do you get the list running in dialog mode?
Regards,
Rich Heilman

Similar Messages

  • Spool list not available from SM37

    Hi All,
    We have scheduled a job and running successfully.
    But spool list not displayed from SM37, whereas spool request generated in SP01 at the same time when the job is completed.
    We've checked with the developer and they dint find anything wrong from program end.
    Kindly suggest what is going wrong here.
    Thanks in advance......

    Hi,
    Apply the following SAP notes to resolve this problem:
    1372936 - Spool lists no longer displayed from SM37 after SP
    1174127 - Job refers to incorrect spool request
    regards,
    Aidan

  • Spool list not available in SM37

    HI,
           i'm facing a error "spool list not avaiable" when i execute a background job and the job status is in finished state,but when i click the spool button i'm facing this error. I tried the sap note 1372936 and 1174127 but both notes are in cannot be implemented status.I tried hard to search a solution, but couldn't find.Please help if anyone knows the solution.

    Hello,
    What release and SP level your SAP system has ?
    Thanks

  • Spool  List not printing in Background

    Hi,
       When i try to execute the report in background in development system i can able to see the spool list, whereas when i try to execute the same report in testimg server(may be with more data) i can not see the spool list but the job is in finish status.
    Please can i know the reason for the same.
    Thanks & Regards,
    Sudheer.

    Hi!
    This may be because you started the program with the option, not to create new spool request, or to delete the spool request immediately.
    When you run your program in background, check the printer options also.
    Regards
    Tamá

  • Backing up the BB messenger contact list not available

    In the old versions of Blackberry, we had the option to backup the BB messenger contact list to the device, the media card, or remotely to an email. However, this feature is not available in the new BB Z10 !!!!! This feature is significant and necessary for all users Why was it omitted in the Z10 ??

    Your BBM contact list is now attached to, and backed up to, your BlackBerry ID.

  • Human Task in jDeveloper 11g users list not available

    I have the problem, I defined SQL authenticator in wenlogic, and I want to do assignment at human task. But, human task only see jazn users, alhough I see the users defined in db at weblogic console
    Caused By: ORABPEL-10509
    User not found.
    User "bpmuser1" is not found in configuration "jazn.com"
    Check if the user exists in the repository specified by the configurations. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
    at oracle.tip.pc.services.identity.jps.JpsProvider.lookupUser(JpsProvider.java:795)
    at oracle.tip.pc.services.identity.jps.AuthorizationServiceImpl.lookupUser(AuthorizationServiceImpl.java:223)
    at oracle.tip.pc.services.identity.jps.IdentityServiceImpl.lookupUser(IdentityServiceImpl.java:171)
    at oracle.bpel.services.workflow.verification.impl.VerificationService.lookupUser(VerificationService.java:3670)
    at oracle.bpel.services.workflow.verification.impl.VerificationService.c
    How do I make users from myrealm in WLS available to the worklist app?

    Hi ppssrr,
    Check the providers are in "SUFFICIENT" mode,both, DefaultAutenticator as your own.
    Other way:
    If I remember correctly, you can use "External Routing", creating an allocation rule from an external supplier.
    Then assign participant based on that rule as.
    More info: Configuring Human Tasks - 11g Release 1 (11.1.1.7)
    Greetings.

  • PWA : Timesheet Manager list not available when submitting TS for Approval

    I've set the Timesheet Managers users in PWA settings and unchecked ‘Fixed
    Approval Routing’.
    On
    submitting the TS for approval in the sending request the control to choose the TS manager approver
    is missing... as there was a fixed route, but it's not the case.

    Hi,
    Please refer to this
    article.
    When you uncheck the fixed approval routing, while submitting a timesheet, Project Server will popup the list of predefined timesheet managers so the user can choose who will be approving his timesheet.
    If you check the option, then Project Server will send the timesheet for approval to the timesheet manager of the user (as it used to be in PS2010).
    Hope this helps,
    Guillaume Rouyre, MBA, MVP, P-Seller |

  • Supplier list not available

    Hi,
    I have created sales order successfully using the id proc_sales. while creating PO using proc_agent user, I need to assign the supplier to the sales order qty which is required to be procuired.
    Now when  I am going to select suplier, It is not showing any supplier, I am stuck here How to get the supplier list.
    Please suggest...
    Regards,
    Sanjeev Mourya

    Hi
    Please find the below log files details.
    LOG File details -
    was sent from host with IP= / Name=. Expiration reason was: . RID=
    [EXCEPTION]
    #6#/webdynpro/dispatcher/sap.com/cafeugpuirtwc/WorkCenterRunTime#127.0.0.1#127.0.0.1#Application session has expired. Please restart the application.#7936e4c0e82b11dbbf9b0018fe79f67c#com.sap.tc.webdynpro.clientserver.session.SessionExpiredLongJumpException: Application session has expired. Please restart the application.
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doSessionManagementPostProcessing(ClientSession.java:800)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:251)
         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.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: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)
    #1.5#0018FE79F67C0068000009400000090400042DD5BD5E66D5#1176295935259#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_1##0#0#Error##Plain###Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.clientserver.session.SessionExpiredLongJumpException: Application session has expired. Please restart the application.
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doSessionManagementPostProcessing(ClientSession.java:800)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:251)
         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.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: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)
    #1.5#0018FE79F67C0068000009420000090400042DD5BD5E6975#1176295935259#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_1##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: com.sap.tc.webdynpro.clientserver.session.SessionExpiredLongJumpException: Application session has expired. Please restart the application.
    Exception id: [0018FE79F67C0068000009400000090400042DD5BD5E66D5]#
    #1.5#0018FE79F67C005E00000D3F0000090400042DD5BD658E5F#1176295935728#com.sap.workflow.wizard.reg.JWFWizardConnector#sap.com/tcwddispwda#com.sap.workflow.wizard.reg.JWFWizardConnector#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###getAllInstances:null#
    #1.5#0018FE79F67C005E00000D400000090400042DD5BD658F2D#1176295935728#com.sap.workflow.wizard.reg.JWFWizardConnector#sap.com/tcwddispwda#com.sap.workflow.wizard.reg.JWFWizardConnector#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###getAllInstances:null#
    #1.5#0018FE79F67C005E00000D410000090400042DD5BD684A37#1176295935916#com.sap.esadiscovery.component.supplier.SuppliersListCompV2Interface#sap.com/tcwddispwda#com.sap.esadiscovery.component.supplier.SuppliersListCompV2Interface#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###In execute() --- begin#
    #1.5#0018FE79F67C006B00000AC70000090400042DD5BD7791A2#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###javax.resource.spi.EISSystemException: failed to connect server localhost due to:com.sap.mdm.net.ConnectionException: Unable to create new connection.#
    #1.5#0018FE79F67C006B00000AC80000090400042DD5BD77972E#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.utils.CatalogDataPoolingManager.init(CatalogDataPoolingManager.java:255)#
    #1.5#0018FE79F67C006B00000AC90000090400042DD5BD7797AF#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.utils.CatalogDataPoolingManager.getCatalog(CatalogDataPoolingManager.java:127)#
    #1.5#0018FE79F67C006B00000ACA0000090400042DD5BD779824#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.connection.MdmManagedConnectionFactory.createManagedConnection(MdmManagedConnectionFactory.java:102)#
    #1.5#0018FE79F67C006B00000ACB0000090400042DD5BD779899#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:320)#
    #1.5#0018FE79F67C006B00000ACC0000090400042DD5BD779912#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:189)#
    #1.5#0018FE79F67C006B00000ACD0000090400042DD5BD779986#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:216)#
    #1.5#0018FE79F67C006B00000ACE0000090400042DD5BD7799F8#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.mdm.MDM_DAO.connectToMDM_Managed(MDM_DAO.java:90)#
    #1.5#0018FE79F67C006B00000ACF0000090400042DD5BD779A68#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.mdm.MDM_DAO.getSuppliers(MDM_DAO.java:689)#
    #1.5#0018FE79F67C006B00000AD00000090400042DD5BD779AD6#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBBean.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBBean.java:47)#
    #1.5#0018FE79F67C006B00000AD10000090400042DD5BD779B55#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.java:103)#
    #1.5#0018FE79F67C006B00000AD20000090400042DD5BD779BD0#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)#
    #1.5#0018FE79F67C006B00000AD30000090400042DD5BD779C3E#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)#
    #1.5#0018FE79F67C006B00000AD40000090400042DD5BD779CAF#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)#
    #1.5#0018FE79F67C006B00000AD50000090400042DD5BD779D1F#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at java.lang.reflect.Method.invoke(Method.java:324)#
    #1.5#0018FE79F67C006B00000AD60000090400042DD5BD779D8D#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)#
    #1.5#0018FE79F67C006B00000AD70000090400042DD5BD779E02#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)#
    #1.5#0018FE79F67C006B00000AD80000090400042DD5BD779E78#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)#
    #1.5#0018FE79F67C006B00000AD90000090400042DD5BD779EEF#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)#
    #1.5#0018FE79F67C006B00000ADA0000090400042DD5BD779F63#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at SoapServlet.doPost(SoapServlet.java:51)#
    #1.5#0018FE79F67C006B00000ADB0000090400042DD5BD779FCE#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)#
    #1.5#0018FE79F67C006B00000ADC0000090400042DD5BD77A03C#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5#0018FE79F67C006B00000ADD0000090400042DD5BD77A0AB#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)#
    #1.5#0018FE79F67C006B00000ADE0000090400042DD5BD77A11D#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)#
    #1.5#0018FE79F67C006B00000ADF0000090400042DD5BD77A190#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)#
    #1.5#0018FE79F67C006B00000AE00000090400042DD5BD77A203#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)#
    #1.5#0018FE79F67C006B00000AE10000090400042DD5BD77A275#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)#
    #1.5#0018FE79F67C006B00000AE20000090400042DD5BD77A2F0#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)#
    #1.5#0018FE79F67C006B00000AE30000090400042DD5BD77A362#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
    #1.5#0018FE79F67C006B00000AE40000090400042DD5BD77A3D5#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
    #1.5#0018FE79F67C006B00000AE50000090400042DD5BD77A446#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
    #1.5#0018FE79F67C006B00000AE60000090400042DD5BD77A4BC#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
    #1.5#0018FE79F67C006B00000AE70000090400042DD5BD77A52D#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5#0018FE79F67C006B00000AE80000090400042DD5BD77A59A#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5#0018FE79F67C006B00000AE90000090400042DD5BD77A608#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
    #1.5#0018FE79F67C006B00000AEA0000090400042DD5BD77A67D#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
    #1.5#0018FE79F67C006B00000AEB0000090400042DD5BD77A700#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###javax.resource.spi.EISSystemException: failed to connect server localhost due to:com.sap.mdm.net.ConnectionException: Unable to create new connection.#
    #1.5#0018FE79F67C006B00000AEC0000090400042DD5BD77A778#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.utils.CatalogDataPoolingManager.init(CatalogDataPoolingManager.java:255)#
    #1.5#0018FE79F67C006B00000AED0000090400042DD5BD77A7E8#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.utils.CatalogDataPoolingManager.getCatalog(CatalogDataPoolingManager.java:127)#
    #1.5#0018FE79F67C006B00000AEE0000090400042DD5BD77A859#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.connection.MdmManagedConnectionFactory.createManagedConnection(MdmManagedConnectionFactory.java:102)#
    #1.5#0018FE79F67C006B00000AEF0000090400042DD5BD77A8CD#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:320)#
    #1.5#0018FE79F67C006B00000AF00000090400042DD5BD77A940#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:189)#
    #1.5#0018FE79F67C006B00000AF10000090400042DD5BD77A9B3#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:216)#
    #1.5#0018FE79F67C006B00000AF20000090400042DD5BD77AA29#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.mdm.MDM_DAO.connectToMDM_Managed(MDM_DAO.java:90)#
    #1.5#0018FE79F67C006B00000AF30000090400042DD5BD77AA96#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.mdm.MDM_DAO.getSuppliers(MDM_DAO.java:689)#
    #1.5#0018FE79F67C006B00000AF40000090400042DD5BD77AB04#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBBean.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBBean.java:47)#
    #1.5#0018FE79F67C006B00000AF50000090400042DD5BD77AB7C#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.java:103)#
    #1.5#0018FE79F67C006B00000AF60000090400042DD5BD77ABF5#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)#
    #1.5#0018FE79F67C006B00000AF70000090400042DD5BD77AC61#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)#
    #1.5#0018FE79F67C006B00000AF80000090400042DD5BD77ACCF#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)#
    #1.5#0018FE79F67C006B00000AF90000090400042DD5BD77AD3E#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at java.lang.reflect.Method.invoke(Method.java:324)#
    #1.5#0018FE79F67C006B00000AFA0000090400042DD5BD77ADA9#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)#
    #1.5#0018FE79F67C006B00000AFB0000090400042DD5BD77AE28#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)#
    #1.5#0018FE79F67C006B00000AFC0000090400042DD5BD77AE99#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)#
    #1.5#0018FE79F67C006B00000AFD0000090400042DD5BD77AF0A#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)#
    #1.5#0018FE79F67C006B00000AFE0000090400042DD5BD77AF7C#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at SoapServlet.doPost(SoapServlet.java:51)#
    #1.5#0018FE79F67C006B00000AFF0000090400042DD5BD77AFE6#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)#
    #1.5#0018FE79F67C006B00000B000000090400042DD5BD77B051#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5#0018FE79F67C006B00000B010000090400042DD5BD77B0BD#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)#
    #1.5#0018FE79F67C006B00000B020000090400042DD5BD77B12D#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)#
    #1.5#0018FE79F67C006B00000B030000090400042DD5BD77B19E#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)#
    #1.5#0018FE79F67C006B00000B040000090400042DD5BD77B216#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)#
    #1.5#0018FE79F67C006B00000B050000090400042DD5BD77B287#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)#
    #1.5#0018FE79F67C006B00000B060000090400042DD5BD77B2F8#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)#
    #1.5#0018FE79F67C006B00000B070000090400042DD5BD77B36B#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
    #1.5#0018FE79F67C006B00000B080000090400042DD5BD77B3D8#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
    #1.5#0018FE79F67C006B00000B090000090400042DD5BD77B448#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
    #1.5#0018FE79F67C006B00000B0A0000090400042DD5BD77B4BE#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
    #1.5#0018FE79F67C006B00000B0B0000090400042DD5BD77B52C#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5#0018FE79F67C006B00000B0C0000090400042DD5BD77B59C#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5#0018FE79F67C006B00000B0D0000090400042DD5BD77B608#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
    #1.5#0018FE79F67C006B00000B0E0000090400042DD5BD77B676#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
    #1.5#0018FE79F67C006B00000B0F0000090400042DD5BD77B716#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: failed to connect server localhost due to:com.sap.mdm.net.ConnectionException: Unable to create new connection.#
    #1.5#0018FE79F67C006B00000B100000090400042DD5BD77BACC#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:226)#
    #1.5#0018FE79F67C006B00000B110000090400042DD5BD77BB43#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.mdm.MDM_DAO.connectToMDM_Managed(MDM_DAO.java:90)#
    #1.5#0018FE79F67C006B00000B120000090400042DD5BD77BBAF#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.mdm.MDM_DAO.getSuppliers(MDM_DAO.java:689)#
    #1.5#0018FE79F67C006B00000B130000090400042DD5BD77BC1A#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBBean.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBBean.java:47)#
    #1.5#0018FE79F67C006B00000B140000090400042DD5BD77BC96#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.java:103)#
    #1.5#0018FE79F67C006B00000B150000090400042DD5BD77BD0D#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)#
    #1.5#0018FE79F67C006B00000B160000090400042DD5BD77BD7D#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)#
    #1.5#0018FE79F67C006B00000B170000090400042DD5BD77BDEB#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)#
    #1.5#0018FE79F67C006B00000B180000090400042DD5BD77BE59#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at java.lang.reflect.Method.invoke(Method.java:324)#
    #1.5#0018FE79F67C006B00000B190000090400042DD5BD77BEC3#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)#
    #1.5#0018FE79F67C006B00000B1A0000090400042DD5BD77BF36#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)#
    #1.5#0018FE79F67C006B00000B1B0000090400042DD5BD77BFA4#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)#
    #1.5#0018FE79F67C006B00000B1C0000090400042DD5BD77C014#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)#
    #1.5#0018FE79F67C006B00000B1D0000090400042DD5BD77C085#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at SoapServlet.doPost(SoapServlet.java:51)#
    #1.5#0018FE79F67C006B00000B1E0000090400042DD5BD77C0EE#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)#
    #1.5#0018FE79F67C006B00000B1F0000090400042DD5BD77C162#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5#0018FE79F67C006B00000B200000090400042DD5BD77C1CD#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)#
    #1.5#0018FE79F67C006B00000B210000090400042DD5BD77C23B#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)#
    #1.5#0018FE79F67C006B00000B220000090400042DD5BD77C2AB#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)#
    #1.5#0018FE79F67C006B00000B230000090400042DD5BD77C31A#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)#
    #1.5#0018FE79F67C006B00000B240000090400042DD5BD77C388#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)#
    #1.5#0018FE79F67C006B00000B250000090400042DD5BD77C3F8#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)#
    #1.5#0018FE79F67C006B00000B260000090400042DD5BD77C467#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
    #1.5#0018FE79F67C006B00000B270000090400042DD5BD77C4D9#1176295936916#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
    #1.5#0018FE79F67C006B00000B280000090400042DD5BD77C547#1176295936931#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
    #1.5#0018FE79F67C006B00000B290000090400042DD5BD77C5BC#1176295936931#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
    #1.5#0018FE79F67C006B00000B2A0000090400042DD5BD77C629#1176295936931#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5#0018FE79F67C006B00000B2B0000090400042DD5BD77C696#1176295936931#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5#0018FE79F67C006B00000B2C0000090400042DD5BD77C701#1176295936931#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
    #1.5#0018FE79F67C006B00000B2D0000090400042DD5BD77C76E#1176295936931#System.err#sap.com/XApps_GetSuppliersByProductID_WS_Ear#System.err#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
    #1.5#0018FE79F67C006B00000B2E0000090400042DD5BD77D08A#1176295936931#com.sap.engine.services.ejb#sap.com/XApps_GetSuppliersByProductID_WS_Ear#com.sap.engine.services.ejb#J2EE_GUEST#0####7a360540e82b11dbb48a0018fe79f67c#SAPEngine_Application_Thread[impl:3]_130##0#0#Error##Java###
    [EXCEPTION]
    #1#com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method getSuppliersByProductID.
         at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.java:119)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
         at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
         at SoapServlet.doPost(SoapServlet.java:51)
         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)
    Caused by: java.lang.NullPointerException
         at com.sap.esadiscovery.mdm.MDM_DAO.disconnectToMDM_Managed(MDM_DAO.java:54)
         at com.sap.esadiscovery.mdm.MDM_DAO.getSuppliers(MDM_DAO.java:699)
         at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBBean.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBBean.java:47)
         at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.java:103)
         ... 25 more
    java.lang.NullPointerException
         at com.sap.esadiscovery.mdm.MDM_DAO.disconnectToMDM_Managed(MDM_DAO.java:54)
         at com.sap.esadiscovery.mdm.MDM_DAO.getSuppliers(MDM_DAO.java:699)
         at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBBean.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBBean.java:47)
         at com.sap.esadiscovery.ejb.getsuppliers.XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.getSuppliersByProductID(XApps_GetSuppliersByProductID_WS_EJBLocalLocalObjectImpl0.java:103)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
         at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
         at SoapServlet.doPost(SoapServlet.java:51)
         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)
    #1.5#0018FE79F67C005E00000D420000090400042DD5BD77DCA2#1176295936931#com.sap.esadiscovery.component.supplier.SuppliersListCompV2Interface#sap.com/tcwddispwda#com.sap.esadiscovery.component.supplier.SuppliersListCompV2Interface#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###In execute() --- error#
    #1.5#0018FE79F67C005E00000D430000090400042DD5BD77DD22#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###javax.xml.rpc.soap.SOAPFaultException: Exception in method getSuppliersByProductID.#
    #1.5#0018FE79F67C005E00000D440000090400042DD5BD77E33D#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:735)#
    #1.5#0018FE79F67C005E00000D450000090400042DD5BD77E3B5#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:857)#
    #1.5#0018FE79F67C005E00000D460000090400042DD5BD77E411#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1432)#
    #1.5#0018FE79F67C005E00000D470000090400042DD5BD77E46B#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.esadiscovery.model.supplier.proxies.Config1BindingStub.getSuppliersByProductID(Config1BindingStub.java:73)#
    #1.5#0018FE79F67C005E00000D480000090400042DD5BD77E4C5#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.esadiscovery.model.supplier.proxies.Config1BindingStub.getSuppliersByProductID(Config1BindingStub.java:89)#
    #1.5#0018FE79F67C005E00000D490000090400042DD5BD77E51F#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.esadiscovery.model.supplier.Request_XAppsGetSupplierByProductID_WSViDocument_getSuppliersByProductID.execute(Request_XAppsGetSupplierByProductID_WSViDocument_getSuppliersByProductID.java:89)#
    #1.5#0018FE79F67C005E00000D4A0000090400042DD5BD77E580#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.esadiscovery.component.supplier.SuppliersListCompV2Interface.execute(SuppliersListCompV2Interface.java:218)#
    #1.5#0018FE79F67C005E00000D4B0000090400042DD5BD77E5DB#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.esadiscovery.component.supplier.wdp.InternalSuppliersListCompV2Interface.execute(InternalSuppliersListCompV2Interface.java:171)#
    #1.5#0018FE79F67C005E00000D4C0000090400042DD5BD77E637#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.esadiscovery.component.supplier.wdp.InternalSuppliersListCompV2Interface$External.execute(InternalSuppliersListCompV2Interface.java:225)#
    #1.5#0018FE79F67C005E00000D4D0000090400042DD5BD77E694#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.caf.eu.gp.ui.co.exec.wd.COExecWD.execute(COExecWD.java:303)#
    #1.5#0018FE79F67C005E00000D4E0000090400042DD5BD77E6EA#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWD.execute(InternalCOExecWD.java:170)#
    #1.5#0018FE79F67C005E00000D4F0000090400042DD5BD77E742#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.caf.eu.gp.ui.co.exec.wd.COExecWDInterface.execute(COExecWDInterface.java:122)#
    #1.5#0018FE79F67C005E00000D500000090400042DD5BD77E79D#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWDInterface.execute(InternalCOExecWDInterface.java:132)#
    #1.5#0018FE79F67C005E00000D510000090400042DD5BD77E7F7#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWDInterface$External.execute(InternalCOExecWDInterface.java:243)#
    #1.5#0018FE79F67C005E00000D520000090400042DD5BD77E851#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.caf.eu.gp.ui.act.container.VContainer.onPlugFromDispatcher(VContainer.java:367)#
    #1.5#0018FE79F67C005E00000D530000090400042DD5BD77E8AA#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.caf.eu.gp.ui.act.container.wdp.InternalVContainer.wdInvokeEventHandler(InternalVContainer.java:167)#
    #1.5#0018FE79F67C005E00000D540000090400042DD5BD77E903#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)#
    #1.5#0018FE79F67C005E00000D550000090400042DD5BD77E95C#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)#
    #1.5#0018FE79F67C005E00000D560000090400042DD5BD77E9B5#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)#
    #1.5#0018FE79F67C005E00000D570000090400042DD5BD77EA0D#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)#
    #1.5#0018FE79F67C005E00000D580000090400042DD5BD77EA66#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)#
    #1.5#0018FE79F67C005E00000D590000090400042DD5BD77EABF#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)#
    #1.5#0018FE79F67C005E00000D5A0000090400042DD5BD77EB18#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)#
    #1.5#0018FE79F67C005E00000D5B0000090400042DD5BD77EB73#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)#
    #1.5#0018FE79F67C005E00000D5C0000090400042DD5BD77EBCC#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:727)#
    #1.5#0018FE79F67C005E00000D5D0000090400042DD5BD77EC26#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:663)#
    #1.5#0018FE79F67C005E00000D5E0000090400042DD5BD77EC7F#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:229)#
    #1.5#0018FE79F67C005E00000D5F0000090400042DD5BD77ECD8#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)#
    #1.5#0018FE79F67C005E00000D600000090400042DD5BD77ED30#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)#
    #1.5#0018FE79F67C005E00000D610000090400042DD5BD77ED8A#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:877)#
    #1.5#0018FE79F67C005E00000D620000090400042DD5BD77EDE6#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_103929350#PROC_AGENT#1f7dfdb0e82b11dbbb620018fe79f67c#SAPEngine_Application_Thread[impl:3]_123##0#0#Error##Plain###     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:227)#
    #1.5#0018FE79F67C005E00000D630000090400042DD5BD77EE3F#1176295936931#System.err#sap.com/tcwddispwda#System.err#PROC_AGENT#83468##iwdfvm2160.ad_ERP_10

  • Pages in offline reading list not available after powering off iPad

    Try this on your iPad:
    1. In safari, save a few web pages to your reading list
    2. Set the iPad to airplane mode
    3. Power off your iPad
    4. Power it back on
    5. Try reading the pages in your reading list
    This is what I did when going on a flight. Most of the pages I had saved could not be displayed once in the air. Some pages could be displayed, but only once. Once I left the page, I could it not bring back up a second time.
    Does anyone experience the same? In my case, the trigger of the problem seems to be powering off the iPad (which is what you are supposed to do during airplane take off).
    Any ideas how I can resolve the issue, other than not powering the iPad off?
    Thank you!

    I could not reproduce the behavior that you are experiencing in Safari. I have no problems at all using the Reading List in Airplane mode after turning the iPad off and on again. You can try some basic housekeeping stuff with Safari and the iPad.
    Clear the Safari cache and see if that helps, reboot the iPad and see if that helps. You can also try closing Safari before you power off so that you are launching Safari all over again rather than just activating it from the inactive state in the task bar.
    Go to Settings>Safari>Clear History, Cookies and Data. Clearing history is not a necessity.
    Reboot the iPad by holding down on the sleep and home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider - let go of the buttons.
    Quit the app completely and relaunch after start up. Go to the home screen first by tapping the home button. Double tap the home button and the task bar will appear with all of your recent/open apps displayed at the bottom. Tap and hold down on any app icon until it begins to wiggle. Tap the minus sign in the upper left corner of the app that you want to close. Tap the home button or anywhere above the task bar. Restart the iPad and launch Safari again.

  • Oracle Reports Components list not available in BI Publisher

    I have configured the Oracle Report Security settings in oracle Business intelligence publisher, Add oracle report, when i try to ADD report in region, it didn't display Oracle Reports Components list. Pl suggest, what should i do
    Regards,

    I had a similar issue in 10.3.3.1.
    Try this:
    http://oraclebizint.wordpress.com/2007/11/06/oracle-bi-publisher-and-bi-ee-invisible-admin-tab/

  • Hierarchy info-package list not available when adding to process chain.

    Knowledgable experts:
    We are on BI 7.0 and I'm trying to add an info-package for a hierarchy load to a process chain.
    The process chain already exists with master data text loads and attribute loads.
    I want to add a hierarchy load to the process chain.
    - When I select Execute Infopackage process type the pop up box to 'Insert Execute Infopackage' is displayed.
    - The Load Data dropdown box does not display any infopackages to choose from. The infopackage does exist and executes correctly.
    Why can't I see any infopackages in the dropdown box?
    We are on SAPKW70013 Support package.
    Thanks for your assistance.
    Den

    Thanks for the quick reply.
    This is a new install, no upgrade.
    I think I found that I need to do a Save Hierarchy process type to get the hierarchy in the process chain.
    However, I would still have the question, why I don't see any of my transaction data loads that are in 3.x formats?
    I will look at the OSS note.
    Thanks
    Den

  • Publishing site announcement list, calendar list not available even activating feature

    " Team Collaboration List " feature is activated on publishing site. Again deactivated and activated, browser restarted, but the problem exists. No announcement list, task list, calendar list template found.
    Please let me know the way to fix the issue.

    Hi Shilabhadra,
    According to your description, my understanding is that you want to use announcement, task list, calendar list template at publishing site in SharePoint 2013.
    Please try to use PowerShell commands to disable and enable " Team Collaboration List " feature at your publishing site. You can do as opening SharePoint 2013 Management Shell, then typing the following commands:
    Disable-SPFeature –Identity 00BFEA71-4EA5-48D4-A4AD-7EA5C011ABE5 -url <the url of the publishing site>
    Enable-SPFeature –Identity 00BFEA71-4EA5-48D4-A4AD-7EA5C011ABE5 -url <the url of the publishing site>
    In the above commands, 00BFEA71-4EA5-48D4-A4AD-7EA5C011ABE5  is the identity of " Team Collaboration List " feature.
    More information, please refer to the links:
    http://platinumdogs.me/2009/12/10/team-collaboration-and-publishing-features/
    http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2011/01/04/activating-and-deactivating-features-with-powershell-in-sharepoint-2010.aspx
    I hope this helps.
    Thanks,
    Wendy
    Wendy Li
    TechNet Community Support

  • Background Job  & Spool List Recipient not receiving all pages

    I have a program that is run during our nightly cycle and is scheduled in SM36 with a spool list recipient designated for the report to be delivered to the user's SAP Inbox.  The job completes successfully and creates a report that is over 100 pages.  The user is only receiving 10 pages in their SAP Inbox.  Is this a Basis system setting?  Can we changes this on a per user basis?
    Thanks,
    Holly

    Hi Holly,
    it's sound like the <b>SAP-Note: 329537</b>
    Symptom
    If a batch job creates a spool and sends it to a recipients, only the first 1000 lines are sent.
    Other terms
    SAPOffice, spool list recipient
    Reason and Prerequisites
    For performance reasons, the output sent to SAPOffice is limited to 1000 lines.
    Solution
    If you wish to send spools longer than 1000 lines in Releases > 4.6B, proceeed as follows:
    1. Apply the support packages or correction instructions mentioned in this note.
    2. Create the following two entries in table TSPOPTIONS with transaction SE16:
                  option: BTC_FIRSTLINE value: < desired value, probably 1>
                  option: BTC_LASTLINE  value: < desired value, e.g. 99999>
    1. Call function module RSPO_OPTION_FLUSH with value NAME = '*'.
    Please note that this change may impact performance, depending on the selected line interval.
    In Releases < 4.6C or if you are not able to apply the support packages or corrections, you can accomplish this with a minor code change.
    In program RSBTCRTE, change the parameter sent to the function module
    RSPO_SPOOLJOB_TO_OFFICE as follows:
    call function 'RSPO_SPOOLJOB_TO_OFFICE'
         exporting
          rqident              =
    spo_list_id
             first_line         
    = 1
    last_line            =
    1000            "<<<  Delete
            last_line            =
    99999           "<<<  Insert
            receiver           
    = recipient_object
             mail_title         
    = document_data-obj_descr
          exceptions

  • Custom playbar does not display in the list of available widgets

    I followed the steps described in the "Skins" page of the Captivate 5 help outlined here:
    http://help.adobe.com/en_US/captivate/cp/using/WSc1b83f70210cd101126156ac11c7f147d6b-8000. html
    Now my problem is, that my custom playbar is not displayed in the list of available playbars (neither in the Project->Skin Editor->Playbar nor in the list of widgets). If I just duplicate one of the existing playbar files in Gallery/Widgets/Playbars it's listed without problems.
    I use Flash CS5 to edit the playbar and tried to publish it as AS3 and AS2 - no success.
    Are there special settings I need to set in the publishing settings to get my playbar in the list? Anything else I'm missing?!
    Thanks,
    Peter

    Try putting the swf for the playbar in ...\Adobe Captivate 5\en_GB\Gallery\Playbars\AS3\

  • In manage add-ons, Adobe Flash Player is listed under Not Available, but is listed as enabled.

    When trying to view something that needs flash player, it tells me that I need to have flash player to do this.  So I go to install it, and it tells me it is already installed with my Windows 8.  So, then it tells me to either Enable flash player or to disable Active x filtering.  Active x filtering is not enabled, so I go to Manage add ons, and it shows that Shockwave Flash Object is listed under the heading NOT AVAILABLE, but is listed as being enabled.  I have tried to reinstall flash player, but it won't let me because it is already installed.  Not sure why it is showing up under Not Available, and not under the Adobe heading with my Adobe PDF reader.  Can anyone tell me how to get flash player back from this point???

    Please ask your question on a forum for the Flash Player

Maybe you are looking for

  • IPad 3 problems

    1- Its not compatible with adobe flash player & hard to find a free compatible app that work same adobe flash player , 2- hard to print from safari or any other program even the emails  unless if I buy a special app to make my wifi printer be complet

  • PMG4 MDD Power Supply dead? Where can I get one?

    Does anyone know of another source for the PMG4 MDD Power Supply? When I press the power button to turn it on, nothing happens. Yes, I have reset the PMU, replaced the battery, left it unplugged overnight, and still nothing at all, no lights noises o

  • MAC Authentication Bybass

    When using MAC authentication Bypass and a switch is reset because of an upgrade, there is a period of 1 to 2 minutes when the MAB fails after the switch is already back up. Logging in to the switch also fails during this time.Is there a way to get r

  • Are there any keyboard shortcuts for navigating conversation view?

    In sparrow- which I'm coming over from due to it's support of Gmail, you can use various keyboard shortcuts to move back and forth in the thread. I prefer the Mail layout, but might have to go back if I have to click everywhere!

  • Mac Performa 200 OS

    Which version of the Mac OS is best for playing old Sierra games on a Mac Performa 200? I was thinking of either using Mac OS 6.0.8L or Mac OS 7.1 or Mac OS 7.5.5. I have 12 MB of RAM (of course only 10 MB are usable).