Release PR by Workflow

Dear all,
I plan to use PR release by workflow using SAP standard offering.
What are the configurations that I need to set in the system in addition to the below setting:
1) Assign workflow indicator to the Release code.  In this case, I use "1"
2) Assign the release code with the user.  In this case, I use user id as the release agent.
Please assume that I have setup the basic workflow setting where the workflow is already working in another component, such as release invoice verification blocked.
Thanks for your help.
Cheers.
Tom

Hi Tom,
•     Release Group
-     Rel. group – 2 digit code which combined with a 2 digit strategy code make                                                                       up the release strategy
-     Rel. object
                      1 – used for Purchase requisitions
                      2 – used for Purchase orders & other purchasing documents
                      3 – used for Service acceptance
-     Class
Only one class can be used for a Release Object
Requisitions can use for example class FRG_EBAN
•     Release Code
-     The release code (denoting a release point) is a two-character ID allowing a person to release (clear, or approve) a requisition item or an external purchasing document.
-     Release codes are assigned to a release group
-     Workflow can also be assigned to the release group/release code
•     Release Indicator
-     For requisitions
Whether the item may be changed by Purchasing or Materials Planning and Control after the start of the release procedure
•     Release Strategy
-     The complete strategy is the combination of release group and strategy, each is a 2 digit code.  Example MD 01.
-     On the details screen you enter the release codes assigned to this strategy, set the release prerequisites,  set the release statuses, and set the values for the characteristics of the assigned class.
•     Workflow
-     For requisitions you determine any workflow you may be using.
-     As of 4.0 or 4.5 workflow is on Purchase orders as well.
Sanjeev

