SP12: CUP: Error for requesttype "change" at auto-provisioning

[Former Member]

Hello,

We have an error while auto-provisioning a change-request in CUP.

The request stages can be approved correctly but after the last stage, the request is rerouted to administrator because of escape-route settings. (auto provisioning failures)

So the audit trail reports an error at auto-provisioning, BUT in the backend-system the user was changed correctly.

If we now want to approve the request on admin-stage, the error appears again. So we have a closed loop reaction.

Any ideas?

Does anybody have the same issue?

Our client have the same problem with SP12 on the prod.system but in the dev.system (also SP12) we can create the request well.

Thanks,

Alexa

[Former Member]

HI Alexa

I also had same issue sometime back with SP 12 where in last approval, request was not getting closed and action (assignment of role in backed) was happening.

Following Steps solved the issue.

1. Added USER DEFAULT in the Request type.

2. Created Dummy entry in USER DEFAULT (all 3 tab need to maintained) and assign to this request.

Along with that we double checked setting in ESCAPE ROUTE tab and AUTO Provisioning tab.

Regards

Asheesh

[Former Member]

Hello Alexa,

Kindly check if you have User Default configured in your system or not. We faced same issue where i did not had user default created for the data that we were provisioning and that was resulting in auto-provisioning failure but the user was changed and roles were assigned(only the request did not complete). It took us quite a lot of time to identify the same but it worked after configuring user defaults.. Does not matter if you have Action for User Default included in the request type or not. Try configuring it, mapping it with a condition and then try.

We are also on SP12 and it happens only for Change request type.

Good luck!

Regards, Varun

[Former Member]

Hello,

thank you for your support, but this workaround doesn't works.

We test it on our dev system, as well as in the other systems of our client.

FYI:

We found the solution in the sap note: 116850 for SP13: Error message "Error provisioning your request" occurs which results in the request is not closing due to provisioning error. The user account is actually being created and roles are provisioned, but the request remains in open status. This is caused by a change made in SP12 that requires user group to be populated and if it isn't, user defaults are not provisioned which causes this error.

But we cannot install SP13 without any tests and so fast. Also don't we have the problem on the dev system (SP12) of our client. So that we decide to install SP12. But now we have that mentioned problem on the prod!!!

So any ideas for a workaround or a solution?

Thanks,

Alexa

[Former Member]

Hello Alexa,

I've had this experience many times in SP12. So far they were resolved with 2 solutions:

1-A. As Varun mentioned, setup a User Default (even a "dummy" if desired that can be empty with no defaults). Assign the default to the request type in User Defaults.

1-B. Go to Configuration --> Request Types and make sure the action "USER_DEFAULTS" is assigned to the NEW and CHANGE account request types.

