In order to resolve one issue I need to figure out the logic how field OBJECT_TYPE is populated in table CRMD_ORDERADM_I.For example, I have the following opportunity line item:

For example, I would like to test relationship type STRSET and then I plan to add it to product category 00001.

In this SCN discussion,Find a Function Module in Update Task dynamically called,a question is asked. For example, if the update function module CRM_PRODUCT_I_UPDATE_DU is called statically as:CALL FUNCTION ‘CRM_PRODUCT_I_UPDATE_DU’ … Then we can easily find all calling places where this function …

All of these three questions are raised regarding the customizing below via tcode COMM_PRAPPLCAT:

In one of my previous blog A small tip to analyze code by code and export to markdown format it is introduced that the following header extension are supported in One order read function module CRM_ORDER_READ.

题目：SAP CRM One Order函数CRM_<Object>_FILL_OW的设计原理There are totally 60 function modules in One order with naming convention CRM_<Object>_FILL_OW:

In previous blogs the READ and UPDATE logic of Opportunity header field Closing Date are explained:

In the previous series of blogs the read and update on Opportunity header fields are discussed. In this blog another scenario will be explained: create scenario on Opportunity header fields. I will again use Closing Date ( and description field ) for example.Execute the following report:

Recently I start to study SD and I found the product hierarchy in transaction code V/76 could not be viewed in tree style and it is not so convenient to check:

In SAP standard development it is very important to use unit test to cover those changes on legacy code to try to avoid side effect. As type reference CL_CRM_BOL_ENTITY is widely used in UI component code, I would like to find a way to construct its reference by sample data.