Use the naming convention CRM*CHANGE_OW to search in SE37 and there are totally 92 function modules found in my system.
Still use the same scenario ( change Closing Date in Opportunity header ) to research how this CHANGE_OW function works:
Use the following report to trigger the corresponding CHANGE_OW function module for Opportunity header, CRM_OPPORT_H_CHANGE_OW.
Execute the report under transaction code SAT and you can easily find this function module consists of five major steps:
(1) CRM_OPPORT_H_READ_OB
The logic is explained in blog Buffer logic in One Order header extension Read.
The input for this object buffer read function module only contains opportunity guid and latest closing date specified by consumer:
The data read from CRM_OPPORT_H_READ_OB:
(2) CRM_OPPORT_H_FILL_OW
This function module fills the latest order data specified by consumer into object work area. Details could be found from this blog: Logic of FILL_OW function module in One Order.
(3) CRM_OPPORT_H_CHECK_OW
Please kindly notice that there are also check logic performed in function module CRM_OPPORT_H_FILL_OW, Let’s recall what kinds of checks are done there:
a. CRM_ORDER_GENERAL_CHECKS_FC
This check could be switched off by function module CRM_ORDER_SET_ACTIVE_OW.
A customer exit if_ex_crm_order_fieldcheck and a new BAdI definition crm_order_fieldcheck_new is allowed for customer to implement their own check logic and called within this check function module.
b. CRM_FIELDCHECK_CALL
This FM will call dedicated check function module for a given field registered in system table CRMC_FIELDCHECK:
And back to CRM_OPPORT_H_CHECK_OW in this blog, the consistency of each field in Opportunity header are checked there.
(4) CRM_OPPORT_H_PUT_OB
Once the object work area passes validation successfully, it will be put to Opportunity header object buffer via function module CRM_OPPORT_H_PUT_OB.
(5) CRM_OPPORT_H_PUBLISH_OW
This function module raises event via generic function module CRM_EVENT_PUBLISH_OW:
In this example why CRM_OPPORT_H_SET_PRICE_DATE_EC is called?
Check via tcode CRMV_EVENT,
And the callback is registered here:
Further reading
I have written a series of blogs to explain how One Order API works. The blogs are written based on a simple scenario: read, change and save field “Closing Date” in Opportunity header level.
Buffer logic in One Order header extension Read
Change Scenario
CRM_ORDER_MAINTAIN
|- CRM_ORDER_MAINTAIN_MULTI_OW
|- CRM_ORDER_MAINTAIN_SINGLE_OW
|- CRM_ORDER_H_MAINTAIN_OW
|- CRM_OPPORT_H_MAINTAIN_OW
|- CRM_OPPORT_H_CHANGE_OW
|- CRM_OPPORT_H_READ_OB
|- CRM_OPPORT_H_FILL_OW
|- CRM_OPPORT_H_CHECK_OW
|- CRM_OPPORT_H_PUT_OB
|- CRM_OPPORT_H_PUBLISH_OW
Save Scenario
CRM_ORDER_SAVE
|- CRM_ORDER_SAVE_OW
|- CRM_EVENT_SET_EXETIME_MULTI_OW
|- CRM_OPPORT_H_SAVE_EC
|- CRM_ORDER_TABLE_SAVE
|- CRM_OBJECT_NAMES_DETERMINE
|- CRM_ORDER_UPDATE_TABLES_DETERM
|- CRM_ORDER_SET_OBJECTS_TO_SAVE
CRM_OPPORT_H_UPDATE_DU
Create Scenario
CRM_ORDER_MAINTAIN
|- CRM_ORDER_MAINTAIN_MULTI_OW
|- CRM_ORDER_MAINTAIN_SINGLE_OW
|- CRM_ORDER_H_MAINTAIN_OW
|- CRM_ORDERADM_H_MAINTAIN_OW
|- CRM_ORDERADM_H_CREATE_OW
|- CRM_OPPORT_H_MAINTAIN_OW
|- CRM_OPPORT_H_READ_OB
|- CRM_OPPORT_H_CREATE_OW
|- CRM_OPPORT_H_CHANGE_OW
