Delete User assigned to a task

Hi experts,
I would like to delete a user assigned to a task using the Administration area in guided procedures tab of the portal.
So I go to : Guided procedures TAB --> Administration --> Maintain Processes --> Running process list --> Change Authorization --> New User Assignments
But unlike this document:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/173dceea-0c01-0010-0698-819d627fed79
on page 7,
the "Remove User" button is not present.
Can someone explain why?
Is this an error of the document or is it possible to remove a user assigned to a task?
Thanks,
Luca

Thank you very much for your answer Sudhir.
Now I know why the button is not present in my portal. 
Luca

Similar Messages

  • OIM 9.1.0.2: Remove user assigned to a task in Provisioning Process

    I have read Note: Ability to Have Multiple Approvers Per Resource Object in OIM [ID 429999.1], and executed each steps described in it. But when grant these resource object to some user. First the request was not sended directly to a approval process, as had been expected that I would. The request was send to a provisioning process, specifically to user has been assigned a task, when the user approves the request until the request is then sent to approval process.
    I need to send directly to a approval process, because that's where I have defined my levels of approval.
    I'm using oim 9.1.0.2 BP18 running on OC4J 10.1.3.5 on AIX 6.1 64-bit clustered install with two nodes, Oracle Database 10.2.0.4 on AIX 6.1 64-bit on RAC.

    Hello Everyone,
    Thanks for your response. Actually i have a Approval Process, where i have defined my levels of approvals. In Resume I have this Env. :
    1.- A Resource: ResourceA
    2.- A Provisioning Process in relation with ResourceA.
    3.- A Approval Process in relation with ResourceA.
    The request was send to a provisioning process, specifically to user has been assigned a task, when the user approves the request until the request is then sent to approval process.
    I need to send directly to a approval process, because that's where I have defined my levels of approval. In other words i need to bypass the user assigned a task in provisioning process.

  • Unable to delete agent assignment from Standard Task 8267 DECISION

    Hi All
    In transaction PFTC_CHG I'm trying to Delete Agent Assignment (Shift + F2), the screen simply refreshes and the action is not performed - the user is not deleted from the Demo Workflows parent folder? I'm not sure how to change or remove this entry? Authorisations check out fine.
    Regards,
    Adrian

    Hi ,
    Go through below links ..i am sure you will find something helpful.
    How to delete agents
    remove assigned agents
    Regards,
    Himanshu Joshi

  • Behaviour of "Disable/Delete User After End Date" Task

    Hi Expert,
    We ran the given OOTB task "Disable/Delete User After End Date" and the behavior is always delete. How,if possible, to change the behavior to disable?
    Thanks in advance.
    SK

    In order to change the behavior, you have to set the system manager preference called "Period to Delay User Delete" to something bigger than the task will make the user disabled and will automatically delete them at a future date.

  • CProjects - Multiple Users Assignment to single task

    Hi All,
             Can we assign multiple users to a single task, by making them in a User Group.
    regards,
    rajesh.

    Hi rajesh,
    Sure, I hope, you are talk about cProject 4.0.
    You can create a role, which have different business partner (users) assigned . you can assign then such business partner (one or multiple) to the task.
    But you can only have a business parnter as responsible.
    Using User-Group is used only for the authorisation aspect.
    Kind regards,
    Zhenbo

  • Getting error for opening shopping cart after deleting user fron org struct

    Hi Experts
    I am getting dump user attribute not maintained after deleting user assignment from org structure.
    what can i do to retain old status. or atleas wants to avoid getting this dump ..while displaying this SC.
    pl provide any solution
    Regards
    Nilesh,

    It is never a good idea to just delete a user assignment. What I find is that people just go on deleting assignments without considering the consequences. And later on it gives a lot of trouble to correct errors.
    So never delete an assignment, but give it an end date (it's there for a reason!).
    On to your problem: as said by someone else, get the user/business partner back into the organisational model (doesn't matter where actually) and there won't be an error. Try first with ppoma_bbp, if that doesn't work use pp01 - use pp01 with care and know exactly what you want to achieve else you'll end up creating a bigger mess than you started with.
    If you have deleted the business partner completely you will have to update the database by hand hacking tables (a big reason never to delete a bp you are not entirely sure about).
    Regards,
    Robin

  • Approval Request assigned to DELETED User

    Hi All,
    I have created an approval process with type "User" and "APPROVER" as user and then I have deleted this user in OIM. But still the approval request is getting assigned to this user "APPROVER".
    Is there way to assign this request to "SYSTEM ADMINISTRATOR" or user's manager or display a kind of error message in the "Approval Details" page.?
    Thanks & Regards
    INIYA

    Don knwo why it is going to Deleted User. It shouldn't go. If it is going then you can raise SR with Oracle.
    For your question, with custom Task Assignment Adapter you can assign it to System Administrator. If your Resource Object has some then you can make one more field with some Default Message.
    If Approver is deleted then you can update the form field with any message you want.

  • Assigning USER values in the task of workflow

    Hi Experts ,
    I am using the USER option in the task to sending workitem to the perticular user which i have given in the user option .
    I am doing this in development .
    When i will move my workflow to Production then if the user id which i have given in develpment will not be present in production then my workflow will not work there .
    And in production also we may not change the user id ,
    so is there any way through which we can able maintain the userid values in production .
    Note : I want to use the USER option in the task not through the expression option .
    thanks
    sarmistha

    Hi Sarmistha,
    Please check this PDF for Adhoc assignment to workflow which determines agents dynamically..
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5023ddbd-de8d-2a10-d7a2-c9910d1ed6ad
    Check this link which also gives you help in assigning agents at runtime using Adhoc step in Workflow
    http://****************/Tutorials/Workflow/adhocAgent/Assignment1.htm
    Hope this would help you.
    Good luck
    Narin

  • How to call OID delete user process task from AD process definition

    Hi All,
    I wanted to call OID delete user process task from AD process def. I have created a process task in AD Process def which will be integrated with OID Delete User adapter. How can i map OID related attributes to the adapter api?
    Expected inputs for OID delete api :
    root DN
    orgDN
    admin pwd
    server
    attr lookupcode
    XLOrgFlag
    sProcessInsKey
    UserID
    PDataOrg
    port
    AdminID
    SSLFlag
    here i cannot map some like : sProcessInsKey
    any pointers would be appreciated.
    Regards,
    Ashok

    OID delete user process task from AD process defWhy don't use call Revoke Resource API ?
    http://otndnld.oracle.co.jp/document/products/id_mgmt/idm_904/doc_cd/javadocs/operations/Thor/API/Operations/tcUserOperationsIntf.html#revokeObject%28long,%20long%29
    Use getObject API
    Iterate through resultset.
    If RONAME == OID User then call revokeObject

  • Process Definition Delete User Task

    Hi All,
    we have created Dummy Resource.For this Dummy resource i have added delete task so that when ever the resource is revoked the request will go to system admin group. so that he will manually update (setResponse) to revoked.
    But when i click on revoke buttom all the task inside that resource are going to cancel state and i am not able to see the delete task in the resource history .
    Thank you

    You need to add Delete user task under Undo Tab of any cancelled task(generally create user task). Once you do this your Delete User task will be triggered.

  • OIM PSFT UM delete user task

    Hello,
    We are using PSFT UM v. 9.0.4 and I can't see any delete user task. The conenctor documentation does not mention it int he supported functions. Does this mean that the connector cannot delete the user or this is a must have for any connector?
    Thanks

    Hi,
    you have to apply undo task (delete task) on an unconditional task.
    Also check Revoke if no longer applied in access policy, so whenever the the group membership rule failed delete task will trigger for revoke.
    There should not be difference via API, your revoke task from OIM does same work .
    Thanks,
    Kuldeep
    Edited by: Kuldeep on May 9, 2012 11:49 PM

  • ADCS Delete user process task

    I am very sorry to ask this question to you, But I am helpless here,
    Dev team has implemented Provisioning/DeProvisioning process for AD. If user terminated, OIm first disable the user's AD account and after 21 days, its deletes the AD account. I am not able to find, how and when "ADCS delete user" task has been invoked by oim. Can any one please help me to find it out.
    Thanks.

    There should be a schedule task which runs daily and check for the Termination Date for all these users, if its > 21 days then it must have been manually inserting this task in the user's AD resource profile

  • OIM11gR2 - iPlanet Connector - iPlanet Trusted Delete User Recon Task

    Hello All,
    What is the standard OOTB action performed on OIM User when I run the iPlanet Trusted Delete User Recon Task?
    I couldn't tell from the connector documentation below:
    http://docs.oracle.com/cd/E11223_01/doc.904/e10446/using.htm#BABIJCFF
    Does it disable the OIM user?
    Does it delete the OIM user? (soft delete? hard delete?)
    I'm interested in soft delete.
    Thanks
    Adr

    Apologies, My previous post was intended for end date reaching.
    It just deletes the user from OIM. It does not care about end date or disable schedule jobs.
    However, the user status will be set as "deleted".
    http://docs.oracle.com/cd/E11223_01/doc.910/e11197/using_conn.htm#CACGJGGA
    P.S I gave this document for AD (However, it applies to any connector document as it is basic definition of trusted source).
    The basic behaviour and definition of trusted reconciliation is to delete the user identity in OIM if itis deleted in the source system.
    Cheers,
    Tejo.

  • Cannot delete users from Catalog Manager

    We're trying to delete users who no longer have access to OBIEE from the Catalog Manager. When we try we get an error saying access denied for user to path /users/[userid]... I know we can go out to the file system and manually delete the folder but we would like to use the Catalog Manager for this so that we can delegate this to our security staff.
    Is a configuration setting wrong somewhere? It fails with users who have been granted admin rights as well as for the administrator id.
    Security is configured with Hyperion Shared Services via an initialization block This is working fine. When we add a user to a group in Shared Services, the user catalog is created when the user logs in. We just can't get rid of it after removing the user from the Shared Services group.
    We are running everything except the Admin Tool on AIX.
    Thanks.
    Jerry

    I'm not sure I understand.
    My system is configured to use Hyperion Shared Services for authentication. We do not create users in OBIEE. We create groups in OBIEE and assign them privileges. We then create the same groups in Shared Services. We add users to the appropriate group in Shared Services. When the user logs in, their user folder is created. When we need to remove a user's access, we take them out of the Shared Services group. We then want to delete their user folder in the catalog. We log in as an admin (we even tried this with the Administrator account), but we get the error.
    Is there any way to delete users via OBI Presentation Services > Administration > Manage Catalog?
    Thanks.
    Jerry

  • Cannot delete users from the Central Management Console

    I cannot delete users from the Central Management Console.  I'm logged in to Enterprise as administrator but still get the following error:
    There was an error while writing data back to the server: Sorry, you do not have the right to 'Delete objects' (id - 22) for 'koberg' (id - 725415). Please contact your system or permissions administrator if you require this right.
    Thanks in advance for any help on this matter.

    Oops, my mistake, sorry. Ok, so the Administrator cannot delete user koberg.
    Check top level:
    Logon to CMC, browse to Home > Settings and select the Rights tab. These are your top level settings. Factory default will show only Administrators and Everyone. Select the Net Access "Advanced" for the Administrators group. NB: Do not select these group names links - they will jump you out of the top level! On the Advanced rights page, ensure the right to "Delete objects" is explicitly granted.
    Then set for the Users top level folder:
    In the CMC, browse to Home, and select Users. Select the "Rights" button. Again - NB: Do not select these group names links - they will jump you out of the Users top level folder! Set the Administrators group to "Full Control". Save.
    That should be all you need. However, there is a possibility the previous admin was busy setting security not only at the account level, but on groups so we need to verify the user:
    In the CMC, browse to Home, and select Users. In the User list, select koberg. In the koberg account page, select the Rights tab. If the Administrators is not set to (Inherited Rights), make it so, and when you select the "Update" button, you should see the Net Access update to "Full Control". If this is the case, you should follow these steps on each account and accomplish this.
    And if you still can't delete it, verify the groups:
    In the CMC, browse to Home, and select Users. In the User list, select koberg. In the koberg account page, select the "Member of" tab. Note all groups koberg is a member of. Then in the CMC, browse to Home, and select Groups. Select the name hyperlink for the group(s) that koberg belongs to. On the group page, select the Rights tab, and ensure the Administrators have (Inherited Rights) - Full Control on all of these, also. If not, set it.
    Finally, I know you inherited this, but let's overview some basics of simplifying your deployment administration. Follow these guidelines, and your administration life will be so much easier.
    1. The Everyone group should never have any subgroups. Ever. All accounts on the system are a member of the Everyone group. Adding subgroups to the Everyone group is redundant.
    2. For simplicity's sake, Application level access should be set on the Adminstrators Group, and the Everyone group. I know there are customers who add groups to application rights. I don't understand why users would have an account on the system if they are not allowed access to InfoView, but it's your system.
    3. From a report object perspective, the Everyone group should be set at the top level to "No Access". This will result in them having no rights on anything at all. You break this inheritance at the application level to give them access to InfoView and other apps. On folders and objects, you ADD groups, then assign (ADD) rights as desired.
    4. If you can help it, never explicitly deny a right to any user or group for any object or application. Explicitly deny overrides any other setting. If a user belongs to group A and group B, and group A is explicitly denied a right, you can explicitly grant it for group B or the user all day long, and it will still be denied. Always try to put yourself in the position of adding groups/users, and adding rights, then inheriting as far down the folder tree as you can.

Maybe you are looking for