Reject a po from release strategy in workflow

Hi all,
  For Purchasing document Release strategy, if a purchase order is rejected by the approver then it should go back to the originator of the document.
I am trying for this scenario for that my configuration is—
     Business object is – Bus2012
     Workflow template is – WS 20000075
In this configuration, I used the originator name in activity (Release of purchase order cancelled )& under this activity I am using the task is TS20000167
But after configure this all thing I am not able to get mail inside the originator mail box
I want to know following thing
     How approver can reject the po
     What setting we can do for getting the mail inside the originator mail box
Regards
Giridhar

Hi Rick,
Thanks for the comments. Below is our actual scenario:
When we did the setup, we did the following:
1. Create a release code
2. Create a position
3. Attach the release code to the position
4. Create a role
5. Attach the position to the role
6. Attach the role to users A and B
When user A resigned, we did the following:
1. Deactivate user A and put "Valid Up to" date.
   We even removed his email address from his account
2. Detach the role from user A
After which, notifications are still being sent to this deactivated users. The said notifications are actually those that happened before he left and this is what Im trying to solve. This is creating too much records in SOST and the system is sending the same notifications over and over.
Do you have any suggestions how to solve this?
Thanks

Similar Messages

  • Reject a Collectivly PR' S from Release strategy

    Dear All,
    How to reject a Collectivly PR' S from Release strategy.
    Regards
    Aamir

    The line items may be approved collectively as a whole or individually, but, each line item must be rejected individually.
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/75/ee14d755c811d189900000e8322d00/frameset.htm

  • Release Strategy with Workflow for PR & PO

    Hi Experts,
    I have configured the PR & PO Release strategy and it is working fine. My client wants the Workflow concept in Releases.
    So User should get the information about the releases for PR & PO.
    But I don't have much idea on Workflow, how it works for Release strategy. Can anybody give information on how to configure the Release strategy with Workflow in PR & PO.
    Points will be awarded .
    thanks & rgds
    Swamy

    Hi Swamy,
    The release workflow is configured by MM functional consultant. As for the workflow determination (i.e. which level should approve first and so forth) depends solely/mainly on the Finance of the company. It differs from one company to another. And the level of approval also differ from one company to another. Hence, like you mentioned, this would be provided by the user, so it is okay. I have replied to someone on another thread asking about workflow, and this is how it works.
    How it works? For example, for a PR release strategy, once the PR is raised by a user for a certain value, the PR raised that matched the classification of the release strategy configured will be triggered. In this sense, once the release strategy is triggered, the releaser holding the release code to release this PR will receive a workflow in their SAP inbox (Not Outlook) for their execution, which is sent automatically by SAP system. These is accessible via the t-code SBWP. Each releaser have a unique login ID and password.
    Assuming the release strategy required 3 levels of release, for example A3, A2 and finally A1 (final release), A3 will first receive this workflow in his/her inbox. After A3 has released, A2 will subsequently receive workflow in his/her inbox for this same PR. In the PR, you will be able to see that A2 release is now possible. This flow will continue until the final releaser, A1 and then, the status of the PR will be unblocked for issuance of PO.
    How is it configured in SPRO? In the Workflow for PR release strategy, you are able to assign a unique ID (usually employee ID) to a particular release code, which these release codes are tied to one or more release strategies. The workflow determines who is to release for a release strategy with that particular release code via the assignment of the ID to that particular release code. Each assignment is only possible for one Plant, and you have to assign the same for many other Plants for the same ID in the workflow if you want him/her to have the authority to release purchasing docs in more than one Plant.
    How to configure?
    Before that, you need to obtain the following information - User ID of the releaser for the specified release code, Plant to be released by the user, and finally of course the Group and Release code (which you already have).
    For PR: IMG>MM>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Workflow
    For PO: IMG>MM>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Workflow.
    Maintain the details u already have in hand:
    For PR: Group (PR or PO), Code (release code), Plant (you have to maintain the same details for each of the Plant that the same release code releases) Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
    For PO: Group (PR or PO), Code (release code), Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
    Please note that PO is not Plant specific, and is usually one releaser to release the PO for GR. It is the PR that during the initial stage has the most level of release (up to max. 8 level) before a PR can be converted to PO.  After the PO is converted, it is usually deemed accepted, hence only one release code is usually required to release the PO.
    Hope this will give you an idea how the workflow works and how to configure it.
    Rgds.

  • Release Strategy and workflow in Purchase Requisition

    Hello All,
    My client wants to activate the release strategy and workflow at the purch req and PO levels. They allow users to create a Preq and reference that preq to the PO, or users may create a PO without referencing a Preq. Since they have the release strategy and workflow working on both levels, what they want done is, if a PO has a Preq reference, it does not need to go through another approval process on the PO level as it has already been approved on the Preq level. Therefore if a Preq is reference in a PO, the PO workflow and release strategy should not be taken into account. Can this happen as a standard config, or will this need a "user exit"?
    Thanks in advance for your help!!

    You will need to activate the user exit. This will keep the PO release strategy simple.
    Have a flag (use USRC1 or USRN1). In your PO release strategy classification, maintain only X in this characteristic.
    In the user exit, check whether the PO is created with reference to PR. If yes, pass "blank" to USRC1, else pass "X". The release will be triggered only in case of X.
    Just a couple of points:
    1) What will you do if one item in PO is created with reference to PR and the another item is not?
    2) What will you do if one item is partially referenced to PR (i.e PR quantity is 100, PO quantity is 200 - of which 100 is referenced to PR and other 100 is not - this is possible by changing in delivery schedule)?
    Hope this helps
    Lakshman

  • Release strategy  in workflow

    how to use release strategy in workflow for purchase order?
    regards
    rose

    For all of you : This is the best you will get: go through and sit with your functional consultant to understand the process.<a href="http://help.sap.com/saphelp_47x200/helpdata/en/1d/ea9d9c7aca11d194b70000e82dec10/frameset.htm">http://help.sap.com/saphelp_47x200/helpdata/en/1d/ea9d9c7aca11d194b70000e82dec10/frameset.htm</a>

  • How to control PO Release strategy using WorkFlow

    please tell me how to control PO Release strategy using WorkFlow.
    Moderator message: please search for available information/documentation.
    Edited by: Thomas Zloch on May 31, 2011 9:35 AM

    Hi,
    Yes they are same unless you differentiate by using
    1> Purchasing Document Category i.e CEKKO -BSTYP
    A.....     Request for Quotation
    F......Purchase Order
    K......Contract
    L......Scheduling Agreement
    So if you just create a characteristics for CEKKO-BSTYP then maintain its values only for F so it will not be applied to RFQ

  • Re: PR Release Strategy with workflow

    Hi Expert,
       Is there a way the scenario given  below will be possible to achieve..
       All the needed config for the  PR release strategy has been define... (release code, group,release strategy,class & characteristic)
      Parameter : Doc Type,
                      Amount
                      Acct Assignment Cat ( K,A,C)
                      Cost Center
                       Sales Order
    The challenge is that when the given
                   Doc Type - NB
                   Amount - >0
                   Acct Assignment Cat = C
                   Cost Center - Empty
                   Sales Order - 9999
    The PR will be subject for release strategy of Project Manager  ( Release Code :PM)
      The PR should be sent to the approver (through workflow) which can be found in the partner function maintain in the Sales Order
      9999..Partner Function   ZM - Proj Manager. which contain Employee No ( from HR)
    She

    hi
    i think u need workflow for release strategy
    Steps involved are :
    1) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Release Codes > here assign Workflow indicator as "1" against each Release Code
    2) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Workflow > Here against each release code assign OT as US and respective User ID's for Release Codes.
    3) Go to OOCU > here under MM, go to MM-PUR,
    4) Click on "activate event linking"
    5) Go for "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button. Activate "Event linkage activated" and also activate "Enable usage of event queue"
    and Save.
    6) Click on "Assign agents" and proceed all above steps.
    BUS2012 is the relevant business object and Releasestep created is the event for the same.
    7) Check SWETYPV transaction for the WF you have activated for BUS2012 and confirm.
    Test the same by creating a PO and check the SBWP for SAP Mail of respective Users
    take help of ur BASIS person
    hope it clears
    regards
    kunal

  • Purchase Order Release Strategy with Workflow

    Hello Experts
       In activity Release Codes workflow column has 3 options.
    (1) Blank  =  No workflow
    (2) 1  =  Role resolution with group, code and plant
    (3) 2  =  Role resolution via user exit
    Can any one explaing in detail what is difference between option (2) & (3)?
    Thanks
    Ankit

    The difference is obvious. In option 2 your workflow will decide the approver based on Release Group, Code and workflow object assignment. In case of option 3, your workflow will decided the approver based on the rules coded in User-exit.

  • PR release strategy and Standard Workflow suddenly doesn't work

    Good day,
    I have PR release strategy and Workflow activated. My workflow is copied from standard PR release workflow in SAP. The only changes I made in the WF is Agent Assignment. It worked like a wonder.
    However this week when I was creating PR, Release Strat still works but WF doesn't kick in. No change was done to both PR release strat and WF.
    Any help/suggestion for this? Is there a period of activation in WF?
    Regards,
    Si

    Hi Diwakar,
    I was able to activate it already yesterday. What I did was to test the workflow in SWDD. After the test, all workflow items were created. Am still wondering though why WF would suddenly stop (not generate workflow items) even with no changes made.
    Thanks for the info and link. Points awarded.
    Regards,
    Si

  • Workflow with Release Strategy for PR & PO

    Hi Experts,
    I have configured the PR & PO Release strategy and it is working fine. My client wants the Workflow concept in Releases.
    So User should get the information about the releases for PR & PO.
    But I don't have much idea on Workflow, how it works for Release strategy. Can anybody give information on how to configure the Release strategy with Workflow in PR & PO.
    Points will be awarded .
    thanks & rgds
    Swamy

    Swamy,
    There are several posts available for this requirement, I would suggest you to search this forum and you would hit many threads which address this in more details and handy explaination
    check this link for PR
    http://help.sap.com/saphelp_47x200/helpdata/en/04/92768046f311d189470000e829fbbd/content.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/04/9276e846f311d189470000e829fbbd/content.htm
    For PO:
    /thread/743773 [original link is broken]
    Standard workflow template for PR and PO are:
    WS20000075
    WS20000077
    These can be viewed using PFTC/SWDD etc.
    Cheers
    Jai

  • Workflow Configuration for Release Strategy

    Hi All,
    At present we are using Release Strategy without workflow. Now we wants to use workflow.
    Request you all to guide what configuration i have to do for workflow.
    I appreciate your help
    Regards
    Anbalagan

    Hi,
         In the case of a release procedure linked to workflow, you must have previously created the user names, positions, jobs, etc. that you here assign to the release code in the organizational plan and must have linked them to the relevant standard tasks in task-specific Customizing (Basis -> Business Management -> Business Workflow -> Perform Task-Specific Customizing).
         You must assign the authorization M_EINK_FRG to the persons who are to be involved in the release procedure ( Authorization Management -> Create Authorization Profiles and Assign to Users).
    If a release code is to be used in workflow, indicate this accordingly in the Workflow field
    The Workflow indicator is also used to control role resolution:
    ·     "1 - Role Resolution with Group, Code and Plant (T16FW)"
    Here you use a role resolution that is supplied in the standard system. To do so, you must assign the release point in the section Workflow
    Assign a processor ID to your workflow-relevant release codes. The processor (member of staff responsible for processing the document) will then receive a work item when he or she is required to effect release.
    You can assign a processor ID either directly or indirectly:
    o     Direct processor assignment:
    Enter a user name.
    o     Indirect processor assignment:
    Enter a job, for example, or a position. At runtime, the system will then determine the member(s) of staff responsible for processing the document.
    Regards
    Sanjay L

  • Purchase Release Strategy - Workflow

    Hello Everyone,
    We have a Purchase Release strategy with workflow. We have an Issue with workflow lying with a approver. Sice the approver is on vacation, is there any way to forward the work item to another user or to automate such scenatio in SAP?
    Thanks in advance
    Uswin

    Hi Guys, thanks for your reply.
    The concern here is we have the release strategies already defined & in the normal cases we don't want either User1 or User2 to approve the workitem. We want User1 to approve all the requests. Only in case of exemption, we want to have alternate user to action the request.
    Anyway to do it?
    Thanks,
    Uswin

  • Purchase Requisition Release Strategy with classification

    Hi there,
    Please help,
    I have the release strategy and workflow working. (Overall Release)
    Problem is that Org Structure is not updated so workflow has been configure going to (US) user. As i am using workflow option 1 which is resolved via Group, Code & Plant, I have to have a code for every region and manager to resolve the workflow. I am not using plant as business requirement is overall release.
    Scenario is that there are 8 regions with 1 senior region manager and 1 executive.
    The region managers can each release up to 20k. Senior region manager must release from 20k - 50k. Executive must release from 50k -250k.
    Release Codes:
    Regions = L1 - L8
    Senior Region Manager = SR
    Executive = X1
    Characteristics are:
    DocType = NB
    AccAsingment = K (Cost Centre requisitions)
    Purchasing Group = (Each region has own group)
    TotValue = 0k -20k, 20k - 50k, 50k - 250k.
    Now the release strategies.
    Even though it is the same senior manager and executive why do i have to create a new strategy for every region's escalation above 20k taking into account that the business requirement is that the correct region manager has to release before the senior manager can release? It just seems so pedantic when i would rather just add the correct Purchasing Group everytime.
    This is only one leg of the Org Structure there are over 40 depts, and managers that will create and release. Do i really need a strategy for every single scenario?
    Thanks for taking the time to read.

    Hello,
    Create a special ID in PRD with access to change characteristics. This ID should be released for specific purposes and with approval (project manager/SAP support manager). You can also turn on auditing so that all activites performed are logged which can be used to satify auditors.
    Cheers !

  • Release Strategy for contracts.

    Hi gurus,
    Good day,.
    Please help on this.
    We have a release strat for Contract. It is working fine when a contract is created, but when several changes were made on the Quantity, release srtat are not being triggered.
    Example.
    Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
    After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
    After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
    what is the standard functionality for this? Should the decrease in quantity will trigger release strategy or not?
    Thank you.

    Dear Acel,
    The example you given was working just fine and correct.
    a)Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
    b)After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
    c)After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
    -> The release strategy will only be reset if the total net value for the contract was higher the previous
    value but not lower.
    As your example, quantity was updated to 1200, then it will reset when changing from 1000
    to 1200. However when it was decrease to 1100, then it will not reset anymore as you had
    release it for a quantity of 1200, then the total net value should higher than the current qty = 1100.
    In system, it always assume if you had approved for the total value of the higher 1 before, then
    it should be fine for the lower total net value for your management and therefore not need to re-approve
    again for redundancy job. This was very logic in common business scenario in many companies.
    However, like in your example , if you had define a different release strategy for a value that met the
    the 1100 quantity, it will redermine the different release strategy. For example:
    USD 1 for every quantity = 1
    Then your contract will be USD 1000 for quantity = 1000, USD 1100 for quantity = 1100 and
    USD 1200 for quantity = 1200.
    Release strategy A for 1000 , characteristics from USD 1000- lower than 1100
    Release strategy B for 1100 , characteristics from USD 1100- lower than 1200
    Release strategy C for 1200 , characteristics from USD 1200 onwards
    Then if you change the quantity from 1200 to 1100, it will redetermine the release
    strategy B which means from Release strategy C to Release strategy B. If you
    only had Release strategy C that had a characteristics from 1000-1200, then
    it will keep the Release strategy C as released and it won't be reset unless
    if you had change it and the condition of the total net value was higher than any value
    before.
    Hope this will explain the logic.
    Ian Wong

  • Overall Purchase requisition Release strategy : Changed after Rejected

    Hi All,
        I have activated overall purchase requisition Release strategy (20000077) . And its working fine when PR is released at each level and saved.
      Problem I have is when PR is rejected .
    When PR is rejected , workitem is created for initiator with ME52 transaction. When initiator changes the contents of PR and saves , the release strategy should resume back from where it stopped. Thats means when Approver A rejects the PR, after initiator make changes , the workflow should trigger back with a workitem for release to approver A.
    But its not happening as expected. When Approver A rejected the PR and initiator changes the PR , Nothing is triggered, as there is no event raised at this point. 
    ME52 changes for PR is not trigerring any event which can trigger the WF.
    Is there any way we can trigger Workflow in this scenerio.
    Please suggest.

    Hi Subhashini,
    This all depend on release strategy. release should reset completely on tha change.
    For the increase of quantities or values you can maintain tolerance limits in the Customizing. When you increase the amount or value via the tolerance limit the system will reset the release.
    When you reduce quantities or values the system only resets the release if another release strategy is determined for the lower quantity or the lower value.
    If no other release strategy is determined by the reduction of the
    amount or value, the system will keep already existing releases.
    changeability in Release indicator also play a major role. You should set it to either 3 or 4. Now if you change any field, which is also used in any charecteristics in release, it will lead to reset of release startegy.
    Sanjeev

