Purchase Requisition (PR) Workflow

Hello all,
I hope you can lend your thoughts/experience.
I have been advised that a PR workflow (without the need of a user exit) can be designed to route notification to the approver based just on the structure in organizational management (OM).
For example in OM users, John and Jane is assigned to Finance department while the approver for Finance department is Mary.
When a PR is created by John or Jane, notification will be routed to Mary based on the structure in OM.
To do the above, I have been advised that the I will still have to maintain the workflow configuration in MM but that I do not need to assign a position to the release group/release code.
The problem is that if I do not assign a position, I cannot save. So this is a dead-end.
My thoughts are that this requires implementation of user exit, M06B0001.
I hope someone can help.

Hi Richard,
I have done many of the Purchase requisition workflows before and according to the customizing it is not mandatory to have a position or the user assigned to a release strategy. It becomed mandatory only if you have the value "1" in the Workflow column of the Release codes. If you do not have a 1 in that field then the event will be raised but it will not start the standard workflow. Once you have a workflow attached to the event "ReleaseStepCreate" and within the workflow you have an activity to release the PR based on the rule which searches for the manager of the user who created the PR you have the workflow ready. Just incase you need it the rule number is 00000168 and you can view it via transaction PFAC.
Hope this helps,
Sudhi

Similar Messages

Overall purchase requisition's Workflow : mechanism of release code

Hi all,
i need to implement Overall purchase requisition standard workflow ; i need to have 2 actors for process's validation, so i set release code like this :
01 - ACTOR1
02 - ACTOR2
The workflow is launched, the ACTOR1 received a work item in his workplace, whe he execute the work item, the transaction ME54N is launched. Well. But the ACTOR1 can a decision for him but also for ACTOR2, why ? the process is not good for me. If ACTOR1 has taken a decision the workflow of release code 01 is finished. An other workflow is launched for release code 02, when the ACTOR2 go to the transaction ME54N he can take a decision for his relase code but he can also cancel the previous decision of ACTOR1, it's not good for me, can you explain to me ?
Thanks for help.
Cheers.

Interesting solution using the user-exit.
I just finished modifying the delivered overall purch req approval WF. I needed to add a few fields for reporting so I created virtual attributes via delagation on BUS2105. I created approval and initiator agent attributes and email addresses. It works fine and I don't have maintain any further code other than what is in my business object which I can use again and again.
Many roads on the way to Rome

Call purchase requisition approval workflow in abap program

Hello,
I copied the standard workflow for the approvaI of a purchase requisition WS00000038 and i tested it. I create a purchase requisition in me51n. This is triggering the event releasestepcreated which starts my workflow. Everything goes ok.
Now, i want to call this workflow in ABAP. I do not know exactly how to do it. Here is the code I tried.
data: ls_objkey type SWR_STRUCT-OBJECT_KEY,
lt_mesage type table of SWR_MESSAG,
gt_container type table of swr_cont,
gs_container type swr_cont.
gs_container-element = 'ReleaseCode'.
gs_container-value = '01'.
append gs_container to gt_container.
gs_container-element = 'requisition'.
gs_container-value = '0010000362'.
append gs_container to gt_container.
gs_container-element = 'RequisitionHeader '.
gs_container-value = '0010000362'.
append gs_container to gt_container.
ls_objkey = '0010000362'.
CALL FUNCTION 'SAP_WAPI_CREATE_EVENT'
EXPORTING
object_type = 'BUS2009'
object_key = ls_objkey
event = 'RELEASESTEPCREATED'
TABLES
input_container = gt_container
MESSAGE_LINES = lt_mesage.
As you can see i filled he RequisitionHeader, requisition and release code. I saw in the workflow that i copied, that these are import parameters. Requisition and release code are mandatory. 0010000362 is a purchase requisition that i created.
After i run the program i receive a work item in SBWP but it has the status error.
Can you help me?Perhaps anyone has done this. I think that i am not filling the correct data or something like that. Maybe you can look in the standard workflow WS00000038 and tell me what I should pass and how.
Thank you,
Efren

Hi Efren,
The Problem is, for the purchase requisition there is two key fields.
So when you pass the keyfiled to workflow it should be the concatenation of Purchanse requisition number and the item number.
You have to pass the object key as below.
ls_objkey = '00100003620010'.
Then only your business object will getting insatanciated.
Thanks,
Viji.

Purchase requisition's Workflow :

