Workflow for PO release strategy agent not found

Hi all,
I m beginner in the workflow. i want to create a workflow for the PO. release strategy I have done all the settings in the SPRO for the release strategy. I have copied the standard workflow definition WS20000075 also done the binding with object type BUS2012. in the steps 'Release of purchase order' i have mentioned the task TS20000166 i.e. 'Release of purchase order' and also maintain the AC Rule 20000027 i.e. 'Person responsible for PO release' for agents. But still its not getting the agents. the workflow is getting triggered but its not getting the agent. What else setting I need to do to get this done.
Thanks a lot.
Regards.

Very well put Rick. In my case if i simulate this workflow from swdd transaction then it works fine but the same workflow when initiated from ME21N doesn't work and throws same error.
1. I have copied standard workflow and task 166 is throwing error.
"Resolution of rule AC20000027 for task TS20000166: no agent found"
2. I have recreated the step but still the workflow is throwing error.
3. If I execute the rule individually (PFAC_DIS) with a specific PO then the rule works fine. The rule executes the below mentioned exit successfully.
4. I am using exit to determine the agent, the workflow works fine if I don't use the exit. The exit is EXIT_SAPLEBNF_005. I am just pulling the agent from a ztable.
Please advise if you can help as I have not seen anyone answering.
by the way irrespective of the explicit rule update in the workflow the step executes AC20000027 by default.
Any help on above is appreciated.

Similar Messages

Error in event receiver in workflow for PO release strategy

Hi Expert,
I am trying to trigger an email through workflow for PO release. I have setup following
In SWETYPV,I have check marked on Type linkage active and Enable event queue. Status no error.
In PFTC, under Triggering events, Object type BUS2012 is green light
When i create the PO in my SAP inbox, i get notification, however, i getting this error u201CERROR IN EVENT RECEIVER".
Also, how can i send the notification to the user's outlook inbox? Your help will be appreciated.

laurarice wrote:
Hi Expert,
>
> I am trying to trigger an email through workflow for PO release. I have setup following
>
> In SWETYPV,I have check marked on Type linkage active and Enable event queue. Status no error.
> In PFTC, under Triggering events, Object type BUS2012 is green light
> When i create the PO in my SAP inbox, i get notification, however, i getting this error u201CERROR IN EVENT RECEIVER".
> Also, how can i send the notification to the user's outlook inbox? Your help will be appreciated.
I suppose, you are using the workflow WS20000075. Add sending email as an additional task to the same workflow in SWDD.

Workflow for PO Release Strategy

Hi all Workflow experts
We are on ECC 6.0. We have created a 3 level Rel strategy PO and are creating the workflow for this scenario.
The business object we are using is BUS2012 and WF Template is WS20000075.
Each time a PO is created/changed workitem will be sent order we have defined, ie. L1, L2,L3. Each time mail goes to the inbox of the concerned approver.
The problem is when the final approver cancels the release. Under activity 'Release of PO canceled, Task TS20000167 we have assigned the agent as Originator of PO. However at this instant mail does not go into the originator's mailbox.
Approver is cancelling the release in ME28 as it should be, I presume.
Are we missing something here? Is there any additional settings required to trigger the mail to the originator?
I would be happy if the responses from you all does not point to SAP .htm files! since I have already gone through them but it is very hard to understand some simple things!
Thanks in advance.
Regards,
Raghu

All,
I gather that ver 4.7 onwards, SAP has supported the PO rejection/cancellation feature. Since I am working on client's server which is 4.6 c I am not able to implement this. Unfortunately, in the process of doing R&D within the sandbox I seem to have damaged the template WS000075. Now I am getting an error message at the first approval level saying "relase written to buffer".
Can anyone tell me what does this mean? Also is there a way to retrive the original template form the development clients?
Regards,
raghu

Workflow for PR Release Strategy

Hi Expert,
   Is there a way the scenario given below will be possible to achieve..
   All the needed config for the PR release strategy has been define... (release code, group,release strategy,class & characteristic)
