CUP: How to delete an account in SAP?

[Former Member]

Hi all,

I'm configuring and testing my workflows in Compliance User Provisioning.

I'm able to create an account in SAP, to assign or remove it roles and so on, but I can't delete it.

I implemented a path starting from the "Delete Account" request. The workflow works well, but on the last stage, when I click to the "delete" button to delete the user in SAP I can see circle image (the typical elaboration image) and nothing happen. It seems it started to delete the user but it nerver finish!

Can you help?

Thanks

[Former Member]

AnnaMarie,

[hkaur]

Hello Annamaria,

Yes you will get Delete and Lock Request types as predelivered request types with AC 5.3 installation.

Harleen

SAP GRC RIG

[Former Member]

Annamaria,

SAP has always delivered all the seven (NEW, NEW Hire, Change, Delete, Lock, Unlock and information) request types in CUP. Have you looked at the actions associated with delete request types as I mentioned before?

The logs also do not contain any reference to the delete request. Can you paste right logs here?

Regards,

Alpesh

[hkaur]

Hello,

Check the actions that your LOCK REQUEST and DELETE REQUEST have.

Make sure that they have the desired lock user and delete user action respectively.

Harleen

SAP GRC RIG

[Former Member]

Hi Annamaria,

Make sure that you (or someone else) are not blocking the user in the backend.

Regards,

Vit

[Former Member]

Hi,

Please check whether the user which you want to delete is opened in the backend system using su01 or su01d. If it is so then please close your su01 screen and do the activity again.

Regards,

Sudip...

[Former Member]

Yes, I checked it and the user I want to delele isn't used.

I have the same problem with the lock funtion.

Thanks.

[Former Member]

Hi Annamaria,

Have you updated any patch? Are your RTA patch nad GRC patch in sync?

Can you check it again after restarting the server? Check both workflows-New user creation and deletion.

Give the System Log in CUP. You can get it from this path-

CUP-Configuration-Monitoring-System Log

Search by request number and copy the logs.It may help us debug the problem.

Regards-Sabita

[koehntopp]

Let's see the logs.

Maybe it's an ABAP authorization issue - try assigning SAP_ALL to the RTA user for testing, then trace it and fix the roles.

[Former Member]

I attached below a part of the log with some detailes related to the delation of a user.

As you can see, no error message exist, but I think the problem could be related to the "isExpired()" messages.

What do you think about?

Thanks

2009-05-06 17:30:28,264 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : WORKFLOW_PATH - 0 Wed May 06 17:04:25 CEST 2009 Tue Sep 05 05:55:00 CEST 2006

2009-05-06 17:30:28,266 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method : cachecom.virsa.ae.service.cache.AEBAPIMapCache@ 4432454ccacheInfoDTOcom.virsa.ae.dao.dto.CacheInfoDTO@ 7c3158d3[cacheName=BAPI_MAPPING,cacheDescription=BAPI Mapping,period=0,timeStamp=Wed May 06 17:09:50 CEST 2009,type=M]

2009-05-06 17:30:28,267 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : BAPI_MAPPING - 0 Wed May 06 17:10:28 CEST 2009 Wed May 06 17:09:50 CEST 2009

2009-05-06 17:30:28,269 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method : cachecom.virsa.ae.service.cache.WorkFlowTypeCache@ 4063a38ecacheInfoDTOcom.virsa.ae.dao.dto.CacheInfoDTO@ 6a78ed21[cacheName=WORKFLOW_TYPE,cacheDescription=Workflow Type,period=0,timeStamp=Mon May 04 09:42:36 CEST 2009,type=M]

2009-05-06 17:30:28,270 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : WORKFLOW_TYPE - 0 Wed May 06 17:04:24 CEST 2009 Mon May 04 09:42:36 CEST 2009

2009-05-06 17:30:28,272 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method : cachecom.virsa.ae.service.cache.RequestActionCache@ 4d86e0a8cacheInfoDTOcom.virsa.ae.dao.dto.CacheInfoDTO@ 4677c73[cacheName=REQUEST_ACTION,cacheDescription=Request Action,period=0,timeStamp=Wed May 06 09:09:35 CEST 2009,type=M]

2009-05-06 17:30:28,273 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : REQUEST_ACTION - 0 Wed May 06 17:04:24 CEST 2009 Wed May 06 09:09:35 CEST 2009

