BUS2012 Release Step Event triggered twice

Hi Guys,
When a PO is created the BO BUS2012 Release Step event is triggered twice.
I am using a condition for my workflow based on the release code.
What could be the problem.Kindly Clarify..
Rgds,

Hi,
Actually I think the problem is with my Start Condition. I have given a start condition(SWB_COND) in my workflow is follows.
Release code = A1 or Release code = A3.
When i check the event log two times event is triggered with an exception and with the following information.
1.Start condition returns 'FALSE' for object [BO,BUS2012,4500000131]
2<b>.Operator 'EQ': The value of the left operand cannot be determined.</b>
I think the second one is the problem. Any idea how to avoid it..
Rgds,

Similar Messages

Subtype event not triggering and supertype event triggers twice!!!!!!

Hi,
We have created a subtype for object bus2030 and also an event created for that. My workflow should trigger whenever an inquiry is created.
I've maintained this as triggering event in SWDD and done type linkage is SWE2 and everything looks fine.
When i simulate or create event the WF is triggered but when create inquiry in VA11 WF does not triggers.
I've checked SWEL for event trace but no event is triggered at all... Am i missing something... I've done almost everything that i used to do...
Even synchronized buffer!!! nothing paid me a solution...
Infact the same was working with 3.1i system but after migration to ECC6 we had to create new WF template for the same Process.
Now I also see that the supertype bus2030-created event is triggered twice but, obviously no receiver type exists. But the zbus2030 event is not being triggered at all!!!!
Kindly help me understanding my mistake...
Regards,
PB

Hope you have already set the deletegation in SWO6.
Now, event dont get triggered automatically, jus because they are defined in object. They have to be explicitly published in thesystem.
Check for a suitable user exit in your transaction, which makes use of function module to create the event, from that you know how to proceed.
If you dont find user exit, try other triggering techniques such as change documents, logistics, BTEs... etc.
regards,
Sandeep Josyula

Creation of a purchase order triggers the event ReleaseStepCreated twice

Hello,
I tried to use the standard workflow for the approval of a purchase order and noticed that i am receiving twice the same mail.
As you know, the workflow is triggered by the event ReleaseStepCreated. After I created a purchase order, i saw that the event is triggered twice, so that is why i am receiving two emails.
I believe this is wrong, Has anyone noticed this problem?
Thanks,
Efren

Hello,
The event linkage contains only one record, which is the one that connects my workflow to the event. This is not the cause.
What do you mean by delegations? Are you talking about delegated objects? If yes, i do not have any.
I looked in transaction SWEC(events for changed documents), and i guess i found the cause. There is a record with change doc. object EINKBELEG with the event ReleaseStepCreated of the object BUS2012. It has the trigger event "On Create", and in the Function Module, in Event Container it has function FRE_ORD_EVENT_PO_DB.
I removed this record and now the event RELEASESTEPCREATED is triggered only once, so i think it is ok.
I guess this record existed before there. Do you have that record with the function module FRE_ORD_EVENT_PO_DB?Or do you know what is the use of this function?

Relese of PP operation - Triggered twice? (AFVC_PM-RELEASED)

Hi
When we release an operation of an PP-order the Event AFVC_PM-RELEASED is triggered twice.
This is a problem for us since we have a linked interface when the status is set to RELEASED.
We only want the status to be changed once - otherwise we get two calls to our interface wich causes error.
Do you know why that EVENT pop up twice?
Best reg
Henrik

Check the linkage table. Did you link this event twice? If you have a subtype, check if the event is linked for the super- and sub-type.

Item close event is triggering twice for Advanced Data Grid

HI, I'm using AdvancedDataGrid for my project. My issue is when click on item close, the item close event is triggering twice. Why it is triggering twice? Thank you...

Hi,
Would you mind reposting your question over on the Flex forums? You'll most likely have better luck over there.
Thanks,
Chris

BOR BUS2012 released not working

hi people
I have a problem in a workflow. The initiating event of the workflow is when a PO is released. I've tried the BOR BUS2012 released but the workflow does not start when I release the PO. The workflow is active and should work. Can anyone help me?
best regards

Thank you very much for replying.
Now it is working.
Previously BUS2012 is triggering twice. To stop this I deleted change document from SWEC. After that it is working fine. I donu2019t what happened suddenly it is not triggering for single time also. Now again I created a change document. Now it is triggering. Why it is behaving like this I unable to understand.
But my problem is solved.

EVENTITEM is triggering twice!!!