Similar Messages

  • 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

  • What is the release code in workflow?

    what is the release code in workflow? why we use this release code and release group? i wanna to to the purpose of these both ? plz explain me in detail?
    thanks in advance

    Hi,
    Refer this link.
    [http://help.sap.com/erp2005_ehp_03/helpdata/EN/8a/60b43bb7492147e10000000a114084/frameset.htm]
    Regards,
    Surendar Reddy.

  • 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

  • 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.

  • Can you any body tell about release codes in workflow

    Hi,
    Can any body tell about release codes in workflow.
    Regards,
    Boddu Rosaiah.

    Hi Naidu,
    You use this component if you wish to set up approval procedures for purchase requisitions or other purchasing documents. Under such a procedure, if a purchase requisition or external purchasing document fulfills certain conditions (e.g. the total order value exceeds $10,000), it has to be approved (by the cost center manager, for instance) before it can be processed further. This process of approving (clearing, or giving the "green light" to) a proposed item of expenditure is replicated in the SAP System by the "release procedure".
    It is sensible to define separate release procedures for different groups of materials for which different departments are responsible, and to define separate procedures for investment goods and consumption goods.
    <b>Features</b>
    Each person involved in the release procedure effects release (signifies approval) via a release transaction, using his or her release code. Once effected, a release can also be cancelled with the same code (that is to say, the original status is reinstated).
    If linkage to <b>SAP Business Workflow</b> has been defined for a release code, rejection is also possible. This is only possible for purchase requisitions.
    <b>Which Documents Can be Released (Approved)?</b>
    Release procedures can be defined for the following documents:
    Purchase Requisition
    The external purchasing documents purchase order (PO), contract, scheduling agreement, request for quotation (RFQ), and service entry sheet
      <b></b>

  • To trigger Overall release for PR workflow (WS20000077)

    Hi,
    I want to know that how can i trigger overall release for PR workflow ( WS20000077 ) of BUS 2105.
    rightnow in my system workflow WS0000038 is activated & when i perform ME51N it is triggred perfectly. and in SWEL BUS2009 is triggered, but it wont trigger BUS2105.
    So how can i trigger BUS2105 & instead of BUS2009, so it will trigger WS20000077 workflow.
    Which seetings needs to be done in SPRO, so it will trigger BUS2105?
    And please give me some idea about overall release for PR workflow & item level release for PR workflow.
    Regards,
    Smit

    Hello,
    Right now, the release strategy is configured item-wise for the PR and so the business object BUS2009 is triggered. To make the release of PR from Item-wise to overall, please make the following configurations in SPRO
    SPRO -> MM -> Purchasing -> Purchase Requisition -> Define Document Types and check the 'OvrelReq' checkbox and then
    SPRO -> MM -> Purchasing -> Purchase Requisition -> Release Procedure-> Procedure with classification->Set Up Procedure with Classification and maintain the Release Groups by checking the 'OvrelReq'  checkbox.
    Once these configurations are done, first check whether the event 'RELEASESTEPCREATED' is published in the system from the event log(SWEL). Once an entry is found,deactivate the linkage between template WS0000038 and activate the linkage of the template WS20000077 which is for the BO BUS2105.
    Hope this will help.
    Thanks,
    Samson

  • How to approve or release a Custom workflow release strategy using a prog.

    Hi There,
                  I am working with a custom transaction with release strategy using custom workflow. I am done with the module pool and workflow templates. And also I can able to start workflow using the FM SAP_WAPI_CREATE_EVENT.
                  My actual Issue is I have set of buttons in the module pool screen with names Approve (1 to 5) and Reject (1 to 5). When I press the "Approve 1" release strategy of the first person need to approved. Is there any Function Module or Classes for approving the workflow release strategy using buttons in screen.
    Thanks in advance,
    Viruman

    Hi
    Make use of the function module SAP_WAPI_DECISION_COMPLETE. To this function moduel pass the workitem ID and pass decision parameter value as 0001 for approve and 0002 for rejection action. You can check in this forum with this function module you will find lot of threads.
    If its not a decision step then you can make use of SAP_WAPI_EXECUTE_WORKITEM or SAP_WAPI_WORKITEM_COMPLETE.
    Regards
    Pavan
    Edited by: Pavan Bhamidipati on May 26, 2011 11:43 AM

  • 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.

  • Releasing problem in workflow

    Hi All,
    I am facing the problem in the releasing of the document in the workflow..
    First step i am using the parked document and save as complete, which is working fine.
    But problem is next step i am using the RELEASE method of the FIPP BO..
    but i am able to get the workitem with RELEASE whover i am assigning.
    if they release, it is showing released, but when i check document is not released, but document getting lock..
    Please let me know this is problem with wf or customizing?
    I have binded Business Object corrctly for the RELEASE method
    Regards,
    Udupi

    Hi,
    Please refer below mentioned thread. I hope it will be helpful for you.
    http://www.saptechies.org/sap-pdf-books-download/FI_Document_Parking_workflow_tutorial292711300832628.pdf
    Regards,
    Sudeesh Soni

  • How to release  PRs through workflows without setting release procedures?

    Dear all,
             I am involved in overall purchase requisition workflow.I have copied standard workflow WS20000077.
             For overall PR release,I will be using the standard task TS20000159 which uses BOR as BUS2105 and method SINGLERELEASE.This method is defined with RELEASECODE as mandatory parameter.
             My functional consultant wants me to get release codes from ztable based on plant and PR value without setting release groups and release code in SPRO transaction.
             So,I have created an entry in ztable for release code with data element FRGCO as in T16FC standard table with SAP log on id of agent ,plant and PR values.I have created a custom background method to pick the appropriate release code from ztable based on PR value and plant.The picked release code now can be passed to he above standard task.Is this a right procedure for PR release?Please correct me if I am wrong ,as this is the first time I am involved in release workflows, for which I will be grateful.
    Thanks and regards,
    S.Suresh

    Dear Swaminathan,
                     Thank you so much for your reply.
                     I will get back shortly once this is done.
    Thanks and regards,
    S.Suresh

  • 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

  • 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—
    &#61656;     Business object is – Bus2012
    &#61656;     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
    &#61656;     How approver can reject the po
    &#61656;     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

  • Rejection of Purchasing Release Step (No Workflow)

    Hello gents,
    I have set up a release strategy witth 3 leves, no workflow activated. Assume that manager at last level (3) denies the release.What is the best way for the manager of level 2 to be aware of it?
    Thank you for any advice...

    Hi
    Like PO, you can unrelease it in ME35K if it is not transmitted to vendor. If it is transmitted to vendor, then you need to delete the line item in contract if PO is not created against it. If PO is created then you need to modify the quantity in which equals the PO quantity so that new POs will not be generated. This is as same as amendment. If you have version management active for your document type it would be helpfull in printing amended contract and transmit to vendor that contract is rejected or cancelled
    Regards
    Antony

Maybe you are looking for