Parameter : Doc Type,
                  Amount
                  Acct Assignment Cat ( K,A,C)
                  Cost Center
                   Sales Order
The challenge is that when the given
               Doc Type - NB
               Amount - >0
               Acct Assignment Cat = C
               Cost Center - Empty
               Sales Order - 9999
The PR will be subject for release strategy of Project Manager ( Release Code :PM)
The PR should be sent to the approver (through workflow) which can be found in the partner function maintain in the Sales Order
9999..Partner Function   ZM - Proj Manager. which contain Employee No ( from HR)
She

Hi,
Thanks..but i have completed all the setting in PR release strategy .. -
Am looking for alternative/ ways that i can incorporate the partner function from SO using the sales order
as the link from the PR (charge to sales order) to trigger where the notification will flow through...
This is more i think in the workflow or userexit or abap, but i took the libertly of posting it here perhaps some of the member had this requirement before and how it was accomplished..

New release strategy should not trgger for PO released with old Rel Strategy

Hi All,
Please suggest. Po has been fully released with Release Strtgy V1 XX. Now I m replacing release strategy XX with ZZ. If I change any po which has old rel str XX , system will reset new release strategy as in config changeability indicator 4 maintained.
But requirement is if there is any change or value decreasing in fully released Pos with old strategy it should not retrigger new release strategy. If value Increases then New strategy should retrigger.
Please help me on this.
regards,
Rohit

HI Rohit
A reset of the release strategy only takes place if
       - the changeability of the release indicator is set to '4' in
          case of a purchase requisition and '4' or '6' in case of
          another purchasing document (purchase order, request for
          quotation, contract, scheduling agreement),
       - the document is still subject to the previous release
          strategy,
       - the new TOTAL NET ORDER VALUE is higher than the old one.
The most important thing to consider in to avoid changes to release strategy customizing once the release strategy is used.
The commom steps are:
1- make sure all of the old POs should have been released.
2- don't delete/change the original release strategy. create a new release strategy with copy function, then the old release strategy will not be replaced.
3- if you delete the original release strategy and add a new release strategy which the characteristics in classification is same as old release strategy then the PO (have been approved) will be replaced with the new release strategy.
Kind regards,
Lorraine

Release strategy is not getting Trigerred for Multiple Plants in PO.

Dear gurus,
I have a Release strategy which is working Fine when I create a PO with Same Plant in line items.
But My release strategy is not getting trigerred when I have Different Plants in Line items.
I have Maintained all the Plants in the characteristic Values of Plant.
Why does the RS work for Single Plant & doesn't work for Multiple Plants in the same PO.
Is there any SAP Note applicable to this? Pl Suggest.
Thanks guys
SN

i got your point but i will again say the same thing that for item level field system is not able to block the po if there are multiple line item in RS and that too with different values against same char as system picks only 1 value and it sends that value in RS to cross check wheteher this po needs to be blocked or not .
now in your case system is getting multiple values against 1 field that is plant so now system is not able to send 1 in backend and hence it sends blank value in back end so system dosent blocks the po
even if you use material group or any other item level field system is going to behave that way only that is it will not be blocking the po

PO release strategy is not triggering if Quantity pre.Qty

Standard SAP design will trigger the 'PO release strategy' if Total net order value (GNETW) is more than set. Lets take if PO created with Qty 100 and Price 50 then first time 'PO release strategy' is triggering when you save the PO. Next time when you change Qty less than the previous value like 80 from 100 then 'PO release strategy' is not triggering but if you enter more than previous value as 120 then its triggering. Ofcourse it makes sense but our user wants to trigger if any changes happened to QTY or PRICE. Is there anyway to trigger?
Found user exit - EXIT_SAPLEBND_002 but not sure what needs to be changed. Can one let me know the solution, if you have any.

