BUS2009 Event significantlyChanged

Hi,
BUS2009 Event significantlyChanged is triggered in Standard workflow WS00000038 when PR release is cancelled or refused. Because of this workflow takes path "Purchase ReqItem significantlyChanged" and notifications are not sent for cancel and rejection.
Can anyone help me with config that can control triggering of this event.
Thanks.

In the workflow step for Release Requisition, it brings the outcomes from the tasks. In the step you need to deactivate the SIGNIFICANTLYCHANGED outcome. In the outcome tab in the step click on the green button in the Act/Inac. column. That should take out your SIGNIFICANTLY changed outcome from the step and it should go to step REJECTED after you reject the requisition.
in case it still does not go to REJECTED, I also changed the terminating event in the task "Release requisition - TS00007986" itself to REJECTION_START instead of REJECTED and it did the trick for me. Now it goes the rejected route and sends notification in case you reject the line (in my case it is on line by line basis).
I don't think you really need SIGNIFICANTLYCHANGED event, all approvals/rejections get canceled if the req is changed anyway and you start over.
Hope this helps,
Sergiy

Similar Messages

Workflow not executing after PR release of PR through ME54N

Hi,
I have a probolem. I have created a workflow for intimation after PR release through ME54N based on release strategy . i.e. an email will go to different persons after releasing of the PR at different levels . My problem when i am releasing through ME54N   the mail is not going to persons but if i execute the workflow directly giving the PR no in that case the mail is flowing . I have used the business object BUS2009 and i have selected the event 'Release Step Created".
Can any one help me out.
thanks in

Hi,
Try triggering the workflow event by coding (calling the FM to create an event - SWE_EVENT_CREATE) in an enhancement at the time of releasing the PR through ME54N.
Also check the following scenario for reference.
Check the organizational data, the release strategy customizing and the event and instance type linkages :
1. First you must have created in the organizational plan the user names, positions, jobs, etc. that you assign to the release code(s), and must have linked them to the relevant standard tasks with the Task Customizing (transaction OOCU).
2. When you create the release code(s) that you need for your release strategy and assign the code(s) to your release group, you should indicate that the release code(s) is (are) relevant to workflow (transaction OMGQ for purchase requisitions and transaction OMGS for purchase orders -> Release code).
The Workflow indicator is also used to control role resolution.
The Role Resolution with Group, Code and Plant (T16FW) [1] is the standard role resolution.
The Role Resolution via User Exit [9] allows you to define a role resolution via customer exit.
Then you should link the release procedure to workflow if you are not using customer exit and assign a processor ID to the workflow-relevant release code(s) (OMGQ or OMGS -> workflow).
3. For the workflow WS00000038 (Workflow for requisition release) you should have maintained the following events with transaction SWE2 (Change View "Event Type Linkages": Overview) or transaction SWE3 (Change View "Instance Type Linkages": Overview) :
RELEASESTEPCREATED with SWE2.
                    Object type     BUS2009
Event          RELEASESTEPCREATED
Receiver type WS00000038
Receiver FM        SWW_WI_CREATE_VIA_EVENT
Check function
Receiver type FM
Destination
[X] Type linkage active
REJECTED with SWE3.
                    Object type    BUS2009
Event           REJECTED
Receiver type   WORKITEM
Receiver FM        SWW_WI_COMP_EVENT_RECEIVE
Check function      ME_REL_CHECK_EVENT_PARAM
Receiver type FM
Destination
[X] Linkage activated
RELEASED with SWE3.
                    Object type    BUS2009
Event           RELEASED
Receiver type   WORKITEM
Receiver FM        SWW_WI_COMP_EVENT_RECEIVE
Check function      ME_REL_CHECK_EVENT_PARAM
Receiver type FM
Destination
[X] Linkage activated
SIGNIFICANTLYCHANGED with SWE3.
                    Object type     BUS2009