Hi all,
i must implement the standard workflow for purchase requisition, i use the number 20000077 - Workflow for overall release of requisition.
I would like to know if it's possible to have many responsibles for a code release in release strategy or it's not possible, for each release code there can be only one agent. I use user-exit to get responsible.
Cheers.

Hi,
You can create positions in organizational management plan for workflow (T-Code : PPOCW). Under each position, you can assign more than one user.
In SPRO, linked the release code to the position (Object Type : S) and assign the position id (from the one you created in organizational management plan) in the workflow.
In your workflow definition, assign the positions as agents to the task. After you assign the agents, you can actually see the users under each position (if you have already assigned users to positions).
When the workflow is triggered, all users for the position linked to the particular release code are sent the work item. If anyone of them have processed the work item, it will be removed from all the workflow inbox of the other users.
I hope this would help...
I just implemented the PR workflow recently but is still new to the field. Please correct me if I am wrong.
Thanks,
YL

Workflow error in release Purchase requisition

Hi All,
I configured the settings for workflow in Purchase Requisition.(both purchsing & task specific )
Now, my workflow is started but its status is Error.
actually it is not able to find the recepient in role 20000026.As i already mark relevent release code as 1 & also assign US user id in the PR release settings & also put the User ID in task specific customization.
Still i am facing this error.One thing i want to mention is i am not aware of the settings required in the Edit Qrganizational Plan tab in SPRO.
If some more clarification is required ,i will prode the same..
Plz suggest some solution in this regard with T codes & bit detail.
Thanks & Regards,
Sandeep Sharma

Sandeep,
Okay here's some details which will help you out. I presume that you have done customizing for PR release strategy.
If not then follow this procedure:
http://help.sap.com/saphelp_47x200/helpdata/en/04/92761846f311d189470000e829fbbd/frameset.htm
Once you establish release strategy , event releasestepcreated will automatically created by system based on release codes.
so say for a standard pr type you have defined two release codes I1 and I2 (based on certain amount- you can see this in class characterisitic using tcode CL02) and class type -032 and class PR_RELEASE most probably, check Char. tab).
Once you define char. in CL02, you gotta run tcode CT04, give the name of char. and fill all tab.
inside tab Addl data, you have to define CEKKO table and field too
this is where we have referenced the event releasestepcreated implicitly.
FOR all customizing of release strategy check this link , this is really great blog
http://www.sap123.com/forumdisplay.php?s=cced678eca43fe7a7e3bb9b83dc94022&f=2
then search for "setting up simple release procedure" thread in it.
It is for PR.
So if I1 release take place event will triggered, say A has approved I1 level and for whole PO release I2 is also required then one more time event releasestepcreated event would be triggered.
You can create workflow for PO release. Approver are determined based on rule AC20000026 (check in PFAC) based on FM which has user exit EXIT_SAPLEBNF_001 where you can write down your own code for approver determination.
I think that you gotta put 9 (in release code settting in SPRO). If you are inserting 1 then you have to define US and user name (which I think you have done).
Hope it will clear your doubts
Cheers
Jai

Workflow for MM purchase Requisition steps required

Dear all,
        I am trying to configure purchase requisition Workflow.
        I am working with Work flow, WS 00000038
        I have assigned agents to TS 20000162
        Now how to proceed further, do i need to maintain some more settings
        or i should try to test system.
        Regards,
        Gaurav sood

Under the assumption that things have not changed much since 4.70, here's quick introduction:
The workflow is started only when a relevant release strategy is found, so customizing of release strategies is a very important (first) step here.
In the Implementation Guide you find the customizing in the following path:
Materials Management
-- Purchasing
-- -- Purchase Requisition
-- -- -- Release Procedure
-- -- -- -- Procedure with Classification
Only the procedures with classification are relevant if you want to use workflow to notify about requisitions waiting for release.
First you must set up a classification class if that has not already been done. Derive your characteristics from the structure CEBAN. The online help is not too bad, I had never set up classifications before and managed to get it working.
If you need data that are not available in CEBAN, or you want to modify them for the purpose of determining the release strategy there is an enhancement you can implement, and there are customer fields you can use. The enhancement definition's name is M06B0002.
As an example of what you can do, I have used it to set the company code in one of the customer fields, and to change the account assignment type. However, whether you need this enhancement or not depends strongly on what data you use to determine your release procedures (a step in customizing you will get to later).
When that is done you define release groups and release codes. Release codes are defined within each release group. Whether you should use one group or several groups is often a matter of choice.
I myself prefer using several groups even if I don't have to, so long as it doesn't lead to having to define duplicate release strategies (which you will soon get to). So, if there is some characteristic that clearly separates your release strategies, e.g. the highest amount that does NOT require release etc, you can define one group for each value (group) of this characteristic.
For instance, if some company codes require release for everything worth more than 100EUR while the default is to require release from 10.000EUR you could create to release groups. None of your release strategies will be duplicates since the value from which release is required will be different and you thus need to have that as a characteristic.
You then check that the set-up of release indicators is OK, and then you are ready to start defining the strategies. Release stragies are defined within each release group, and use one or more release codes (two or more release indicators).
It is fairly self-explanatory once you get into the screens. The thing to be observant about is to not define overlapping strategies, as this will prevent the solution from working.
When you are done, and have tested the solution in DEV it is time to transport it to the QA system. That's when I got a rather unpleasant surprise. The classification data are not transported, so both the characteristics and class, as well as the classification data in each release strategy had to be redefined. And in roughly two hours I have to do it again in production.
It is possible to transport classification information, it is described in SAP OSS Notes (different solutions for different versions).

