Purchase Requisition workflow issue

Hello friends,
i have created a workflow for PR release by copying standard WS20000077 .
the WORKFLOW trigeers properly ,
but when it created it goes to all users of applied release strategy , before release of previous one
what may be problem .
kindly suggest me .
Thanks & Regards
Digvijay Rai

Hi,
but when it created it goes to all users of applied release strategy ,
before release of previous one
You mean to say in the 1srt level Approval it goes to all People right. How you are determining the Agent, check that.
For PR Workflow See the Following,
WS20000077 this std. Workflow for the PR Release this has multiple levels of approvals, Depends on the no. of approvals it will flow.
The approver can picked using the User Exit M06B0001 (EXIT_SAPLEBNF_001), here you have to write a logic to pick the Approver.
The approval workitem comes to SAP Inbox, once the approver click the workitem it will open the Transaction, there the user can approve.
To see the status of the Workflow, Go to ME53N, in the top left a button, Service Object, click on that, a drop down appear in Workflow > Workflow Overview, you can see the status here.
Regards,
Surjith

Similar Messages

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

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.

Link a MRP Purchase Requisition to a Purchase Requisition Workflow

Hello Gurus,
I have a Purchase Requisition Workflow already created.
I want to create a MRP purchase requisition that start my workflow.
How can I do that?
Thanks in advance,

Hello Charlie.
Our release strategy hasn't classification. When we I create a MRP purchase requesition, the release stratagy is already assigned to that. however the worklow is not started.
thanks

Purchase order workflow issue

Hi All,
A PO is created and rejected by a user in user decision step.The workflow will end.If the PO is changed(amount) again,the release strategy is triggered for the same user.But the workflow is not triggering.If the release strategy is for a different user,its triggering the workflow.I have used a fork inside which 1 parallel branch contains a wait for significantly changed event & another branch contains the user decision step,po release step & rejection reason scenario.
Please refer the thread below.
PO Release Strategy Issue
Replies will be greatly appreciated.
Edited by: Feddie on Jan 3, 2008 11:43 AM

Hi,
This is not workflow issue(work flow is different term)
It seem problem of BADI (program written for creation of purchase order based on sales order)
Take help of ABPer so he/she can solve this issue
Kapil

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

Deadline monitoring/Escalation - Purchase Requisition Workflow WS20000077

Dear Friends,
I have read some stuff on SDN but still couldnt figure out the soultion.
Its a common problem. We have set a release strategy in Purchase Requisition and are using std workflow WS20000077.
Now 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.
I have set the deadline monitoring using the workflow wizard for model deadline monitoring. With this, The work item gets deleted from the approvers inbox. Next in the obsolete path I have set a process control which specifies the worklow step as the step in which deadline monitoring was specified.
When I check in SWI1, the work item is set as obsolete but it doesnt go to the next approver for approval.
Your replies will be highly apprecialted.
Thanks & Regards,
Fawaz

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.

Regarding Purchase Requisition Workflow.

Hi Friends,
In PR release ,if i have multiple level of approvers, more than 1 than do we need to handle this seperately or the SAP std. workflow will take care by itself. In the activity 'Overall release of requisition' there is a task which uses 'singlerelease' method of business object BUS2105. Does this method require any changes or only maintaining the release strategy congiguration will help.
PLS help me on this. If question is not clear than pls tell me .

The question wasn't so clear.
Regards,

Purchase requisition - Workflow

Hi
I have one issue related to PR Release,Some requisitions are hanging in the users workspace and few of them are related to released requisitions and few of them are set as a deletion flag from IW32 transaction but these PRs are still exists in users Q. Can any one suggest me how can we delete these requisitions from users Q?
Your help is appreciated
Regards,
Nag.

Hi Nag,
Go to the t-code SWI5. Enter "US" for Type and key in the user's ID number. Then select "Work to Be Completed" and then remove the date. Hit Execute.
You should be able to see a list of workitem pending release, including the workitem that may be stucked for this user. Double click on the workitem to confirm that it is the PR number.
After reviewing that you got the workitem you want, you may proceed to delete from their inbox.
Hope this helps.
Rgds.

Very urgent purchase requisition workflow

Hi,
I have been asked to develop a pr workflow,here i have to capture the tracking number along with the pr no and based on the trancking number it should go to the respective department person to release it.How can I do it.
Regards,
Latha prabhu.

Hi Latha,
You could do you agent assignment using Rules (Called Role Resolution in 4.6C and below). You can create a Rule using Txn PFAC. Create a rule of category F (Agent Determination: Function to be executed). You will have to develop a function module which must adhere to a predefined interface. You can either extend the PR object to have Tracking Number as an attribute and pass it on to the FM or pass the PR to the FM and determine the tracking number in the FM. You can then determine the User or Org Object responsible. Please read the documentation and see some of the standard rules available in the system.
Cheers,
Ramki Maley.

Purchase requisitions idoc issue

