Chinaunix首页 | 论坛 | 博客
  • 博客访问: 1317791
  • 博文数量: 932
  • 博客积分: 10
  • 博客等级: 民兵
  • 技术积分: 10208
  • 用 户 组: 普通用户
  • 注册时间: 2011-07-08 12:28
文章分类

全部博文(932)

文章存档

2021年(1)

2020年(134)

2019年(792)

2018年(5)

我的朋友

分类: 架构设计与优化

2020-02-06 15:07:57

how can I know the business scenario about CRM_PRODUCT_I_A_CHANGE_ORGM_EC an

# Question

I would like to know the design about when CRM_PRODUCT_I_A_CHANGE_ORGM_EC will be called.

# Answer

tcode CRMV_EVENT, type CRM_PRODUCT_I_A_CHANGE_ORGM_EC and press F8:

We get result below.

It means whenever the sales area data is created or changed by Organization model determination or manual change by end user, these two FMs will be called by one order framework.

Why CRM_PRODUCT_I_A_CHANGE_ORGM_EC should be registered for organization model change? This could be analyzed from business point of view.

Inside CRM_PRODUCT_I_A_CHANGE_ORGM_EC, you can find attributes from settype CRMM_PR_SALESG are read by the function module in line 102 and then filled in internal buffer.

We know this settype is organization unit dependent settype, which means its value could only be determined by a specific sales organization + distribution channel.

As a result the purpose of registering CRM_PRODUCT_I_A_CHANGE_ORGM_EC on AFTER_CREATE & AFTER_CHANGE event on organization model is: once there is new change on organization model data, the corresponding value for settype CRMM_PR_SALESG must be reread accordingly. With the help of one order framework, here the design pattern "Observer" is achieved: CRM_PRODUCT_I_A_CHANGE_ORGM_EC is one of the many listeners for Organization model change, it subscribes the change via tcode CRMV_EVENT. Whenever Organization model changes, it publishes the change event by function module below. Al listeners will catch up this event and do tasks accordingly. CRM_PRODUCT_I_A_CHANGE_ORGM_EC, as one of the listeners, will fetch latest data based on the new organization model data accordingly.

阅读(409) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~