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>

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

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.

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
     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

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.

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

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

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 !

Purchase order release strategy Workflow not working

Hi All,
I am working on PO Approval release strategy and it is not working fine . The release strategy set up is configured by my functional consultant . I just copied the standard workflow template WS20000075 and making changes to my custom workflow template . When ever po is created an event "RELEASESTEPCREATED" get triggered and the first approver receives an workitem and when he approves it goes to Second Approver and it is working fine . But when rejected then a notification email goes to initiator . Now when an initiator login into ME22N and made any changes ( even material text change ) in it then again "RELEASESTEPCREATED" event getting triggered . But I need to trigger my workflow only when there is change in PO Net value .
Kindly help me how to achieve this functionality .
Thanks and regards
Dilip

Hi Vikram,
There is already an existing entry for BUS2012 with event CHANGED against the change doc EINKBELEG .
Acutlly when login as initiator and try to change PO through ME22N here are my observations :
case 1: When Buyer click on " Cancel Reject " button and do any changes ( even text change ) then RELEASESTEPCREATED and CHANGED events are triggering . But since the event linkaged is set to RELEASESTEPCREATED workflow get restarted again.
Even the CHANGE event does'nt have 'RELEASECODE' as parameter to restart workflow .
Case 2: When Buyer doesn't click on " Cancel Rejection" buttion and do any changes then only CHANGE event get triggered
which do nothing since there is no event linkage .
Is to click on " Cancel Reject" button mandatory ? . But even though we make " Cancel Reject" as Button mandatory then RELEASESTEPCREATED Button triggering for any change but we need to trigger it for only net Value change .
Thanks and regards,.
Dilip Kumar

Purchase Order Release Strategy Workflow

Dear SDNers,
I created a custom workflow to trigger workflow when PO created. This workflow send mails to portal for approval to approve the release stratagies of purchase order.
From portal side its working fine. Once the approval approves, user decision step going to next level. every thing is fine from portal side.
But if they go for R3 side to release PO at ME29N, here facing probelm
Suppose, Workitem is waiting at level1. Approver1 recieves used decission step at portal. But by logging into R3 system and release PO, the workitem which is at approver1's inbox has to vanish from his inbox. Its not happening now.
What I hav to do. Kindly let me knwo.
Thanks in advance,
Regards,
Venkat

Hi Venkat,
Two things you should change here:
1. The Event that triggers your workflow should be BUS2012(RELEASESTEPCREATED). This event occurs when a release strategy is activated for a PO due to various reasons.
2. You workflow should have a 1 : 2 fork . One path (fork path) should follow the User Decision path using a portal and the other should be a asynchronous workitem with the following 3 as terminating events:
      BUS2012         RELEASED
      BUS2012         RESET
      BUS2012         SIGNIFICANTLYCHANGED
The workitem can be with or without agent.
This should help you.
Regards
Gautam
Edited by: gautam maini on Jun 28, 2011 5:13 PM
Edited by: gautam maini on Jun 28, 2011 5:14 PM

External mail for workflow of release strategy for PO

Dear All,
I have configured the workflow of two step release strategy for purchase order and the internal mail is getting generated in the sap business workplace with the error message SWF_RUN 594 this i have taken care with SWE2 with changing the settings of "Behaviour upon error feedback" from "default" to "do not change linkage"
Now the requiremnt is that the message has to be send to first level releaser through external mail and once first level release the PO external mail should be send to second level releaser.
Please help me with the configuration step that is to be done
Thanks in advance
Naveen Singh

Schedule the report Rswuwfml2. this will send workitem from sap inbox to respective user external mail id maintain in user master.

Release strategy in workflow

Similar Messages

Maybe you are looking for