Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Get click event Screen.

ronaldo_aparecido
Contributor
0 Likes
790

Hi experts.

I have been  working with determination with bopf.

My Determination is called in all modification screen.

I need it be called only when the user click in a nwbc menu option specific.

How can i know what menu is clicked by the user to put in my code?

If i need create a event to menu please send a tutorial.

I have a TM guide but i didnt find how to do it.

For example in sap ecc the abap use sy-ucomm but how to do it in bopf inside a determination?

Thanks.

Hi experts.

I have been  working with determination with bopf.

My Determination is called in all modification screen.

I need it be called only when the user click in a nwbc menu option specific.

How can i know what menu is clicked by the user to put in my code?

If i need create a event to menu please send a tutorial.

I have a TM guide but i didnt find how to do it.

For example in sap ecc the abap use sy-ucomm but how to do it in bopf inside a determination?

Thanks.

2 REPLIES 2
Read only

former_member190794
Active Participant
0 Likes
617

Hello Ronaldo,

"determinations" are intended to be used to handle side effects. They do not offer any parameters that allows consumers to hand over details. If you would like to execute logic immediately as soon as a user clicks on a menu option, an "action" would be more suitable. There are different ways of modeling:

  1. If you have multiple actions however based on the same implementing class, you can inside switch between different implementations by the help of IS_CTX-ACT_KEY importing parameter.
  2. Or of course you can have one single implementing class for each action as this is the standard way of modeling actions.
  3. Finally you might create an action importing parameter to allow the consumer to hand over some kind "function code" that is evaluated inside of your code via IS_PARAMETERS.

If you however have a real side effect and thus you would like to keep the determination, you might need some kind of customizing that can be evaluated in your determination and that is maintained upfront by the consumer.

Best regards

Tilmann

Read only

Former Member
0 Likes
617

For your requirement, create a Custom Action on that Node using BOPF workbench. Put all the logic in the Action class Execute method. After this, go to the Customizing Config of the UI and click the Button. In the properties of the button mention the Name of Action. Tada ! your logic will trigger only when user clicks on the button, else not.