Hi.
According to note 493900, question 4, release strategy is reset only
for some specific case. Alternatively, please question 5 from this note
release strategy might be redetermined. However in order to determine a
new release strategy the field that is changed in PO must be included
as one of the fields in the strategy. Thus there is no standard way
for resetting/redermining release strategy for a change of e.g. text
on header or item level.
Please also kindly refer to other 2 useful notes for this area:
662993 Resetting an already occurred release
365604 FAQ: Release strategies in purchasing
BR
Nadia Orlandi

Business Workflow for PR Release...

Hi Experts,
Can anybody please tell me how to work with BUSINESS WORKFLOW for PR Release from scratch.
I am new in Workflow and i had tried with myself but not getting exactly.
Please reply me with step-by-step process from scratch to release PR.
thanks in advance..

Where did you get stuck? All the steps needed could be found in the customizing and the customizing documentation explains them. Also make sure you have done the workflow configuration in SWU3.
Regards,
Martin

Retrigger Workflow if PO Release Strategy changes

Hi All
I have configured workflow for PO release.Now through work item if I am deleting a line item of the PO such that PO is capturing new release strategy due to change in PO value then workflow does not gets re-triggered again as per new release strategy.How can I achieve this?
Edited by: satish kumar on Apr 18, 2009 9:13 AM

Hi,
For Creation it working fine right, i.e. Event triggering fine
1) After Changing the PO, save it
2) And tell functional consultant, whether they configure for the settings for PO change in SPRO
Regards,
Surjith

Email functionality for PO Release Strategy:

Email functionality for PO Release Strategy:
>When PO is blocked an email must be sent out to the first approver.
>If there is a second approver there should be sent out an e-mail after the first level is approved and soon.
>When a PO is released by last approver an e-mail must be sent to the creator of the PO
I need develop this demand without workflow.
I found an Exit 'EXIT_SAPMM06E_013' which is triggering when 'ME21N' is executed.
But i'm unable to update the table EKKO before my code is executed.
Here i need Rel. gr(FRGGR),
            Rel Str.(FRGSX),
            Rel Indicator(FRGKE),
            subject to release(FRGRL) AND
            Rel Status(FRGZU) from table EKKO to check whether the PO is Blocked or Released.
Based on the values got from the table EKKO, i need pick email ids from ZTable which stores Email Ids.
I'm able to get the PO no which is currently genereated and i need to pass this PO no. to table EKKO to get the above fields.
But Table EKKO is updating in the database after the execution of my code.
What do i need to do to get table EKKO updated in the database before my code is executed.

Email functionality for PO Release Strategy:
>When PO is blocked an email must be sent out to the first approver.
>If there is a second approver there should be sent out an e-mail after the first level is approved and soon.
>When a PO is released by last approver an e-mail must be sent to the creator of the PO
I need develop this demand without workflow.
I found an Exit 'EXIT_SAPMM06E_013' which is triggering when 'ME21N' is executed.
But i'm unable to update the table EKKO before my code is executed.
Here i need Rel. gr(FRGGR),
            Rel Str.(FRGSX),
            Rel Indicator(FRGKE),
            subject to release(FRGRL) AND
            Rel Status(FRGZU) from table EKKO to check whether the PO is Blocked or Released.
Based on the values got from the table EKKO, i need pick email ids from ZTable which stores Email Ids.
I'm able to get the PO no which is currently genereated and i need to pass this PO no. to table EKKO to get the above fields.
But Table EKKO is updating in the database after the execution of my code.
What do i need to do to get table EKKO updated in the database before my code is executed.