Event          SIGNIFICANTLYCHANGED
Receiver type   WORKITEM
Receiver FM        SWW_WI_COMP_EVENT_RECEIVE
Check function      ME_REL_CHECK_EVENT_PARAM
Receiver type FM
Destination
[X] Linkage activated
Regards,
Harish

Problems with event when changing Purchase Requisition. (BO:BUS2009)

Hi experts,
I have a doubt with this. When i erase a position in the Purchase Requisition (ME52N), the event SIGNIFICANTLYCHANGED of BUS2009 is raised.
When I try to modify the Purchase Requisition not erasign the position but changing the Material group the event is not raised. Can i customize the system to define that changing the Material group is a significantly change for my system? If not, can i raise another event when this happens?
Thanks!!
Artur.

Hi,
Simply create a custom event called CHANGED in the BO.
Create a entry for this event in SWEC tcode. Select the radio button on change.
This should do the job.
Note : This event will be raised for any kind of changes in this purchase requisition.
Regards,
Raj

Start events via change documents (BUS2009)

Hi All,
I'm currently working on ECC 6.0 and need help for starting events via change documents.
I want to restart a workflow whenever a cost centre in the PR is changed. So I have created an entry in SWEC with Change doc. object as BANF and triggering event as On Change.
In the field restriction I have entered EBKN-KOSTL. I want trigger two events SIGNIFICANTLYCHANGED to end previously started workflow and RELEASESTEPCREATED to start the new workflow.
But whenever these events are triggered the new workflow starts with an error status and the old one remains as it is. The error for new workflow seems like there is no binding between triggered event object and started workflow.
Please suggest. m i missing something ?
Thanks,
Shounak

It's the same old bug. I think you have already configured the release strategy which triggers all the necessary events, now when you make entries in SWEC, this also triggers the event and the overlapping takes place resulting in the error you are getting. Either you remove the release strategy or the entries in SWEC. Further make sure you have terminating event "Changed" or "SignificantlyChanged" in the approval task based on your requirement.
For the conditions, you can either control using start conditions or using the release strategy Characteristic FRG_EBAN_KOSTL if you want to stick to release settings.
Regards, IA
Edited by: Imthiaz Ahmed on Jul 29, 2008 10:51 AM

ZBUS2009 .significantlyChanged Workflow Restarts

Hi All,
BUS2009 implementation uses event significantlyChanged.
I would prefer that any change restarts the workflow.
The root of the problem is a price change. We would prefer if the price is changed the WF is restarted rather than having to move between valuation tresholds defined in our release strategy's.
Is this possible to configure? I have checked SPRO and came up empty.
I was able to manipultate WFL security in SRM for BOR BUS2121, is there anything similar in ERP 6.0?
Thank you,
Will
Edited by: Bill Conlon on Dec 10, 2010 7:02 AM

Ha. Sorry Rick, indeed it is an event. I guess we need to find out where the even is raised and change the conditions... meaning changing a standard program probably. That will not be possible. I guess I will need to post in a diffeerent forum.
Cheers,
Will

Event not triggering for SWEC entry (MM_SERVICE) on create

Hi All,
I have been trying to trigger a customised event for BUS2009 based on creation of the Change Object MM_SERVICE. I have created an entry in SWEC as follows:
- Change Doc Object: MM_SERVICE
- Object Cat : BOR
- Object Type: BUS2009
- Event: RELEASEDREQCHANGED
- On Create
(no field conditions)
However, the event does not seem to publish upon an insert of ESUH-SUMLIMIT (Overall Limit on the Purchase Req - a field in Change Object MM_SERVICE), as I am not seeing the event in SWEL. Please note I have also tried to do this with field conditions in SWEC, but to no avail.
Alternatively, I have tried to setting the Change Doc config via SWU_EWCD, however, it comes back with an error message saying "No change document object for business object type BUS2009" - I believe this might have to do with the incompatibility of the key structures between MM_SERVICE and BUS2009. We have written a function module to overcome this problem and placed same in SWEC, which is why the (BUS2009) event is currently publishing for "on change" of MM_SERVICE - is there any way around this?
On the other hand, the event will publish OK if the SWEC entry is amended to "ON CHANGE" (with field conditions) - upon changing the value of ESUH-SUMLIMIT, not insert/create.
Would anyone be able to kindly advise how I can get the event to publish upon "ON CREATE" as well?
Thanks in advance.
~Andy.