Hi,
We have found a new interesting thing happening in ECC.
IDOCs does not get processed due to PurReq is being processed.
Then the IDOC goes into status 51 and can no longer be processed by the batch jobs that is running for status 64.
1) Is it possible to keep the status as 64 for these types of errors?
2) If not is it possible to reset these IDOCs from 51 to 64 in a batch job
3) or is it possible to get the batch job to run for IDOCs with status 51?
Regards,
RSK

Hi,
new !
that's just the normal behaviour since... almost the beginning of IDoc history.
1. yes. program RC1_IDOC_SET_STATUS.
2. yes, but that's not recommanded, as your idoc has been already processed, and it said to you "I cannot update this object because someone or something is currently treating this same object".
if it's a permanent error like (this customer does not exist), that means with a background process (with a too short frequency) you will overload your system for nothing with a treatment like:
"idoc 64 -> 51" + "background change: 51-> 64" + "reprocess: 64 -> 51", etc...
when it's one idoc, it's ok, but if a day you a complete source files with several idocs which are in error.... you will reprocess them several time to say to you the same thing "cannot update because customer does not exist" (for instance).
3. yes. RBDMANIN in background, or tx BD87 in foreground.
According to me, it's better to use BD87 as it's a human you can analyze and decide to retreat the data.
Use background program only if you are sure that the data (in error) was sent a 2nd time after. In your case of purch req. i did not recommanded that.
Have a look a that:
Idoc1: role = change value with A on pruch req 123. This idoc is in error (like in your exm: already processing by another...)
Idoc2: role =change value with B on purch req 123. This idoc arrives 5 min after idoc1. but this times the other processing is finished, and so ecc can integrate this idoc2. So in your systm you have value "B".
And you with your background process which runs (every hour, for instance), one hour after your Idoc2, you will retreat idoc1, and so now for your purch req, the value is "A"... and no more "B" which was the last value sent by your source system. => Problem !
4. So why not use it, but be clever/smart before to use such a background retreatment. Estimate the pro/cons.
regards.
Mickael
P.S : it's because we can, that we have to do it.

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

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

WF-BATCH user in Purchase Requisition

Hello Guru's,
I am developing a Purchase Requisition workflow and using a background method (BUS2105-Release) to release the requisition. My problem is when the item is changed/Released in background the User is getting filled as "WF-BATCH".
To fix the issue i am creating one more activity step after the Release method step in workflow and in that activity step using a custom method to update the values in CDHDR table by validating the exact record from CDPOS table(to avoid deadlock using Enque/Deque).
Can anyone suggest me, if there are any simple solutions or straight solutions to fix.
Thanks,
Sudhir.

Hi Sudhir,
the release is done with the BAPI function
BAPI_REQUISITION_RELEASE_GEN
Some of these BAPI's do offer an import element, saying "USER", where you can overwrite the current user with another one's ID, to avoid having the background user as the last change of the object.
In this case, this option is not available, so to say, there's nothing that can be fixed.
The solution to set and overwrite the release step with another user id, is exactly to change the change documents. So you've already found what you were looking for.
Best wishes,
Florin

Purchase requisition release procedure through User-Exit

Hi Workflow Guru,
I have a requirement to configure purchase requisition workflow . the workflow should trigger through release strategy.
The approver should determine through user-exit and the approver should determine based on value and quantity and that can be define in user-exit. as per my knowledge the value should mantain in SPRO-Release procedure. Please clarify me is it possible through user-exit. I am worked on user-exit for release procedure based on purchasing group.
Thanks in advance.
Regards,
Ranjan Tiwari

Hi,
There is BADI ME_REQ_POSTED
in method POSTED you can write your code to trigger the workflow and get the information related to release strategy and
Purchase requisation .
for more than one PR use below logic .
LOOP at im_eban into gwa_im_eban .
    concatenate gwa_im_eban-banfn gwa_im_eban-bnfpo into gwa_objkey .
add data into container -----------------
      gwa_event_container-element = 'PurchaseRequisition'.
    gwa_event_container-value = gwa_im_eban-banfn.
    append gwa_event_container to gi_event_container.
    clear: gwa_event_container.
    gwa_event_container-element = 'ItemOfRequisition'.
    gwa_event_container-value = gwa_im_eban-bnfpo.
    append gwa_event_container to gi_event_container.
get the other details and create event to start workflow .
select single * from eban into lwa_eban where banfn = gwa_im_eban-banfn
                                              and bnfpo = gwa_im_eban-bnfpo .
        if sy-subrc <> 0 .
      call function 'SWE_EVENT_CREATE'
        exporting
          objtype           = 'BUS2009'
          objkey            = gwa_objkey
          event             = 'zcreated'
        tables
          event_container   = gi_event_container
        exceptions
          objtype_not_found = 1
          others            = 2.
ENDLOOP .
Hope this will resolve your issue.
Thanks and Regards,
Deepanker Dwivedi

Purchase Requisition workflow issue

Similar Messages

Maybe you are looking for