Ad-hoc agent not found ??? :-(

Hi everybody,
I was trying to activate the workflow por PO Approval (1 step):
- Event Linking: WS14000089
- Agent Assignment: TS14007970
I assigned the agents without any problem, but.. when I want to test my config, I receive this error:
"Ad-hoc agent not found "
I have no clue about this =( I dont know if this behavior is due to a configuration or the abap guy modified the standard WF =(
Any idea ?
Thank you !
Diego

Diego,
As Pierre explained, the PO standard WF in SRM assigns agent dynamically in the WF.
You have to define the task as a general task to "allow" the WF to assign the right agent (purchaser's manager in your case).
In fact if you want yto define the approver yourself, use the n-level WF based on BADI for PO.
Regards.
Vadim

Fields suitable for PO release strategy

Hi,
I had worked with the PO release strategy in which a characteristic is created with the fields BSART ( Order type ), WERKS ( Plant ), Value ( GNETW ), EKORG ( Purchasing group )
Other than these fields what are the list of fields over which we can have a control through the release strategy.
Pl expedite.
RD

Hello,
Please check the documentation for the activity 'Edit Characteristic' in the IMG:
[...] Requirements
In communication structure CEKKO you will find all the fields that can be used as characteristics for a release condition (e.g. BSART for the order type and GNETW for the total order value).
Check which fields you wish to use as characteristics for your release strategy. To do so, choose Tools -> ABAP Workbench -> Development -> Dictionary, enter CEKKO in the field Database table, and choose "Display".
Note
If you wish to define a separate release strategy for the various document categories (PO, RFQ, etc.), you must create a characteristic for each relevant document category.
So theoretically one can use any field from CEKKO.
For the workflow, customisation is linked to release strategies and codes, not directly with the classification fields.
Regards,
Michal

Release Strategy is not picking up in the PO.

Hi All
I have defined a Release Strategy for the Purchase Order.
The Characteristics are
PO category
Pur Org
Total Net Order Value
All the lights are green which i check the release strategy.
But the Release Strategy is not picking when PO is created.
Kindly let me know what is the mistake i have dont or i need to make any corrections.
Thanks in advance
Renukaprasad.

Hi Renuka,
im using ECC6, my PO rel strategy dont have PO catergory,
but you can try this:
Maintained PO characteristics:
PO doc type
PO Plant
PO Pur Grp
PO total Value
Once your PO meet this, Rel Strategy triggres.
When you define the Rel Strategy, there is rel indicator Approved and Block, configure based on your requirement.
Hope this helps a little
Regards,
Maia

User exit for triggering release strategy

Hello Experts,
My requirement is when changes are made in purchase order (ME22N) then once again release strategy will have to get trigger.
is the user exits exists for this purpose,if yes, What is it?. I searched alot but not able to find right exits.

Hello ,
I think you can achieve this via configuration .Basically you want the release strategy to get redetermined based on the changes in the item or if the price of these items increase a certain level .if you have the release startegy as changeble in the SPRO ticked it will automatically go for new release strategy if you have the value of release indicator set .This can be done SPRO->MM->Purchase order->Release procedure for purchase order->Define release procedure->Release indicator.
Set the appropriate value .
Remember you need to know what is that it retrigger that release strategy .
The link below deals with similar requirement ....
[http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/retrigger-release-strategy-for-purchase-requisition-with-any-change-1858101]
Thanks
Anjaneya .
Edited by: Anjaneya Bhardwaj on Aug 31, 2011 8:21 AM

Release strategy tab not appearing in purchase order

Hi Experts,
I have customized release strategy for purchase order that is created characteristic value & pur organization , created class ,assigned char to class , define rel grp, rel codes , rel strategy and checked everthing is showing in Green in developent client , then i Transported to testing client , here I have created same char & class , assigned & also i have checked in Cl24 N
Now i when i create Purchase order& save it in testing client , Release strategt tab is not appraring in PO
Please help me in thids regardby your valuable suggestions

Hi,
Please check carefully note 365604 on release strategies in purchasing
which includes some common problems with release strategies.
If the trx CL30N is ok, It could be that the release strategy was not determined due
to missing code in the user exit EXIT_SAPLEBND_002 in the include
MM06EF0S_STRATEGIE_CEKKO.
In this case the code e_cekko = i_cekko should be missing Please
include this line in your user exit and then retest your scenario.
I hope this helps you
BR
Nadia Orlandi

Workflow for PO release strategy agent not found

Similar Messages

Maybe you are looking for