Thanks for your prompt response Surjith.
However, I believe the above setup in SWEC is already configured for the purpose of triggering the event. The customised event in BUS2009 (RELEASEDREQCHANGED) is linked to the Change Document Object MM_SERVICE via "on create" in SWEC - it's just that there are no events coming up in SWEL
I have exactly the same config setup for RELEASEDREQCHANGED, MM_SERVICE via "on change" - and this is working perfectly fine (ie. I can see the event in SWEL whenever there is a change in any of the restricted fields of MM_SERVICE).
My understanding is that upon "on create" (in SWEC), it is not necessary to set up field restrictions in order to publish the event. In any case, I have tried to trigger the event both with and without any field restrictions, none of which came up with any event when a field in MM_SERVICE has been inserted. This is the reason why I tried SWU_EWCD instead, however, due to the incompatibility in the key structure between BUS2009 and MM_SERVICE, the transaction did not allow me to complete the setup.
Is there any way around this?
Many thanks.
~ Andy

Issue with BUS2105 events

Hi,
I have Custom workflow and Business Object for BUS2105. It is working fine and generating and email notification for next user to take a decision on the PR. Now, the issue is when a user cancel the one release steps two events are getting triggered (RELEASESTEPCREATED & SIGNIFICANTLYCHANGED). To handle this i have used these two events (RELEASESTEPCREATED & SIGNIFICANTLYCHANGED) in Basic data of the workflow. And I have used the Fork to handle these events 1 to run the normal business logic and other to send email notification to notify the PR is step is cancelled. In this email notify I have used the wait step to wait for the event SIGNIFICANTLYCHANGED. But the workflow is just executing the business process and workflow is completed.
Could you please let me know the how to handle this situation.
Thanks,
Sriram POnna.

Hello,
Define SIGNIFICANTLYCHANGED as a terminating event for your workflow.
regards
Rick Bakker
hanabi technology

WF : Event ReleaseStepCreated not triggered BUS2013/2014

Hi,
We have approval WF for PO(BUS2012),SA(BUS2013) and Contracts(BUS2013). We have the following scenario for a PO.
1. When a PO is changed (Value/new line item) when it's approval is still in process and it is Blocked state event CHANGED is fired.
2. When a PO is changed when it is in Release state, event 'ReleaseStepCreated' is fired along with 'CHANGED'.
Now this is not happening for SA and contracts. I checked the release strategy and found all of them had '9' in the workflow column for Release Code.
Any suggestions what could be missing.
Regards
Manish

Hi,
the event .Reset is not in use anymore (see event definition in transaction SWO1, declaring it as "Not used").
When cancelling a given release(code), a new event .ReleaseStepCreated will be risen, as that particular release codes is open again.
During the release procedure and signifcant changes on the purchase order (or requisition), which is customizable, the system may reset all given release codes at once, which results in new events .ReleaseStepCreated and an event .SignificantlyChanged (to close all previous workflows).
To get an event like .AllReleaseCodesReset or something similar, you'll have to create a new custom event, creating it through change documents that say EKKO-FRGZU_OLD <> space AND EKKO-FRGZU_NEW = space.
However it could be a good idea to switch on the log (as you already did) and see what events the SAP Standard will created in a certain situation.
Best wishes,
Florin

PR WorkFlow Events Clash