2. Setup a "Service Level" for NEW and CHANGE account request types. In SP12, auto-provisioning errors are also caused by not having a service level created (even if you don't plan to report on service levels).

Hope this helps you out a little.

-Dylan

[Former Member]

Hi,

servie level and user defaults aren't the solution.

The error exists still.

Thanks,

Alexa

[Former Member]

Hi Alexa,

Can u please provide the system log. We need to invastigate the reason why auto provisioning is faling

Kind Regards,

-Srinivasan

[Former Member]

2010-10-15 13:45:54,456 [SAPEngine_Application_Thread[impl:3]_32] DEBUG ProvisioningBO.java@1794:getProvisioningStatusDTO() : OUT of the method

2010-10-15 13:45:54,458 [SAPEngine_Application_Thread[impl:3]_32] DEBUG ProvisioningBO.java@1827:getProvisioningStatusDTO() : OUT of the method

2010-10-15 13:45:54,458 [SAPEngine_Application_Thread[impl:3]_32] DEBUG com.virsa.ae.accessrequests.bo.ProvisioningBO : autoProvision() : : listMessagesForSysType,list size=1

2010-10-15 13:45:54,459 [SAPEngine_Application_Thread[impl:3]_32] DEBUG com.virsa.ae.accessrequests.bo.ProvisioningBO : autoProvision() : : listMessagesForSysType #0# element:com.virsa.ae.configuration.po.ApplicationLogPO@31cf3f2[userId=GRC_20,emailId=<null>,reqNo=716,system=LS_DI6_300,recDate=10/15/2010,changedBy=AKOLB,logAction=USER CREATE,newValue=GRC_20,description=<null>,error=true,singleMessage=false]

2010-10-15 13:45:54,461 [SAPEngine_Application_Thread[impl:3]_32] DEBUG ProvisioningBO.java@248:autoProvision() : Preparing Provision to SAP ... DONE

2010-10-15 13:45:54,463 [SAPEngine_Application_Thread[impl:3]_32] DEBUG ProvisioningBO.java@277:autoProvision() : OUT of the method

2010-10-15 13:45:54,465 [SAPEngine_Application_Thread[impl:3]_32] WARN RequestBO.java@5924:autoProvisioningForApprove() : Exception occured during auto provisioning , error messages : [com.virsa.ae.configuration.po.ApplicationLogPO@31cf3f2[userId=GRC_20,emailId=<null>,reqNo=716,system=LS_DI6_300,recDate=10/15/2010,changedBy=AKOLB,logAction=USER CREATE,newValue=GRC_20,description=<null>,error=true,singleMessage=false]]

2010-10-15 13:45:54,469 [SAPEngine_Application_Thread[impl:3]_32] ERROR RequestBO.java@6665:approveRequest() : AutoProvisioning Exception, checking if the escape route is enabled

2010-10-15 13:45:54,478 [SAPEngine_Application_Thread[impl:3]_32] ERROR RequestBO.java@6681:approveRequest() : AutoProvisioning Exception, escape route is enabled, going for the escape route

2010-10-15 13:45:54,490 [SAPEngine_Application_Thread[impl:3]_32] DEBUG com.virsa.ae.accessrequests.bo.RequestBO : rerouteRequest() : AKOLB : INTO the method with toPathName : , poRequestDetails : com.virsa.ae.accessrequests.po.RequestDetailsPO@70e31b05[requestForOthers=false,userLookupEnabled=false,userIDFieldEnabled=false,userFirstNameFieldEnabled=false,userLastNameFieldEnabled=false,approverLookupEnabled=false,locationFieldEnabled=false,departmentFieldEnabled=false,emailFieldEnabled=false,telephoneFieldEnabled=false,companyFieldEnabled=false,employeeTypeFieldEnabled=false,managerTelephoneFieldEnabled=false,managerEmailFieldEnabled=false,managerNameFieldEnabled=false,requestorTelephoneFieldEnabled=false,requestorEmailFieldEnabled=false,requestorNameFieldEnabled=false,addRole=false,approveReject=,approveRejects=approveRejects,accessChanged=false,fileAttached=false,reqDataApplProvDTOs={com.virsa.ae.dao.dto.RequestDataApplicationProvisionDTO@46b5291a[reqNo=716,application=LS_DI6_300,provisionAction=ASSIGN_ROLES,userId=GRC_20,roleId=2,isProvisioned=true,isNew=false,LMD=<null>],com.virsa.ae.dao.dto.RequestDataApplicationProvisionDTO@1f9d8e3a[reqNo=716,application=LS_DI6_300,provisionAction=ASSIGN_ROLES,userId=GRC_20,roleId=3,isProvisioned=true,isNew=false,LMD=<null>],com.virsa.ae.dao.dto.RequestDataApplicationProvisionDTO@20e4920d[reqNo=716,application=LS_DI6_300,provisionAction=ASSIGN_ROLES,userId=GRC_20,roleId=4,isProvisioned=true,isNew=false,LMD=<null>]},accntValidationmsgs=[],connectionFailedSystems=,userExistSystems=,userNotExistSystems=,comm_method_type=,cstmFldName=,usersPOList=[com.virsa.ae.accessrequests.po.RequestUserPO

[koehntopp]

What are the provisioning actions assigned to the CHANGE request type?

[Former Member]

Hi,

the action are the same like in the other SP, I compared the configuration settings with the screen from the other SP.

CHANGE_USER Change User

ASSIGN_ROLES Assign Roles

[Former Member]

The logs do not show any error. Try to approve the request and right away go back to logs and search for exception and then paste the logs here.

Regards,

Alpesh