Create request approval

Hi,
Create Request approval is taking 2 times approval. One request level and one is approval level. I check the approval policies, there is create user approval of RL and OL and both are checked auto approval. Even it is checked as auto approval, it is taking 2 timeS approval of sysadm for creating a user in OIM.
I need to make approval only one time, can any one help me how we can do.
It is OIM 11g.
Thanks in advance.

Hi,
It seems that approval policy not formed properly. Please see step “6.5. Creating an Approval Policy in OIM” of OBE lab:
http://apex.oracle.com/pls/apex/apex_util.count_click?p_url=http://st-curriculum.oracle.com/obe/fmw/oim/oim_11g/developing_oim_custom_approval_process_for_role_request/developing_oim_custom_approval_process_for_role_request.pdf&p_cat=OBELINKS&p_workspace=175833227484562117&p_id=4883
You must create the same auto approval policy for one policy.

Similar Messages

  • GRC CUP Error creating request. Approver not found

    Hi,
    We just upgrade from GRC CUP 14 to GRC CUP 15.6 support pack.I already performed post upgrade steps and when i try to create a request i am getting approver not found.i didnot change workflow.In stage for role approver we have approver determinator "role".
    system log report
    com.virsa.ae.workflow.NoApproverFoundException: No approvers found for req no : 493, for reqPathId, 662, for path, PROD_APPRV_PATH and approver determinator : Role
         at com.virsa.ae.workflow.bo.WorkFlowBOHelper.handleApproversTransactions(WorkFlowBOHelper.java:1469)
         at com.virsa.ae.workflow.bo.WorkFlowRequestCreateHelper.handleWFForNewPath(WorkFlowRequestCreateHelper.java:278)
         at com.virsa.ae.workflow.bo.WorkFlowRequestCreateHelper.createNewWorkflow(WorkFlowRequestCreateHelper.java:167)
         at com.virsa.ae.workflow.bo.WorkFlowBO.saveNewWorkflow(WorkFlowBO.java:120)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:579)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:381)
         at com.virsa.ae.accessrequests.actions.EUCreateRequestAction.createRequestHandler(EUCreateRequestAction.java:135)
         at com.virsa.ae.accessrequests.actions.EUCreateRequestAction.execute(EUCreateRequestAction.java:68)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Please let me know solution ASAP.This is high priority.
    Thanks
    Yakoob.

    It looked like some old request stuck in DB.But, not sure about it.I tried by changing the number ranges in configuration by giving the current request number in "from number",but it didn't work.
    This is strange some time it gives "error creating request: path not found." and once this error gone then "error creating request : approver not found".
    To avoid this i created one more stage by custom approver determinator with application attribute and approver assiged.This stage, i assigned before role approver stage then it worked,Request get created and request get provisioned.
    i don't understand why it's not working,if i assigned role approver stage first in a path of workflow.role approver (approver determinator:"role" standard one, "approver" gets from configuration:roles:create role:role approver OR upload from role import).
    Please help
    Thanks
    Yakoob.

  • How to create Request programmatically to trigger Approval Process

    My scenario is dificult... I need to start Approval Process when the user want to assign AD Resource to other user without Request service. So I want to create Request programmatically from Event Handler to start Approval Process for Provision Resource request type.
    Is this right Way?

    If you talk of request, you will have to use RequestService. You can use code to work with the RequestService to create the request and the approval for you.
    -Bikash

  • How to create iView for Leave Request Approval for ESS Tab in Portal

    Hello ,
    I am new to  Enterprise portal. I got a requirement for creating iViews.
    How to create iView for Leave Request Approval for ESS Tab in Portal.??
    Please give me clearly or provide any document.
    Thanks
    Risha

    Hi Risha,
    is it customized application ?
    If so in SWFVISU transaction maintaain the entry .
    Use transaction SWFVISU to prepare standard setting for your Workitem in the UWL. --Parameters for Work Item Visualization in the UWL.
    Have a look at below link
    http://help.sap.com/saphelp_nw2004s/helpdata/en/59/d516690e854c7090ae15bf492a869f/content.htm

  • Standard workflow for downpayment request approval

    Hi,
    Is there any standard workflow for downpayment request approval?
    Please suggest.

    Hi,
    There is no standard flow for the down payment request generally in many projects down payment requests are rarely created process starts with Down payment request F-47 then Down payments F-48
    then clearing of Down Payment f-54
    Down PAyment request is just a template.If you want to use then use then u can skip this step.
    regards
    Deepa

  • Problem in changing label in leave request approval screen

    Hi All,
    I have followed the SAP note 1234273 to change labels in our Leave request iViewin ESS and could do it successfullybut I could not able to know how to change the labels in Leave request approval screen because I have created a custom role and assigned Universal work list to it and assigned it to manager to view the leave requests applied. I navigated to Leave request approval screen via that role but ctrl + right click is not working on that page. Please suggest me

    Check your uwl config, normally it is configured to directly call concerned(leave req approval) application hence your iview may not be getting called. You can try changing the uwl config to call PCD page instead of direct wdp application call.
    ~cheers
    avadh

  • Create an Approval Workflow for User Creation in AD

    Hi
    Anyone, tell me how to create an approval workflow to create users into AD. For example, before provisioning user into AD resouce the request should go to the Manager of the user for approval.
    P.S: I am using OIM 9.1
    Thanks
    Sireesha

    Hi Sireesha
    You want to create a new Process definition, selecting "Approval" as the process type.
    Then associate it with the AD User Resource Object. Add a "Manager Approval" process task and use a Task Assignment Adapter to to assign the task to the manager of the request target.
    In order for the Approval Process to fire, you need to ensure that you provision the AD User Resource Object via a Request, rather than directly.
    HTH
    Cheers
    Rob

  • Create request template in OIM11g

    Hi Friends,
    I have created request template in OIM11g and I created it for user creation and assigned a manager for approval.
    After I finish the user creation task and as the user is approved by the manager. The user status in Approved but I m not able to find the user in the User list.
    let me know how to find the user is created or not.. ?
    regards
    Srikanth

    First of all you should verify the user USR table in OIM - Database.
    If user exist in DB but still not visible in user list, there may be problem with authorization policy, So create an authorization policy so that user have access to view, edit modify etc permission.

  • Create and Approve Absence using BAPI_ABSENCE_CREATE/APPROVE

    Hello Experts,
    Have any one ever used BAPI_ABSENCE_CREATE and BAPI_ABSENCE_APPROVE for creating and approving absence?
    Please help me with test data that can be used on to the BAPI.
    Thanks,
    Suma

    Hi Thyagu,
    I was able to create an absence using BAPI_EMPLOYEE_ENQUEUE, BAPI_ABSENCE_CREATE/REQUEST in a sequence. But not able to approve the same using BAPI_ABSENCE_APPROVE.
    Approve BAPI has the following input fields(input data that I am passing):
    1. EMPLOYEENUMBER - Emp Number
    2. SUBTYPE - 0200
    3. OBJECTID - 01 "not sure if I am using correct data here"
    4. LOCKINDICATOR - X
    5. VALIDITYBEGIN - Start date
    6. VALIDITYEND - End Date
    7. RECORDNUMBER - 000
    8. NOCOMMIT - blank
    It returns the following error " No data stored for 2001 in the selected period".
    In a critical situation please help
    Thanks in advace,
    Suma
    Edited by: Suma B on Oct 14, 2008 11:04 AM

  • CUP 5.3 - X Error creating request

    Good day.
    I have a issue, that I need assistance in resolving. I have successfully installed CUP 5.3 and I am testing the end to end functionality. I have create a request (request type - change account), populated all the mandatory fields, Selected a Role and successfully run the Risk Analysis.
    When I click on the Approve button, I recieve the error Error creating request. I am not sure where the issue resides.
    Any suggestions?
    Regards,
    Michael Hannie

    Good day William and Frank.
    What a day! I have double checked and the Number Range is activated. Please review the system log below.
    Thank you for all you assistance thus far -
    2009-01-14 21:39:01,902 [SAPEngine_Application_Thread[impl:3]_39] INFO  com.virsa.ae.commons.utils.Util : getDate() :   :
    tmz : sun.util.calendar.ZoneInfo[id="CAT",offset=7200000,dstSavings=0,useDaylight=false,transitions=3,lastRule=null]
    2009-01-14 21:39:01,902 [SAPEngine_Application_Thread[impl:3]_39] INFO  com.virsa.ae.commons.utils.Util : getDate() :   :
    tmz : sun.util.calendar.ZoneInfo[id="CAT",offset=7200000,dstSavings=0,useDaylight=false,transitions=3,lastRule=null]
    2009-01-14 21:39:01,902 [SAPEngine_Application_Thread[impl:3]_39] INFO  com.virsa.ae.commons.utils.Util : getDate() :   :
    tmz : sun.util.calendar.ZoneInfo[id="CAT",offset=7200000,dstSavings=0,useDaylight=false,transitions=3,lastRule=null]
    2009-01-14 21:39:01,902 [SAPEngine_Application_Thread[impl:3]_39] INFO  com.virsa.ae.commons.utils.Util : getDate() :   :
    tmz : sun.util.calendar.ZoneInfo[id="CAT",offset=7200000,dstSavings=0,useDaylight=false,transitions=3,lastRule=null]
    2009-01-14 21:39:05,293 [SAPEngine_Application_Thread[impl:3]_30] INFO  com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll :   :
    going to return no of records= 24
    2009-01-14 21:39:38,418 [SAPEngine_Application_Thread[impl:3]_27] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:39:48,840 [SAPEngine_Application_Thread[impl:3]_36] INFO 
    com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction : checkRoleValidity() :   : INTO the method
    2009-01-14 21:40:01,981 [SAPEngine_Application_Thread[impl:3]_10] WARN 
    com.virsa.ae.accessrequests.actions.RequestDetailsHelper : copyUserPropertiesToRequest() :  : Company Code not available in
    the system:
    2009-01-14 21:40:01,981 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:40:05,653 [SAPEngine_Application_Thread[impl:3]_15] INFO 
    com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction : checkRoleValidity() :   : INTO the method
    2009-01-14 21:40:16,716 [SAPEngine_Application_Thread[impl:3]_35] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:40:19,997 [SAPEngine_Application_Thread[impl:3]_31] INFO 
    com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction : checkRoleValidity() :   : INTO the method
    2009-01-14 21:40:36,935 [SAPEngine_Application_Thread[impl:3]_27] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:41:00,169 [SAPEngine_Application_Thread[impl:3]_39] INFO 
    com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction : checkRoleValidity() :   : INTO the method
    2009-01-14 21:41:00,185 [SAPEngine_Application_Thread[impl:3]_39] INFO  com.virsa.ae.dao.sqlj.ApplicationDAO :
    findAllForContext :   :  going to return ImmutableList(empty)
    2009-01-14 21:41:00,185 [SAPEngine_Application_Thread[impl:3]_39] INFO  com.virsa.ae.dao.sqlj.ApplicationDAO :
    findAllForContext :   :  going to return ImmutableList(empty)
    2009-01-14 21:41:14,591 [SAPEngine_Application_Thread[impl:3]_14] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:41:17,920 [SAPEngine_Application_Thread[impl:3]_27] INFO 
    com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction : checkRoleValidity() :   : INTO the method
    2009-01-14 21:41:17,935 [SAPEngine_Application_Thread[impl:3]_27] INFO  com.virsa.ae.dao.sqlj.ApplicationAreaDAO : findAll :
      : findAll() going to return # of records= 1
    2009-01-14 21:41:46,686 [SAPEngine_Application_Thread[impl:3]_28] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:41:50,139 [SAPEngine_Application_Thread[impl:3]_2] INFO 
    com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction : checkRoleValidity() :   : INTO the method
    2009-01-14 21:41:50,154 [SAPEngine_Application_Thread[impl:3]_2] INFO  com.virsa.ae.accessrequests.actions.RequestViewAction
    : pageLoad() :   : INTO the method
    2009-01-14 21:41:50,154 [SAPEngine_Application_Thread[impl:3]_2] INFO  com.virsa.ae.accessrequests.actions.RequestViewAction
    : pageLoad() :   : request number :
    2009-01-14 21:41:55,014 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:41:55,029 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestAuditHelper :
    logMajorAction() :   : intHstId : 183
    2009-01-14 21:41:55,029 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    saveNewRequest() :   : calling saveRequestHeader()
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] ERROR Ignoring exception
    com.virsa.ae.core.NoRecordsFoundException: no service level values are found for request attributes : {Request Type=CHANGE,
    Application=[400], Priority=LOW, Role=ZD_MM_BUYER_BCX}
    at com.virsa.ae.accessrequests.bo.SelectServiceLevelHelper.getServiceLevel(SelectServiceLevelHelper.java:92)
    at com.virsa.ae.accessrequests.bo.RequestBO.getDueDate(RequestBO.java:7873)
    at com.virsa.ae.accessrequests.bo.RequestBO.saveRequestHeader(RequestBO.java:7719)
    at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:345)
    at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:261)
    at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:88)
    at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:256)
    at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process
    (ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    adjustUserId() :   : INTO the method for strUserId : MICHAELH, user email : michael.hannieATa.bcx.co.za
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    adjustApproverDetails() :   : INTO the method for strApproverId : JOHANSW, approver email : johan.swanepoelATbcx.co.za
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    saveNewRequest() :   : calling saveUsers()
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    saveNewRequest() :   : calling updateWithDefaultRoles()
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    updateWithDefaultRoles() :   : Considering default roles is not enabled
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    saveNewRequest() :   : calling updateWithRoleMappingRoles()
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    updateWithRoleMappingRoles() :   : Role mapping is not enabled
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.accessrequests.bo.RequestBO :
    saveNewRequest() :   : calling saveApplications()
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.service.sap.SystemDAOFactory :
    getRiskAnalysisDAO() :   : cc version : 5.3_WS
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.service.sap.SystemDAOFactory :
    getRiskAnalysisDAO() :   : risk analysis dao is set to RiskAnalysisWS52DAO
    2009-01-14 21:41:55,045 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.service.sap.SystemDAOFactory :
    getRiskAnalysisDAO() :   : cc uri : http://xgpmid01:50000/VirsaCCRiskAnalysisService/Config1?wsdl&style=document
    2009-01-14 21:41:55,061 [SAPEngine_Application_Thread[impl:3]_10] ERROR java.lang.LinkageError: loader constraints violated
    when linking com/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO class
    java.lang.LinkageError: loader constraints violated when linking com/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO class
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:511)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:80)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveRiskAnalysis(RequestBO.java:2851)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:374)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:261)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:88)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:256)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process
    (ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    2009-01-14 21:41:55,061 [SAPEngine_Application_Thread[impl:3]_10] ERROR Exception during EJB call, Ignoring and trying
    Webservice Call
    com.virsa.ae.service.ServiceException: Exception in getting the results from the EJB service : loader constraints violated
    when linking com/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO class
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:295)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:511)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:80)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveRiskAnalysis(RequestBO.java:2851)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:374)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:261)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:88)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:256)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process
    (ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.LinkageError: loader constraints violated when linking
    com/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO class
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)
         ... 26 more
    2009-01-14 21:41:55,483 [SAPEngine_Application_Thread[impl:3]_10] ERROR java.rmi.RemoteException: Service call exception;
    nested exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
    java.rmi.RemoteException: Service call exception; nested exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
         at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:90)
         at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:99)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:312)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:452)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:559)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:80)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveRiskAnalysis(RequestBO.java:2851)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:374)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:261)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:88)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:256)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process
    (ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.Exception: Incorrect content-type found 'text/html'
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ClientMimeMessage.initDeserializationMode
    (ClientMimeMessage.java:120)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage
    (MimeHttpBinding.java:956)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1437)
         at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:83)
         ... 28 more
    2009-01-14 21:41:55,483 [SAPEngine_Application_Thread[impl:3]_10] ERROR com.virsa.ae.core.BOException: Exception in getting
    the results from the web service : Service call exception; nested exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
    com.virsa.ae.core.BOException: Exception in getting the results from the web service : Service call exception; nested
    exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:80)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveRiskAnalysis(RequestBO.java:2851)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:374)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:261)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:88)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:256)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process
    (ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.virsa.ae.service.ServiceException: Exception in getting the results from the web service : Service call
    exception; nested exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:344)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:452)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:559)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         ... 22 more
    Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
         at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:90)
         at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:99)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:312)
         ... 26 more
    Caused by: java.lang.Exception: Incorrect content-type found 'text/html'
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ClientMimeMessage.initDeserializationMode
    (ClientMimeMessage.java:120)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage
    (MimeHttpBinding.java:956)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1437)
         at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:83)
         ... 28 more
    2009-01-14 21:41:55,483 [SAPEngine_Application_Thread[impl:3]_10] ERROR BO Exception in Save request
    com.virsa.ae.core.BOException: Exception in getting the results from the web service : Service call exception; nested
    exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:80)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveRiskAnalysis(RequestBO.java:2851)
         at com.virsa.ae.accessrequests.bo.RequestBO.saveNewRequest(RequestBO.java:374)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.createRequest(CreateRequestAction.java:261)
         at com.virsa.ae.accessrequests.actions.CreateRequestAction.execute(CreateRequestAction.java:88)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:256)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process
    (ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.virsa.ae.service.ServiceException: Exception in getting the results from the web service : Service call
    exception; nested exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:344)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:452)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:559)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         ... 22 more
    Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
         java.lang.Exception: Incorrect content-type found 'text/html'
         at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:90)
         at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:99)
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:312)
         ... 26 more
    Caused by: java.lang.Exception: Incorrect content-type found 'text/html'
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ClientMimeMessage.initDeserializationMode
    (ClientMimeMessage.java:120)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage
    (MimeHttpBinding.java:956)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1437)
         at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:83)
         ... 28 more
    2009-01-14 21:41:55,483 [SAPEngine_Application_Thread[impl:3]_10] INFO  com.virsa.ae.dao.sqlj.SAPConnectorDAO :
    findAllActiveSAPConnectors :   :  going to return no of records= 4
    2009-01-14 21:42:27,577 [SAPEngine_Application_Thread[impl:3]_21] INFO  com.virsa.ae.dao.sqlj.RequestTypeDAO : findAll :   :
    going to return no of records= 24

  • Create with Approval.

    When testing the 'Create with Approval' functionality in Oracle Portal (3.0.8),I found that sometimes (not always) items that not yet has been approved is shown to unauthorised users through a folder portlet in a portal page. When I navigate the content area, everything works as expected (Items awaiting approval is hidden from users without proper access rights). Have anyone else experienced a similar problem ? Could this have somrthing to do with the page caching content from content area ?
    Morten
    null

    I have tested some more, I am now able to reproduce the problem at will.
    It seems to me that the problem has something to do with the server caching page content (even though my page setup is: Cache page definition only).
    If a user who has the privilige to se items avaiting approval is the first one to request a portal page containing a folder portlet after the content has changed (complete reload from database), he can see items awaiting approval in the portal page. If another user who does not have this privilige then access the same page, he will also see the items avaiting approval !!
    If the public user access the page first, he cannot se item awaiting approval. Now the person who has the privilige cannot se them either until he provokes a complete reload of the content from the database by customizing a portlet on the page, editing content or similar actions.
    I have tested this by using two computers that way eliminating that this is a problem with local cache.

  • Error creating request. Path not found

    Hi,
    We are trying to create a request in CUP. We have given input in all the mandatory fields like Requester Name, Manager Name, Application and we have selected Roles. Those roles were already assigned to approvers.
    When we press the APPROVE button, it is asking to Approve. After clicking APPROVER button, it is giving error like u201CError creating request. Path not foundu201D.
    Please check and advice me where we are missing while creating request in CUP.
    Thanks & Regards,
    KKRao.

    Hi Sabita/Alpesh,
    Thanks for your reply. We have created two conditions under Initiator with AND and AND. We have cleared and we are not getting error like Path not found.
    Now we are getting error like "Error creating request. Approver not found".
    We have selected the Manger name in the request which we have defined in the Custom Approver Determinater. Still we are getting the error like Approver not found.
    Please check and correct me.
    Regards,
    KKRao.

  • ESS Loan Request Approver side validations

    Dear All,
    I am using standard ess loan request service.Here I have to perform certail validations at MSS side(Loan Request Approver IView).
    Here manager can edit the values of Granted Amount,payment date,payment amount and payment type.But without entering these values also the loan request is getting approved by clicking on Review button.
    I want to validate the above mentioned fields in case any of thefields left blank and also I have to validate the granted amount(should not be greater than requested amount).
    As we know we have following BADI's available thru which we can perform validations when employee is applying for a loan.
    1.Eligibility check
    2.Custom Validations
    3.Determine Approver.
    Is there any BADIs available to perform validations at MSS part(Loan Request Approver)
    Please give some input!
    Thanks,
    Reddy.

    Dear Roy,
    Thanks for your response.
    According to your reply I understand that I need to write my validations in the approval task(TS18900024).In the workflow Approval task there is a standard class CL_HRPBSIN_LOAN_REPAY_WF available.I cannot create a method under it since this is a standard class.Do I need to take a copy of it and create a method?
    But how can I Import the parameters from approver screen like Granted amount,payment amount,payment date and payment type.
    Please clarify...

  • Error while creating request list Unable to detect the SAP system directory

    We are upgrading SAP BW (NW 7.0 EHP1) to SAP BW (NW 7.3)
    source OS: Windows 2008 R2,  source DB: MSSQL server 2008 R2 SP1 CU3
    I had started the upgrade by running: STARTUP.BAT
    I had started the DSUGui on the server (CI / DB on the same server) from: D:\usr\sap\BP1\upg\sdt\exe\DSUGui.bat
    I ran both programs (run as administrators).
    Once SAP Gui connects and was able to create userid/ password and when ready to start the initialization phase (click next)
    gives me the error
    Error while creating request list - see preceeding messages. Unable to detect the SAP system directory on the local host
    I had tried STARTUP.BAT "jce_policy_zip=Z:\export-import\downloads\jce_policy-6'  and still the same error.
    I had started DSUGui.bat with trace and the trace file contents are
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[2.0.7.1006]/>
    <!NAME[D:
    usr
    sap
    bp1
    upg
    sdt
    trc
    server.trc]/>
    <!PATTERN[server.trc]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/>
    <!ENCODING[UTF8]/>
    <!LOGHEADER[END]/>
    Jan 11, 2012 10:14:58 AM [Error]:                          com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:102) [Thread[ExecuteWorker,5,main]]: Execution of command com.sap.sdt.engine.core.communication.CmdActionEvent@376433e4 failed: while trying to invoke the method java.io.File.getAbsolutePath() of an object returned from com.sap.sdt.dsu.service.req.DSURequestListBuilder.getSystemDir()
    Jan 11, 2012 10:14:58 AM [Error]:                          com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:103) [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException: while trying to invoke the method java.io.File.getAbsolutePath() of an object returned from com.sap.sdt.dsu.service.req.DSURequestListBuilder.getSystemDir()
    Jan 11, 2012 10:14:58 AM [Error]:                          com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:103) [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException: while trying to invoke the method java.io.File.getAbsolutePath() of an object returned from com.sap.sdt.dsu.service.req.DSURequestListBuilder.getSystemDir()
    Jan 11, 2012 10:14:58 AM [Error]:                                                 com.sap.sdt.engine.core.communication.CmdActionEvent [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException: while trying to invoke the method java.io.File.getAbsolutePath() of an object returned from com.sap.sdt.dsu.service.req.DSURequestListBuilder.getSystemDir()
         at com.sap.sdt.dsu.service.req.DSURequestListBuilder.persistSystemInfo(DSURequestListBuilder.java:277)
         at com.sap.sdt.dsu.service.DSUService.createRequestList(DSUService.java:338)
         at com.sap.sdt.dsu.service.controls.DSUListener.actionNext(DSUListener.java:144)
         at com.sap.sdt.dsu.service.controls.DSUListener.actionPerformed(DSUListener.java:67)
         at com.sap.sdt.server.core.controls.SDTActionListener$Listener.actionPerformed(SDTActionListener.java:46)
         at com.sap.sdt.engine.core.communication.CmdActionEvent.actOnEvent(CmdActionEvent.java:43)
         at com.sap.sdt.engine.core.communication.CmdEvent.execute(CmdEvent.java:69)
         at com.sap.sdt.engine.core.communication.ExecWorker.handleCmd(ExecWorker.java:36)
         at com.sap.sdt.engine.core.communication.AbstractWorker.run(AbstractWorker.java:93)
    I could not get Upgrade started.  Any help is appreciated
    Thanks
    Prathap

    Did you get this solved?
    I have the same problem

  • Unable to get dataset while creating request

    Hi All,
    I am using OIM 11g. I want to provide resource attribute details during provision request. I have created a GTC with DBAT connector and I import the dataset xml successfully (varified by exporting the same). But while creating request I am not able to see the dataset attributes in the Resource Details page.
    File Name: ProvisionResourceAPPLICATION1_GTC.xml
    <?xml version='1.0' encoding='UTF-8'?>
    <request-data-set xmlns="http://www.oracle.com/schema/oim/request" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.oracle.com/schema/oim/request" name="ProvisionResourceAPPLICATION1_GTC" entity="APPLICATION1_GTC" operation="PROVISION">
    <AttributeReference name="Employee Number" attr-ref="EMPLOYEENUMBER" type="String" length="50" widget="text" required="true" available-in-bulk="false"/>
    <AttributeReference name="Employee Name" attr-ref="EMPLOYEENAME" type="String" length="40" widget="text" required="false" available-in-bulk="false"/>
    <AttributeReference name="Email Address" attr-ref="EMAIL" type="String" length="40" widget="text" required="false" available-in-bulk="false"/>
    </request-data-set>
    After importing I ran PurgeCash and also restarted the server but got no effect.
    please help me out.
    Regards,
    Avijit Sengupta

    Hi,
    I have logged in with xelsysadm and I am not able to see dataset during creation of request template at point no 6 and 7 except service account check box.
    While creating GTC I have given the resource name "*APPLICATION1*" but after creation it is showing APPLICATION1_GTC.
    I used APPLICATION1_GTC as entity in my dataset.
    As the dataset is not visible in normal request base provisioning process as well as custom request template, I didn’t create any authorization policy.
    Regards,
    Avijit Sengupta

Maybe you are looking for