Reg Workflow Copy while copying Purchase Requisition to different user ID

Hello Guru's,
Will anyone suggest me, i have copied a purchase requisition from user D1 to user ID2. Once it has copied to ID2 it should work as per the workflow which is assigned to ID2. But it is taking *ID1 workflow* is there any way to stop it and assign it to ID2 workflow. Will anyone guide me.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Apr 22, 2008 12:57 PM

Hi Ram
In SWI5 transaction, check whether a work item has got generated for director and VP or not.....
You will find the work items in SAP Inbox if system has generated a work item for director or VP....
That will narrow your analysis
Regards
Virender Singh

Purchase Requisition to Purchase Order conversion through workflow

Hello Experts,
My requirement is to create purchase requisition to purchase order automatically through workflow. How to proceed with these conversion, since am new to workflow please help me with the valuable inputs.
Thanks,
Naveen

How does the senior person approve? using workflow or using transaction ME54N?
if it's the standrad transaction then again, use a user exit or the released event.
even if the approval is done in the workflow I would not recomend using creating the purchase order as part of the workflow since this is not a workflow issue, but if there is no other option create a new method in BUS2105 (use delegation) and call the BAPI in it.

Purchase Requisition Workflow - Organizational Plan required?

Hi,
We are implementing purchase requisition workflow.
Based on what I have read, it says that the workflow table (table V_T16FW) and SAP HR-PA-OM (organizational plan) must be set up to support the solution.
Question: If we are routing the workflow to a UserID, i.e. Object Type = US (and not an HR data object like Position or Job), do we require an Organizational Plan to be also set up?
Cheers,

Thanks so much for your response.
What about assigning tasks to users, etc. that is usually done in org plan, correct? If object type US is only used, I assume this is not required either?
Also, what is the benefit of using Object type = 'S', i.e. position? At my company, most of the time, when people leave, the position is deleted and a new one is created (there are a couple reasons for this), which means, even if we did use positions, the workflow table would still need to be maintained everytime a person leaves/joins the company (I understand if only the user to position mapping changes, then it makes sense to use positions, and therefore the workflow table stays constant, and only the user to position mapping changes). Are there any other benefits of using S instead of US?
Also, is it possible to NOT use a workflow table, and ONLY define an organizational plan? I was thinking to activate user exit M06B0001, and perhaps ONLY maintain an org plan, and use this to determine approver, rather than maintaining both MM workflow table and SAP Organizational Plan (HR-PA-OM). Bottom line, we want to maintain as little data as possible.
Your thoughts?
Cheers

SAP workflow for purchase requisition and purchase order

Hello Sap Workflow,
Can you please help me on building workflow for purchase requisition and purchase order with the necessary screen shots ?
your quick response will be greatly appreciated.
Thanks in Advance

Hi,
Please check http://help.sap.com .
http://help.sap.com/erp2005_ehp_04/helpdata/EN/04/92761846f311d189470000e829fbbd/frameset.htm
http://help.sap.com/erp2005_ehp_04/helpdata/EN/04/92775546f311d189470000e829fbbd/frameset.htm
Configuration guides are available in SAP Solution Manager.
Regards,
Masa

Purchase requisition workflow - reset release via BSP and BAPI

