Shulou(Shulou.com)05/31 Report--

This article mainly introduces "how to understand the on_new_focus of SAP CRM". In the daily operation, I believe many people have doubts about how to understand the on_new_focus of SAP CRM. The editor consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful to answer the doubts of "how to understand the on_new_focus of SAP CRM"! Next, please follow the editor to study!

# question

While I was doing the exercise at 16:00 (eheroine f in step 3), I found a description like this:

Double click on method CONNECT_NODES.Make Value node 'Competitors'

Dependent from BTAdminH.

METHOD connect_nodes.

DATA: coll_wrapper TYPE REF TO cl_bsp_wd_collection_wrapper.

Coll_wrapper = btadminh- > get_collection_wrapper ().

SET HANDLER me- > competitors- > on_new_focus FOR coll_wrapper ACTIVATION

Iv_activate.

ENDMETHOD.

I found that this so-called dependent relationship didn't have any actual effect when I was in debug. In theory, handler is set to on_new_focus that it should be called through raise event, but it is finally called by calling the method name directly. How do you understand it? And is there any special application scenario for the so-called dependent here?

# answer

Two field on the UI are put into the same header view, such as product ID and product description (the same level), but the field in the Genil mode they bind is not the same level, but has a father-son relationship.

Connect_nodes is needed in this case. The goal is to automatically refresh the child node when the parent node changes, ensuring that the value of the two field displayed on the ui is correct.

In a word, if the field of the same level on the UI comes from different UI component context node, and there is a father-son relationship between the node in the Genil mode bound to these context node, then all the child context node in the UI component context node should implement on_new_focus.

This is a typical example:

Your question, I guess you are directly call event handler in this example, rather than using raise event to trigger it in the code, right?

You can set a breakpoint in the connect_nodes and create_produom methods. When you create a new product on ui, the latter will trigger first, and the former has not been executed yet, so the event of new focus has not been register yet.

And the latter triggers exactly where manual call event handler is in this code:

Why add 21 lines? In fact, this involves the difference between model node and value node. In product creation scenario, we expect that after user does not have any errors in typing on ui, we will actually walk through four level, and finally create a product in DB. So before the ui input passes through the validation, all the ui inputs are stored in the value node, and then when the ui input passes through the validation, it is converted from value node to model node.

2743 register 2818 of new focus events

Here 2818 threw the event of new focus.

2743 when receiving an event, handle:

What will be the problem if you comment out the 22nd 25 of your highlight? I skipped this line in debugger in the case of product, and then executed it again, which seemed fine.

At this point, the study of "how to understand the on_new_focus of SAP CRM" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.