PO-Release (Workitem -WFBATCH)

Hi,
PO Release -workflow
1.3 level of approvers.
2.using Fork (Waiting For Changes)
3.using Loop
4.Two Startevents (Releasestep Created. Changed Event)
5. In First level workfing fine.
PRoblem. IN second level Workitem goes to WF-BATCH?

Simple create one more method / attribute and get the agent . Replace this wf_initiator with this agent. Remember to concatenate 'US'.
REgards
Venkatesh

Similar Messages

  • PR Release Workitem  in inbox

    Hi Friends,
    I have worked on standard BO. 
    PR release workflow as purchaseofficer got the mail and pr release-please register workitem..that's fine.
    But purofcr should be  click on workitem. he is not saved. then purofcr back to inbox. but workitem is not inbox. it's go to outbox.
    now client requirement workitem is not saved still in inbox  after saved then go to outbox.
    Plz need your's help.

    Hi,
    i  know difference in mail  & workitem.  and check also outbox.
    my Workflow purchase officer got mail and workitem both.he is click on workitem. then he is not check the confirm  button. he is back to inbox.
    not before confirm check box disappear on workitem in inbox.. then after check the check the disapper in workitem.
    Regards
    MSR

  • PO release workitem won't clear - 'Check FM ends with exception'

    Hi all,
    I've got a workflow with multiple approval steps even after all steps in the PO complete successfully, i have one work item in the middle of the approval process that won't clear and the event log shows 'Check FM ends with exception' even though the PO is released successfully.
    i've got the BUS2012 RELEASED event set as a terminating even to task TS20000166 as standard but i think the release code might not be getting received correctly.  How can i debug this or fix it?
    Regards
    Amir

    Hi Kjetil
    Unfortunately it is not a customer function.  ME_REL_CHECK_EVENT_PARAM is a SAP standard Check Function and has trapped me before.  Basically it checks the workitem container (before image if you like) against the event container.  (see Below)
    Get the release code from the workitem container.
    swc_get_element wi_container 'RELEASECODE' wi_release_code.
      if sy-subrc ne 0.
        raise container_error.
      endif.
    Get the release code from the event container.
    swc_get_element event_container 'RELEASECODE' evt_release_code.
      if sy-subrc ne 0.
        raise container_error.
      endif.
    Compare the two release codes; if not equal: raise exception.
       if wi_release_code ne evt_release_code.
         raise release_codes_different.
       endif.
    Weird, huh.
    Regards
    Gareth

  • Terminating Event in PO Release Workflow. Workitem is not terminating

    Hi WF Experts,
                            I have done Purchase Order Release Workflow with 10 level release With 2 days dead line. Since standard release supports only 8 level release i have opted for Role Resolution Via User Exit 9 . and i am picking release codes from ztable.
    I was working fine till now.But suddenly end users are facing problem that workitem is not terminating even after they have released the PO.
    What could be the issue what is the terminating event for PO Release workitem.
    Please suggest me how to resolve this issue.
    Regards,
    Hari

    Hi Hari,
    Please check if the following links helps:
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/sap%252bworkflow%252bevents
    http://help.sap.com/saphelp_nw04/helpdata/en/c5/e4b590453d11d189430000e829fbbd/frameset.htm
    Hope this helps!
    Regards,
    Saumya

  • Rearrange workitems after organisation and staffing change

    Hello,
    I have a question regarding workitems after an organisation and staffing change.
    Old situation
    Organisation A has Position A and B.
    Position A is described by responsibility E
    Position B is described by responsibility F
    Position C is described by responsibility G
    Position D is described by responsibility H
    New situation
    We disconnect responsibilies E, F, G and H from position A, B, C and D.
    We created Organisation Q with position W and X.
    Position W is described by responsibility E, F.
    Position X is described by responsibility G, H.
    I expected that the workitems which were not already assigned to users were taken over to the new positions. This is not the case.
    Should I run a job or did I do something wrong?
    Regards, Ramon.

    Hi,
    I run the program, assigned an item to myself and then released it. The workitem is now attached to the new position and not to any user. This is what I want.
    Is there a transaction/program to assign and release workitems en masse?
    It's about 21.000 workitems which have to be reassigned.
    Thank you in advance.

  • Get Workflow protocol

    Hello.
    for our workflow regarding Purchase Order release strategy we need to know which
    agent has processed the last release (=Workitem).
    Now i found FM "SAP_WAPI_DIALOG_PROTOCOL". This FM shows up the needed
    information in tab "Workflow objects" in dialog.
    But anybody knows how to get this information from the database tables ? Or is there
    any FM or class which will provide this information without dialog ?
    Thanks a lot.
    Sebastian

    Hi Sebastian
    You can use FM SAP_WAPI_WORKITEMS_TO_OBJECT to get the Work items associated with your PO.
    Call the FM where OBJECT_POR-SIBFBORIID = PO Number, = 'BO' (if your workflow uses Business Object) or 'CL' (if the WF uses ABAP Classes and SIBFCATIDSIBFTYPEID = BO name / Class Name.
    You will then get the list of all objects associated with your PO - all workitems in table WORKLIST.
    Now you need to remove all items which are not dialog steps - delete WORKLIST where WI_TYPE <> 'W'
    Now remove Non Completed Ones - delete  WORKLIST where WI_STAT <> COMPLETED
    Now you have all completed dialog items - sort them by WI_ID DESCENDING -> Last work item on top
    Read the first line to get WI_AAGENT - the actual agent who completed the step.
    Regards,
    Modak

  • Error In Wortk flow.

    Hi All,
    We are enabling the work flow for PO release strategy.The workflow is working fine for SA, but as per PO as concerned it is stopping at the Release Purchase order though we have released all the level as provided in the release strategy.
    We have switched on trace by using SWEl,we found the following error message.Please help me out to resolve this issue.
    Check FM ends with exception,
    In binding i am getting relcode event, what is this, why this code has occurred.
    Pls help me out.
    Regards,
    Santosh S Jajur

    Hi ,
    please refer to following threads-
    PO Release wf -Check FM ends with exception
    PO release workitem won't clear - 'Check FM ends with exception'
    hope this helps.
    thanks,
    sahiba

  • Mass approval of CATS Timesheets

    Currently CATS timesheets show up on the UWL and users click on the timesheets individually that opens up the screen   RCATS_APPROVE_ACTIVITIES in transaction CATSW and the users either Approves or Reject it. Now they want some way of mass approval of timesheets to show multiple records in one screen. What are my options to do that? I am kind of novice in UWL and workflow so please elaborate on things if necessary

    Hello,
    Starting from ERP2005, new and improved standard tasks have been provided for Cross Application Timesheet.
    Before this release, workitems were created for each employee. Approver had to click on each workitem in order to approve records , which was time consuming. With ERP2005, the approver gets at the maximum only one workitem which contains CATS records for all the employees sorted according to personnel numbers. So the approver has only one workitem to work with which makes Approval more easier and saves him lot of time.
    To achieve this new functionality you have to make use of new Standard tasks TS31000004, TS31000006, TS31000007. The old tasks will still work in ERP2005 but it may yield some un-desirable results. Hence it is highly recommended to use the new tasks.
    Best Regards,
    Deepak.

  • Loop step creating more than 1 workitem in PO release wf

    Dear Experts,
    I am using copy of std workflow ws20000075. I have three release codes (three approvers - L1, L2, L3). So i added a loop step in my workflow that is until bus2012.releaseindicator = 'R' the loop will iterate. Now problem is that for first level i am getting one workitem for his release. In L2 level i am getting 2 workitems for same PO. In L3 level i am getting 3 workitems in inbox for his release.   I have in tcode SWEL. There instead of single RELEASED event for BUS2012 there are 3 entries for a single approver level. This is SWEL output i get for L2 approver level.
    BUS2012   RELEASED 13.08.2009     17:16:03     WORKITEM     SWW_WI_COMP_EVENT_RECEIVE (First record)
    BUS2012      RELEASED  13.08.2009     17:16:03     WORKITEM     Check FM with exception (Second record)
    BUS2012      RELEASED  13.08.2009     17:16:03     WORKITEM     Check FM with exception (Third record)
    But except first record i am getting error that is red indicator in second and third records. I am getting the desired output anyhow that is PO gets released at all three levels successfully but why more than one workitem is generated for a single approver. Kindly help me in this regard.

    Dear kakholi,
    Thanks a lot for your reply. I went to the following path Olme(Tcode) -> Goto Purchase order -> release procedure for purchase order -> define release procedure. There for three levels of release codes L1 - creator, L2 - Checker , L3 - approver.
    I have given below settings in under each button.
    Release Prerequisite : There are six checkbox. three on top right and three on bottom left. All three boxes in bottom left are checked.
    Release Statuses: There are four rows with three check box in each row. First row no box is checked. Second row L1 is checked. Third row L1, L2 are checked. Fourth row L1,L2,L3 are checked. In input help for release indicator first three are set as B and last one is set as R.
    Classification: When i click this i am getting message as Error in classification (class Z_RFQ class type 032).
    Release Simulation: Release Group input is set as PO (PO release) and release strategy input is set as 02 (PO Release strategy),Release ID is set as B.
    Regards,
    S Bharath

  • Getting two same workitems in PO release workflow for 2 level

    Hi experts,
    I am working in PO Release workflow upto two level of release.
    But while triggring my workflow by creating PO I get two same workitem.One of the two has correct Release Code(I have checked that in workflow log) and another has Release Code with no value.If I execute one of them Its working fine.But 2nd one still remains in inbox.I think my workflow has been triggred twice while I am creating a PO.
      Can someone suggest, where is the problem?
    Thanks,
    Manas

    Hi,
      According to your instruction I have got 5 event trace.
    BUS2012     RELEASESTEPCREATED     14.02.2008     16:31:57     WS99900003     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
    QCYBUS2012     CREATED     14.02.2008     16:31:57          @AI@     No receiver entered
    BUS2011     QUOTATIONCREATED     14.02.2008     16:31:57          @AI@     No receiver entered
    BUS2012     RELEASESTEPCREATED     14.02.2008     16:31:57     WS99900003     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
    FREBUS2012     CREATED     14.02.2008     16:31:57          @AI@     No receiver entered
    I have given you the details of the event traces.
    Here I notice RELEASESTEPCREATED event occurs twice.
    Can you please suggest why this is happening?
    Thanks,
    Manas.

  • PO Release WF not sending workitem to inbox

    Hi All,
    We are working on activating the PO release WF 'WS 20000075'. We activated it thru OOCU and it is triggering when we save the PO (i checked in SWEL) but we do not see any workitems in SBWP (inbox). I 'Agent Assignment' is in GREEN and is a 'General Task' in the task.
    This is the config we did in SPRO:
    SPRO -> MM -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders -> Define Release Procedure for Purchase Orders > Workflow -> Here we assigned OT as US and respective User ID's for Release Codes.
    When i double-click on the entries in SWEL:
    - The 'Receiver Data' section is BLANK and in the 'Trace Data' section, action says 'No receiver entered'.
    I think the WF is not able to read the AGENT. Not sure. Can anyone please help me with this/
    Thanks in advance.
    Karuna.

    Karuna,
    How have you managed to read the agent?

  • Change workitem text using PFTC in ECC for Task TS20000172 – release contract

    Hello,
    I would like step by step guidance on changing the worklist item description for Task ID TS20000172. Currently the contract goes for approval and the worklist item reads “Release  of Contract 4600000000”. How can I add the value of the contract in the worklist text? I looked in transaction PFTC, Container tab but could not find the variable ‘Value?’. Please advise?
    Thanks, Naz

    Hi Naz
    The Base object (_WI_Object_ID - Leading Object) in the this task is of type BUS2014.
    1) Create a subtype of BUS2014 and do the delegation between the two. (This will enable new attributes to be referenced directly using BUS2014.
    Use this link to know more on delegation:
    Business Object Delegation - Business Intelligence (BusinessObjects) - SCN Wiki
    2) Create a new virtual attribute in that subtype which calculates the value of the contract
    Following links can guide you to create Virtual Attributes
    http://scn.sap.com/docs/DOC-39432
    **************** - Working with Business Objects
    3) Now include the value in the standard task -> PFTC-> Task Type as TS -> Task as  20000172-> Display ->Select tab Basic Data-> then Menu Item Edit ->Work item text - Redefine
    Use the new attribute created for value to display the value. ( by delegation, you can now refer to this new attribute of Z subtype using _WI_Object_ID - Leading Object
    Regards,
    Modak

  • Logical problem in Purchase Order Release (urgent)

    Hai Guys ,
                            I am defining a workflow for PO release and i did the release procedure for 3 levels of approve. My workflow running successfully. the workitem send to the appropriate users and they release the workitem as very well. I used the standard workflow. my logic was
               Release Code      =            Approver
                      01         =            user1
                      02         =            user2
                      03         =            user3
    when i create the PO the workitem was send to the user1 for release. he execute the workitem it will go to the release screen and he is able to release. after releasing and before saving user1 is able to release the user2 and user3 releases also. that was the logical mistake happening. the user1 should not allow to release the user2 and user3 releases. how it can be done?
                  Thanks in Advance.
    Regards,
    R.Sathis Kumar.

    Your rel strategy has to be fixed, some extract from standard doco.........
                                                                                    o   Release code                                                          
             Via the release code, you specify the release codes with which the    
             user may release purchasing documents.                                                                               
    Examples                                                                               
    For user Miller, the following values have been defined in the            
         authorization object:                                                                               
    o   Release group: 01 and 02 (see example b)                                                                               
    o   Release code: 01 and 02                                                                               
    The user Miller may thus release POs and RFQs using the release codes 01  
         and 02.
    Hope this helps, also what version are you on?

  • Reg : Advancing With Workitems

    Hi All,
    I am working in 4.6 with Purchase Requisition Workflow (Overall Release - BUS2105).
    The requirement is when the user rejects & saves the PR in ME54 I'm supposed to give a pop-up screen to enter rejection text.
    I tried various options like using SOFM-COMPOSE, calling text editor function modules via methods/reports/transaction codes etc.
    But everytime the user rejects the PR and saves it, he is taken to his inbox where that new workitem is present. Then he has to execute it seperately. I don't want the user to go back to his inbox to execute the workitem again. I want to advance with the workitems without going back to inbox.
    How can i achieve this?
    Thanks & Regards,
    Raj

    why dont you call the text editor FM in some of the userexits or badi before save.
    There check for the condition..if PR is rejected....then call the FM and get the rejection reason

  • Issue with PO release (multi level approval)

    Hi,
    Need help regarding PO release. I am working with 4 level  approval process.
    Information:
    it is sequential release as I can see in workflow log, a new workflow gets generated for next level only after previous level executes the workitem.
    Facing following issue at 2nd Level :
    Level 2 releases item and it goes to Level 3, but workitem doesn’t disappear from inbox.Once Level 3 releases item, an acceptance mail goes to Level 2. But along with the mail, updated workitem (i.e. showing release by 3rd level) also appears in inbox of Level2. Now two work items appear in Level2 Inbox.
    In Workflow Log, this is how its behaving:
    WORKFLOW STARTED-->
    1st WF appears in WF log.
    Level 1 releases WI ->
    2nd workflow appears in WF log +
    1st workflow with (in process status)
    Level 2 releases WI ->
    3rd WF appears +
    2nd workflow with (in process status) +
    1st workflow with (in process status)
    Level 3 releases WI ->
    3rd WF appears +
    2nd workflow with (in process status) +
    1st workflow with (in process status)
    ISSUE: As soon as Level 3 sends back acceptance to Level 2, updated WI item appears( i.e. with latest release status which in this case is: released by level1, Level2 and Level3) along with the mail.
    Level 4 releases WI ->
    4th WF appears +
    3rd WF appears (in process status) +
    2nd workflow with (in process status) +
    1st workflow with (STATUS COMPLETED)
    ISSUE: As soon as Level 4 sends back acceptance to Level 2, updated WI item appears( i.e. with latest release status which in this case is: released by level1, Level2, Level3 and Level 4) along with the mail.
    Result:
    PO gets released.
    In workflow log 2nd, 3rd and 4th workflow appear with IN PROCESS STATUS. All of them show process stopped at LEVEL2.

    Hi Kjetil,
    Release strategy is being used. Configuration for release strategy is given as following.
    RGroup Rcode   Workflow     Agent
    Z6          R1         1                Blank
    Z6          R1             1                Blank
    Z6          R1             1                Blank
    Z6          R1             1                Blank
    Release is sequential.
    For column 'Agent' mentioning position or User is not really useful because we are getting agents through Z table. Reason is: current org structure supports 1 position with multiple users from same department. In our scenario we need to find initiators department then find relevant approval levels for that departemnt. So I cannot mention any position in 'Agent' Column as release code will be locked against one position and one departetment.
    Agents picked through Z table. Table has fields  Agent/ UserID , level, department.
    Logic to pick agents( Object and method created ): 
      When workflow starts, it finds department of the initiator.
      For that department-> find approval levels available(L1, L2,  L3).
      For these levels -> Find Agent mentioned for that level.
      Onece Agents are found for all levels -> Pass them to WF  container.
      In task activity, These agents are passed back to the rule and  the task comes to know which agent it should go to.
    Result : Four workflows start in sequence. When last level releases, only 1st workflow shows COMPLETED status. Rest three hang at level 2. If I see Me29N , release for that item is shown completed. To me it seems triggering of only first workflow is enough for release. Is there any way I can avoid trigerring of other three workflows?
    Edited by: User112 User112 on Jan 25, 2008 6:30 AM
    Edited by: User112 User112 on Jan 25, 2008 6:31 AM

Maybe you are looking for