cancel
Showing results for 
Search instead for 
Did you mean: 

Request creation error for mitigation control workflow

Former Member
0 Kudos

Dear Expert,

I had activiate the workflow from RAR to CUP on Mitigated User assignment, I had completed following customizing:

1)RAR->configaration->Workflow

2)CUP->configaration->initiator, stage, path.

but when I created mitigated user assignments in RAR, after click "Submit", error popup: "Request creation error"

can some one help?

thanks!

View Entire Topic
Former Member
0 Kudos

Hello Fan,

Did you check the logs in RAR to see what error is coming there?

Make sure that you have followed all the steps mentioned in the Configuration Guide to make the Integration Configuration in CUP and RAR. I suspect some error in integration only. Check the Following:

1. Workflow settings given in RAR. Specially the webservice that you give in RAR for request submission in CUP.

2. Check the Request types (MITOBJ), initiators, path, stages etc in CUP.

3. Check that you have done the Exit settings for RAR workflow in CUP.

If you could provide the logs from RAR when this error occurs, that will be very helpful.

Regards, Varun

Former Member
0 Kudos

Thanks Varun,

actually, I check the customizing you mentioned above, all are created setup.

can you tell me how to check the logs of RAR, I couldnot find it in Configaration.

Regards, yangfan

Former Member
0 Kudos

Hello Fan,

As soon as you recreate the error go to the debugger by using the URL below

http://<SERVER>:<PORT>:/webdynpro/dispatcher/sap.com/grc~ccappcomp/CCDebugger

There you will see the button for View log. Click that button to see the log. I suggest you copy the entire log using CTRL+A and then paste it into text file for better view. Go to the bottom of the file and then start searching upwards for the keyword "error".

This should take you to exact place you got the error.. You can copy some part of error here for us as well to check.

Regards, Varun

Former Member
0 Kudos

Dear,

the log is below:

ERROR service 'SAPGW00' unknown

TIME Thu May 20 13:33:16 2010

RELEASE 701

COMPONENT NI (network interface)

VERSION 38

RC -3

MODULE niuxi.c

LINE 1732

DETAIL NiPGetServByName2: service 'SAPGW00' not found

SYSTEM CALL getservbyname_r

COUNTER 375

May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred

INFO: Exception in Server YYY:

com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.

This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.

Could not start server: Connect to SAP gateway failed

Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00

ERROR service 'SAPGW00' unknown

TIME Thu May 20 13:33:16 2010

RELEASE 701

COMPONENT NI (network interface)

VERSION 38

RC -3

MODULE niuxi.c

LINE 1732

DETAIL NiPGetServByName2: service 'SAPGW00' not found

SYSTEM CALL getservbyname_r

COUNTER 375

May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred

INFO: Exception in Server YYY:

com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.

This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.

Could not start server: Connect to SAP gateway failed

Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00

ERROR service 'SAPGW00' unknown

TIME Thu May 20 13:33:16 2010

RELEASE 701

COMPONENT NI (network interface)

VERSION 38

RC -3

MODULE niuxi.c

LINE 1732

DETAIL NiPGetServByName2: service 'SAPGW00' not found

SYSTEM CALL getservbyname_r

COUNTER 375

May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred

INFO: Exception in Server YYY:

com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.

This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.

Could not start server: Connect to SAP gateway failed

Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00

ERROR service 'SAPGW00' unknown

TIME Thu May 20 13:33:16 2010

RELEASE 701

COMPONENT NI (network interface)

VERSION 38

RC -3

MODULE niuxi.c

LINE 1732

DETAIL NiPGetServByName2: service 'SAPGW00' not found

SYSTEM CALL getservbyname_r

COUNTER 375

May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred

INFO: Exception in Server YYY:

com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.

This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.

Could not start server: Connect to SAP gateway failed

Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00

ERROR service 'SAPGW00' unknown

TIME Thu May 20 13:33:16 2010

RELEASE 701

COMPONENT NI (network interface)

VERSION 38

RC -3

MODULE niuxi.c

LINE 1732

DETAIL NiPGetServByName2: service 'SAPGW00' not found

SYSTEM CALL getservbyname_r

COUNTER 375

May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred

INFO: Exception in Server YYY:

com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.

This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.

Could not start server: Connect to SAP gateway failed

Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00

ERROR service 'SAPGW00' unknown

TIME Thu May 20 13:33:16 2010

RELEASE 701

COMPONENT NI (network interface)

VERSION 38

RC -3

MODULE niuxi.c

LINE 1732

DETAIL NiPGetServByName2: service 'SAPGW00' not found

SYSTEM CALL getservbyname_r

COUNTER 375

May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred

INFO: Exception in Server YYY:

com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.

This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.

Could not start server: Connect to SAP gateway failed

Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00

ERROR service 'SAPGW00' unknown

TIME Thu May 20 13:33:16 2010

RELEASE 701

COMPONENT NI (network interface)

VERSION 38

RC -3

MODULE niuxi.c

LINE 1732

