Modeling Suppliers As Orgs

Our company is implementing ASCP and we're debating whether to model our contract manufacturers as supplier orgs. We have a requirement to manage the collaborations of critical components, and the standard way to do that is via supplier orgs (multi-tier planning). Our fear is that collecting all the necessary data into a supplier org will be nearly impossible. Have others had success doing this? Would you do it again? Any lessons learned?
I'm guessing we'd use legacy intergration, and only load the data to the planning server since we don't need to track the financials. We'd start with maybe one or two CM sites.
Thanks!

Hello Patrick,
Are you interested in planning of critical components(simply the lead time and production process) manufactured by Supplier
if you say yes, you may need to think about the following
1.Is your supplier is in house supplier or remote part.
2.How frequently the supplier production progress information can be collected from your supplier?
3.progress entries in system
In all case if you are planning to define supplier org, the following are the key points need to be addressed.
1.Costing of procured item from the supplier.
2.How the Purchasing and payment to the supplier will happen in your system( since the item is virtually processed in your system).
3.How flexible is your client is in going with double entries like IR & ISO Cycle for planning and Actual purchasing process?
Warm Regards
Sivaraman.G

Similar Messages

  • (Org Model) Obtain Sales org's object id from position object id.

    Hi All,
    In the org model, I have the object id of a position and i want to find the object id of the sales org to which this position is assigned.
    Is there any FM that does this..?
    Thanks in Advance,
    Raviraj

    Hi Gun,
    When i tried tu check out this FM, COM_OM_ORGUNITS_OF_MANAGER, it says "NOTHING_FOUND"
    the params i passed are :
    PLVAR                         
    MGR_OTYPE     O
    MGR_OBJID     50001049   => position id of the user
    SELDATE       02/28/2006
    NO_DIALOG     X
    SEL_MULTIPLE  X
    am i missing something ?
    The hierarchy is :
    SOME_SALES_ORG
            |
            |-- ASSIGNED_PERSON
    I have the ID of this person and want the ID of the sales org
    regards,
    raviraj
    Message was edited by: Raviraj Khare

  • Assigning position hierarchy within Org Model

    Hi,
    have maintained the org model with sales org and position in crm 5.0. This position is President sales and would like to maintain General Manager under this position as a subordinate. While doing so, I get the following message:
    <b>Before you select a function, select suitable entries in the structure.
        Message no. 5W707
    Diagnosis
        You have chosen a function for which a selection of  suitable entries in the structure is a prerequisite.
    Procedure
        Select one or more suitable functions in the structure and choose the function again. You can use the right mouse-button to display all the functions you can carry out for an entry.</b>
    What else am I missing here
    Thanks
    Kumar

    Hi Diana,
    Thanks for the inputs. I have rewarded points.
    As per your mail, we could maintain two positions under single organization unit one with the 'head of org unit' check and the other without that. Now they both appear under the same org unit but they appear as two positions (only difference is that the icons are different).
    What I am looking at is, Sales Org 1 should have a sub tree (arrow mark) with Mgr Director position, when I drop down this positions arrow mark, then I only I should be able to see the General Mgr's position (the GM's position should not appear parallel to the MD's position on the tree structure but should be within the MD's position)
    Can we assign any position to the head position by any standard means ?
    Hope you got my requirement clear, else let me know I can explain in more detail.
    Thanks
    Kumar

  • Java.lang.ClassCastException: org.model.Question

    I'm trying to typecast a list of question Objects to Object StudyQuestionPage. Im doing this becase i want to set the list of question to its boolean validate property to validate the return of validate. Im getting a typecast error:
    [ROOT] ERROR [http-8080-1] DispatcherUtils.serviceAction(237) | Could not execute action
    java.lang.ClassCastException: org.model.Question
    at org.webapp.action.DemogAction.saveQuesOrder(DemogAction.java:1147).
    Here is the code of what im doing:
    questionsList = demogManager.getQuestions(sqp);
    for(Object sqpTemp:questionsList){
         questionTemp = (StudyQuestionsPage)sqpTemp; <---- /* im getting the line error here*/
         questionTemp.setValidate(validate);
         studyPageManager.saveStudyPage(sqp);
    }

    shendel wrote:
    I'm trying to typecast a list of question Objects to Object StudyQuestionPage. Im doing this becase i want to set the list of question to its boolean validate property to validate the return of validate. Im getting a typecast error:
    [ROOT] ERROR [http-8080-1] DispatcherUtils.serviceAction(237) | Could not execute action
    java.lang.ClassCastException: org.model.Question
    at org.webapp.action.DemogAction.saveQuesOrder(DemogAction.java:1147).Okay so?
    You don't have a StudyQuestionPage you have an org.model.Question. If StudyQuestionPage extended org.model.Question then you could, but it doesn't so you can't.

  • BOM Supply Type - How does it default ?

    Can anyone please tell me how the Supply Type flag under Material Control tab on the BOM form is defaulted ? I have checked the profile BOM: WIP Default component type.
    Scenario:
    1.Created items:
    TEST ATO 1 - Created with template - ATO model, Supply Type=Assembly Pull
    TEST ATO 2 - Created with template - ATO model, Supply Type=Assembly Pull
    2. Created BOM
    TEST ATO 1
    |--- TEST ATO 2
    For TEST ATO 2, the supply type is being defaulted to 'Phantom' and not 'Assembly Pull'
    Suggestions please ?

    Sandeep Gandhi, Independent Consultant wrote:
    It takes the supply type from the org item record.
    Can you double check the supply type on org item?I am also seeing the same behaviour..
    I did check at item level too..
    Please advise
    Thanks
    Mahendra

  • PO not visible in WEBUI when Multiple Sup. loc linked to one Sup Org BP,SNC

    Hi,
    We are implementing SAP SNC 7.0 and started small testing's.
    When one supplier location(each individually) is assigned to Supplier org BP, PO is visible in WEBUI.
    When two supplier location is assigned to one supplier org BP, PO is not visible and message says"Order not found for the selection"
    Whereas when i go to SMI details, it shows data for both supplier location in WEBUI.
    Their is no visibility of POand demand.
    Thanks & Regards,
    Siva

    Hi Siva,
    You have created PO when one supplier location(each individually) is assigned to Supplier org BP.
    In Purchase order Supplier field=<Supplier BP Org> so when two supplier location is assigned to one supplier org BP you have removed supplier BP org for which you have created Purchase order and this is the reason why it is not visible.
    Eaxmple:
    Supplier1:10000
    Supplier2:20000
    Case 1)when one supplier location(each individually) is assigned to Supplier org BP
    say Supplier1:10000 is assigned to supplier Org BP=10000
    say Supplier2:20000 is assigned to supplier Org BP=20000
    and you have created Purchase order 45000001 for supplier 10000.
    Case 2) when two supplier location is assigned to one supplier org BP
    say Supplier1:10000 and Supplier2:20000  is assigned to supplier Org BP=20000
    or
    supplier Org BP=30000 then you won't be able to see purchase order in SNC web UI as when you have created purchase order supplier BP org was 10000 and now it is 30000 or 20000.
    Regards,
    Nikhil

  • List partitioning multi-org tables

    Hi
    I am doing list partitioning on receivables multi-org tables on org_id column. Running into a performance problem with multi org views. The multi-org views for receivables tables are defined like below with a nvl condition on org_id (partitioned column) in their where clause
    create or replace ra_customer_trx
    select select * from ra_customer_trx_all
    WHERE NVL(ORG_ID,NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV ('CLIENT_INFO'),1,1), ' ', NULL, SUBSTRB(USERENV ('CLIENT_INFO'),1,10))),-99)) = NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV ('CLIENT_INFO'),1,1), ' ', NULL, SUBSTRB(USERENV ('CLIENT_INFO'),1,10))),-99)
    Queries against the view are doing all partition scan when I exptected partition pruning to kick in and the query goes only against the spefific partition.
    select count(1) from ra_customer_trx ---- does all partition scan
    select count(1) from ra_customer_trx_all where org_id = <> ---- does single partition scan, works well.
    When I recreate the view with out any function calls on the org_id column partition pruning happens.
    In a non partitioned environment which has an index on org_id column, both the above sqls use the index and yield same result.
    So my questions are -
    1. Is there a way to get around this problem without having to modify the oracle supplied multi-org views? Any options I can supply in the partition script?
    2. In a non-partitioned env, with an index on org_id how is the optmizer able to go against the index and where as it is not able to in partitioned environment..? Both these envs has the same view definition with NVL(org.......) consition.
    Does anyone have any suggestions?
    Thank you.

    user2317378 wrote:
    1. Is there a way to get around this problem without having to modify the oracle supplied multi-org views? Any options I can supply in the partition script?You mean to say that the expression used in the view belongs to some Oracle supplied schema, like APPS? Or is this a view you've created yourself?
    Can you show us the output of EXPLAIN PLAN using DBMS_XPLAN.DISPLAY when querying the view? Use the \ tag before and after to use proper formatting in fixed font.
    Please make sure that the "Predicate Information" section below the plan is also included in your post. If it is missing your plan table is old and needs to be upgraded using $ORACLE_HOME/rdbms/admin/utlxplan.sql or dropped if you're in 10g which provides a system wide PLAN_TABLE.
    2. In a non-partitioned env, with an index on org_id how is the optmizer able to go against the index and where as it is not able to in partitioned environment..? Both these envs has the same view definition with NVL(org.......) consition.
    These are two different questions. One is about partition pruning not taking place, the other one about an index not being used.
    Can you show us the output of EXPLAIN PLAN using DBMS_XPLAN.DISPLAY when querying the unpartitioned example? Use the \ tag before and after to use proper formatting in fixed font.
    Please make sure that the "Predicate Information" section below the plan is also included in your post. If it is missing your plan table is old and needs to be upgraded using $ORACLE_HOME/rdbms/admin/utlxplan.sql or dropped if you're in 10g which provides a system wide PLAN_TABLE.
    It would be interesting to know how Oracle can use the index given the complex expression in the WHERE clause.
    Regards,
    Randolf
    Oracle related stuff blog:
    http://oracle-randolf.blogspot.com/
    SQLTools++ for Oracle (Open source Oracle GUI for Windows):
    http://www.sqltools-plusplus.org:7676/
    http://sourceforge.net/projects/sqlt-pp/

  • Org Unit Business Partner number missing

    Hi Guy's
    I have created some Org models with some Org units and positions in it... But for some reasons I could not able to see any business partner numbers assigned to these Org units..... I hope these numbers automatically come from CRM system...
    Could you tell me is it a Technical issue or Functional issue???
    Please let me know if you have any solution to resolve this
    Thank you very much in advance....

    Hi Sr,
    To get the role 'organizational unit'  for BP make sure you have  HRALX - OPROL - BUP004
    You can mail to [email protected]
    Regards,
    Paul Kondaveeti
    <b>Also see the help extract from customizing:</b>
    Set Up Integration with Organizational Management
    In this IMG activity, you integrate business partner data with HR master data (organizational model and employees).
    Activities
    1. Activate global HR integration by setting the main switch HRALX/HRAC to 'X'.
    2. Activate the integration between business partners and organizational units by setting the switch HRALX/OBPON to 'ON'.
    3. Activate the integration between business partners and employees by setting the switch HRALX/PBPON to 'ON'.
    4. Numbers can generally be assigned in three ways when creating business partners:
    a) Number is taken as before from the general internal interval for number range object BU_PARTNER.
    b) Number is taken from the special internal interval for the object.
    c) Number is taken from HR and given a prefix. A special external interval is used, which has to be defined as XX00000000 to XX99999999, where XX stands for any two letters.
    Number assignment is set for organizational units using HRALX/ONUMB, and for employees using HRALX/PNUMB.
    The number range object for all switch values is BU_PARTNER, the interval being dependent on the switch value. The internal standard interval is used for switch value 1, for switch values 2 and 3 the interval is defined by the switch HRALX/OSUBG or HRALX/PSUBG. For switch values 2 and 3, a grouping also needs be created for these intervals using transaction BUC2.
    To enable the system to connect the grouping and the number range interval, the name of the grouping must be exactly the same as that of the corresponding number range interval. The name of the grouping is in the first column of the table.
    If you choose number assignment type 3 for business partners with the role employee (switch HRALX/PNUMB = 3), create the switch HRALX/PSUBG manually in table T77S0.
    5. If you would like users to be informed by e-mail when errors occur, the recipient can be defined in switch HRALX/MSGRE (0=No messages, 1=Workflow administrator is notified, 2=User receives mail, 3=Both are informed).
    6. If addresses are required to generate business partners correctly, the switch HRALX/OADRE must be set to 'X'. The standard address to be assigned to every organizational unit without its own address can be defined using HRALX/OADBP.
    To create a standard address, create a business partner with an address and then enter this business partner's number in the switch.
    7. If qualifications for employees are also to be transferred, the switch HRALX/PQUAL must be set to 'X'.
    Effects on Existing Data
    If you have already transferred employees from a connected HR System in an earlier CRM Release and have now upgraded, the relevant employees (personnel numbers) must be transferred again to the CRM System by initial distribution. This enables important employee information to be stored in the target system, and changes to be transferred correctly to the business partner master records.
    Message was edited by:
            Paul Kondaveeti

  • Generating BP for each org unit

    hi friends ,
    when creating the org.model for each org.unit one BP is generated. wt is the purpose of generating BP for each org.unit.
    where we can use this one? pls guide me.
    thanking u in advance.

    hi there
    the purpose behind creation of BP for each org unit is to use that for the working inside the org
    see the BPs are created inside the system using three:
    person
    group
    org
    and then we differentiate them on the basis of the roles
    so when BP is generated for particluar org it assumes the specific role and later on the same role will work according to the rules determination inside the org
    else if you want to specify the attributes inside the org ,how would you be able to work around in the absence of BP
    see the thumb rule of CRM is that each and every iondividual is BP here ,so same goes here that if org has to fucntion then employees and customers should be there inside it so that something goes determined
    and if BPs are not there how would u achieve that
    guess i have cleared the doubt
    best regards
    ashish

  • 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

  • Deployed models are cached during unit tests

    I am using Stardust 2.1.1, and currently I am writing unit tests with JUnit, Spring and an in-memory Derby database. I would like to create a clean state for each of the unit tests, so I create and initialize the database before every test method and drop it after method executions. I also dispose of the Spring application context and initialize it between test methods with the @DirtiesContext(classMode = ClassMode.AFTER_EACH_TEST_METHOD) annotation.
    My problem is that despite dropping the database and reinitializing the Spring context after every test method my previously deployed models are still cached and I get an authorization-related exception:
    org.eclipse.stardust.common.error.AccessForbiddenException: AUTHx01000 - The user 'motu' does not have the permission 'model.deployProcessModel'.
    at org.eclipse.stardust.engine.core.runtime.utils.Authorization2.checkPermission(Authorization2.java:332) ~[carnot-engine-2.1.1.jar:2.1.1]
    at org.eclipse.stardust.engine.core.runtime.beans.interceptors.GuardingInterceptor.invoke(GuardingInterceptor.java:52) ~[carnot-engine-2.1.1.jar:2.1.1]
    at org.eclipse.stardust.engine.core.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:130) [carnot-engine-2.1.1.jar:2.1.1]
    at org.eclipse.stardust.engine.core.runtime.beans.interceptors.AbstractLoginInterceptor.performCall(AbstractLoginInterceptor.java:201) ~[carnot-engine-2.1.1.jar:2.1.1]
    at org.eclipse.stardust.engine.core.runtime.beans.interceptors.AbstractLoginInterceptor.invoke(AbstractLoginInterceptor.java:131) ~[carnot-engine-2.1.1.jar:2.1.1]
    at org.eclipse.stardust.engine.api.spring.SpringBeanLoginInterceptor.invoke(SpringBeanLoginInterceptor.java:79) ~[carnot-spring-2.1.1.jar:2.1.1]
    at org.eclipse.stardust.engine.core.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:130) [carnot-engine-2.1.1.jar:2.1.1]
    at org.eclipse.stardust.engine.api.spring.SpringSessionInterceptor.doWithDataSource(SpringSessionInterceptor.java:142) ~[carnot-spring-2.1.1.jar:2.1.1]
    at org.eclipse.stardust.engine.api.spring.SpringSessionInterceptor.access$000(SpringSessionInterceptor.java:48) ~[carnot-spring-2.1.1.jar:2.1.1]
    at org.eclipse.stardust.engine.api.spring.SpringSessionInterceptor$1.doInConnection(SpringSessionInterceptor.java:87) ~[carnot-spring-2.1.1.jar:2.1.1]
    at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:350) ~[spring-jdbc-4.1.6.RELEASE.jar:4.1.6.RELEASE]
    I looked into the code and found out that the ModelManagerBean and ModelMananagerBeanPartition classes cache my test model. I set the Infinity.Engine.Caching property to false in my carnot.properties as per the online documentation but the model is still getting cached.
    What is the proper way to disable caching in Stardust or how can I ensure that it disposes of everything that is cached?
    Thank you.

    In the Authorization2.checkPermission(...) method there's the following call:
    List<IModel> models = ModelManagerFactory.getCurrent().findActiveModels();
    This is a call to the ModelManagerPartition.findActiveModels() method. This class also has a deleleAllModels() method. If I try to call either of them manually after deploying the model in the first test, I get a NullPointerException.

  • Enhanced backend integration version of the CRM organizational model

    Hi,
    I want switch from Enhanced org Model to Standard Org Model While doing client copy in EHP 1
    Existing client is with Enhanced Org Model.
    Any Suggestions?

    Hi,
    As per SAP , if you are already using enhanced backend integration model , you can " NOT"  return to the standard backend integration version,
    http://help.sap.com/saphelp_sm40/helpdata/en/15/fbbb3ee5bf7173e10000000a114084/content.htm
    Hope it helps,
    regards,
    PRASHANT

  • How to prevent for a particular org manually created IR/ISO should not be considered for Constrained EDD plans

    We have a situation that around IRs with ~500 parts which manually created in Org A and ISO Created in Org B and ISO picked as well. But due to some reasons, shipment will get delay for 1 month and till that time plan should not be considered this IR' as supply in Org A.
    Currently our Constrained EDD plan is considering this IR quantities as supply for the Org A demands and not generating any Planned orders. Seems we don't option to firm IRs by changing the need by date after 1 month. Also its not respect the need by date of IR and its getting reschedule in action and pegged to the current Demand in Org A. Please advise if you have any thoughts.

    We have a situation that around IRs with ~500 parts which manually created in Org A and ISO Created in Org B and ISO picked as well. But due to some reasons, shipment will get delay for 1 month and till that time plan should not be considered this IR' as supply in Org A.
    Currently our Constrained EDD plan is considering this IR quantities as supply for the Org A demands and not generating any Planned orders. Seems we don't option to firm IRs by changing the need by date after 1 month. Also its not respect the need by date of IR and its getting reschedule in action and pegged to the current Demand in Org A. Please advise if you have any thoughts.

  • Useful Document/resources For Begginners

    this document is easily on net
    WS-BPEL Guide
    Last changed on Dec 10, 2004 by Matthieu Riou
    What is this article about ?
    This is an introduction to WS-BPEL that should give you a practical understanding of what you have to do to create a nice WS-BPEL process, dwelling on most important details. After reading this article you probably won't be able to write a WS-BPEL process from top to bottom. But you should have a pretty good notion of what can be done with it, what it involves and be familiar with the main elements of the grammar.
    First things first, here are the answers to the most trivial questions:
    •     What this new and unique acronym means? Web Services Business Process Execution Language.
    •     What is WS-BPEL? It's an XML grammar (a W3C schema) defining and standardizing structures necessary for web services orchestration.
    •     What does WS-BPEL? Well, actually nothing as it's just a grammar. But a WS-BPEL engine can do many things when executing your process. Like reacting to message reception, manipulating the message data, sending messages to web services and evaluating expressions.
    •     Where does it come from? It has been written by IBM, BEA Systems and Microsoft. Siebel and SAP joined these three and the specification has bee donated to OASIS.
    •     Where does WS-BPEL fit? It's a very good candidate to add an orchestration layer to a Service Oriented Architecture. It will make your services collaborate nicely and will encapsulate the cross-service business logic. It will also help you to introduce long-living transactions.
    Now that the introductory questions have been answered and before going any further I would like to clarify one thing about WSDL (I voluntarily wrote WSDL here, it's not a weird typo). WS-BPEL heavily relies on WSDL to describe the web services it is interacting with (we will see that soon) but that doesn't mean that it can only interact with services using XML(SOAP)/HTTP. WSDL introduces bindings which are the declaration of your services underlying communication medium. Bindings can be declared for local Java, JMS, RMI or anything you like (you might want to check Apache WSIF ). So a WS-BPEL engine using the right bindings could very well invoke many different services.
    So let's see how we are going to take a look at WS-BPEL. First, I'm going to give a very simple and classic example, just to give you a taste of what can be done with WS-BPEL. Then I'll introduce briefly its main activities. We'll see how to handle your process data and manipulate it and also how a particular process execution can be identified among all others. Finally we'll talk about how WS-BPEL introduces long-living transactions.
    A very simple yet demonstrative example
    After reading this chapter, most of you will probably think that the example I'm going to use is too simple and not realistic. I agree. But my goal here is just to give you a flavor of how WS-BPEL can be used, a realistic example would take more than all this article by itself.
    Now, you are the owner of a small bank granting loans to some of your customers. You have sales offices creating new customer contracts. You also have a web site and customers can directly ask for a loan online for small amounts. But before accepting a contract, some verifications are necessary. Those verifications are done using a risk assessment system maintained by a third party and by an in-house system that files the most tough requests. Loan specialists are part of your staff and then use this in-house system to take the final decision.
    So here is, step by step, the process that must be followed:
    1.     A loan request is issued, either from your web site of from one of your agencies. This request is made for a customer and for a certain amount.
    2.     A risk assessment system must be contacted to check whether the risk associated with the customer asking for the loan is high or low (probably based on his credit history).
    1.     If the loan amount is lower than $10,000 and the risk associated to the customer is low, the loan is directly approved (which saves time).
    2.     Otherwise, the loan request must be filed in your in-house system.
    1.     A loan specialist checks the request and gives his final decision.
    2.     The in-house system let you know the specialist's decision.
    3.     The response is sent to the customer.
    So how those pieces would be implemented in a "WS-BPEL aware" architecture? Here we go:
    •     One message triggered by your web site or your sales system and targeted at your process web service. It would hold at least the customer's name and the loan amount.
    •     One message triggered by the WS-BPEL engine to the risk assessment system to ask for the risk associated with the customer. If you pay your bills correctly, an answer message from this message should be expected.
    •     If needed, one message from the WS-BPEL engine to your in-house system to fill the loan request.
    •     One message from your in-house system to the process web service to give it the loan specialist's answer.
    •     Finally, one message back to your web site or to your sales system to give the final answer.
    One thing some of you probably already noticed is that when talking about the process I mentioned the "process web service". That's right, every process created inside a WS-BPEL engine is published as a web service with its own endpoint. When you want to send a message to your process, you actually send it to this web service.
    So now that you have a better idea of what it would take to implement this process in WS-BPEL, it's time to step back a bit.
    Private vs. Public Processes
    It's quite important to differentiate private and public processes (they are called executable and abstract in WS-BPEL). It is the same kind of opposition as between orchestration and choreography and it has a great impact on your architecture.
    Private processes manage services inside a given organization. They act as a service themselves and are centralized. As in an orchestra, there is a chief conductor (the process engine). Public processes manage services across several organizations. Each organization knows about it's own part of the process but doesn't know anything about the activities executed by other parties (for obvious confidentiality reasons). It's a peer-to-peer approach where you know the incoming and the outgoing messages, but nothing about what is done before, after or even meanwhile.
    WS-BPEL is quite good to handle private processes but doesn't perform so well for public ones (don't shoot me!). I have a feeling that even the members of the Oasis committee working on WS-BPEL don't know too much what to do with those. But actually, service choreography (public services) is not completely mature yet in terms of standards and market acceptance where as orchestration already has a widely embraced specification (WS-BPEL, in case you didn't realize) and many commercial implementations as well as open source ones (you may want to check Twister ). So good news, what you are going to learn in this article might prove useful.
    After those high-level considerations, we'll now look into WS-BPEL guts to see what's there and what we could use to build our process.
    WS-BPEL Activities
    In WS-BPEL, everything being part of your process body is an activity. There are basic activities (the ones that do something) and structured activities (the ones that organize basic activities without doing anything by themselves, just like your boss).
    Basic activities
    Invoking a web service is as simple as that:
    <invoke partnerLink="riskAssessor" portType="assessor" operation="assess"/>
    Pretty simple isn't it? In our initial example this declaration would be used to invoke the risk assessment system. Well, I'm actually cheating, you'll see later that you usually need a bit more (like input and output data) but this is a valid invocation.
    To wait for an incoming message, you'll write:
    <receive partnerLink="inhouseSystem" portType="inhousePort" operation="registerLoanRequest"/>
    That would be used to wait for the loan specialists' answer after registering the loan request in your in-house system. Now let's say that you want to send an immediate synchronous answer to this "receive". You'd write, after the receive:
    <reply partnerLink="inhouseSystem" portType="inhousePort" operation="registerLoanRequest"/>
    But how exactly does a WS-BPEL engine know, upon reception of a message, if it has to trigger the creation of a new process execution (a process instance)? Well, there's an attribute just for that: "createInstance".
    <receive partnerLink="loanRequester" portType="loanProcess" operation="processLoanRequest" createInstance="true"/>
    These 3 declarations use common attributes: partnerLink, portType and operation. If you know WSDL, you are already familiar with the port types and operations. Partner links have been introduced in WS-BPEL to model a two-way interaction between a process and a partner (a web service or another process). It lets you define the role of each of the two party in the interaction.
    There are two more basic activities that could prove useful (or at least one of the two):
    <wait until="'2002-12-24T18:00+01:00'"/>
    <empty/>
    Structured activities
    To start with, 3 basic ones: sequence, switch and while. If their behavior is not clear yet, here are examples:
    <sequence>
    <receive .../>
    <invoke .../>
    <invoke .../>
    </sequence>
    <switch xmlns:inventory="http://supply-chain.org/inventory" xmlns:FLT="http://example.com/faults">
    <case condition= "bpws:getVariableProperty(stockResult,level) > 100">
    … do something
    </case>
    <case condition="bpws:getVariableProperty(stockResult,level) >= 0">
    … do something else
    </case>
    <otherwise>
    … do the last thing
    </otherwise>
    </switch>
    <while condition="10 < bpws:getVariableData('loopVar', 'main', '/counter')">
    <assign>
    <copy>
    <from expression="bpws:getVariableData('loopVar', 'main', '/counter') + 1"/>
    <to variable="loopVar" part="main" query="/counter"/>
    </copy>
    </assign>
    </while>
    Another structured activity is 'pick'. It's just like several receive activities waiting at the same time with an additional alarm construct to avoid waiting forever the occurrence of a message:
    <pick>
    <onMessage partnerLink="" portType="" operation="">
    … do something
    </onMessage>
    <onMessage partnerLink="" portType="" operation="">
    … do something else
    </onMessage>
    <onAlarm until="2004-12-31T23:59:00">
    … hey, what the hell are you waiting for?
    </onAlarm>
    <pick>
    Like the receive activity, it's possible to declare a 'createInstance' attribute on the pick element to trigger the creation of a new process instance.
    Finally, for those who found all those activities way too structured and were missing a bit of anarchy, WS-BPEL introduced a flow activity. You basically declare all your activities as you like and then create links that take those activities as origin and target. The flow is also the only way to enable the execution of several parallel branches.
    Process Data
    To handle the process execution data, WS-BPEL introduces a new and unique concept: variables… Ok, that was just a bad attempt to keep you interested. Here is the context: your process engine must receive and send messages as defined by web services WSDL descriptions. To be able to do anything useful it must retain those messages and let you manipulate their content to create new messages or influence the process flow in variables. Therefore variables hold the state of a process execution. WS-BPEL variables can either hold a WSDL message or an arbitrary XML structure defined by a schema.
    An example for the declaration of a variable that can hold a WSDL message (the first stanza comes from the WSDL description, the second is a part of the process definition):
    <message name="creditInformationMessage">
    <part name="firstName" type="xsd:string"/>
    <part name="lastName" type="xsd:string"/>
    <part name="amount" type="xsd:integer"/>
    </message>
    <variable name="requestLoan" messageType="creditInformationMessage"/>
    So now, how do I stuff an incoming message into this variable? Here is the stuffing:
    <receive partnerLink="loanRequester" portType="loanProcess" operation="processLoanRequest" variable="requestLoan"/>
    Hey hey! That's our old receive! A variable attribute can be specified for a receive to hold the incoming message. For a reply, there's also a variable attribute to give the content of the message to send. And for an invoke, there's an inputVariable attribute to give the variable to send and an outputVariable to hold the response (for a synchronous invocation).
    We have variables to hold our message and we know how to give them a value upon reception of a message. But how do you initialize a variable when you want to send a message using it? How do you build a variable using parts of other variables? The answer is assignment. There's an additional activity I didn't mention yet (yes, I'm holding information) named assign. It lets you "copy and paste" the whole content of a variable, only a WSDL part in a message or even just an element (using Xpath). Again, examples are better than idle words:
    <assign>
    <copy>
    <from variable="ob1"/>
    <to variable="knob"/>
    </copy>
    <copy>
    <from variable="userInfo" part="homeAddress"/>
    <to variable="address"/>
    </copy>
    <copy>
    <from variable="house" part="bathroom" query="/shower/soap"/>
    <to variable="cleaningAgent"/>
    </copy>
    <copy>
    <from>hey you</from>
    <to variable="song" part="title"/>
    </copy>
    </assign>
    Once your variable has been set correctly, you can simply use it as inputVariable for an invoke.
    There's still one mystery unsolved in the way you can use variables in WS-BPEL: referencing them in expressions. Let's say you have a variable holding a specific value and want to use this value in the condition of a switch case, how do we do that? By using two functions:
    bpws:getVariableProperty ('variableName', 'propertyName')
    bpws:getVariableData ('variableName', 'partName'?, 'locationPath'?)
    The first function accepts the name of your variable and a property (we'll introduce property later but right now you just need to know that a property is a named XPath expression). The second accepts your variable, an optional part and an optional XPath expression relative to the part root.
    It's now time to see your first complete WS-BPEL example. It triggers the execution of a process upon reception of a message and iterates over a value contained in the message until 10. It's a very stupid example and it's probably the last thing you want to do with WS-BPEL (just as a reminder, WS-BPEL is used to orchestrate web services, not iterate over a value) but it illustrates almost everything we talked about in this paragraph.
    <?xml version='1.0' encoding="UTF-8"?>
    <process name="loop"
    targetNamespace="http://www.smartcomps.org/twister/example/loop/process/"
    xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    xmlns:def="http://www.smartcomps.org/twister/examples/loop/service/"
    abstractProcess="no">
         <variables>
              <variable name="loopVar" type="loopVarType"/>
         </variables>
         <correlationSets>
              <correlationSet name="counterCorrel" properties="def:counterId"/>
         </correlationSets>
         <sequence>
              <receive partnerLink="loopPartner" portType="loopPort" operation="loopOp"
              variable="loopVar" createInstance="true">
                   <correlations>
                        <correlation set="counterCorrel" initiate="yes"/>
                   </correlations>
              </receive>
              <while condition="10 > bpws:getVariableData('loopVar', 'main', '/counter')">
                   <assign>
                        <copy>
                             <from expression="bpws:getVariableData('loopVar', 'main', '/counter') + 1"/>
                             <to variable="loopVar" part="main" query="/counter"/>
                        </copy>
                   </assign>
              </while>
         </sequence>
    </process>
    As you probably already realized, data manipulation can quickly become a bit verbose. The WS-BPEL Technical Committee is currently working on it to have something easier for WS-BPEL 2.0.
    Correlation
    Correlation is a notion that can be a bit hard to grasp at first but is very important. So hang on and I'll do my best to be even more clear (somehow) than usually. During its execution, a process has to interact with several different services. This interaction is stateless so there is no way to make sure you will be addressed to a particular instance of a service. So let's imagine you own a wine store and have a web site allowing users from all over the world to order cheap and very good French wine. A service provided by your bank does the billing for you and you also use a shipper to send the orders all over the world. When a user places an order online, your web site generates an order id. But your bank doesn't know anything about your order id, it creates its own billing id corresponding to your order and you always must use this billing id when interacting with your bank (to confirm the transaction just after shipment for example). The shipper also creates his own shipment id that will be used when he confirms that the order has been sent.
    You want to use a WS-BPEL engine to handle those tasks automatically and orchestrate all the services (there's probably much more than three services and many steps involved). That's a really good idea!!! But how do you deal with all these different ids ? Yep, you guessed it: correlation. How does it work? A correlation is an unique way to identify the interaction of your process execution with a given party. A correlation is a list of property elements and a property element is a named XPath expression. This XPath expression must select a value in the exchanged messages that will be the value of the correlation for this particular message. So for our previous example we would define the following elements:
    <property name="billId" type="xsd:string"/>
         <propertyAlias propertyName="billId" messageType="createBillMessage" part="billInfo" query="billId"/>
         <propertyAlias propertyName="billId" messageType="confirmTransactionMessage" part="billId"/>
         <property name="shipId" type="xsd:string"/>
         <propertyAlias propertyName="shipId" messageType="shipMessage" part="shipId"/>
         <correlationSets>
              <correlationSet name="bankCorrelation" properties="billId"/>
              <correlationSet name="shipperCorrelation" properties="shipId"/>
         </correlationSets>
    A correlation can be composed of more than one property (separated by spaces). A property can also have several aliases for each type of message the correlation is used for.
    Usually a correlation is declared for each actor your process has to communicate with. The correlation is initiated during the first message exchange between your process execution and a party and is reused anytime your process execution sends a message to this party.
    Compensation
    I'm not going to detail this chapter as much as I did for the previous ones. This article is already far too long (and therefore too boring). Talking about compensation in a detailed manner would require another article like this one. But to whet your appetite, I'll tell you what its is and what it is the problem it has been designed to solve.
    Compensation is related to error handling. WS-BPEL processes are usually long-lasting (there could be days between 2 activities), they use asynchronous messages and interact with several different services. Introducing the concept of ACID transactions in this context is quite tough. Each of the services involved can locally use its own transaction but it's impossible within your process to control them (and you probably don't want to). So what can you do if you have three asynchronous operations, like 3 invoke / receive couples, that must be executed in an "all or nothing" fashion? How to cancel the two first operations that have already been committed if the third fails?
    Compensation is basically a set of activities attempting to cancel operations that have already been completed inside an unit of work. If an activity fails or a fault is thrown inside this unit of work, this set of activities is supposed to roll back everything that has been already completed in the unit of work in a way specific to your business case. You are the only one who really knows what to do if something goes wrong so you have to provide the necessary operations.
    But this system has important drawbacks:
    •     It is your responsibility to execute the right activities to handle the cancellation.
    •     All the services you are interacting with must support a way to rollback a previously committed transaction (most probably requiring some hard coding).
    Conclusion
    WS-BPEL has been a bit criticized principally for its absence of human participant interaction (as in conventional workflows), everything is a service. But whether you like it or not, it's already standard and if you use it for what it is good at, a pretty good one. Besides it's a good step in the right direction to standardize the BPM - SOA - 'call it what you like' space. And you can always rely on good products like Twister to introduce Worklist functionalities (remember, always a bit of marketing in a conclusion).
    Resources
    WS-BPEL Specification: http://www-106.ibm.com/developerworks/library/ws-bpel/
    Oasis WS-BPEL Technical committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsbpel
    Twister WS-BPEL Open Source Implementation: http://www.smartcomps.org/twister

    Where can I get a document like this for the IQ775? I have asked HP several times, but get no response. I just want to know how to open the damned thing!

  • Af:tree with command link

    hi experts,
    am using jdeveloper 11g version 11.1.1.5.0 - adfbc components - oracle db 10g.
    am trying some examples regards,
    af:tree with commandLink,
    here what i did:
    i achieved the af:tree with the help of some association between two tables and then i exposed in ui,
    you can see in this pics1 :
    http://www.4shared.com/photo/kGE2M1yl/pics1.html
    and then af:tree output can also seen in pics2:
    http://www.4shared.com/photo/GQTB9icb/pic2.html
    this is the code for af:tree
    <af:tree value="#{bindings.ApplBusFunSuiteView1.treeModel}"
                         var="node"
                         selectionListener="#{bindings.ApplBusFunSuiteView1.treeModel.makeCurrent}"
                         rowSelection="single" binding="#{backing_untitled1.t1}"
                         id="t1">
                  <f:facet name="nodeStamp">
                     <af:outputText value="#{node}"
                                     binding="#{backing_untitled1.ot1}" id="ot1"/>
                  </f:facet>
                </af:tree>ok thing which i did all are ok.
    but my need is :
    you may see in pics2.
    http://www.4shared.com/photo/GQTB9icb/pic2.html
    i make red mark on the on a child.
    here am going to explain my need
    in the picture you can see CRM as parent
    MKG as first child
    MKG3200 as last child.
    command link should be appeared.
    when i click that it will navigate to the corresponding page.
    for eg: if i click MKG3200 navigate to the MKG3200 page.
    how can i do this.? i need some guidance.
    sorry for my poor english.
    Edited by: Erp on Dec 1, 2011 4:34 AM

    hi am waiting for john
    retrieves the page IDhere the author get the node id.
    in my task n get the page id and navigate to it. as you said.
    http://andrejusb.blogspot.com/search/label/Tree
    thanks to andrejus and you(john)
    package view.backing;
    import java.util.Iterator;
    import java.util.List;
    import javax.el.ELContext;
    import javax.el.ExpressionFactory;
    import javax.el.MethodExpression;
    import javax.faces.application.Application;
    import javax.faces.application.FacesMessage;
    import javax.faces.context.FacesContext;
    import oracle.adf.controller.TaskFlowId;
    import oracle.adf.view.rich.component.rich.RichDocument;
    import oracle.adf.view.rich.component.rich.RichForm;
    import oracle.adf.view.rich.component.rich.data.RichTree;
    import oracle.adf.view.rich.component.rich.fragment.RichRegion;
    import oracle.adf.view.rich.component.rich.input.RichInputText;
    import oracle.adf.view.rich.component.rich.layout.RichPanelGroupLayout;
    import oracle.adf.view.rich.component.rich.layout.RichPanelSplitter;
    import oracle.adf.view.rich.component.rich.nav.RichCommandButton;
    import oracle.adf.view.rich.component.rich.nav.RichCommandLink;
    import oracle.adf.view.rich.component.rich.output.RichMessages;
    import oracle.jbo.Row;
    import oracle.jbo.uicli.binding.JUCtrlHierBinding;
    import oracle.jbo.uicli.binding.JUCtrlHierNodeBinding;
    import org.apache.myfaces.trinidad.component.UIXGroup;
    import org.apache.myfaces.trinidad.event.AttributeChangeEvent;
    import org.apache.myfaces.trinidad.event.SelectionEvent;
    import org.apache.myfaces.trinidad.model.CollectionModel;
    import org.apache.myfaces.trinidad.model.RowKeySet;
    import org.apache.myfaces.trinidad.model.TreeModel;
    public class Main1 {
        private RichForm f1;
        private RichDocument d1;
        private RichTree t1;
        private RichMessages m1;
        private RichCommandLink ot1;
        private String taskFlowId = "/WEB-INF/dummy-task-flow-definition.xml#dummy-task-flow-definition";
        private RichRegion r1;
        private UIXGroup g1;
        private RichCommandLink cl1;
        private RichPanelSplitter ps1;
        private RichPanelGroupLayout pgl1;
        private RichInputText it1;
        private RichCommandButton cb1;
        private String i1;
        public void setF1(RichForm f1) {
            this.f1 = f1;
        public RichForm getF1() {
            return f1;
        public void setD1(RichDocument d1) {
            this.d1 = d1;
        public RichDocument getD1() {
            return d1;
        public void setT1(RichTree t1) {
            this.t1 = t1;
        public RichTree getT1() {
            return t1;
        public void setM1(RichMessages m1) {
            this.m1 = m1;
        public RichMessages getM1() {
            return m1;
        public void setOt1(RichCommandLink ot1) {
            this.ot1 = ot1;
        public RichCommandLink getOt1() {
            return ot1;
        public TaskFlowId getDynamicTaskFlowId() {
            return TaskFlowId.parse(taskFlowId);
        public void setR1(RichRegion r1) {
            this.r1 = r1;
        public RichRegion getR1() {
            return r1;
        public String dynaminflow()
             taskFlowId = "/WEB-INF/supplier-task-flow-definition.xml#supplier-task-flow-definition";
              return null;
        public String mainflow1()
                taskFlowId = "/WEB-INF/dummy-task-flow-definition.xml#dummy-task-flow-definition";
              return null;
        public void setG1(UIXGroup g1) {
            this.g1 = g1;
        public UIXGroup getG1() {
            return g1;
        public void setCl1(RichCommandLink cl1) {
            this.cl1 = cl1;
        public RichCommandLink getCl1() {
            return cl1;
        public void setPs1(RichPanelSplitter ps1) {
            this.ps1 = ps1;
        public RichPanelSplitter getPs1() {
            return ps1;
        public void setPgl1(RichPanelGroupLayout pgl1) {
            this.pgl1 = pgl1;
        public RichPanelGroupLayout getPgl1() {
            return pgl1;
        public void setIt1(RichInputText it1) {
            this.it1 = it1;
        public RichInputText getIt1() {
            return it1;
        public void setCb1(RichCommandButton cb1) {
            this.cb1 = cb1;
        public RichCommandButton getCb1() {
            return cb1;
        public void setI1(String i1) {
            this.i1 = i1;
        public String getI1() {
            return i1;
        public String cb1_action() {
            // Add event code here...
          if(this.getI1().equalsIgnoreCase("SUP1000")  ) {
                         dynaminflow();
          else  if(this.getI1().equalsIgnoreCase("MAIN1000")  ) {
                               mainflow1();
          else{
                    FacesContext ctx = FacesContext.getCurrentInstance();
                    FacesMessage fm =
                        new FacesMessage(FacesMessage.SEVERITY_ERROR, "Page Not found",
                    ctx.addMessage(null, fm);
                    return null;
            return null;
        public void onTreeSelect(SelectionEvent selectionEvent) {
         /*   //original selection listener set by ADF
            //#{bindings.allDepartments.treeModel.makeCurrent}
            String adfSelectionListener = "#{bindings.ApplBusFunSuiteView2.treeModel.makeCurrent}";
            //make sure the default selection listener functionality is preserved.
            //you don't need to do this for multi select trees as the ADF binding
            //only supports single current row selection
            /* START PRESERVER DEFAULT ADF SELECT BEHAVIOR */
           /* FacesContext fctx = FacesContext.getCurrentInstance();
            Application application = fctx.getApplication();
            ELContext elCtx = fctx.getELContext();
            ExpressionFactory exprFactory = application.getExpressionFactory();
            MethodExpression me = null;
            me =  exprFactory.createMethodExpression(elCtx, adfSelectionListener, Object.class, new Class[] { SelectionEvent.class });
            me.invoke(elCtx, new Object[] { selectionEvent });
            /* END PRESERVER DEFAULT ADF SELECT BEHAVIOR */
          //  RichTree tree = (RichTree)selectionEvent.getSource();
          //  TreeModel model = (TreeModel)tree.getValue();
            //get selected nodes
         //   RowKeySet rowKeySet = selectionEvent.getAddedSet();
         //   Iterator rksIterator = rowKeySet.iterator(); */
            //for single select configurations, thi sonly is called once
         /*   while (rksIterator.hasNext())
                List key = (List)rksIterator.next();
                JUCtrlHierBinding treeBinding = null;
                CollectionModel collectionModel = (CollectionModel)tree.getValue();
                treeBinding = (JUCtrlHierBinding)collectionModel.getWrappedData();
                JUCtrlHierNodeBinding nodeBinding = treeBinding.findNodeByKeyPath(key);
                Row rw = nodeBinding.getRow();
                System.out.println(""+nodeBinding.getRow()); */
                //print first row attribute. Note that in a tree you have to determine the node
                //type if you want to select node attributes by name and not index           
            /*    String rowType = rw.getStructureDef().getDefName();
                System.out.println(""+rw.getStructureDef().getDefName());
                if(rowType.equalsIgnoreCase("SuplrDocHdView")){
                    System.out.println("This row is a department: " + rw.getAttribute("SuphdBu"));
                else if(rowType.equalsIgnoreCase("EmployeesView")){
                 System.out.println("This row is an employee: " + rw.getAttribute("EmployeeId"));
                else{
                    System.out.println("Huh ????");
                // ... do more usefuls stuff here
            RowKeySet selection = this.getT1().getSelectedRowKeys();
            if (selection != null && selection.getSize() > 0) {
                for (Object facesTreeRowKey : selection) {
                    this.getT1().setRowKey(facesTreeRowKey);
                    JUCtrlHierNodeBinding root = (JUCtrlHierNodeBinding) this.getT1().getRowData();
                    JUCtrlHierNodeBinding node = this.getFirstChild(root);
                    while (node != null)
                        System.out.println(node.getRow().getAttribute(0));
                        if(node.getRow().getAttribute(0).toString().equalsIgnoreCase("APM2010") )
                            dynaminflow();
                        else  if(node.getRow().getAttribute(0).toString().equalsIgnoreCase("APM2020")  ) {
                                             mainflow1();
                        //node.getRow().remove();
                        if ( node.getChildren() != null) {    
                            node = this.getFirstChild(node);
                        } else {
                            while (this.getNextSibling(node) == null && node != root)
                                node=node.getParent();
                            if(node != root) {
                                node = this.getNextSibling(node);
                            } else {
                                node = null;
                    System.out.println(root.getRow().getAttribute(0));
                    if(root.getRow().getAttribute(0).toString().equalsIgnoreCase("APM2010")  )
                        dynaminflow();
                    else  if(root.getRow().getAttribute(0).toString().equalsIgnoreCase("APM2020")  ) {
                                         mainflow1();
                    //root.getRow().remove();
        private JUCtrlHierNodeBinding getFirstChild(JUCtrlHierNodeBinding node) {
            if (node.getChildren() != null) {
                return (JUCtrlHierNodeBinding)node.getChildren().get(0);
            return null;
        private JUCtrlHierNodeBinding getNextSibling(JUCtrlHierNodeBinding node) {
            JUCtrlHierNodeBinding parent = node.getParent();
            int index = parent.getChildren().indexOf(node);
            index = ++index;
            if(index < parent.getChildren().size()) {
                return (JUCtrlHierNodeBinding)parent.getChildren().get(index);
            return null;       
    }i get my output. what i need.
    you must check whether am going correct?
    please suggest me.
    sorry : pulling this thread to up.

Maybe you are looking for

  • Safari won't open & NOTHING will minimize! Please help!

    I think this started after the latest round of software updates. I left the house after clicking "update now" and when I returned home it said "some updates were unable to be installed." The problems started after I restarted the computer, but I can'

  • Difference Between Enterprise and Personal Editions?

    Hi All, I want to install Oracle 9i on Window XP Pro. I am wondering what is the difference between the Enterprise Edition and the Personal Edition? Do they both come with the Enterprise Manager clients that I am used to using? Any advice much apprec

  • Import Bookmarks from HTML

    I am trying to import a Safari bookmarks.html file into Firefox. Your support page says go to "Bookmarks" select "Show All Bookmarks" and select "Import". Please be advised that there is NO "Import" listing under "Show All Bookmarks"! I am using a Ma

  • "fixed" my G5, but can't calibrate

    I'll try and make this brief and appreciate any help I can get. I've had an original Dual 2.0Ghz G5 since late October 2003. It always gave me a little trouble with the odd kernel panic and the like, but it wasn't regular enough to send in, or replac

  • Production order no is missing the Batch short text field in MSC2N T.code

    Hi Guys, I have some requirement in my project. I have maintained Batch management in my project. When I create & release the Production order in CO01, immediately Batch number (Produciton order: Goods receipt tab) creates automatically by the system