Hi,
I needs to send mail if PR is released or unreleased or reject or cancel rejection to the creator.
So I created a workflow which contains event of BUS2105 in START EVENT - RELEASESTEPCREATED, RELEASED, REJECTION_STOP, REJECTION_START.
So if anything happen in ME54N a mail should get triggered.
I used FORK which contains 4 wait event because only 1 event will be triggered for 1 PR. And accordingly formatted mail will be send.
If PR is released for the first time mail is triggered successfully. If that same PR is unreleased and then again released for same release code mail is triggered twice and keeps triggering twice if again it is unreleased and then released.
In SWEL below messages is seen twice for RELEASE event.
BUS2105 RELEASED 20.07.2011 19:23:58 EVENTITEM SWW_EI_EVENT_RECEIVE_IBF
so same mail is triggered twice.
This this is same for all remaining events.
When I show in SWE3 and in OBJECT DATA, their exist a entry of PR(object key) for BUS2105 release event. If I delete that entry then again for the first time it will trigger 1 mail but for next release of same PR will trigger mail twice.
The whole problem is for all events mentioned in FORK.
Thanks in advance.

Hi,
You are correct.
I removed worflow configuration from SPRO for release code. So REJECTION_STOP, REJECTION_START wait event are working properly means only 1 mail is triggered and below msg is shown only once. But as soon as I reconfigure release code in SPRO mail start triggering twice means in SWEL i can see below msg. 2 times :-
message in SWEL --> BUS2105 RELEASED 20.07.2011 19:23:58 EVENTITEM SWW_EI_EVENT_RECEIVE_IBF
As you said their might be some configuration problem of release code, So I developed a separate workflow which has only 1 event RELEASE and no WAIT EVENT is used, then it works perfectly means only 1 mail is triggering.
So I also think that the problem is of WAIT EVENT(receiver type EVENTITEM) and RELEASE CODE configuration.
I think, I need to control the receiver type --> EVENTITEM triggering for release code.
I don't know how to solve this issue. Please help to solve the issue...
Thanks & Regards,
Mihir

PR triggering twice

Dear All,
Am creating a workflow for Purchase requisition. When the workflow is initiated the first level approving authority is getting 2 work items. When I trigger the event from SAP Menu u2013Tools u2013Business Workflowu2014Developmentu2014Utilitiesu2014Create Event (Business object-BUS2105, Event- RELEASESTEPCREATED ) then it is generating only one work item, but when I try through transactions ME51 and ME51N it is triggering twice. If you can share your knowledge about this issue it will be grateful for me.
Regards,
Surya

Hello Athadu,
line-item approval is done with business object type BUS2009. So BUS2105 is triggered on header level and -- usually -- only once after creating, and then after each release code has been set.
I know of two possibilities, why you have two events coming up:
- Check transaction SWEC for an entry BANF BO BUS2105 (on create) with event = RELEASESTEPCREATED and delete this entry.
- You have more than one release code available and open at the same time. Check in the started workflow the container element "ReleaseCode". To avoid or configure this, use the customizing "prerequesites" in the section of the release strategy.
Best regards,
Florin
Edited by: Florin Wach on Jun 25, 2008 3:49 PM

Worflow triggering twice

Hi guys,
my workflow is triggering twice.
why
how can i resolve this issue.
please give me suggestion.
Thanks
Sankar

