PR Release Workflow WS20000077

Hi Workflow Gurus,
I am using SAP provided standard workflow (WS20000077)for PR Release. This workflow is triggered when event Release step generated is raised in the system.
I have PR with two release code L1 and L2. If i see the workflow it has only one level.
My question is that is it necessary to add another level insiade my workflow?
or
When level one (L1) releases,current workflow will be completed with L1 release and agin workflow will be triggered for the same PR with release code L2.
Please help.
Thanks in advance.
Regard
Sagar

Hi Sagar,
If it is value based, then u need to create characteristics for price value and include that characteristics in class and then use that class in release strategy. And u need to give the range of value in Classifications in Release Strategy. you can refer the following link for release strategy,
http://help.sap.com/saphelp_47x200/helpdata/en/04/92761846f311d189470000e829fbbd/frameset.htm
Regards,
JMB

Similar Messages

PR overall release workflow

Hi All,
I am working on PR overall release workflow (WS20000077) and had activated workflow for PR rejection 'wf_pur_rejo' (WS65400029). When i create a PR using ME51N workitem gets created. When we reject the PR by executing the workitem i receive the workitem for rejection also. Everything is fine till here.
But when i try to execute the workitem (Purchase Requisition XXXXX Rejected) i get an <b>error 'No Administrator found for the task'</b> and i observed that in workitem log it is shown in READY STATE. This happens for some user ids and it works fine with some other user ids.
Can any please tell me where i am going wrong and if i am then eloborate on what should i be doing?
Thanks in advance,
Regards,
Lakshmi Narayana.S

I have got it, ran the Transaction SWU_OBUF to synchronize the buffers and re-logged into SAP. Now the problem is solved.
Regards,
Lakshmi Narayana.S

Additional PR release step while using standard workflow WS20000077

Our current PR release strategy is overall release and based on 3 characteristics: doc type, creation indicator and total value of PR. Release code is relevant to standard workflow WS20000077 with role resolution using user-exit. User exit is based on the position of PR creator to navigate HR org structure for assigning manager who has sufficient release authority as workflow approver.
There is a request for additional release step in case the PR contains item for a particular material group or fixed vendor, then the 1st release step should be taken by a dedicated position/user.
I found that it is quite confusing while PR release strategy is overall release but referring PR item level data. Please advise is it possible and how to implement the additional release step. Thanks.

