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.

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.

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

  • Workflow inbox level  given  message Error in event receiver .

    hi guys,
    workflow standard  purchase order copy to custom and create to purchase order event will be triggered successfully.but inbox level this errors has come but not display the purchaser order please help to me:
    Error in event receiver
    Error processing following event linkage:
    BUS2012 RELEASESTEPCREATED WS90000015
    Following error occurred:
    SWF_RUN 594
    Thanks&Regards,
    Bikshapathi.

    Hi BP,
    are you using any rule in your WF?
    check if binding is proper,
    check if you passing PO parameters properlty, as ReleaseCode would be a mandatory field in your WF/task container.
    Hope it helps.
    Aditya

  • Want to fire event receiver before workflow is execute while adding File in Document Library.

    Hi,
    I have Event receiver and workflow attached to same Document
    Library.
    Is it possible to fire event receiver before Workflow is
    executed ?
    Regards,
    Milind

    Hi,
    According to your description, my understanding is that you want fire event receiver before workflow is excuted.
    If the workflow for a list is set to auto-start, it will always execute before event receiver by default.
    Here is a similar thread for your reference:
    http://sharepoint.stackexchange.com/questions/3147/execution-order-of-event-receivers-and-workflow-on-a-list
    As a workaround, you can set the workflow start by manually. Then , after executing the event receiver, you can start workflow using code at the end of event receiver.
    Here is a demo for your reference:
    http://zimmergren.net/technical/starting-a-sharepoint-workflow-from-code-event-receiver
    More information about start workflow using C#:
    http://jainnitin2411.wordpress.com/2012/07/06/programmaticallystartsharepointworkflow/
    Best regards,
    Zhengyu Guo
    Zhengyu Guo
    TechNet Community Support

  • Error in event receiver

    Hi Friends, mails from SAP are sent to HR users from WF-BATCH.The users are unaware why the message have been sent.
    The message that is being sent is given below:
    Messages received from: Batch WF-BATCH
    Subject: Error in event receiver
    Body of message:
    Error processing following event linkage:
    KNA1 STATUSCHANGE WORKITEM
    Following error occurred:
    WL 605
    000003807054
    Message text:
    Work item 000003807054 locked by user (enqueue error)
    Event container appended as attachment.
    Event linkage not changed.
    Event stored temporarily.
    Events can be redelivered via event queue
    administration (transaction SWEQADM).
    Kindly help.

    Hi,
    Please refer the link [Workflow System Administrator Role|http://help.sap.com/saphelp_nw70ehp2/helpdata/en/8c/1923ce932b11d2a5ea0060087a79ea/content.htm] - The administrator needs to be assigned with these roles mentioned in this hellp documentation.
    The error message in your case indicates that there is some problem in the "Event Linkage". KNA1 is the Customer Master Table. I guess it is the "STATUSCHAGED" event of Customer Object is having some event linkage problem. You can check the event type linkages in SWETYPV Transaction. Thanks.
    Regards
    Suresh

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

  • 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

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

Maybe you are looking for

  • Building a budget desktop PC for CS5 (under $1,700)

    After reading most of the posts here and elsewhere about building a PC to run Premiere CS5 I decided to take a stab at assembling the components to build my own (keep in mind I have never done this before). Below are the items in my Newegg shopping c

  • Every time I touch my keyboard my phone goes back to the home screen

    It's only when I have to type! This happens with all my apps including the ones like settings mail message ect! Plz help!

  • Nokia N8 SMS outbox message

    I have a SMS message in the outbox that I can't delete, The status says that it will be sent later, It does not help to press the message and keep it pressed Solved! Go to Solution.

  • Robohelp 8 fails to launch

    Robohelp 8.0.0.203 will not launch on my desktop PC: I've tried the shortcut, selecting a project file and clicking "Open with", and opening from the Programs list. Same results: 1 or 2 seconds of churn, then the cursor goes back to a pointer and not

  • N93 RINGTONE ISSUES AND GENERAL SLUGGISH BEHAVIOR!...

    I've been battling with my n93 for about 6 months now and recently got all excited about the release of the 20.0.058 firmware update hoping it would solve most of the phone's catalogue of problems. One of the most annoying problems for me was the fac