Previous work items agent

Guys,
I have a main work flow which calls a sub workflow
First step of the sub workflow is a decision step. in that decision step i want to sepcify the agent as the same one which completed the last step of the main workflow..
can you tell me what standard container variable do i need to use..

Dear Ravi,
Create a method in your BO. In that method include the logic for getting the previous workitem id and pass it to SWWWIHEAD before user decision.
Now use this method in task of your activity step. Make the task as background processing by enabling the check box inside task. As per the logic receive the last processed agent id in a workflow container element (say last_agent)
Once you enable this you need not assign any user to activity and it will not break the user decision process. Now in user decision step in expression press F4. You will see the element last_agent. Make it as the agent and you will get the desired output.
KR,
S Bharath

Similar Messages

  • UWL displays details of the previous work item:

    Hi Folks: I have posted this query in the EP Implementation forum but no response yet. Please see if anyone can advise
    If a user opens a work-item in the UWL, closes the browser window, and then opens another item on the UWL list, the new window still pops up the details of the previous work item. I tried looking at the cache parameters but with no luck.
    The undesirable workaround to the above problem is to refresh the page every minute via the parameter refresh="60" in the uwl.standard file in the
    View name= DefaultView
    Can someone advise a possible fix?
    Best Regards,
    Phani - SAP Basis Expert.

    Hi,
    As far as showing the name of the previous processor in the UWL is concerned, i believe its not possible, as Harsimran says. But there can be various workarounds.
    One is that in the second action of the process, you can give a text area or some input field in the callable object; the second processor can write something in this field, and this field can then be mapped to third screen, which tells the 3rd processor that it has been reviewed.
    Another neat solution is that, make a callable object of type:
    <b>User Management</b> -> <b>Read User Information</b>
    This callable object extracts the user information from the user who has logged into the portal and returns a lot of other information like firstname, lastname etc as output parameters. You can map these parameters to your third action and use it to display some message, say:
    <b>The review has been done by <FirstName></b>
    Reward points if it helps.

  • Please Help me with the Work Item agent to agent forwarding error

    hi folks ,
    This is the error I am getting when I am trying to forward the work item from agent to agent.
    "Work item 000000017188: Method SAP_WAPI_FORWARD_WORKITEM not allowed for type F "
    Please Help in this regards. its Urgent.
    thanks in advance for your help
    Krishna Chaitanya

    The F type Workitem cannot be forwarded because it represents Workflow (Also Subworkflow) workitem Id.
    You have to find out with workitem which has status W(Dialog Work Item; Represents a Single-Step Task) from SWWWIHEAD table and status should be in process and the TOP_WI_ID should be the value that you are trying to forward.
    Thanks
    Arghadip

  • Calling Interactive Adobe Form from workflow work-item

    Hi Experts,
    Here is the requirement.
    WE have Interactive Adobe Form developed and now the requirement is to call this form in our workflow as work-item.
    When the work-item agent double-click on the work-item he must call the adboe form.
    Please provide your inputs/suggestions/Solution/Tips.
    Regards
    Krishna

    Hi Gurprit,
    Thanks for answering my question , appreciated.
    When I am in transaction SWFVISU in the drop-down for the Visualization type I dont see "Adobe Form" .  Whether we need to create an ABAP Webdynpro to call Adobe form.
    Please explain.
    Regards
    Krishna

  • Delete Work Item from PO Releaser's Inbox during Workflow

    Hi All
    How can I delete the previous Work Item that was created in the PO Releaser's Inbox if a PO was changed which re-triggered the PO Release workflow but this time to a different PO Releaser.
    The workflow is working correctly, i.e. creating the new release item in the new releaser'd Inbox but not deleting the old Work Item for the previous releaser.
    Any idea on how I can accomplish this?
    Kind Regards
    Utian Goliath

    PLease refer the below stuff................create a task and put the code inside the method.This task should be fisrt step in your workflow.
    User sets doc to Complete from FBV2 , Complete event triggered and workflow triggered.
    Workitem goes to approver .
    Now , the user immediately changes doc from FBV2 , sets it to Complete again and workflow triggered
    workitem goes to the same approver for the same document.
    SAP_WAPI_WORKITEM_TO_OBJECT - Worklist table will giv all parent id's for the object key concatenation of
    com code , doc no and fiscal year.
    SWP_WORKFLOW_INSTANCE_DELETE - Pass the parent id and will delete the entire instance but not
    parent workitem id.
    SAP_WAPI_WORKITEM_DELETE - Pass parent id everything will be deleted .( Check_final_state = blank ).
    No trace found in SWI14 and SWI2_FREQ.
    To remove the previous workitem , create a method in the begining of the workflow , use F.M.
    SAP_WAPI_WORKITEM_TO_OBJECT to get the workflow id's and then
    SWP_WORKFLOW_INSTANCE_DELETE or SAP_WAPI_WORKITEM_DELETE to delete the previous instance.
    data : lt_worklist type table of SWR_WIHDR,
           lw_worklist type SWR_WIHDR,
           lv_objkey type SWOTOBJID-OBJKEY,
           lv_return type sy-subrc,
           lv_id type SWP_HEADER-WF_ID.
    concatenate object-key-sourcecompanycode object-key-documentn
    object-key-fiscalyear into lv_objkey.
    CALL FUNCTION 'SAP_WAPI_WORKITEMS_TO_OBJECT'
    EXPORTING
      OBJECT_POR                     =
       OBJTYPE                        = 'FIPP'
       OBJKEY                          = lv_objkey
      TOP_LEVEL_ITEMS                = 'X'
      SELECTION_STATUS_VARIANT       = 0001
      TIME                           =
      TEXT                           = 'X'
      OUTPUT_ONLY_TOP_LEVEL          = ' '
      LANGUAGE                       = SY-LANGU
      DETERMINE_TASK_FILTER          = 'X'
      REMOVED_OBJECTS                = ' '
    IMPORTING
       RETURN_CODE                    = lv_return
      TABLES
      TASK_FILTER                    =
        WORKLIST                       = lt_worklist
      MESSAGE_LINES                  =
      MESSAGE_STRUCT                 =
       if lt_worklist is not initial.
    loop at lt_worklist into lw_worklist.
      object-instance = 'X'.
    move lw_worklist-wi_id to lv_id.
    CALL FUNCTION 'SWP_WORKFLOW_INSTANCE_DELETE'
      EXPORTING
        WF_ID                         = lv_id
        DO_COMMIT                     = 'X'
    EXCEPTIONS
      WORKFLOW_DOES_NOT_EXIST       = 1
      OTHERS                        = 2
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ENDLOOP.
    ENDIF.
    Second way is to create a fork , and use wait for event step in it with the same event that is triggering the WFL
    In the same branch take a process control to end workflow instance.
    In the second branch carry out normal processing.
    Necessary branch = 1.
    So incase the user triggers the event again, a new instance will be created ,
    and in the previous instance , the first branch will follow ending the
    previous instance and the workitems of other branch will be logically deleted.

  • Repetitive Work Items for the same trip in UWL

    Hi Experts,
    Every time user clicks on save and send button , work flow gets triggered and work item is sent to user's UWL.
    For the same trip no multiple workitem are appearing in approver's uwl.
    Please suggest how we can restrict one work item at a time.
    Regards,
    Kamal

    Dear Surjit,
    1) Create a parallel fork, in the starting point of the workflow. In one branch put all the step which you developed.
    It was already created.
    2) In another step, create a "Wait for Event", in this call the change event.
    I changed from Created Event to Changed Event.
    But still the previous work item is not getting completed.
    When I have checked in SWEL.
    When I changed the Travel Expense then 2 events are trigerred.
    i)  Changed
    ii) Created
    Work Item is trigerred through Created Event.
    Do we need to map the Work flow object with Events somewhere ?
    Regards,
    Kamal Rawal
    Edited by: Kamal Rawal on Mar 26, 2009 11:43 AM

  • Incomplete Approval Work Item Removed from Agent Inbox

    Dear All WF Experts,
    I noticed this strange scenario:
    Let say Agent A and Agent B are sent a work item.
    If Agent A has executed the work item in SBWP previously, the work item is removed from Agent B's inbox (And the status is changed to 'STARTED'). However, the work item is not processed yet.
    Is there anyway to make the work item stays in the inbox until either agent approved the work item?
    Thanks in all advances.
    Regards,
    YL

    Thanks Arghadip for your response. Sorry for my blunt question.
    Actually, the Agent A and Agent B are the approvers for PR approval by position (Agent A and Agent B are the users in the mentioned position).
    Thus, when a PR is raised, both Agent A and Agent B received the same PR work item.
    If Agent A execute the work item but does not release the PR, the work item still remains in Agent A's inbox as there is no terminating event. So, based on the logic, in Agent B's inbox, the work item should still be there because the work item is not fully processed yet (no terminating event takes place).
    But, now, from what I saw, as long as any of the responsible agents executed (started) the work item, even if they do not release it, the work item is removed from all other agents' inbox and only remain in the inbox of the agent who first executed the work item.
    I interpreted this as there is at least one agent already view the work item and know the existence of the PR to be approved, thus the other agents do not need to bother about the PR anymore. But, is my interpretation correct? And is there anyway to make the work item stay in the inbox of all approvers until there is one terminating event?
    Thank you so much.
    Regards,
    YL

  • Work Items to PR Agents (Only one of two agents received)

    Dear all,
    I am facing a problem like this:
    In my PR Workflow, the task TS00007986 is assigned agents by position. There is one position applied for a particular release strategy and there are two agents under this position.
    Now, there is one PR created, it went to the correct release strategy and thus sent to the correct agent. However, only one of the agent is receiving that work item while the other don't. In another words, instead of sending to both the agents, only one received.
    In SWEL, the possible agents are showing both agents' names, but the icon "In User's Inbox" is only appearing on one of the agent.
    I would like to know, what would be the possible error for this and in such cases, how could I trace the errors?
    Thank you very much in all advances.

    Here's an update on this issue:
    For example, the two agents are Agent A and Agent B.
    I think Agent A and Agent B both received the work items. However, Agent A executed the work item but later canceled the action without processing the work item (approved or rejected the PR). When Agent A executed the work item, the same work item would be removed from Agent B's inbox, but it is still in Agent A's inbox.
    The problem is, the work item has yet to be processed. In this case, how this issue should be solved (only processed work item is removed from all the agents' inbox)?
    Thank you very much.

  • ERMS work items not visible in IC Web Client Agent Inbox

    We have configured ERMS rule modeler with a routing to an organisation unit if email content contains a specific word.
    ERMS seems to work fine as workflow is triggered and work items created in the relevant user SAP inbox (any user assigned to the organisation unit used in ERMS routing.
    When I log into the IC Web client and check for email items in the Agent Inbox, the emails are not visible!!!
    Has anybody faced a similar issue?

    Hi Manoj,
      Have you look at this configuration in SPRO
    ->Agent Inbox ->Setting for Asynchronous Inbound Processing -><b>Define Receving Emails/Fax settings</b> inthis Set Comm.method as <b>INT</b> i.e E-Mail.
    Pls check this config and get back me..
    Regards
    Raju

  • Agent Inbox Work Items

    Hi Forum
    I have this problem whereby if an agent deletes an email in their agent inbox, it shsows that its deleted, but once you search again that same email that was deleted is shown in the result list
    Tried logging off and on but the deleted work item is still displayed in the Agent Inbox
    Ritchie

    Glen we are using crm5
    Note 908153 is applicable in our situation. BADI was implemented and it seems we need to add in method BEFORE_DELETE
    We need to provide coding on this
    Any idea how to achieve using R_DELETE_ALLOWED
    Ritchie

  • Amending List content (deleteing & renaming) - Effect on previous created work items/reporting

    Hi, 
    I going to be changing the naming and structure of support groups and incident tier groups. I'd like to know what effect this has on all previously created work items and the reporting on those work items. 
    In addition, I am also adding list items to impact and risk list to change incident prioritisation settings and want to know the effect it will have on the live work items and historical work items.
    Cheers,
    Pete

    When you're thinking about editing enums in a live system, it's important to know a little but about how they work on the back end. 
    each enumeration entry essentially breaks down into a GUID and a display string; there are other properties, like Parent, Ordinal, InternalName etc, but those don't come in right now. when you use a console form to look at an incident, the control reads
    the GUID that is stored on the incident in the property in question, and then goes and collects the list that property references, and shows you the correct display string for your language. the specifics are not important, but the fact that what's stored
    on the incident is that system generated GUID is. when you edit a list, each entry has a unique GUID, that can't be changed or seen through the UI.
    Adding a new entry will add a new guid and a new display string. this option will be available the next time the form is opened. this works pretty much the way you would expect it to. 
    Renaming an enumeration keeps the GUID the same, but changes the display string. any incident with that GUID will see the new string, and the data warehouse will be updated with the new string, so
    historical incidents that had that value will now have the new display string.
    Deleting an enumeration will remove the entry from the list and break the mapping of that guid to the display string, but does nothing to the incidents that have that guid on them. the net-net of this is that any incident with that guid
    will have a value (i.e. not null) but it won't have anything to show to analysts, so it will look like it isn't set. the datawarehouse keeps those mappings even after they are deleted, so removing a mapping will not affect reporting. 
    the end of this is that you should re-classify any items before deleting an enumeration, you should only rename an enumeration if that new name makes sense for all work items for all of history. it is possible to reorder enumerations while keeping their
    GUIDs, but it requires some XMLing. I've posted about it elsewhere in this forum, so let me know if you need a link

  • Work item cannot be processed from IC WebClient  agent inbox

    Hi forum,
    When I select a work item (service ticket) and click on the
    "Interact" or "Edit" button to process the ticket the info
    message is displayed as "Unable to process selected inbox item".
    If I selct e-mail work item and click on "Interact" its
    navigating to the account identification screen, which seems to
    be correct. What might be the problem with work item for service
    ticket processing from the agent inbox by clicking interact or
    edit push button.
    Shridhar

    Hi Shridhar,
    1. Is service ticket link available in your webclient.If not add the service ticket link in the navigation bar profile.
    2. Also make sure that the transcation type(with which the search of service ticket happens) is assigned to the business transcation profile.
    Wish the information is useful.If it helps, do reward with points.
    Regards,
    Shalini Chauhan

  • Agent not receiving work item assigned to him

    Dear gurus,
    we're using SRM server 550 with SP08. We are using n-step workflow for contract change version. The approvers are being determined by reading from a table. In total there are 8 approvers determined. We then add one more approver manually. Then we do the approval. The approver1 manage to approve the contract successfully. However the problem come when approver2 want to approve, in which the contract not appear in his inbox.
    When we check the contract again, we still see the approver as approver2, with slight difference in which there is no information "In approval since xxxx".
    Can anyone suggest how can we prevent this to happen? And what can we do if such case happens?
    Best regards,
    John

    Hi,
    Why do you want to add the approver manually?
    where do you add the approver? as second approver?
    In the N-step badi , system will always retrieve the approver based on the coding in the BADI.
    In the Badi you will be specifying the index for each of the approver involved in the approval chain.
    looks like in your case , system is not able to identify the correct approver and so the work item is not send out.
    is the approval flow working correctly without an added approver?
    regards

  • Work Item not getting logically deleted

    Hi All,
    We have created a custom workflow for PR approval at Item Level. I have RELEASE STEP CREATED as triggering event.
    I have used a FORK with 5 branches with 4 wait events and min cond as 1. The inherited business object ZBUS2009 has been created with events CHANGE, DELETED. The business object has been delegated to Original Business object BUS2009.
    To trigger the events like DELETED and CHANGED, I have used POSTED METHOD of ME_REQ_POSTED BADI.
    When a PR Item is created the agents are determined successfully and work item is placed in his SAP Inbox. Later the PR Item has been deleted and saved the BADI Implementation is triggered and I can see the log in SWEL for DELETED event with success icon.
    However when i go back to PR Item which i have deleted and see the workflow log the work item is still in the approver's inbox. but the graphic log shows that the DELETED branch of the fork is completed. I tried all options like Buffer synch, background job, queue admin etc with no success.
    I did the same workflow at one of my previous clients and it is working perfectly for last 2yrs.
    Can any one guide me on what could have gone wrong or what i am missing?
    Thank you all in advance for help...
    Regards,
    Lakshmi Narayana

    Hi Arghadip,
    Thanks for your quick response.
    The fork is having 5 parallel branchs and 1 necessary branch and is INDEED HAS NO EXTRA CONDITIONS.
    Also as i mentioned the graphical log shows that the completion of BRANCH Beneth DELETED but the work item is still in approver's inbox. 
    Please let me know if I am missing something....
    Rgds,
    Lakshmi

  • Work item not getting displayed in the portal

    Hi  experts,
    We are creating a protoype for one of the standard HCM form for change in working time. When we initiate the process, the workflow is supposed to identify the agent(which is the manager in this case) and push the work item in the inbox of the manager.
    In our issue, we are able to see the workitem in SAP inbox, but the same work item is not getting displayed in the portal.
    If we try to approve from the SAP inbox, the hard coded message u201CWork item can only be executed using the Portal and the UWLu201D comes. [this comes through the method of  one of the tasks 17900101 which we are using for approving the form]
    We commented the message by using a Z class. Now we donu2019t get the hardcoded message, but still the workflow does not complete from here.
    Can this be aan integration issue of the workflow tasks with the portal??Can someone elaborate on this??

    <ItemType name="uwl.task.webflow.TS17900101.SAP_ECC" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="launchWebDynPro" executionMode="default">
          <ItemTypeCriteria systemId="SAP_ECC" externalType="TS17900101" connector="WebFlowConnector"/>
          <Actions>
            <Action name="launchWebDynPro" groupAction="" handler="SAPWebDynproLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
              <Properties>
                <Property name="WebDynproApplication" value="ApproveFormApp"/>
                <Property name="WebDynproDeployableObject" value="sap.com/pa~asr~formstep"/>
                <Property name="newWindowFeatures" value="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no"/>
                <Property name="openInNewWindow" value="yes"/>
                <Property name="display_order_priority" value="5"/>
              </Properties>
              <Descriptions default=""/>
            </Action>
          </Actions>
        </ItemType>
    You have to say to your portal team to modify their XML file as above. In simple you hvae to configure the task in the portal and in the SWFVISU txn as follows with the following vizualization parameters
    Task TS17900101 and visualization type is JavaWebDynpro
    APPLICATION     ApproveFormApp
    PACKAGE     sap.com/pa~asr~formstep

Maybe you are looking for