Skip to Content

SAP CRM OneOrder Advanced Search WebUI Component – part1


Create a search component for one order objects. The Search component has 2 views, one for search criterias and the other for result list respectively.

Go to Genil Model Browser via Transaction Code GENIL_MODEL_BROWSER. As shown below the Dynamic Search/Query Object BTQ1Order is available in the Genil. This Dynamic Query Object BTQ1Order has the BTQR1Order as Query Result Object.

The Query Result Object is associated to BTOrder via relation BTADVS1Ord.


Dynamic Query Object – BTQ1Order


Query Result Object – BTQR1Order

  1. Go to transaction code BSP_WD_CMPWB and enter the component name. e.g. ZRAK_ORDERSRCH.
  1. Add the BT Model.


  1. Right Click on Views and choose ‘Create’ from context menu.


  1. Enter View name ‘Search’.


  1. Add Both the Model nodes. Use model BTQ1Order to enter search criteria and BTQR1Order for result list purpose.


  1. Choose the Empty View.


  1. Create new Custom Controller. E.g. QueryCuCo.


  1. Define the Model Node BTQR1Order of type BOL BTQR1Order to keep & Share the search result list.


  1. As shown below choose ‘Create’ to define new Context node for Custom Controller QueryCuCo.


  1. Enter the Model Entity BTOrder of type BOL BTOrder.


  1. Choose Higher Level Context node as BTQR1Order and choose BOL Relation BTADVS1Ord.

  Note: The relation BTADVS1Ord was already discussed at the start which we found in Genil model Browser.  


  1. Go to the Search View and create binding for context node BTQR1Order.


  1. As shown below enter the BSP Application, Controller Type, Custom Controller Name and Target Context node of Custom Controller.16.JPG
  2. Create new view Result.


  1. Define the Model Node BTQR1Order of type BOL BTQR1Order to store the one order result list. Also define the Model node BTOrder of type BOL BTOrder. Use the Higher level node BTQR1Order with BOL relation BTADVS1Ord.18.JPG
  2. Create binding/links of context node BTQR1Order with the custom controller context node BTQR1Order.


  1. Choose view type as Table View and Configurable checkbox too.

  Note: Make sure context node BTQR1Order is selected from list box.  


  1. As shown below create new View Set.


  1. Enter view set name as SearchVS and mention grid size as Lines 2, Columns 1.


  1. Enter View areas names (e.g. Search & Result) and respectively choose the positioning of ViewAreas.


  1. As shown below the wizard displays the overview of ViewSet ViewAreas.


  1. Select the ViewArea Search, right click and choose ‘Add View’.


  1. Choose View name ‘Search’.


  1. In the same way, choose the ViewArea Result and assign ‘Result’View.

  2. Add ViewSet ZRAK_ORDERSRCH/SearchVS into Window ZRAK_ORDERSRCH/MainWindow (default). Choose the MainWindow, right click and choose Add View. 27.JPG

  3. Enter the view name SearchVS.


  1. Make sure to flag it as Default.


  1. Go to the implementation class of Search View.


  1. Open the Super class (e.g. ZL_ZRAK_ORD_SEARCH) and change the inheritance of controller class with new class CL_BSP_WD_ADVSEARCH_CONTROLLER.


  1. Choose ‘Yes’ to keep the redefinitions of methods.


  1. Choose the context node BTQ1Order of View ZRAK_ORDERSRCH/Search and open Implementation Class ZL_ZRAK_ORD_SEARCH_CN00.


  1. Replace the super class inheritance with new class name CL_BSP_WD_CONTEXT_NODE_ASP.


  1. Copy the below code into the Search.htm page.

  <%@page language=”abap” %>

<%@extension name=”thtmlb” prefix=”thtmlb” %><%@extension name=”chtmlb” prefix=”chtmlb” %><%@extension name=”bsp” prefix=”bsp” %>

<thtmlb:advancedSearch id                = “advs0”
                       fieldMetadata     =
“<%= controller->GET_DQUERY_DEFINITIONS( ) %>”
                       header            =
“<%= BTQ1ORDER->get_param_struct_name( ) %>”
                       fieldNames        =
“<%= controller->GET_POSSIBLE_FIELDS( ) %>”
                       values            =
                       maxHits           =
                       onEnter           =
                       ajaxDeltaHandling =
