How to find the enhancement/badi/exit where event is triggered?

[Former Member]

Hello Experts,

Event RELEASESTEPCREATED is linked with BO BUS2105 and my workflow.

Whenever PR is created this event is triggered and in turn my workflow gets triggered.

I want to find the place (i.e enhancement / badi / exit), where exactly the workflow is called.

Thanks

- KP

[pokrakam]

/h

Save

Debug

Easy.

[I042439]

Hi Kulprakash

Finding the code where the standard triggers an event (if done by code) is like looking for a pin in a haystack.

Rather than looking for the event trigger (which most probably will be on SAVE and without much checks)..... you should look for ways to solve the main issues you face.

1) If the PR is not created "correctly" -> See if you can check that in a Start conditions of the workflow. If you are using a standard workflow, check if you can create a subtype of your Business Object, do the delegation and create Virtual attribute (example VALID_PR)  which has the coding to check for "correctness" of your PR. Use this Attribute in your workflow start condition (via SWB_COND tcode).

2) For a change in Qty or Price, ask your Functional consultant to configure the release strategy correctly so that the release is reset and retriggered. This will retrigger the event RELEASESTEPCREATED.

Regards,

Modak

[anjan_paul]

Hi,

I think, It is from change dcoument.  Check in SWEC for the Event is there

[Former Member]

Hi Anjan,

Event in not there in change document.

- KP

[anjan_paul]

Hi,

  Check the trace in SE30 or   ST05 , and which are the common Fm used there  at the time of   PR

[Former Member]

Is there any FM which is used to invoke event or workflow.

At which i can put breakpoint or watchpoint.

Any help will be greatly appreciated.

[SandySingh]

Hello

You can put a break point on function module's

CALL FUNCTION 'SWE_EVENT_CREATE_IN_UPD_TASK' and CALL FUNCTION 'SWE_EVENT_CREATE'

SAP_WAPI_CREATE_EVENT

Regards

Sandy

Message was edited by: Sandy !

[Former Member]

It is possible that the event is created by the standard (and not from user-exit or BADI or whatever). I don't know why you want to find the place where the event is getting created. Perhaps it gets triggered unnecessarily? If this is the case, most likely you need to take a look to the PR release configuration, where you can have a control for the event creation.

Kind regards,

Karri

[Former Member]

I want to find so because if PR is not created correctly, and we are changing some value of PR like quantity and saving it. Than workflow should be re-triggered and hence approval process.

But it is not happening.

Whereas for correctly created PR's, when quantity is changed, workflow is re-triggered and hence the approval process.

[Former Member]

Hi Sandy,

I tried keeping breakpoint on the mentioned FMs but it didn't trigger.

- KP

[Former Member]

>I want to find so because if PR is not created correctly

What is wrong with the PR? How is it incorrect?

I think you should give more details about your problem. There might be some easy and logical solution for it. Now you want to find the place where the event gets triggered - but what then if you find it? It could very well be a dead end - you cannot "fix" the standard. Instead you do some small configuration change, or trigger your own event (from SWEC) or whatever, and your problem will be fixed.

Kind regards,

Karri

[SandySingh]

Hello Kulprakash,

You should debug in update task.

Refer link below

Regards

Sandy

[ronen_weisz]

If the release strategy which is in the first approval level  and the changes in the PR do not cause a change in the release strategy (it is still, for example, in the same value range) will not re-trigger the event.

From the application point of view still in the same point (first approver) so there is no need for the change. (check with your MM consultant - maybe there is no need for the change at all)

It is possible to manually create your own event using change documents (SWEC), but you will need to pay attention that there are 2 events (significantlychanged and releasestepcreated) that you will need to trigger - one to close the old workflow and one to create a new one - and their timing.

It might also be possible to reset the strategy from the MM side, causing the needed change in the workflow, but that is again a question to the MM (development team this time).