DETAIL NiPGetServByName2: service 'SAPGW00' not found

SYSTEM CALL getservbyname_r

COUNTER 375

May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred

INFO: Exception in Server YYY:

com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.

This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.

Could not start server: Connect to SAP gateway failed

Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00

ERROR service 'SAPGW00' unknown

TIME Thu May 20 13:33:16 2010

RELEASE 701

COMPONENT NI (network interface)

VERSION 38

RC -3

MODULE niuxi.c

LINE 1732

DETAIL NiPGetServByName2: service 'SAPGW00' not found

SYSTEM CALL getservbyname_r

COUNTER 375

May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred

INFO: Exception in Server YYY:

com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.

This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.

Could not start server: Connect to SAP gateway failed

Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00

ERROR service 'SAPGW00' unknown

TIME Thu May 20 13:33:16 2010

RELEASE 701

COMPONENT NI (network interface)

VERSION 38

RC -3

MODULE niuxi.c

LINE 1732

DETAIL NiPGetServByName2: service 'SAPGW00' not found

SYSTEM CALL getservbyname_r

COUNTER 375

May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred

INFO: Exception in Server YYY:

com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.

This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.

Could not start server: Connect to SAP gateway failed

Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00

ERROR service 'SAPGW00' unknown

TIME Thu May 20 13:33:16 2010

RELEASE 701

COMPONENT NI (network interface)

VERSION 38

RC -3

MODULE niuxi.c

LINE 1732

DETAIL NiPGetServByName2: service 'SAPGW00' not found

SYSTEM CALL getservbyname_r

COUNTER 375

May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit

INFO: END POOINT URL: http://9.186.143.129:50100/AEWFRequestSubmissionService_5_2/Config1?style=document

May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit

INFO: before submit:

May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit

INFO: wftype: MITIOBJ reqid: GRC01

May 20, 2010 2:10:50 PM com.virsa.cc.rulearchitect.dao.dto.MitObjDTO getObjContext

FINEST: validfrom: 2010-05-20 validto: 2011-05-20

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: MITREFNO

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: MOMITREFNO

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: CT01

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: RISKID

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: MORISKID

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: ZC02

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: LANG

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: LANG

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: EN

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: MONITORID

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: MONITORID

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: GRC01

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: Integer

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: STATUS

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: MOSTATUS

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: 0

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: DATE

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: VALIDFROM

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: VALIDFROM

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: 05/20/2010

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: DATE

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: VALIDTO

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: VALIDTO

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: 05/20/2011

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: BU ID

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: BUID

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: null

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: Approver ID

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: MOAPPROVERID

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: null

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: OBJTYPE

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: OBJTYPE

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: U

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Data Type: String

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Descripton: OBJID

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Name: OBJID

May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext

INFO: Value: 207471

May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit

INFO: Return code: 2010 Message: com.virsa.ae.core.ObjectNotFoundException: Invalid Priority Value : MO_HIGH workflow id: null Status: null

May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit

WARNING: 2010: null

Former Member
0 Kudos

Hello Fan,

In the logs i could see that you are getting errors related to JCO created in RAR. However, this should not be related to CUP workflow. Can you kindly check if you have the workflow type MITOBJ activated in CUP? You can check the same by going to CUP configuration -> Misc. Here check if you see workflow type MITOBJ here. Also, check if you see the request type MITOBJ in list of request types and they should be active. Kindly also check if you have defined the approver for this MITOBJ request type in CUP. If the approver is not defined then the error will come.

As for the JCO error in RAR, kindly check the connector that you have created in RAR. If you have created the JCO connection then kindly test and ping the same to make sure that they are doing the same without problem. Specifically check the gateway service that you have given in the RFC for RAR.

Regards, Varun

Edited by: Thakur Varun on May 20, 2010 8:39 AM

Former Member
0 Kudos

Fan,

Here is the error:

com.virsa.cc.workflow.bo.WorkflowBO submit INFO: Return code: 2010 Message: com.virsa.ae.core.ObjectNotFoundException: Invalid Priority Value : MO_HIGH workflow id: null Status: null May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit WARNING: 2010: null

It seems you are missing MO_HIGH priority. Make sure that you have a request type related to MITOBJ and priority related to MO_HIGH by going to configuration -> request configuration -> request type and priority.

Make sure to follow Varun's suggestion and if you are not able to activate workflow type related to MITOBJ then import the initial data file again.

Regards,

Alpesh

Former Member
0 Kudos

Dear Alpesh,

the problem has been resolved based on the instruction of yours and Varun's, but there is another question,

when the request has been posted to approver, the approver can only see the MItigation control ID without description, if so how could approver approve this request? is there any config can make "description" field comes or enable detail drilldown?

thanks!

Former Member
0 Kudos

Fan,

What SP level are you on? I have not used this functionality recently but did you check wtih SAP @ this?

Alpesh

Former Member
0 Kudos

Dear

SP level is 05, do I need to apply higer level? by which level?

thanks!