on 03-09-2009 1:13 PM
Hi Friends,
I am working on a issue, where there is a SD workflow "Approval of dunning level". This work flow is having configuration as Triggering Event "BO >BSEG>CHANGED"
My issues related this is,
1 - When I check VF03 and check workflow overview at both Header as well item level.. It's giving msg that "There are no workflow which has already worked with this object".
2 - But when i check in SWWWIHEAD then I got some work item related to the document number.
and found that a number of workitem of decision step gone to the approver.
3- And when I have checked the change history in VF03 then it is showing nothing is changed in DOC.
Then without changing the DOC how it's triggering?
So now I am not getting that why multiple notifications of WI are going and how should I proceed on this.
Regards
Dev
Is VF03 the Billing Document? If so, isn't that an SD document, which as a Business Object is not BSEG. I may be mistaken.
However, if I'm not, that's why you're getting the message "No ... for this object".
Go to FB09 for and check the Workflow Overview there, and while you're there check for document changes. It may lead to what is causing the change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thomas,
Thanks for your inputs,
I will again tell you whole scenario,
There is a dunning work flow, which is configured for BO BSEG-->CHANGED as event.
when I have checked the document number in FB03 and navigate to wf overview then I have got that work flow has been triggered many times for the same instance key in some difference of time.
then I have checked the changes if any in the document from FB03 transaction but it's showing no changes.
So here i am confused that from where this event has been triggered?
I have also checked swe2 entries
there are three entries made against BSEG business object.
BO <--> Event <
> Receiver FM
BSEG---CHANGED
BSEG---CHANGED
FM
BSEG---CREATED -
FM
I dont have any idea what the 1st entry is for ? Here is this SUBSCRIBE making any difference ?
So that's the whole situation.
Regards
Dev
Hi,
From the details you have provided, i understand that there are two workflows attached with the BO BSEG and event changed. So this means that both the workflows will be triggered when CHANGED event occurs.
Check if the status of document changes everytime during approval process. If it changes, check the Change doc. object. You can use start conditions in workflow or Field Restrictions in change doc. object.
Regards,
Raj
Hello,
Are you sure you're comparing the correct full key value in all cases here?
Check SWEL to see which keys are being used with the event.
regards
Rick Bakker
Hanabi Technology
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Actually in basic data it's configured for BSEG->CHANGED event the discription of event in BO is "Object subject to release changed". As event log in not switched on in Production so i can not see that event is triggered.
But here my doubt are
1st what the event discription singnify
2nd - This workflow is related to dunning in FI, so what all can be the sources for multiple triggering of WF.
Regards
Dev
Hi Dev,
> 2nd - This workflow is related to dunning in FI, so what all can be the sources for multiple triggering of > WF.
Since your WF is attached with an Event, it will Trigger only when the Event is allowing it to trigger.
That Means if the Event is getting triggered, its Triggering the WF.
> 1st what the event discription singnify
Event Description signifies what exactly is the purpose of Event.
Let me know whether I have cleared your Doubts.
Regards,
Kanika
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.