2009-05-06 17:30:28,275 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method : cachecom.virsa.ae.service.cache.FunctionalAreaCache@ 52075d5bcacheInfoDTOcom.virsa.ae.dao.dto.CacheInfoDTO@ 194c736e[cacheName=FUNCTIONAL_AREA,cacheDescription=Functional Area,period=0,timeStamp=Tue May 05 18:27:40 CEST 2009,type=M]

2009-05-06 17:30:28,276 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : FUNCTIONAL_AREA - 0 Wed May 06 17:04:15 CEST 2009 Tue May 05 18:27:40 CEST 2009

2009-05-06 17:30:28,278 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method : cachecom.virsa.ae.service.cache.MessageCache@ 61822b6fcacheInfoDTOcom.virsa.ae.dao.dto.CacheInfoDTO@ 6a2e47bb[cacheName=MESSAGE_CACHE_NAME,cacheDescription=Message Objects,period=0,timeStamp=Tue Sep 05 05:55:00 CEST 2006,type=M]

2009-05-06 17:30:28,280 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : MESSAGE_CACHE_NAME - 0 Wed May 06 17:04:20 CEST 2009 Tue Sep 05 05:55:00 CEST 2006

2009-05-06 17:30:28,282 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method : cachecom.virsa.ae.service.cache.RequestPriorityCache@ 28f1b66ccacheInfoDTOcom.virsa.ae.dao.dto.CacheInfoDTO@ 29184823[cacheName=REQUEST_PRIORITY,cacheDescription=Request Priority,period=0,timeStamp=Tue Apr 07 10:21:51 CEST 2009,type=M]

2009-05-06 17:30:28,284 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : REQUEST_PRIORITY - 0 Wed May 06 17:04:22 CEST 2009 Tue Apr 07 10:21:51 CEST 2009

2009-05-06 17:30:28,285 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method : cachecom.virsa.ae.service.cache.RequestStatusCache@ 14ff8174cacheInfoDTOcom.virsa.ae.dao.dto.CacheInfoDTO@ 792806e8[cacheName=REQUEST_STATUS,cacheDescription=Request Status,period=0,timeStamp=Tue Sep 05 05:55:00 CEST 2006,type=M]

2009-05-06 17:30:28,286 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : REQUEST_STATUS - 0 Wed May 06 17:04:20 CEST 2009 Tue Sep 05 05:55:00 CEST 2006

2009-05-06 17:30:28,288 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method : cachecom.virsa.ae.service.cache.WorkflowStageCache@ 128bf171cacheInfoDTOcom.virsa.ae.dao.dto.CacheInfoDTO@ 261b6447[cacheName=WORKFLOW_STAGE,cacheDescription=Workflow Stages,period=0,timeStamp=Wed May 06 16:13:00 CEST 2009,type=M]

2009-05-06 17:30:28,289 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : WORKFLOW_STAGE - 0 Wed May 06 17:04:23 CEST 2009 Wed May 06 16:13:00 CEST 2009

2009-05-06 17:30:28,291 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method : cachecom.virsa.ae.service.cache.ApplicationCategoryCache@ 21983b3acacheInfoDTOcom.virsa.ae.dao.dto.CacheInfoDTO@ 32dda77c[cacheName=APPLICATION_CATEGORY,cacheDescription=Application Category,period=0,timeStamp=Tue Sep 05 05:55:00 CEST 2006,type=M]

2009-05-06 17:30:28,292 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : APPLICATION_CATEGORY - 0 Wed May 06 17:04:14 CEST 2009 Tue Sep 05 05:55:00 CEST 2006

2009-05-06 17:30:28,294 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method : cachecom.virsa.ae.service.cache.CompanyCache@ 11586e11cacheInfoDTOcom.virsa.ae.dao.dto.CacheInfoDTO@ 505484dc[cacheName=COMPANY,cacheDescription=Company,period=0,timeStamp=Thu Apr 30 13:28:12 CEST 2009,type=M]

2009-05-06 17:30:28,295 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : COMPANY - 0 Wed May 06 17:04:15 CEST 2009 Thu Apr 30 13:28:12 CEST 2009

2009-05-06 17:30:28,297 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method : cachecom.virsa.ae.service.cache.ApplicationAreaCache@ 44a226fccacheInfoDTOcom.virsa.ae.dao.dto.CacheInfoDTO@ 761ed7fa[cacheName=APPLICATION_AREA,cacheDescription=Application Area,period=0,timeStamp=Tue Sep 05 05:55:00 CEST 2006,type=M]

