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

Similar Messages

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

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

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

Can't use Overall Release for Purchase Requisitions

I have two groups, AA and ZZ. Each group has it's own Class.
Group AA uses Cost Center Class (CN) (uses Characteristics Cost Center and Line Amount)
Group ZZ uses Order Class (OC) (uses Characteristic Order)
I have built one and only one Release Strategy for each of these Groups. These Strategies both work successfully when I select the other group to be the group for Overall Release. That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully. However, if I modify the req the strategy for ZZ, does not get applied.
The opposite is true. When AA is set to be for Overall release, then ZZ works. However, if I modify the req, then AA's release strategy does not get applied.
Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release. However, neither strategy works if its group is set to be the one for Overall Release.
What am I missing? I only have two classes, two groups, and two release strategies.

SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
Release procedure is of two types
Release Procedure without classification
             This procedure is applicable only for Purchase Requisitions.
             Here PR is released Item by Item only.
Release Procedure with classification
            This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract and scheduling agreements.
            Item by Item and Header level releases can be configured
            For PR - both item by item and Header level release can be configured
            For external purchasing documents - Release is possible only at Header level.
Step 1:
Create Characteristics
In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
            1) Total value of PR more than Rs 50,000
               create characteristic as "Release_PR_total_value" in transaction code CT04.
              Tab - Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency eg. INR or USD"
              Tab -values key in > 50000 INR
              Tab - Additional Data- Table Name "CEBAN" and Field Name "GSWRT"
              Tab - Restrictions - class type - 032 - Release strategy
            2) Plant
                 Create characteristic "Release_PR_plant" in transaction code CT04.
                 Tab - Basic data - Data type - CHAR; Number of chars - 4
                 Tab - Values - Key in all the plants for which you are required to configure release proc. eg. 1000,2000,3000
                 Tab - Additional data - Table name CEBAN and Field Name is WERKS.
            3) Purchaisng Group
                 Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                Tab - Basic data - Data Type - char, Number of chars eg. 3
                Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
Step 2:
Define class in transaction code CL02
Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
Tab - Basic data - Enter description as "PR_Release-Proc",
status- Released, Same classification - check the push button - Warning Message
Tab- CHAR Enter above created 3 characteristics
1.Release_PR_total_value
2.Release_PR_plant
3.Release_PR_PurchasingGroup
step3:
Menu path is
SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
here define
1.Release Groups
Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
Here assign class "PR_Release_proc" against release code "01"
check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
2.Release codes
Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
PRs are released by users in transaction code ME54N.
Eg
Type of user            - Level -             Release code
PR creator - clerk or Business user -
Approver    - Supervisor                 -   R1
Approver -   Project Lead              -   R2
Approver   - Asst. Manager             - R3
Approver   - HOD/General Manager - R4
Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
For detailed info please refer
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
3. Release Indicator:
Release indicators show the release status of a Purchase Requisition.
For detailed info please refer SAP Help official site
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
4.Release Pre requisites:
These define the order in which individuals or departments release the PR in sequence.
3.Release strategies
Create a new release startegy eg ."A1" or "U1" , write its description PR release for value >1 lakh
Now select release codes according to the Chart of Authority set by your client.
Eg.
Release startegy " A1 - PR release for value >1 lakh"
R1 - Supervisor
R2- Project Lead
R3- Asst. Manager
R4- General Manager
Now click on" Release Prerequisites "push button and check all the boxes in ascending order.Save the document
click on "Release statuses" push button, check release statuses then click on "Continue" push button.
In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
Classification data for example
1. Value - > 100000
2. Plant - 1000,2000,3000 etc
3. Purchasing groups - 101,102,103 etc
By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
In this way you can configure all the required Release startegies.
Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
Tcode - ME54N - For Individual Release
Tcode - ME55 - For Collective Release
For detailed info please visit SAP HELP website
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Regards,
Indranil

Purchase Requisition Overall release amount

Hi,
I am working on PR overall release amount workflow.
How can i find the overall release amount in the tables of PR while entering into the workflow.
Depending on this amount we need to further proceed for approval process.
Regards,
Gopinath Addepalli.

Dear Marco Antonio,
I have never faced your issue, but have an idea of what you can do.
Activate Enhancement M06B0005 EXIT_SAPLEBND_004
Then in the program zxm06u31 put the following code line:
e_ceban = i_ceban.
and also a breakpoint so that it stops automatically upon PR verification or saving.
Activate and then create a PR with the problem you are facing. On saving the program will stop in your breakpoint.
Look at structure i_ceban there you will find the values that your release strategy is getting from the document and with which it will try to determine the strategy based on your classification.
I the standar logic is not what you want maybe you can put some logic of your own based on account assignments in structure C_EBKN.
Well, tell me what happens
Best Regards,
Sebastián Ligueros

Overall Requisition Workflow