Hi Folks,
New to work Flows......
I have Created a PR Work Flow using 'BUS2105 ' and used 'releaseStepCreated' Event. which is working fine. But, main problem is that when the user is changing the PR DOC then changes are reflected in the event 'significantlyChanged''. So, please let me know how to handle the situation of using both the events in the same work flow using the workitems Fork as well as wait for event .
Please do you remember that I'm determining the agent after the fork step, which is not at all executing. However if I remove the fork step and use the work flow either for release event / significantly changed event that is automatically determining the agent through the rule and the whole process is crystal.
thanks in advance for your help ..
Points for sure ...
thanks and Regards,
M krishna Chaitanya

What is the business requirement?
I think you can use the wait for event step in the branches of fork. The fork should have 3 parallel branch and 1 necessary branch. In 1 branch the approval should be there and in the others the wait for event step for 2 events.
You can make use of the Basic Data tab in the Workflow there you have the event tab that you can use.
Thanks
Arghadip

Regarding Purchase Order Release Strategy

Dear SDNers,
I want to create a worfklow for PO release strategy.
For this to take events for BO, I swich on the evnet trace at swels.
After creation of PO, BUS2012 - RELEASESTEPCREATED even triggered.
For release the PO, BUS2012- RELEASESTEPCREATED,RELEASED two events were triggered.
But when I change PO, BUS2011 - CREATED_VIA_SPEC2000_MESSAGE event triggered.
No change event for BUS2012. I checked at SWEC. Radio button On change is selected for BUS2012-CHAGE event
Even though its not triggered. What might be the problem?
Thanks in advance,
Regards,
Amarnath S

Hello Venkat,
Did you checked SWE2 entry. If not, please check if for BUS2012 SIGNIFICANtLYCHANGED event is maintained for your WF template and is active or not.
Also check in SWE3, for event SIGNIFICANtLYCHANGED and object type BUS2012, please check if receiver type is WORKITEM.
Note - Whenevr you changed any PO there will be event related to chnaged document maintained in swec and SWE3.
Rewards will be appreciated.

PO Cancel release problem

Hi, experts:
I am a beginer of SAP workflow, I've got a problem when testing customized PO cancel release workflow.
My workflow is quite simple, just test whether the event 'SIGNIFICANTLYCHANGED' was trigered when cancel PO. I will receive information in my SAP Business workplace.
Here is the configuration of PO release Strategies:
RGroup Rcode Workflow Agent
PO     C1     1     Blank
PO     C2     1     Blank
PO     C3     1     Blank
PO     C4     1     Blank
In my customized workflow template, I use the event 'SIGNIFICANTLYCHANGED' to deal with PO cancel release.
But I find that this event will not be triggered from Level C4 cancel to C3.
Here is my test result:
Cancel        Result
C4->C3       Not triggered
C3->C2       Trigered
C2->C1       Trigered
I can get the result from my Business workplace except cancel PO from C4 to C3.
Does anyone come across with this problem?
Please tell me why and how to handle it, thanks a lot!
Best regards!

Hi,Swaminathan PJ
Appreciate for your reply!
So, shall we change another event or even customize our own event?
My requirement is that send e-mail with PO item detail (*.xls file) to specified users when final release or cancel final release.
Thank you for any good advice.
Best regards!

URGENT: PO release flow doesnt trigger message to approver

Hi,
I have an urgent request for support. I copied the standard workflow WS20000075 to WS9950000013. The message to the first approver is triggered just fine. But upon setting the release, there is no message triggered to the next and last approver. Find below a screenshot of the SWEL log. I get an error message for the event SIGNIFICANTLYCHANGED: No configuration for workflow WS99500013 . In anotger system for another client I just activated the workflow and done. Don't know what causes the problem here since as far as I could see setup is the same in both systems
Any help appreciated

Hi Joris,
First With template WS20000075 , SIGNIFICANTLYCHANGED event has been configured and I think this event will work only for the template WS20000075. In place of copying the template WS20000075 create a new versoin of this and change the template according to your need. SAP allows change in template WS20000075.
Second Please check whether any release stretgy change has been done ?
BR,
Prakash