2009-05-06 17:30:28,298 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : APPLICATION_AREA - 0 Wed May 06 17:14:51 CEST 2009 Tue Sep 05 05:55:00 CEST 2006

2009-05-06 17:30:28,299 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method : cachecom.virsa.ae.service.cache.EndUsersDetailsCache@ 71ad8d97cacheInfoDTOcom.virsa.ae.dao.dto.CacheInfoDTO@ 5cdeb0b7[cacheName=ENDUSERSDETAILS,cacheDescription=End User Details,period=7,timeStamp=Wed May 06 17:26:52 CEST 2009,type=D]

2009-05-06 17:30:28,301 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : ENDUSERSDETAILS - 7 Wed May 06 17:26:51 CEST 2009 Wed May 06 17:26:52 CEST 2009

2009-05-06 17:30:28,302 [Thread-91] DEBUG DBCacheVerifier.java@ 63:isExpired() : ENDUSERSDETAILS - 7 Wed May 06 17:26:51 CEST 2009 Wed May 06 17:26:52 CEST 2009

2009-05-06 17:30:28,304 [Thread-91] DEBUG DBCacheVerifier.java@ 107:getExpireTimeStamp() : INTO the method : cacheInfocom.virsa.ae.dao.dto.CacheInfoDTO@ 5cdeb0b7[cacheName=ENDUSERSDETAILS,cacheDescription=End User Details,period=7,timeStamp=Wed May 06 17:26:52 CEST 2009,type=D]cacheDateWed May 06 17:26:51 CEST 2009

2009-05-06 17:30:28,305 [Thread-91] DEBUG DBCacheVerifier.java@ 125:getExpireTimeStamp() : OUT of the method : Wed May 13 17:26:52 CEST 2009

2009-05-06 17:30:28,307 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method : cachecom.virsa.ae.service.cache.RoleNameCache@ 392aeecfcacheInfoDTOcom.virsa.ae.dao.dto.CacheInfoDTO@ 6a7d834e[cacheName=ROLENAME,cacheDescription=Role Name,period=0,timeStamp=Wed May 06 17:28:22 CEST 2009,type=M]

2009-05-06 17:30:28,308 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : ROLENAME - 0 Wed May 06 17:28:28 CEST 2009 Wed May 06 17:28:22 CEST 2009

2009-05-06 17:30:28,310 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method : cachecom.virsa.ae.service.cache.LDAPFieldMappingCache@ 31a4755bcacheInfoDTOcom.virsa.ae.dao.dto.CacheInfoDTO@ 62f59aab[cacheName=LDAP_FIELD_MAPPING,cacheDescription=LDAP Field Mapping,period=0,timeStamp=Tue Sep 05 05:55:00 CEST 2006,type=M]

2009-05-06 17:30:28,311 [Thread-91] DEBUG DBCacheVerifier.java@ 58:isExpired() : LDAP_FIELD_MAPPING - 0 Wed May 06 17:04:12 CEST 2009 Tue Sep 05 05:55:00 CEST 2006

2009-05-06 17:30:28,313 [Thread-91] DEBUG DBCacheVerifier.java@ 52:isExpired() : INTO the method :

[Former Member]

Follow Harleen's recommendation. If you upgrade 5.3, sometimes you lose association of action with request types. Go to configuration -> request type -> select 'delete' and click on change. Check if you have 'DELETE_USER' action in the assigned actions (left hand panel) panel or not. You must have this action in the delete request type for delete account to work.

Regards,

Alpesh

[Former Member]

Hi Annamaria,

Have you checked the workflow type for Delete Account?

This message- WORKFLOW_TYPE doesn't come normally.

Check it -

1. CUP-Request Configuration-Request Tpye-Delete

Check if it has workflow type -CUP and it is active.

2. Goto change mode and check if it has associated actions as Harleen has mentioned-DELETE_USER

3. Check whether your JCO is active and connector is working fine. Sometimes if the webuser is give nas type communication, it gets expired so JCo dosnt work.

4. Confirm if your webuser has SAP_ALL authorization.

5. Confirm if your GRC and RTA patches are in sync.

6. Sometimes restaring the server also solves problem.

Regards-Sabita

[Former Member]

I found a note (SAP Note 1131800) in which is written:

"The Standard Request Types that are delivered with the product for provisioning are:

- New

- New Hire

- Change

Any Custom Request types for provisioning or delete/lock User are currently not supported in Compliant User Provisioning."

Do you if in the 5.3 release Delete/Lock user has been supported?

Thanks.