Hiya mates,
How to execute an approval or rejection release via ME54N through workflow for BUS2105: Overall Release of Requisition? Then follow by trigger the rejection action for workflow to provide a list of users to be chosen for email notification?
Cheers..

Hi Ronen,
How to execute overall pr rejection or release via ME54N? I tried those tasks actvt for overall pr rejection and follow by build up user decision to select restricted users only for send email notification when pr is rejected. Basically, the send email notification works fine as email notification sent out when pr is rejected. However the pr rejection seems didn't capture the rejection. When execute the workflow via "Rejection Execution", the workflow tasks seems brought me into ME22 or ME23 instead of ME54N as there is no rejection or release button after clicked "change". The workflow will automatically generated task/message - "PR rejection with Num###" and then let requisitioner to choose restricted users for email notification. However when go into ME55 to verify the workflow rejected pr, it still appear in ME55 for overall release. This rejected pr suppose should not appears in ME55 after workflow is executed for rejection.
Could you show me how to execute ME54N for overall pr rejection & release? Then the workflow or sap could capture either the "rejection" or "release"? Any methods or objects or steps recommend?
Many Thanks and cheers...

PR Overall release issue

PR release strategy issue comes when Line items in PR added by two different persons, PR Release strategy(overall release) not getting triggered.
Release strategy is working fine if i create PR with only one user id.
Both id's maintained in classification.
Is this sap standard behavior??
Created PR 4201001933 line item 10. using User ID - 20061704
Triggered correct release strategy TD QH.
Added line item 20 using user Id - 345045 --- (release startegy gone)
classification Maintained for TD QH

We have a similar equirement since we have cost center as one of the characteristics in PR overall release strategy.
In our case we agreed with Business that the CC in the first PR line item will decide the release strategy. (Or the first CC of thefirst line item in case of multiple account assignment.) We wrote a small piece of code to achieve this, to enter that CC in ceban-kostl.
If your business requirement permits, you may follow this strategy, where user id of the first line item will derive release strategy.
Regards.
Satish Patankar.

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

Why can we only use 1 release class for overall Release of Purchase Req?

Hi,
After realizing that it would be beneficial to use more than one release class for overall release of Purchase Requisition with classification, in use with release groups for overall release, I now ask if someone knows why SAP has chosen to only allow 1 release class for overall release of Purchase Requisition?
In my scenario I would like Release group US, used for release strategies for US-plant to be able to use 1 release class with a specific set of characteristics.
For example class REL_PREQ_CLASS_OVERALL_VALUE_IN_USD including a characteristic PR_TOTVAL_USD looking at CEBAN-GFWRT. The chosen currency for this characteristic would be USD.
I would then like to allow Release group FR, used for release strategies for FRANCE-plant to use another release class with another set of characteristics.
For example class REL_PREQ_CLASS_OVERALL_VALUE_IN_EUR including a characteristic PR_TOTVAL_EUR looking at CEBAN-GFWRT. The chosen currency for this characteristic would be EUR.
In this way the release strategies for the respective release groups US and FR, could maintain their overall limit values in their respective release strategies in their own currencies.
1. Observe that I do not want to use the same Release class for both release groups for overall release, even though I know that this is currently the only allowed option, as far as I've understood.
2. Observe that I do not want to specify the two characteristics PR_TOTVAL_USD and PR_TOTVAL_EUR for overall value in the same release class, as this would lead to double maintenance for a large number of release strategies. Also consider the maintenance when new countries with new currencies want release strategies.
3. Observe that I only want to use overall release.
What I'm trying to avoid is having to continuously translate local business USD overall value limits to limits in the currency chosen for the overall value characteristic. If this for example is specified in DKK, this would lead to a need to adjust the overall value limits as soon as the exchange rate between USD and DKK changes in the system.
Please consider this simple example:
Local requirement is that USD purchase requisitions should be blocked when the USD value is above 1000 USD. However in my release strategy I would have to maintain a value of >5365 DDK, if DKK is chosen as the currency for overall characteristic.(e.g exchange rate 5,365).
Next month the currency exchange rate in the system between USD and DKK has changed, and therefore I would have to go into CL24N and maintain the value to reflect the new exchange rate between USD and DKK. Lets say it has gone up to 5,435. I would now have to maintain a value of > 5435 DKK in my release strategy to correctly reflect the local business requirement of 1000 USD.
So if anyone could please explain why SAP has taken the decision to make the Release class for overall release client specific that would be much appreciated and awarded accordingly. Also if you have any suggestion on how I could obtain the above scenario on maintaning overall value limits in different currencies than that would be awarded to.
BR Jakob F. Skott

You can give feed back to Apple from the iTunes drop-down menu in the iTunes menu bar..
You can also contact the iTS Customer Service from the links on this page - http://www.apple.com/support/itunes/store/
MJ

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

PR overall release workflow

Similar Messages

Maybe you are looking for