Hello,
We have a small workflow to release purchase requisition.
A mail is send to the approver. The approver opens an BSP application to release or refuse the PR.
The approval works well.
The rejection doesn't work well.
I use the BAPI_REQUISITION_RESET_REL_GEN to reset the first release of the PR (00 release key)
We have 00, 01, 02 as release key, and all the release have to pass to release completely the PR.
00 is the requester level.
My problem is :
for example I am the 01 level. I received the mail from 00 level, I refuse the PR via the BSP. In ME53N, the current release key is now 00 but when I look at the workflow, the following agent (corresponding to 02 release key) is determined. Normally nothing has to happen.
Someone has an idea to stop the workflow ?
thanks
Véronique

Hi Martin,
When I checked the contain of container in the workflow (in the log), I saw that the release key is 02.
I don't know why but the WF received the event RELEASESTEPCREATED instead of normaly it is finished.
When I reset the release via ME54N, the WF ends correctly and no new event is received.
How can't I see why the event is started in the BAPI.
In fact it is very strange, if I used the BAPI alone, all works, no new event is started.
But if I used the BAPI in my BSP, a new event is started.
Thanks
Véronique

Purchase requisition & Purchase order Workflow

Hi,
We have activated workflow for Purchase requistion & Purchase order. Workflow is working fine but the client requirement is to have mail to be triggered to the person who creates purchase requisition or purchase order through workflow to go ahead for sending to vendor i.e it should trigger message through workflow to the user saying he/she can forward this PR or PO to vendor.
The following workflow objects are used.
WS20000075
WS20000076.
Can anybody let me know how this can be achieved through workflow.
The message should be like your purchase order has been approved & you can send it to vendor.
Regards
Ravi Shankar.

Hi,
We have used user exist in the release strategy after release of PO/PR mail will be sent to PO/PR creator with required text.
These text are maintained through SO10 by technical team.
Regards
Ravi Shankar.

Workflow purchase Requisition through transaction ME51.

Dear Friends,
Can anybody help me out by telling me a step-by-step process as setup up workflow purchase Requisition. and one more thing i wants to complete this through purchase Requisition transaction .
scenario is just like,
firstly i want create the purchase Requisition then this is directly connected for approver through WORKFLOW,
How to connect the creation purchase Requisition through Transaction and that number goes for take approver through Workflow.
Can you please you give me one example step by step , so i can do this one.
Thanks in Advance for help.
Cheers.
Puneet.

You check standard Business object BUS2009 thru SWo1 and standard Workflow Template WS00000038 thru PFTC_DIS.
<b>Please reward points if useful</b>

Workflow Purchase Requisition

Dear Friends,
we activated WS00000038 Workflow for requisition release. But we have a problem in this condition; if the initiator is approver in any step, purchase req must be approved automatically. How can we do?
Thanks.

Hi,
I guess you are looking at creating a custom workflow, a copy of WS00000038 would be a good start. This custom WF would have additonal step to check if the next approver is the initiator and if true do a background step by calling the "Release" method from the object "BUS2009-Purchase requisition item".
Remember to change workflow starting event to your custom WF to avoid multiple WF instances.
Viren.

Purchase Requisition workflow escalation

Hi All,
I need help with purchase requisition workflow escalation. The workflow for the requisition escalate to the next level if not approved within 24 hours.So i dont want the workflow to escalate on weekend.
I want to know what can i do.
Tx Rosi

Hi
For your Requirment :
"the requirement is that if an approver doesnt approve in 2 days time then the PR will automatically go to the next approver for release."
Please follow the below steps.in copy of WS20000077.
1.For taskTS20000159:Overall release of requisition , go to
Latest END tab: put ACtion as :Modeled , Refer.date/time:Workitem creation , below time : choses: DAY, and on left add 2.
Outcome :Deadline Montoring.
2.Then come to OUTcomes tab of the same task: see there are 3 lines 1.Step executed, 2.Latest end:Deadline Montoring, 3.Processing obsolete:Processing obsolete ,, all are ACTIVE or not , if not, Activate .then all should be Green.
4.next in the OUtcome :Deadline Montoring , use a process control step. to Set missed workitem to obsolete, in Function: chose : set Work item to Obsolute. and Workflow Step : chose then step no for the above task(TS20000159:Overall release of requisition).
5.In "Processing obsolete" path, again call the same task TS20000159. in different activity . and see to the agent assignment.
I think this will slove your problem.
How it works:
1st the PR is send in a WI to the perticular agent by the 1st activity . if the agent do not execute for 2 days. then that WI will set to obsolute . and process flow to" Processing obsolete" path, then agian PR is send to the next agent using the same task but activity created in step 5.
thanks
Kakoli.

Purchase Requisition (PR) Workflow

Similar Messages

Maybe you are looking for