“false” />
button id      = “search”
onClick = “search”
text    = “Search” />  

  1. Open the Configuration tab of View ZRAK_ORDERSRCH/Search. Click on Edit button. Choose the search fields from available search criteria’s. Then click on ‘Save’ button.


  1. Open the Configuration tab of View ZRAK_ORDERSRCH/Result. Click on Edit button. Choose the fields to be displayed from available fields. Then click on ‘Save’ button.


  1. Test the Component. The following window with Search and Result views should appear.


  1. Create new event in View ZRAK_ORDERSRCH/Search.


  1. Enter event name ‘search’.


  1. The event handler method EH_ONSEARCH would appear as shown below.


  1. Copy the following code.

Reads the current context of BTQ1Order (search parameters) into dynamic query service object LR_QUERY_SERVICE. The method GET_QUERY_RESULT returns the one order collection into dynamic query result LR_RESULT. The result list collection will be assigned to result context node BTQR1Order.


DATA: lr_query_service TYPE REF TO cl_crm_bol_dquery_service,
TYPE REF TO if_bol_bo_col.

lr_query_service ?= me->typed_context->btq1order->collection_wrapper->get_current( ).
lr_result = lr_query_service->get_query_result( ).
CHECK lr_result is BOUND.

me->typed_context->btqr1order->set_collection( lr_result ).

  1. The event names are Case Sensitive. Make sure to match the event name in Search.htm page and DO_HANDLE_EVENT method of its implementation class.


  1. Your Search component is ready to use.  Mention the search criteria (e.g. ID 5000000) and then either press enter key or click the ‘Search’ button. The result appears in result list.


You must be Logged on to comment or reply to a post.
  • If you are on EHP1, you can avoid most of the steps mentioned above. You can create a search page view, which will generate three views – Search, Result and the Viewset. All actions will be handled by the wizard. 🙂

    The problem arises when you will require to change the htm view layout as the wizard will use a standard template. Nevertheless for quickly creating a search view page in EHP1 requires a very small effort.

  • Can you explain me What is one order framework, whether it is different in WEBUI or in Backend GUI. What are important one order frame work in SAP CRM 7.0



  • Nice Blog

    What are the search parameters that are being read into the dynamic query search object i.e LR_QUERY if I enter no search parameters and press the ‘search’ button? What does the context node BTQ1Order contain?



  • Hi Rahul,

    I tried implementing this. When i add code in search.htm i didn’t get configuration tab. So, i closed the transaction and reopened it. But when i did that there were no context nodes in search view. Can you please tell me why this problem occurred?

    I am getting an exception “CX_SY_CREATE_OBJECT_ERROR” in the config tab.

    • Hi Pallavi,

      Why we are not getting the configuration tab is , while creating the search view , in the step


      Choose the Empty View ….. here on the right hand side you can see “properties” configurable check box , if you check this , then only you can see the configuration tab for a view . But for an Empty view, this will be greyed out . If you want the configuration tab, choose the “form ” or “Table” view as view type 🙂 …..

      • Hi rekha,

        While creating the search view.It is chosen as empty view.Iam getting an exception while opening the configuration tab of search view CX_SY_CREATE_OBJECT_ERROR.Can you please help me to fix this.If I choose the type as table then i am getting errors.

  • Amazing blog, I was able to do all the steps successfully and got the search result for the Order. Thank you very much Rahul …

  • While creating Search View you did not tick on Configuration, than how did you get Configuration tab in the Search View?

    Also when I am executing the UI component I am getting dump

    method do_init_context.

        lv_cnode type ref to cl_bsp_wd_context_node_asp,
        lr_qs    type ref to cl_crm_bol_dquery_service.

       field-symbols: <qs_name> type crmt_ext_obj_name.

    * set flag for later intialization in DO_PREPARE_OUTPUT
       me->set_init_qs( abap_true ).

    * check if QS already exist
       lv_cnode = get_dquery_cnode( ).

       lr_qs ?= lv_cnode->collection_wrapper->get_first( ).—-dump in this line

    Access via Null object reference not possible



  • While creating the search view.It is chosen as empty view.Iam getting an exception while opening the configuration tab of search view CX_SY_CREATE_OBJECT_ERROR.Can you please help me to fix this