Maybe you are looking for

  • How to find out all user exits edited

    Hi All, Would you know how to find out all user exits have been ever edited? Can we find out those user exit by some tcode or table? Thank you very much Best Regards, Calvin Edited by: Sam Sum on Mar 2, 2009 5:09 AM

  • Error in Jboss after upgrading to AutoVue server 20.2.2 from 20.1.0

    We've developed an integration to view the files using AutoVue server. At the first stage the integration we used AutoVue server 20.10 and the functionality works fine. After upgrading to AutoVue server 20.2.2 following error comes when accessing the

  • Burrito

    Hello, today I opend one of my projects with the latest Flash Builder, (Burrito) Since its buggy for me( design view is empty) i uninstalled it. Now I tried to open my project with the release of FB4 and I get an error when I try to run it : VerifyEr

  • I have lost access to Safari on my imac

    I have done something and have now lost access to Safari.  I get the error message: You can't open the application Safari because it may be damaged or incomplete.  How can I reinstall Safari? Can you help?

  • Cpsid_82829r5 can't install CS 5.5

    Hi, I had to rebuild my computer and the only software product that doesn't make it is Creative Suite 5.5 with a cpsid_82829r5 error. I use Windows 7 SP1 and tried the following so far: install as administrator read forum posts clean the installation