are these events triggered simultaneously?
activate event trave and do a step by step change on the master data. This way you can find out if the event is triggering twice.
Form your post I do gather that the event on FREBUS2012 is caused by some kind of custom programming (badi, or ecit or something like that)
You can also try to simulate the event (I'm not on SAP at the moment so you have to search for this transaction yourself) if the event has only 1 receiver, you know that the problem isn't to be found in the event linkages.
Kind regards, Rob Dielemans

Chapter 6 Event-triggered campaigns

From William...
Chapter 6 Event-triggered campaigns is an exercise in the CCMO training where we send an email to Recipients who recently converted from Prospects to Clients, detected by a change in their status.
Possibly the simplest way of accomplishing this is with the Incremental Query activity. However, to prevent pulling Recipients who are Clients already at the start of the campaign, the Incremental Query needs to be run twice, the first time to set the history.
According to the documentation
https://support.neolane.net/doc/AC6.1/en/WKF_Repository_of_activities_Targeting_activities .html#Incremental_query
"The population already targeted is stored in the memory by workflow instance and by activity... two tasks [executions of a workflow step] based on the same Incremental Query for the same workflow instance will use the same log."
In other words, two runs of an Incremental Query activity in a workflow share the same history log. For the first run of the Incremental Query activity, uncheck the 'Plan execution' option and transition into an End activity. This will set the history log to current Clients. For the 2nd run of the Incremental Query activity, check the 'Plan execution' option and transition into the Delivery.
The 2nd (and subsequent) runs of the Incremental Query activity will pick up only new conversions from Prospect to Client.

Hi Oguz,
If you're trying to communicate between two loops, triggering the second from the first, then you should look at producer consumer type structures in File»New... under From Template.
Stephen Meserve
National Instruments

How to disable the "turn page" event triggered by the scroll/swipe function?

The problem is as follows.
The default behaviour of Acrobat Reader (both stand alone and browser plug-in) is to allow scrolling/swiping with the mouse wheel/trackpad. This is useful when the pdf's page length is greater than the screen's own length, because you can read the pdf with no need to distract your attention from the text to the scrollbar button. However, the same scroll/swipe function turns into a usability problem when the pdf is embedded in a html page and the pdf's page length is smaller than the browser's length. In this case, the scroll/swipe turns the page, distracting your attention from the text to the unintended behaviour of the browser. What happens is that you are so used to scrolling/swiping that you did it unintentionally in the pdf's caption area. You really did not want to turn pages in the pdf. Furthermore, if the pdf takes the whole html page, being a website, the scroll/swipe function flips the website pages in ways that neither the reader nor the writer had ever intended. Hence the question. How to disable, in this case, the "turn page" event triggered by the scroll/swipe function? A JavaScript should do, but the SDK documents did not help so far...
Message was edited by: 41457173
Message was edited by: 41457173

... or release a patch for the API,
... or suggest an alternative route to achieve the intended result.

Bug in scrollbar event triggering?

In LabVIEW 8.6, I am trying to fire an event when I finish moving the scrollbar of an array indicator. I use the "mouse up" event to avoid having the event structure fire constantly the entire time I am moving the scrollbar. However, there seems to be a bug (?) in the event detection. It works fine as long as I have the mouse on top of the scrollbar when I release it. However, Win XP allows you to continue to move the scrollbar even if the mouse is off to the left or right of the bar (when you click on the scrollbar it "locks" the focus onto it). However, LabVIEW does not seem to realize this and if I have the mouse slightly off to the right of the scrollbar when I release, the event doesnt fire. LV seems to base the event off of whether the mouse is on top of the pixels of the indicator rather than whether I still have control of the scrollbar.

Technically it is not a bug. There is no event triggered because when you do the Mouse Up, you are no longer on the scrollbar. Unfortunately, the behavior in Windows that allows you to continue to move the scrollbar even when you aren't on it is conflicting with the desire to detect when you let go of the scroll bar.
There was a recent thread discussingthis very issue and a way to get the behavior you are looking for.
Re: Handle mouse up on numeric slider control - even when mouse leaves control

Perform check after release step of purchasing requisition

Hi,
does anybody have a suggestion where to place best some logic which needs to be performed after a release step is performed successfully.
background: we use different types of Purchase requisitions, while each one is assigned to a static release strategy. I like to change it in more dynamic way by adding certain logic after a release step is performed.
example: if preceeding release step was 10 and purchase requisition is of type x then check purchase value and account assignment in order to process the current stepo automatically.
Currently the logic runs during a nightly job, but I would like to add it immediately after a release has been performed. I would imagin something like user exit, BusinessAddIn, or an event which I can use assign the job.
Can anybody suggest something?
Thanks in advance
Best regards
Torsten
Edited by: Torsten Hübsch on Apr 29, 2011 10:36 PM

Hi,
Enhancement M06B0005 is relevant for PR in case of overall release
Check on trx SMOD :
Enhancement        M06B0005
Short text         Changes to comm. structure for overall release of requisistion
--> Function module                Short Text
EXIT_SAPLEBND_004              Changes to Communication Structure for Over.
Enhancement        M06B0002 is for item-release
Short text         Changes to comm. structure for purchase requisition release
-->
Function module
EXIT_SAPLEBND_001
BR
Nadia Orlandi

Additional approval/release step req in WF20000397 (Rel. prc. blocked inv)

Hi Workflow Experts,
I am curretnly using SAP standard WF 20000397 for the release of (price) blocked invoices. The concept behind this wf is the following: Starting event is IncomingInvoice.blockedPrice (BOR is BUS2081). The system then determines the purchasing group entered in the purchase order an sends the workitem to the assigned users of the respective purchasing group. The receivers can than clarify the blocking reason and either mark invoice as not clarifiable or release the invoice. The WF ends then.
Problem/requirement: Due to compliance the puchasing group should not be able to release a vendor invoice for which they were the responsible purchasers. However, those guys are the one with the most knowledge about the purchase and therefore best capable of clarifying differences with the vendor.
The idea now would be to let them clarify things and do a first "release" and add another final release step after this task that is done by some superior. However, I have no idea how to solve this problem.
Thx in advance for any help. BG. Jo

Hello,
You can put some condition in workflow which will check if approver was involved in purchasing. In case yes then go for 2 level approval - 1st level by purchaser and 2nd level by superior. In case no then complete worklfow after 1st level of approval only.
Hope this helps.

Workflow Triggering twice when executing transaction cj21n

Hi Experts,
when i am executing transaction cj21n my workflow is triggering twice but earlier it was working fine ..
please provide your input on the same
Thanks
Deepanker Dwivedi

Hi,
The 'event' which mapped to workflow triggered twice or another event may added to the workflow
1) Did you give additional event for the workflow in the Basic Data -> Start events, if yes remove that event and test it.
2) If 'No', In the SPRO configurations some settings might have changed, Check with your Function Consultant ask any changes they done in the SPRO settings related to the T.code cj21n.
Regards,
Surjith

BUS2012 Release Step Event triggered twice

Similar Messages

Maybe you are looking for