Wednesday, 29 May 2013

50. UI OBJECT TYPE AND DESIGN OBJECT



With the help of UI object types in CRM, we can do following things. 

1.       We can make different VIEW CONFIGURATIONS
2.       We can create DYNAMIC NAVIGATION
3.       We can CONTROL FIELD LABELS, VALUE HELPS FROM DESIGN LAYER.
4.       We can control the visibility of attributes of BOL objects.
5.       We can give access to our Z components from navigation bar.



One UI object type will have design objects grouped under it and each design object can control attributes of BOL objects. 

As a first step,
We will create one call back class. Go to the transaction SE24 and create one new class. This class should have interface IF_BSP_DLC_OBJ_TYPE_CALLBACK.




Let us make one new UI object type. Follow the below path in the SPRO transaction. In the next screen choose new entries. 






Enter the entries as shown below and save them.
 


 





Call back class is used to provide sub object types which will be useful in creating view configurations. Give the class name that we have created above. We will implement required method later point of time.
Next we are going to use this UI object type on service contracts, give the genil component name (BT). 

BTOrder is main root object of BT component. 

BUS2000112 BOR refers to service contract type.  SAVE the entries. 

We have created new UI object type.  As next step, we need to create a design objects under this new UI object type. 

Follow the below path in spro Customer Relationship Management-> UI Framework-> UI Framework Definition->Design Layer-> Define Design Objects.
It will ask for UI object type. Give the new UI object type that we have just created.






Click on new entries. Enter the following information and save the entries. 







Once you save the entries, click on DESIGN on the same screen. it will open a new screen like below.






Click on new entries.  In the next screen fill up the entries as shown below. 




Here I want to control the OBJECT_ID attribute of BOL object BTAdminH. So I have chosen the OBJECT_ID. 

In the LINK TO BUSINESS OBJECT LAYER, we can mention any another BOL object and its attribute if we want. 

I also added the new field label.  If we choose HIDDEN, then this field won’t be available for any configuration (it won’t be shown in the available section on configuration tab in the view). 

We can also make particular field as a drop down or check box if it has some value range by selecting the check box VALUEHELP from ABAP dictionary. (We will see it later). Once data entry is done, then save the entries.
We are ready with UI OBJECT TYPE and design object. In the next step, we need to assign it to the required context node with base entity BTAdminH. We will do it in the next chapter.


1 comment:

  1. Hello Mannala,

    If we mention a different BOL and attribute name in the "Link to Business object layer" and not BTAdminH what we have entered above, what difference it will make.Is it that we can link two BOL objects here?

    -Abhishek

    ReplyDelete