Solved: 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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hi Michael,

I can see there are couple of issues as per the logs:

1) Maintain service level: Go to configuration -> service level and create at least one service level. This should resolve the problem.

2) Turn off RA during request submission: Go to configuration -> risk analysis and select 'No' for perform risk analysis on request.

Now, go ahead and create the request. It should work.

Regards,

Alpesh

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Alpesh, you are absolutely correct!

Your suggestions resolved my issues. Thank you for your prompt and profession answers.

Regards,

Michael Hannie

Good day Alpesh.

I trust that you are well. With regards to the issue CUP 5.3 - X Error creating request, you provided me with two (2) solutions. I need some clarification on the second point - Turn off RA during request submission: Go to configuration -> risk analysis and select 'No' for perform risk analysis on request.

For project documentaion purposed, what is the purpose of Risk Analysis On Request Submission, and by setting the option to NO, how did this resolve my issue

Thank you.

Regards,

Michael Hannie

Answers (3)

Michael,

The issue was resolved by creating Service level.

Here is the explanation for 'Risk analysis on request submission':

When it is 'Yes', it will try to run a risk analysis when the request is being submitted, sometime this takes a long time or errors out. By turning it off, at least request can go through.

Regards,

Alpesh

SAP GRC Manager (PwC)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thank you for your reply.

You are welcome, Michael. I am glad that I was able to help.

Regards,

Alpesh

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Michael,

1-Please check your stages and path configuration.

2-Paste Error log here.

Thanks and Regards,

Jagat

Edited by: Jagat Bir Singh on Jan 14, 2009 1:28 PM

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Jagat.

I hace checked and double checked my stage and patch config. It seems to be configured correctly as per the config guide.

Another issue I noticed is that, once I clicked on Approve, the Request Information screen appears and there in no Request Number maintained.

Regards,

Michael Hannie

Michael,

Have you maintained your number ranges in the configuration tab and activated the range?

As for your initial problem, CUP errors are rather nebulous. Can you go to the configuration page -> Monitoring -> System Log and paste the relevant information here (after you receive your error)?

Thanks.

I bet the number range hasn't been activated - that one got me once or twice already

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)