Thanks for your quick response.
I also think about this to keep workflow side untouch by including one additional release code in MM release strategy configuration. Unfortunately material group is item-wise, material group of item 1 may not be the same as item 2 (unless we restrict all items' material group to be identical by user-exit). Otherwise, I'm not sure how to incorporate this into a document level overall release strategy.

To trigger Overall release for PR workflow (WS20000077)

Hi,
I want to know that how can i trigger overall release for PR workflow ( WS20000077 ) of BUS 2105.
rightnow in my system workflow WS0000038 is activated & when i perform ME51N it is triggred perfectly. and in SWEL BUS2009 is triggered, but it wont trigger BUS2105.
So how can i trigger BUS2105 & instead of BUS2009, so it will trigger WS20000077 workflow.
Which seetings needs to be done in SPRO, so it will trigger BUS2105?
And please give me some idea about overall release for PR workflow & item level release for PR workflow.
Regards,
Smit

Hello,
Right now, the release strategy is configured item-wise for the PR and so the business object BUS2009 is triggered. To make the release of PR from Item-wise to overall, please make the following configurations in SPRO
SPRO -> MM -> Purchasing -> Purchase Requisition -> Define Document Types and check the 'OvrelReq' checkbox and then
SPRO -> MM -> Purchasing -> Purchase Requisition -> Release Procedure-> Procedure with classification->Set Up Procedure with Classification and maintain the Release Groups by checking the 'OvrelReq' checkbox.
Once these configurations are done, first check whether the event 'RELEASESTEPCREATED' is published in the system from the event log(SWEL). Once an entry is found,deactivate the linkage between template WS0000038 and activate the linkage of the template WS20000077 which is for the BO BUS2105.
Hope this will help.
Thanks,
Samson

Error in PR standard workflow WS20000077

Hi Friends ,
I have activated the standard workflow WS20000077 which is for PR release procedures . When i am creating a PR it is triggering the workflow with an error " Import container contains errors (are any obligatory elements missing?) " .
I have checked the forum for the same error but i did not find ant exact solution for that .
In SWEL , the object key is being populated by the PR no . So i think this is the problem due to the Release code which is not getting any value in the event container after the event " Releasestep craeted" gets triggered .
So please guide me on the same how to resolve the above error .
I am using ECC 6 version of SAP .
Thanks in advance
Sarmistha

Thanks again for your reply .
I have tested the workflow in SWUE by assigning the Release code value manually and the workflow is triggering without any error .
So as you told i think some SAP Notes needs to be implemented to resolve this issue .
If you have any idea on this please guide .
Thanks
Sarmistha

PR release Workflow

Hi All,
Wanted to set up PR release workflow.
1. While having look at a template WS00000038, came to know that Agent assignment is not available for std template.
Whereas documentation says that rule 00000148 shuld be used for item level release workflow step.
Do i have to do the configuration of the template to include this and its binding inside workflow template?
2. Do i have to configure both the templates i.e for item wise release and Overall release?
Thanks in advance.
Regds,
Akshay

Hello Akshay
You might have to configure both workflows (and relevant customizing) for item-wise and overall release depending on your client's needs; if they need one, the other, or both, you implement that one. The standard workflow for overall release is WS20000077, just in case.
As for setting up the rule in the template, the agent assignment rule for task TS00007986 is not found in the workflow, but rather in the task itself. Check the task definition and take a look at the "Default Rules" tab of the task: you'll find rule 00000148 and its corresponding binding there.
Of course, if you want to tinker around with the standard configuration (which depending on your client's needs is a likely possibility), in my opinion it's good if you just copy the standard and adjust the copy.
Hope this helps!
Juan Ramos

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.

PR Overall Release Workflow - Agents Determination Failed

Dear All WF Experts,
I have used the standard workflow WS20000077 for PR Overall Release. I have assigned the agents to the task TS20000159 by position maintained in the Workflow Organizational Management Structure. The agents' names are showing correctly in the task's agent settings.
However, when I execute the workflow, the error 'Agent Determination Failed' for that step (TS20000159). I have checked the agent settings in workflow and SPRO, they look fine. Could anyone please kindly give me advices how to solve this error? Thank you so much.

Hi, to all the experts who have helped me all these while,
Thank you very much for spending time helping me to go through this issue.
Yesterday, I ran through the coding for the function module for the rule AC20000026 again. I found out that there is one part of the coding which is causing the failure of determining an agent. The code disregard the company code for overall release of Purchase Requisition while the business requirement involves company codes in every PR created. Thus, by changing that code, the problem is solved.
The snippet of code of function module (ME_REL_GET_RESPONSIBLE):
   CASE t16fc-frgwf.
* keine Ermittlung
      WHEN space.
        RAISE nobody_found.
* Ermittlung ¨¹ber T16fW
      WHEN '1'.
        IF eban-gsfrg EQ space.
*     Einzelpositionsfreigabe Banf
          SELECT SINGLE * FROM t16fw WHERE frggr = eban-frggr
                                       AND frgco = rm06b-frgab
                                       AND werks = eban-werks.
        ELSE.
*     Gesamtfreigabe Banf
          SELECT SINGLE * FROM t16fw WHERE frggr = eban-frggr
                                       AND frgco = rm06b-frgab
                                       AND werks = space.
There is always a value in werks in my business scenario...
SELECT SINGLE * FROM t16fw WHERE frggr = eban-frggr
                                       AND frgco = rm06b-frgab
                                       AND werks = space.
So, by changing it to
AND werks = eban-werks
it will work, however, I think it's better to just remove the If statement
IF eban-gsfrg EQ space.
, since it has no effect anymore.
I hope this would give a hint to all the rest who might be facing the same problem as well.
Thank you very much,
YL

Issue in PO Release Workflow WS20000075

Hi All,
We have activated Std. PO release Workflow WS20000075 for two step release levels. When New PO created with release strategy this workflow will trigger and send workflow items to Agents to release Purchase Order. Up to this it's working fine.
But the problem occurs to trigger Workflow again after PO price change. We have release change indicator with 5% variance of price. That means when some one changes the Price or Quantity and if the total values variance more than 5% of price variance then Release strategy will activate again in PO. But in this case Workflow WS20000075 not sending workflow items again to the agents.
Is there any workflow setting causing the issue?

Hi Sivaparvathy ,
As far I can understand in SWEL event trace for the second time the event is getting triggered but there is no appropriate receiver for that event. Can you please specify the event name. If it is any event other than RELEASE for eg lets say if it is CHANGE, in the workflow WS20000075 header you will have to bind the workflow with this event and activate linkage for this particular event as well(without changing the previous configuration for PO release event). So that the workflow is triggered for this event as well..
Hope this helps
Regards
Anik

PR Release Workflow Problem in   " Rejection of PR   "

Hello Everybody ,
When Purchase Req is Created by End User , this is Approved by Higher authority   When PR is Released Workflow is trigering but when PR is Reject Work flow is not trigering ?
Is there any soultion for Rejection of PR ?
Regards,
Sandeep

Hi ,
are you using the standard workflow..?
can you see the standard workflow   WS00000038(purchase requisition release).
Have u maintained these things.?
                                                Release Groups
                                             Release Codes
                                             Release indicator
                                             Release Strategies
                                             Workflow
may be it is useful.
and check the 'userdecision' .
once PR requisition is released, we can goto tcode ME53N there we have to select
release,or rejected .
if the rejection is not working properly please check the released codes.
if you know more about this plz post the reply.
regards,
sateesh.c

PO Release Workflow Problem

Hello,
This is regarding PO release workflow(WS20000075).
I fail to understand as to how I can trigger workflow on realising PO
from ME29N, though using SWUS (Test Workflow) I am receving message
in the sapoffice mail.I am not really able to link the application with the workflow.
Secondly I dont understand why the second task i.e., Release Purchase Order Effected' does not trigger when I test the workflow.The message i receive is 'Please release purchase order no ....' and not 'Purchase order Released' when I test the workflow using SWUS.
Kindly advice.
Regards,
Sumit

The deactivation is happening as there is some error in the instances. Please change the settings in SWE2 for WS20000075 entry and change the field of Feedback after error as Do Not Change Linkage. The error might be due to some authorization issue please check from SWEL and analyse accordingly.
Thanks
Arghadip

Dead Line Monetering in Purchase Order Release Workflow

Hi Experts,
I have activated Standard Purchase Order Release workflow and it works fine now i have a requirement of Dead Line monetering for 2 days. In Standard Release Activity TS20000166 if i give 2 days in Latest End.
Will it work in such a way that if the first approvar does not take any action for 2 day then it automatically esculates to the next person in the release strategy.
Or should i use Modeled Deadline for esculation to next Level.
Regards,
Hari

Hi,
If you just have 2 days on the latest end tab, the workflow will only send a deadline notification to the current agent and WILL NOT escalate.
You have to use modelled deadline and in that branch route the workflow to the next approver based on your agent determination rules.
Satish

FI Payment Release Workflow Agent assignment and SPRO settings.

Hi Experts,
I am working on Payment release workflow for 2 stages. So for this i have activated the main workflow WS00400012 and for First level release WS00400011 and for second level release WS00400021.
Now where should i assign the agent for First level release and second level release ? and what setting should i do in SPRO as FI settings.
Any of you suggestions will be of great help me to resolve this issue.
Regards,
Hari

Hi,
Thank you for your reply.Should i mention the main workflow number in SPRO or
just the subworkflows alone ?.
Assign main workflow number
Can i assign users directly in workflow itself insteas of assigning position in SPRO.
Don't assign users inside the workflow, if the user id you want to change then again you have to change the workflow.
Regards,
Surjith

Payment Release Workflow

Hi Folks,
         We are working on Payment Release workflow in AR module.
         Once the invoice is posted, workflow is able to block the payment, but not sending mails to the agent for approval.
         For testing, i have entered a dummy userid as the agent and checking for the mails.
         How can we debug or monitor to check why the agent is not getting mails in SBWP.
         Pls suggest how to solve the problem.
Thanks in advance,
Shyam.

Hello,
Okay, let me correct that for you:
"We are working on Payment Release workflow in AR module.
Once the invoice is posted, workflow is able to block the payment, but not sending WORKITEMS to the agent for approval.
For testing, i have entered a dummy userid as the agent and checking for the WORKITEMS.
How can we debug or monitor to check why the agent is not getting WORKITEMS in SBWP.
Pls suggest how to solve the problem."
Have you looked in SWI5 to see if it is listed for the user there? Check that there are no excluded agents.
The solution is likely that you haven't set the task to General Task, as already suggested.
regards
Rick Bakker
hanabi technology

Error in Payment Release Workflow in the task Determine Subworkflow

Hi Experts,
                  I am working on Payment release workflow WS00400012. When a document is posted I am getting an error in the task TS00407859 (Determine Subworkflow Release for Payment). Within this I found "SUBWFDETERMINE" is getting executed in this task I am getting an error. I did debug the method SUBWFDETERMINE from SWO1 there I am gettng an error "Error in workflow customizing" this is because the field SUBNR is initial. Can anybody tell me in the customizing where I am doing the mistake.
Thank you.
Srija

Hi Arghadip,
                     Thank You.
                     I checked out the table VBWF01 I found the subworkflow "WS00400011" in SUBNR field.would be there any other reasons why its getting error?
Please suggest me.
Thank you.
Srija

PR Release Workflow WS20000077

Similar Messages

Maybe you are looking for