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

Similar Messages

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.

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

How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok

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 avoid po release strategy replicating in RFQ

Dear Sapiens,
I am aware as we are using same class for PO RFQ and Contract the release strategy will repliacte in rest,
but I dont want PO release strategy to get repliacted in RFQ,because I dont have realease for RFQ
how to avoid po release strategy replicating in RFQ?
Regards
Kantha

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

Item category control the release strategy?

Hi,
Currently the purchase of a material needs to be released.
My issue is that as soon as I change the item category in the sales order,
the material does not need to be released.
How does item category control the release strategy?
Sincerely,
Ketan

Hi Ketan,
You can set item category in the characteristic of a release strategy.
In your case, I guess the item category characteristic is already created. So you can just add the desire value into the characteristic.
Go to SPRO > IMG > Material Management > Purchasing > Purchase Requisition > Release Procedure > Procedure With Classification > Set Up Procedure With Classification > Release Strategies
Select the related release strategy, double click to view the detail. You will see there are 4 buttons in the bottom of the screen. Choose 'Classification' and enter you value of item category.
Thanks & regards,
JT

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

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

How to control 2 epos motor using microcontroller 50/5

Hi. i've done a program from epos integrated to labVIEW to control 1 epos motor. i do the program by using the given epos sub-vi to labVIEW, but i only know how to do for controlling 1 motor. Anyone can help me or tell me how to control 2 motors or wad is needed?? thanks for your help :-D
Solved!
Go to Solution.

Hi Spydi,
up to now, I never did it with two EPOS. But you should first check your setup with the EPOS-Studio. You need to set two different Node ID`s and after this works from the EPOS-Studio <you should do two seperate lines of programming in LabVIEW. I attach some VI`s from maxon which are simple in using for one EPOS. I assume you just need to program them in parallel.
And you don`t need the CANopen Library, it`s possible to use but very difficult. The EPOS-Library from the download is a Set of VI`s which where developed by maxon in Switzerland and free of use, they use a Communication DLL behind. If you`re interested maxon develops a new release right now. If you want to use them instead of the one you already had, let me know, I can ask there for a BETA and place it here at the forum.
Kind regards
Alex Rudolph
NI Switzerland
Attachments:
EPOS Module.zip ‏77 KB

CCreate Release Strategy using department name in "Release Code", not User ID SAP.

hi experts...
i wanna create new release strategy, but in part "choose activities => Workflow => assignment of role to release code"
in field Agent ID usually we fill SAP user ID, but i wanna using department name.
is there anyone can help me
thanks,

Hi Raju,
Are you setting release for purchase requisition or purchase order ? If you are setting the release strategy for purchase requisition you need to enter table name as CEBAN and for purchase order give table name as CEKKO.
Enter tcode SE11 and give database table name as CEKKO and choose the appropriate field name for the desired component from here. Do the same with table name CEBAN for pur req.
Hope this was helpful.
Cheers,
XsNitin

How to turn off Release strategy

Hi,
We need to upload purchase orders via LSMW. While doing so, we do not wan the release strategy to be active to avoid the need for approving each order. How can I turn off the release strategy.
Thanks in Advance.
Regards,
Pavan

Hi
Not sure if this requirement is to handle the cutover POs/ POs which were already approved in legacy system, I have handled this by two ways in the past ( as due to last minute changes we were not sure abiut frequency and need of turning release strategy to on / off
1. We have use a charactertistc (corressponding to PO date ) in Rel strategy and setup in such a way that REL strategy is active for PO with PO date > Go-live date ( all legacy POs were loaded with s date earlier than Go -live date)- this ensure that we need not to do on/off several time
2. another case we created a seperate PO doc type and excluded from rel strategy, no uses was given authorization for creation of this except the cutover / data migration team which was responsible for cutover
Hope these suggestion helps
Reg
Dheeraj

How to set the Release Strategy without classification for PR

Hi,
I am able to set Release Strategy for PO with classification, however, now I want to set the Release Strategy for PR with classification. Can someone tell how to proceed to set the Release Strategy to PR with Account Assignment.
I crated the Release Codes, however not able to find what options to choose in the following steps :-
Release indicator
Assign Release Indicators
Release Points: Prerequisites
Determination of Release Strategy
Regards,
Yogesh

1. Release codes
   Create the release codes.     For Purch. Officer, Manager and Sr. Manager
Like PO, MG, SM
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.
You can use sytem defined indicator in this case you dont have to do anything
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.
Here you can define the you criteria but one thing you keep in mind that you hae to define all criteria.
E.G if you will not define the Material group here but it will default in req in that case this will not work thats the reason you have to work with Classification.
<b>In the classification whatever criteria you need that only you have to include like in your case you care about A/C category and value only.     </b>

How to configure oracle alerts to use Workflow mailer?

Hello Guys:
We were trying to setup oracle alerts using workflow mailer. I have created a dedicated mailer for handling oracle alerts related mail.
Here is what I need to clarify:
1. Having setup a new mailer for Oracle alert do I have to still configure the Options in Oracle Alerts. This is where you choose which type of mail u want to use ( like Unix mail,Windows NT mail )
2.How do I tell oracle alert to use the new mailer that I created exclusively for this? While creating the mailer at some point I remember putting ALR in configuration form.
I am on 11.5.10 CU2. I am on 11i.ATG_PF.H
Regards,
Bala

Hi Hussain:
Based on the note I realised that my oracle alerts will user unix sendmail. But then If u go to " Oracle Alert Options "
-- > Mail systems -- I check Unix send mail
-- > Mail server options ( Do I have to fill this section? )
My guess is that the send mail will post the email to a IMAP account ( I created oraclealert account ) and IMAP account will push the alert email to Recipient
Mail Database/Server Name --- imap.mydomain.com
Mail Priority --- Normal
Accounts
Application Installation username Password
Blank ** Blank ** oraclealert pwd
Blank ** Blank ** oraclealert pwd
** - It wont allow me to choose an application.
Is there a simple test to make sure that my oracle alert is working or not? I appreciate your help.
Regards,
Bala

How to Display PO Release Strategy in Enjoy Screen

Dear all,
I have a PO with a release strategy, which contain several release codes to release the PO (i.e. M1 & V1).
However, I am only able to display the release code (i.e. M1 & V1) in t-code ME23. I could not do the same in the enjoy screen t-code ME23N for the same PO number.
In the item level, there should be a tab with release strategy to display the PO release strategy (similar to PR), but it is not appearing.
Could anyone tell me what is the problem here? I just could not find the tab or menu to view the release strategy of a PO in the enjoy screen. Similar goes to other PO. I could not view it as well. But in the old screen, I could view it.
Thanks a lot.

Thanks 4 the reply Rahul.
I understand that it is only possible to release at header level. What my problem is that I am unable to view the release strategy (which code to release and who to release) for the PO in enjoy screen.
In my earlier thread replying to Ankur, I am simply describing that I could just select a line item, click on the release strategy button and the release strategy is displayed. A different line item with different value generated a different release strategy of course. Different amount require different set of release strategies, usually more level of approvals.
So, actually this question is not about where or how I can release a PO, but actually I could not view who is releasing for a PO in ME23N.
I even simulate it in the development server and still the same thing happen. Is it the same for everyone else? If yes, how to view who is releasing the PO in ME23N? Version of system is 4.7.
Thanks and appreciate if anyone could help.

How to control PO Release strategy using WorkFlow

Similar Messages

Maybe you are looking for