CRM Bol programming Debugging Tips and Code Snippet on how to read & populate values

This blog explains on how to do basic debugging and write code in CRM. It covers the below topic areas

1. Requirement: To disable one specific field in an Address section

2. Find the UI component

3. Find technical object to do code changes

4. Get value using IF_BOL_BO_PROPERTY_ACCESS

◉ Debug to find where the value is coming from

5. Get value of UI field using me-> context type

◉ Debug to find how this gets populated.

6. Add a default Blank row in CRM UI

1. Requirement: Disable a specific UI element field

For customer overview screen when user clicks on edit to update the address information

Disable a specific field called “Delivery service type” and do not allow to update Phone and email sections as highlighted below.

2. Find the UI component

UI component was BP_ADDR

And View value as BP_ADDR/AccountAddressEF

3. Find Technical object to do code changes

Use transaction obsp_wd_cmpwb to be able to open the component in backend CRM system

Specific fields can be found in

Context_Nodes > Implementation class > Attributes >STRUCT.FIELDNAME

◉ GET_XYZ – This is used to get the data of attribute (XYZ) from the BOL Layer and display it on the UI

◉ SET_XYZ – This is used to set the data of the attribute from the UI to the BOL layer

◉ GET_M_XYZ – This defines the meta data (type) of the attribute

◉ GET_I_XYZ – This defines whether the attribute is editable or non-editable i.e., using Get_I method you can make your field as grade out based up on any condition.

◉ GET_V_XYZ – This defines the content of drop down values, F4 Help etc i.e., you can retrieve the drop-down values based up on your condition.

◉ GET_P_XYZ – This defines the property of attribute whether it’s drop down, text box, F4 help, check box etc. Also, if any follow-up event should trigger the same is mentioned here i.e., you can call specific even handler using P method .

◉ There are two more methods which have recently got added from the above two as mentioned below

◉ GET_A_XYZ – This is used to hide or display the attribute based on the Switch ID.

◉ GET_AC_XYZ – This is used for Field Action Menu Getter

◉ Since I need to make the field disabled, I need to make use of the field value GET_M_DELI_SERV_TYPE

◉ You can find this method in context node Buildaddress> Attributes> STRUCT.DELI_SERV_TYPE which has a set of predefined methods as seen below

The code which was used to set the value as disabled would be GET_I_XYZ

If the icon does not look green as in the above screenshot choose to redefine or one of then options below to activate the method

Add the source code as below:

METHOD get_i_deli_serv_type.

CALL METHOD super->get_i_deli_serv_type

EXPORTING

iterator    = iterator

RECEIVING

rv_disabled = rv_disabled.

IF zl_bp_addr_accountaddress_impl=>gv_addr_disabled IS NOT INITIAL.

rv_disabled = zl_bp_addr_accountaddress_impl=>gv_addr_disabled.

ENDIF.

ENDMETHOD.

4. Get value of UI field using IF_BOL_BO_PROPERTY_ACCESS

I would like to read the address number value from the UI

To access a specific value coming from the previous or current screen use the BOL property access type as mentioned below where you want to read the value from

In my case I am using ZGO_BOL_PROPERTY  of type IF_BOL_BO_PROPERTY_ACCESS defined in class ZL_BP_ADDR_ACCOUNTCOMMNUM_IMPL where I want to read the attribute address number and address GUID which are attributes in that class.

If you check the interface IF_BOL_BO_PROPERTY_ACCESS, it has properties as below:

To be able to use the value stored in the property below code needs to be run

// In ZL_BP_ADDR_ACCOUNTEMAILSE_IMPL DO_PREPARE_OUTPUT

DATA: lo_bo        TYPE REF TO  cl_crm_bol_entity,

lv_addr      TYPE ad_addrnum,

lv_addr_guid TYPE bu_address_guid.

IF zl_bp_addr_accountcommnum_impl=>zgo_bol_property IS NOT INITIAL .

lo_bo ?=  zl_bp_addr_accountcommnum_impl=>zgo_bol_property.

ENDIF.

IF lo_bo IS BOUND .

lo_bo->get_property_as_value(

EXPORTING

iv_attr_name =     'ADDRESS_NUMBER'

IMPORTING

ev_result    =       lv_addr

).

lo_bo->get_property_as_value(

EXPORTING

iv_attr_name =     'ADDRESS_GUID'

IMPORTING

ev_result    =       lv_addr_guid

).

ENDIF .

4.1.  Check in debug mode where the value is coming from

You can also navigate to container proxy by using the code as below

ZL_BP_ADDR_ACCOUNTCOMMNUM_IMPL=>ZGO_BOL_PROPERTY

Where ZGO_BOL_PROPERTY is of type IF_BOL_BO_PROPERTY_ACCESS

1. Go to container_proxy

2. Go to Data_Ref

3. Click on data type which opens up

4. Open the attribute_ref

5. Find the address number and address value in there

The above would directly come to container proxy

Click on Data_ref

Click on the type below

Click on Attribute ref

Find the values

5. Get value of UI field using me-> context type

For debugging as a starting point use the implementation class  and find from Context what specific field value are you looking for. Example I am looking to find the address number field as below

You can use “Me” and navigate inside to find the values

Inside “Me” you can find the context Type which can be Z or standard in my case I defined a ZContext

ztyped_context->builaddress->collection_wrapper->

Get the 3 entities list

Go to the BUILADDRESS

Insider collection wrapper you would find collection reference

Insider collection reference look for below

Look for entity list as above which shows 3 entries as there are 3 BP addresses on the UI

Go to one of the entities and it would have container proxy

Follow the same steps as in 4.1

1. Go to container_proxy

2. Go to Data_Ref

3. Click on data type which opens up

4. Open the attribute_ref

5. Find the address number and address value in there

6. Add a default blank row in the CRM UI table

As you can see below default Blank line was added to the email so the user can enter but no default blank line was added for Mobile Number

Now when we add the code as below to method DO_PREPARE_OUTPUT of class ZL_BP_ADDR_ACCOUNTCOMMNUM_IMPL

CALL METHOD super->do_prepare_output

EXPORTING

iv_first_time = iv_first_time.

This would add a default blank line to the component

I found CRM debugging quite difficult initially but was helpful to understand once  I understood how to navigate in debug mode.

I hope this article was helpful for someone who is looking to understand how the BOL programming works and the different layers to go through to find the right values in CRM nodes.