Shulou(Shulou.com)06/01 Report--

In this issue, the editor will bring you about the use of SAP CRM transaction code CRMV_EVENT. The article is rich in content and analyzed and described from a professional point of view. I hope you can get something after reading this article.

How can I know the business scenario of CRM Product change Organization?

# question:

I want to know when to call the design of CRM\ u PRODUCT\ u I\ u A\ u CHANGE\ u ORGM\ u EC.

# reply

T encode the CRMV_ event, type CRM_PRODUCT_I_A_CHANGE_ORGM_EC and press F8:

We get result below.

This means that whenever the sales area data is created or changed by the organization model or manually by the end user, both FMs will be invoked by an order framework.

Why should CRM_PRODUCT_I_A_CHANGE_ORGM_EC be registered as an organizational mode change? This can be analyzed from a business perspective.

Inside CRM_PRODUCT_I_A_CHANGE_ORGM_EC, you can find the attribute in settype CRMM_PR_SALESG, which is read by the functional module on line 102 and then filled in the internal buffer.

We know that this collection type is dependent on the collection type of the organizational unit, which means that its value can only be determined by a specific sales organization + distribution channel.

Therefore, the purpose of registering CRM_PRODUCT_I_a_CHANGE_ORGM_EC on the "after created and changed" events on the organizational model is that once new changes occur to the organizational model data, the corresponding values of the settype CRMM_PR_SALESG must be reread accordingly. With the help of an order framework, the design pattern "observer" is implemented here: CRM_PRODUCT_I_A_CHANGE_ORGM_EC is one of many listeners that organize model changes, subscribing to changes through tcode CRMV_ events. Whenever the organizational model changes, it publishes change events according to the following functional modules. All listeners will track this event and perform the task accordingly. As one of the listeners, CRM_PRODUCT_I_A_CHANGE_ORGM_EC will get the latest data according to the new organization model data.

We know that this collection type is dependent on the collection type of the organizational unit, which means that its value can only be determined by a specific sales organization + distribution channel.

Therefore, the purpose of registering CRM_PRODUCT_I_a_CHANGE_ORGM_EC on the "after created and changed" events on the organizational model is that once new changes occur to the organizational model data, the corresponding values of the settype CRMM_PR_SALESG must be reread accordingly. With the help of an order framework, the design pattern "observer" is implemented here: CRM_PRODUCT_I_A_CHANGE_ORGM_EC is one of many listeners that organize model changes, subscribing to changes through tcode CRMV_ events. Whenever the organizational model changes, it publishes change events according to the following functional modules. All listeners will track this event and perform the task accordingly. As one of the listeners, CRM_PRODUCT_I_A_CHANGE_ORGM_EC will get the latest data according to the new organization model data.

The above is the use of the SAP CRM transaction code CRMV_EVENT shared by the editor. If you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

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.