WF BUS2012 RESET- not triggered (SWEL)

Hi Anirban ,
Could you tell me when the event RESET is triggered by the system
I guess is triggered when the PO is released through ME28.
Is it when you press 'Release' and then 'Cancel Release'?
I could not see this in the event trace in SWEL. What should I do inorder to see it in SWEL?
Entry is already made in SWE3(BUS2012, RESET, WORKITEM, SWW_WI_COMP_EVENT_RECEIVE).
Do I need to maintain any other entry?
I am using the std PO WF 20000075, where the terminating events for the Release step are RELEASED, RESET and SIGNIFICANTLYCHANGED.
Also from sbwp PO workitem which takes you to ME28, will a person be able to reject the PO?(similiar to approving by ME28 RELEASE+SAVE).
I would also like to know about the event SIGNIFICANTLYCHANGED -when triggered and what is it used for in the WF?
Note: The SAP version is 4.6C.
I am able to see the event RELEASED in SWEL and WF works fine when PO is released.
Many Thanks.

Hi,
the event .Reset is not in use anymore (see event definition in transaction SWO1, declaring it as "Not used").
When cancelling a given release(code), a new event .ReleaseStepCreated will be risen, as that particular release codes is open again.
During the release procedure and signifcant changes on the purchase order (or requisition), which is customizable, the system may reset all given release codes at once, which results in new events .ReleaseStepCreated and an event .SignificantlyChanged (to close all previous workflows).
To get an event like .AllReleaseCodesReset or something similar, you'll have to create a new custom event, creating it through change documents that say EKKO-FRGZU_OLD <> space AND EKKO-FRGZU_NEW = space.
However it could be a good idea to switch on the log (as you already did) and see what events the SAP Standard will created in a certain situation.
Best wishes,
Florin

How to create event for BOR BUS2009 Object ?

How to create a new event for BOR BUS2009 Object ?

Hi,
Please create a subtype for BOR BUS2009, say Z_BUS2009 and include your custom characteristic entities like Events, Methods, Key fields etc and finally do delegation. After delegation, all your custom changes reflects in BOR BUS2009.
Regards,
Prasanth

Terminating Event with Decision Step

Hi,
In our purchase requisition approval workflow, I need to have a decision step in which to prompt approver to either approve the req. or reject the requisition. In this decision step, I need for it to have terminating events for "SIGNIFICANTLYCHANGED", "RELEASE", "REJECT" and "RESET".
First, I copy the generic decision task 8267 to my my own custom decision task. Then I added a BUS2009 in the container, releasecode and other needed elements. In this custom decision task, I was able to add these terminating events that has been defined in the BUS2009. I was able to setup binding, except the one binding
Terminating Event ->   Task
&_EVT_OBJECT&      ->   &_WI_OBJECT_ID&
Since the &_EVT_OBJECT& for the terminating event is BUS2009. And the custom decision task &_WI_OBJECT_ID& is DECISION business object. They're incompatable business object. So I replaced that binding with
Terminating Event     -> Task
&_EVT_OBJECT&    ->   &PURCHASE_REQ&
After all the configuration has been setup. I created a new purchase requisition. Upon the RELEASESTEPCREATED event, it create a custom decision workitem in my agent's inbox. When I triggered the "RELEASE" event, it is however not terminating my custom decision workitem. The workitem still sits in the agent's inbox waiting to be execute.
Is it possible to setup terminating events for decision step? Any kind of suggestions or inputs would be greatly appreciated.
Thank you.
Jennifer Tran
System Analyst

I will suggest you to create a fork with 2 parallel branch and 1 necessary branch. Put the approval step in 1 branch and the wait for Release step event in another branch in this way you can suffice your requirment.
Thanks
Arghadip

BUS2009 Event significantlyChanged

Similar Messages

Maybe you are looking for