Workflow with release strategy

Hi All,
Can anyone tell me if it is necessary when using workflow to help with the PR release that it be first released by the requisitioner, then the approver, then the buyer. Then it will be ready to process the PO. We are configuring workflow into the system and it is my understanding that this is the way it has to be in order for workflow to work properly. Can someone please tell me if this is right? Does the requisitioner and the buyer have to be part of the release strategy in order for this to work?

Hi Gregory
Requistioner and then further approvers are required but there is no need to have buyer as one of the approver. because any how he is going to invoilve in PO release.
Regrds
Yogesh

Similar Messages

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 for release strategy in PO

Dear All,
Will anybody tell me how to configure the workflow for release strategy for PO.
Regards
R Panda

Dear Manish,
I have done all the configuration as per your guidance.
But I am not getting the mail in mail box. I have done the following config
Gr                 Cd                WF                            Descrip
02     I6     1     HOD Logistics-JSR
02     I7     1     GM Logistics-JSR
Gr                 Cd                         Descrip                      OT                  Agent it
02     I6     HOD Logistics-JSR     US     RP
02     I7     GM Logistics-JSR     US     DD
OOCU---
MM-PUR
1) Activate event linking- WS 20000075---BUS2012-RELEASESTEPCREATED-ACTIVATED (I ticked both the check boxes)
                                               Linkage status-no errors      error feedback---system defaults
2) Assign agents----WS 20000075Create agent assignments-I assigned above two user ids against user......
                                        In attributes it was no general task & not classified.
In trxn code SWETYPV both the check boxes are ticked with no error.
Please reply.
Regards
R Panda

Customizing steps of workflow for Release strategy

Hi Experts,
Iam looking for step by step customizing details of workflow for Release Strategy for Purchase Requisition.
I need necessary classification and Customizing settings for a release procedure in the purchase requisition to the workflow.
I am looking for the steps, in which the purchase requisition can be edited straight from the workflow inbox.
Regards
Nani

Hi Nani,
First you have to confirm what kind of release it is in Purchase req you have Item level release and over all release.
Item level release - WS00000038
Over all Release - WS20000077
Now please confirm with your MM consultant that he has done the release Strategy and tesed it Ok.
Escecially things like assigning plant, Assigning Agents,Release codes and so on when everything is done by him in SPRO.
Now your work starts If it is just release use the standard workflow.
If they need additional notification mails and things like that copy the standard workflow and do the customization in the copied version and deactivate the standard workflow.
You can also do dead line monitering (Factory Calander) and many more things.
also please go through these 2 links you will get better idea.
http://www.****************/Tutorials/Workflow/POReleaseStrategy/Details.htm
http://www.****************/Tutorials/Workflow/PRRelease/PRRelease1.htm
If you have any othere queries please feel to ask.
Regards,
Dheepak
Edited by: dheepak on Dec 1, 2008 7:48 PM

User exit for workflow for release strategy

HI,
I got the user exit M06E0005 for workflow for release strategy. Is there any user exit during PO saving time, so that depending upon the PO no and the release code, the mail will go to respective person for the release of PO.
Regards,

Hi,
Refer the below Link for PO workflow set up, for more information you can co-ordinate with your workflow team.
http://help.sap.com/erp2005_ehp_05/helpdata/en/4c/16443c4a089537e10000000a114084/frameset.htm

Send purchase order e-mail with release strategy

Hi!!
I have a problem with sending e-mails in purchase order that are blocked with release strategy.
I create a purchase order that is block for the release strategy, then I release it. This is working OK, but I can't send an e-mail with this released puchase order, to do it, I have to modify something in the purchase order.
Somebody knows what is happening?
I would like to send e-mails without previous modification of the purchase order.
Thanks for your help.

Hi,
Purchase order via e-mail in SAP sys,the configurations and pre-requisites are follow:
1. You must maintain an e-mail address in the address in the vendor master.
2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
For more details, check SAP note:191470
Regards,
Biju K

