cancel
Showing results for 
Search instead for 
Did you mean: 

How are standard BOR events triggered?

Former Member
0 Kudos

Hello Gurus,

I am trying to identity how are standard BOR events triggered in SAP.


For example. BUS2034 has an event called 'CHANGED'. It triggers when i do changes to the sales document.

I would like to know, where are the settings for this event trigger maintained.

I checked 'SWEC' and did not find anythign relevant. For what all changes and conditions are this events set to trigger?

Where can I get this info from?

Thanks in advance

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

The thing is that you don't necessarily see it anywhere (other than in the code). Basically somewhere deep in the standard code there is a code that triggers the event. If you know your ABAP and can do some debugging you can find the code.

Sometimes you can have an effect whether the standard events are raised or not. SAP gives you an options for this. In these cases, you can normally configure it somewhere in the IMG. For example, if I remember correctly there is a setting in IMG for parked documents, and when you set the on, the standard event FIPP.PARKED (might remember the name of the event wrong) gets triggered.

Do you actually have some problem with the event(s), or are you just curious?

Regards,

Karri

Former Member
0 Kudos

Thanks for your helpful reply.

My requirement is that I want to trigger a workflow for standard CHANGED event, but want to exclude changes on 2 fields.

     I know i can create a subtype for the BOR and create events which trigger only for selected fields. Is there another way, where it should trigger for all changes except few ?

Any help is greatly appreciated

former_member185167
Active Contributor
0 Kudos

Hello,

If this is for starting a workflow then you could add a start condition to the workflow instead of trying to control the event.

regards

Rick Bakker

Former Member
0 Kudos

Hmmm, Rick's answer is basically correct, the start condition(s) are many times a best way to go. But in this case I am not sure what is your actual requirement? You want to start your workflow when the document is changed, but you want to exclude few fields (if they have been changed, then do not start the workflow)? If this is the case, you may not be able to use the start conditions, because you cannot compare the old and new values of the fields, right?

If you really want to use the standard event, you might need to add some kind of check (background step) to the beginning of the workflow, which checks the changes from change documents, and end the workflow immediately when needed. If I were you, I would not probably choose this route. Perhaps I would just check if there was some useful BADI, user exit or whatever (many times there is), in which you can compare the old and new values, and then create a CUSTOM event whenever needed. Another option could be to use SWEC, but then you would again need a new event for your object. (Takes 10 minutes if you know what you are doing.)

Kind regards,

Karri

former_member186746
Active Contributor
0 Kudos

Hi,

When you want to control wether a workflow is triggered or not you rarely try to influence the event triggering.

Instead you influence the event-->workflow part.

There are conditions SWB_COND where you can control this. What I ususally do is copy the BO add some extra (virtual) attributes delegate it and then use these attributes for controlling the workflow triggering.

In some cases a check function module is the way to go swe2 event-->linkage double click and type in your FM.

If in the end you really really want to influence the event triggering you can always add a check function module on the event with transaction SWEINST

Kind regards, Rob Dielemans

Answers (1)

Answers (1)

former_member185167
Active Contributor
0 Kudos

Hello,

Turn on the event log and check the details in SWEL, it might give you a clue.

You could also try a where-used on fm SWE_EVENT_CREATE or (less likely) SAP_WAPI_CREATE_EVENT.

Strange that it's not in SWEC.

regards

Rick Bakker