Workflow Mail for PO release strategy is in outbox not in agent mailbox

Hi Team,
i wrote a method in ZBUS2012(copy of buz2012), to send email, i tested the method and its working and with the task (SWDD-WS90100007) the mail is getting triggered. the mail is moving inbox to outbox in SBWP. but the mail is not going to agent mailbox. Is there any setting is required or we need to extract agent mail-id in any other method. background task is not excuting, is there config is required in SWU3
Thanx in advance
Kesav

Hi,
Go to the T.Code SOST, check your mail is sent.
If found check it and execute it. Now you check the email box.
If working, then inform basis Team to schedule the mail dispatch program.
Regards,
Surjith

Similar Messages

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

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

  • Workflow activation for PO release

    Hi Guru,
    How to activate workflow for Purchase order Release,
    Requirement is like 3rd level is rejecting the purchase order, how to communicate to the 2nd and 1st level with rejection reason.
    Can I have some configuration guide?
    Waiting for your reply.
    Thanks,
    Samir Bhatt

    http://www.sap-img.com/workflow/workflow-of-purchase-requisition-release-strategy.htm
    Use the Above link Else go to saptechnical dot com Website and Click on Business Workflows then Workflow Scenario Configuration Here you will find the Detail Configuration of Workflow with Screenshots.
    Regards,
    Ashok

  • 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

  • Tables for PO Release Strategy

    Hi,
    could you send me the list of tables for "Tables for PO Release Strategy".
    Rgs,
    Priya.

    Hi,
    EKKO - FRGGR  (Release group)
    EKKO - FRGSX  (Release Strategy)
    EKKO -  FRGKE  (Release indicator)
    EKKO  - FRGZU  Release status
    T16FB                          Release Indicator: Purchasing Document
    T16FC                          Release Codes
    T16FD                          Description of Release Codes
    T16FE                          Descriptions of Release Indicators: Purchasing documents.
    T16FG                          Release Groups
    T16FH                          Descriptions of Release Groups
    T16FK                          Release Statuses
    Regards,
    Chandra

  • Workflow variant for payment release

    Hello ,
      I have done the configuration of workflow variant for payment release but still the invoice is not getting blocked when we are paying it .
    Find below the configuration done for it . SPRO-Accounts Receivable and Payable-Business Transactions-Release for payment
    1.t.code  PPoce: Users is  assigned to each position and this was assigned to approval path
    2. Create workflow variant
    3.Assign Company code to workflow variant
    4.Define Release Approval Groups for Release for Payment
    5.Define Release Approval Paths for Release for Payment
    6.Assign Release Approval Paths for Release for Payment
    7.Assign Release Approval Procedure for Release for Payment
    2010-2010-1000-inr-WS10000052-WS00400011
    9.Define Users with Authorization to Payment Release
    11.Define Payment Block Reason for Payment Release
    Then in the vendor master i have inputted the relase group  also .
    But when i make the payment for that vendor , no blocking of invoice is happening nor it is going for approval procedure.
    Please guide me what all other checklist available for executing the Workflow variant for payment release .
    Thanks.

    Thanks Kiran ,
    Now hte invoice is getting blocked automatically and i am getting the error as
    Line item not relevant for payment release
    Message no. F5783
    for which i changed the error message to warning mgs and saved the invoice .
    But while making the payment i was not getting any payment block. I was able to make the payment
    Actually I should get the payment block while I am making the payment and then i should release it through FB13 .
    Please let me know if I am wrong .
    Thanks

  • How to have more than 8 release code for a release strategy

    Hi,
    In standard only 8 level of release is possible for a release strategy.  Our client requires more than 8 levels i.e., more than 8 release codes for a release strategy.  How can we achieve this?
    Pls provide your views/ideas.
    Reards,

    Hello,
    In case you require more than 8 levels in release strategy , write to SAP, maybe they could give a fitting reply.
    By the way , 8 levels of release should be more than enough . Try to incorporate the client business process
    within this.
    Regards
    Anis

  • 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

  • Inconsistency for Previous Release Strategy of PO

    Dear colleagues,
    Is there any standard program to come up with new values and criteriau2019s for new release strategy if pre defined release strategy, with class, is deleted for PO approval.
    Best regards,

    Hello Metin,
    can you please elaborate your question, it is not very clear, as it is not showing the clear picture of your requirement.
    regards,
    Prashant Rathore.

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

  • 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 - Wait for PO release

    Hi ALL,
    My requirement is that, after the PO change by ME22N the WF should Wait for PO release before I can call MIGO for Goods receipt.
    But my WF is directly calling MIGO after the ME22N, even though I have put a Wait for event task in between.
    Object type - BUS2012
    The WAIT event is - RELEASED
    the bibding parameters are &_EVT_OBJECT& from Event to &PURCHASEORDER& in the workflow.
    The wait condition is executing successfully and then MIGO is called, where as I have not yet Released the PO.
    How to make the WF wait for the Release.
    DP

    Hi,
    As per my understanding, is your workflow goes for next step after release of any level ?
    Please check whether the event RELEASED triggers for each level of release.
    Regards,
    JMB

  • User Exit for Requisition Release Strategy

    Hi All,
    Is anyone able to provide any guidance on determining the release strategy of a purchase requisition via a user exit? It has become neccessary to do this due to certain shortcomings of the classes and characteristic functionality.
    I believe it's possible, I just don't know how.
    Thanks.
    Richard

    go SMOD and enter enhancement M06E0004      it is exit LXM06U13

  • Release Group for PR Release Strategy

    Hi ,
    When i am trying to define new "Release Group" AA , with Class "Z_PR" (it has Plant and Item Value as charcteristics ) , I am receiving message "Please Check Release Classes" , Message no. ME492.It doesn't allow me to save this new release group.
    Please also note that other two release Groups are already available.
    Do u know what I am missing  and how can I save my Release group ?
    ALSO as per the LONG text of this prompted message
    "Diagnosis
    Here you can assign release groups to release classes. Only one release class should be used within the release groups for overall release and the release groups without overall release in each case. However, in this instance several release classes have been used."
    What does it mean ?
    Sandeep

    Hi,
    The message has explained the problem.
    You cannot have two classes for the same document release and you are tryng to break this rule by adding another entry (the fact that you have give it a different release group does not make any difference this is still another class for the same document.)
    You should be able to do what you want without the need for a new release group or additional class, after all everyone else that uses SAP is using one class per document.
    Why diod you think that you needed another release group / class?
    Steve B

Maybe you are looking for