Workflow In Release Strategy

Dear All,
Do you know how to use workflow in Release Strategy? I have used the standard workflow (1) in order when every document is released an e-mail to be sent to the next releaser. I maintained also the users at the "workflow". Can you please specify some settings??
thanx

hi,
You shd check, it could be very usefull for you....check in the tree structure as per the document:
[WORKFLOW SETUP|http://help.sap.com/erp2005_ehp_04/helpdata/EN/6f/9eeb85cd6b11d1ad77080009d2232d/frameset.htm]
Regards
Priyanka.P

Workflow for release strategy of Po's

Dear Experts,
We want to have Workflow for release strategy of Po's please let me know what settings are to be done from MM side. & form Abap what developments are required.

Hi
Pl check the below link
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/enterprise-resource-planning/sap%20mm%3a%20purchase%20requisition%20with%20classification%20and%20workflow%20approval.pdf
SAS

Can we implement workflow for release strategy in 4.7

can we implement workflow for release strategy in 4.7 for PO's please provide some documents.

HI,
Check the links
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30c81e21-cd00-2c10-bbba-edb8ce4961be?quicklink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70fef212-b6cb-2c10-e085-c84b80d7068e?quicklink=index&overridelayout=true
Regards
KK
Edited by: Kishore Kumar Galla on Mar 19, 2010 3:40 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.

PR Workflow for release strategy

Hi,
Could you please let me know the steps how to configure the workflow for the PR release strategy for both item level as well as header level.
Thanks in advance
Shp

Hello,
If you wish to work with procedure 1, define the following:
Release codes
Release indicators
Assignment of release indicators
Release prerequisites
Determination of release strategy
1. Release codes
Create the release codes.
2. Release indicators
Define release indicators and branch to the detail screen. Here you define whether fixed purchase requisitions may be changed by Materials Planning, for example, and whether an RFQ or a purchase order may be created from the requisition.
You can also determine the field selection here.
In the area "Changes after the start of the release procedure", you specify whether a requisition may be changed after the release procedure has begun. You specify whether the strategy has to be redetermined after changes, or whether the release procedure has to start all over again from the beginning.
This parameter bears a relation to the parameter "Value change". For example, previous releases are not cancelled if the value of the requisition item after the change does not exceed plus 10% of its original value.
Attention:
Be sure to create a release indicator (e.g. B for "blocked") that serves as the starting point for subsequent indicators. Do not set the indicators for release for the issue of RFQs and PO on the detail screen for this indicator.
Also create a release indicator characterizing the released status. Set the indicators for release for the issue of RFQs and PO on the detail screen.
3. Assignment of release indicators
Assign a release indicator in dependence on the status of the release.
Example:
You create a release strategy S1 consisting of two release codes 01 and 02. Release with 01 is a prerequisite for release with 02. If release has been effected with 01, the requisition has been given the "all clear" for the issue of RFQs.
You have created the release indicators B (blocked), 1 (cleared for issue of RFQs) and 2 (cleared for RFQs and PO).
Now enter the following as assignment:
Strategy   C1 C2 C3 ...
S1                           B (blocked)
S1         X                1 (RFQ)
S1         X   X            2 (RFQ/PO)
4. Release prerequisites
Define which release codes are involved in a release strategy. Specify whether a code is set for a release status following release, and whether one release status is a prerequisite for another (+).
Example:
Strategy   Code C1 C2 C3 ...
S1         01    X
S1         02    +   X
5. Determination of the release strategy
Determine the conditions under which each release strategy is assigned. The criteria are account assignment category, material group, plant, and value of the requisition item.

Purchase Order E-mailing with Release Strategy

Hello,
We are experiencing an issue when e-mailing a Purchase Order which has a release strategy. When the order is released, the confirmation e-mails are going to the person who releases it when it is supposed to go to the person who has created the P.O. We are using a Smartform P.O. based on /SMB11/BL_MM_PO_L and print program /SMB40/FM06P. I must note that there was a bug found in the aforementioned print program and before that was fixed e-mailing would not work at all.
We have also attempted to use all combinations of standard unmodified print programs and standard unmodified smartforms and have had no luck at getting the confirmation e-mail to send to the correct person this way either.
SAP has recommended that we use program SAPFM06P with form Medruck. While this combination does work correctly, Medruck is not a Smartform. Has anybody here used a smartform Purchase Order with a release strategy and had the confirmation e-mail send to the created and not the releasor?
Below is a list of the print programs and forms we have tried in various combinations. We are running ECC6/Basis 7
Print Programs:
/SMB11/FM06P
/SMB40/FM06P
SAPFM06P (Sapscript Only)
Forms:
/SMB11/BL_MMPO_L
/SMB11/MMPO_L
/SMB40/MMPO_L

Hi,
Purchase order via e-mail in SAP sys,the configurations and pre-requisites are follow:
1. You must maintain an e-mail address in the address in the vendor master.
2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
For more details, check SAP note:191470
Regards,
Biju K

Chek budget in PO with release strategy

Hi
When i created a PO with a release strategy and the comand need it, the budget are not checking at the save, only when i release the PO.
Is it possible to check the budget (on a PM order or on WBS element) at the PO save.
Thank's
serge

Normally checks like those happen once the PO is released ( example - output is not allowed etc)...
You may need to add something in the PO release strategy user exit to do the check before release (after save), Look into the below to see if this works.
Name of the Enhancement: - M06E0004
Name of the function module: - EXIT_SAPLEBND_002
Hope this helps

Why PO is automatically assigned with release strategy?

I created a PO with PO document type NB and NB is not assigned with any release strategy.
But the PO with NB type is automatically assigned with release stragety when I save it as a completed PO. Why?
And only when the PO is in held status, there is no release strategy assigned to NB PO.
Is the normal ERP behavior?
I only assigned a release strategy to PO document type DB, which means dummy document type.

Please check the release strategy of PO, whether document type NB is assigned to it. May be you are checking the wrong release strategy. Look up the release strategy under CLASSIFICATION button, may be if multiple release strategies are used, your document type is assigned to some other strategy.
Easier way to check which strategy is getting applied, is in PO release strategy look up rel. strat No. which will come under release group, look up in spro with this release strategy no. in spro which will shorten your search.
Edited by: Afshad Irani on Jun 3, 2010 1:58 PM

PO Workflow for release strategy approval process (BUS2012)

Hi Experts,
I have configured a workflow that should get triggered by the event "RELEASESTEPCREATED" in the Business Object BUS2012.
The workflow is triggering perfectly and is working exactly as per the requirement, but the problem I am facing is the event "RELEASESTEPCREATED" is getting triggered twice.
I went to SWEL and saw that the above event is getting triggered twice by the system. I am not calling the event in any user exit. I have de-activated the event linkage in the standard workflow. Only my custom workflow link is active.
Due to this all my workitems, mails are getting duplicated as the workflow is being called twice.
I just need to know, why the event is getting triggered twice in the system.
If you need more details in the issue, I will provide that.
Your help is highly appreciated. Points will be awarded to the helpful answers.
Thanks
Anirban

Hello,
First off a small comment on terminology because a lot of people say this:
Events are not triggered, they are raised or published by the application (regardless of workflow). An event is the trigger for a workflow.
Now we have that cleared up, have a look at the workflows that are triggered by your events and check the container to determine the release codes for each workflow. It seems to me like you are probably processing two different release codes at the same time. This could be perfectly normal (e.g. you may want to perform two approvals at the same time) and is controlled by the MM config for the release strategy. If this is not what you want then this should be adjusted by your friendly MM people.
Cheers,
Mike

Workflow with release strategy

Similar Messages

Maybe you are looking for