Ansicht
Dokumentation

CRMC_UIU_SRVMON - Define Customer-Specific Objects for Search

TXBHW - Original Tax Base Amount in Local Currency   CPI1466 during Backup  
This documentation is copyright by SAP AG.

In this Customizing activity, you can do the following:

• Remove a business object from the service monitor search options.

• Change the business object that is preselected for searches in the service monitor (users can select a different business object in the dropdown box).

• Add new business objects to the service monitor.

If you want to add a new business object to the service monitor, you need to do the following:

1. Create a dynamic query object as follows:
1. Create a new structure that includes the search criteria.
2. Create a new dynamic query object.

You do this in Customizing for Customer Relationship Management, under CRM Cross-Application Components -> Generic Interaction Layer/Object Layer -> Component-Specific Settings -> Business Transactions -> Extend Model for Business Transactions with New Nodes.

To identify a dynamic query object as an item query, its name must end with ItmMon.

To minimize implementation effort we recommend using the existing implementation class CL_CRM_QSRVMON_RUN_BTIL (with the entry CL_CRM_QSRVMON). You can enhance the code of this class using the following Business Add-Ins (BAdIs):

BAdI: Enhancement of Service Monitor Search

BAdI: Enhancement of Service Monitor Result

Enter a result object for the query (for the header query use BTQRSrvMonHdr and for the item query use BTQRSrvMonItmAdv).

1. Create an entry for the supported operators.

You do this in Customizing for Customer Relationship Management, under CRM Cross-Application Components -> Generic Interaction Layer/Object Layer -> Component-Specific Settings -> Define Operators for Dynamic Queries.

Create an entry for the new dynamic query object in table CRMC_Q1O_OBJ (if an entry does not yet exist) with the following result structures:

CRMS_SRV_MON_ITM_ADV_RES_RF for the item query

CRMS_SRV_MON_HEADER_RESULT_RF for the header query

1. Create a new UI object type.

You do this in Customizing for Customer Relationship Management, under UI Framework -> UI Framework Definition -> Define UI Object Types.

It is also possible to use an existing UI object type, but note that this UI object type influences the input helps for the partner function and status. Note also that the configuration of the search parameters and search results in the service monitor is determined according to this UI object type.

1. Create the following new OTR short texts in transaction SOTR_EDIT:

• A text for the search result message (describes the number of results) for the case that only one result is found, for example, Result List: 1 Service Order Found

• A text for the search result message (describes the number of results) for the case that multiple results are found, for example, Result List: 55 Service Orders Found

This text is also shown in the dropdown list of supported objects for which a search can be performed.

• A text for the title of the service monitor work area, for example Search: Service Orders in Service Monitor

You then need to proceed as described in the section Activitiesbelow.

The following objects are available in the service monitor in the standard system. We recommend that you do not change these entries, with the exception of the settings Inactiveand Default:

Object	UI Object Type	Query Name
Service order	BT116_SRVO	BTQSrvOrdMon
Service order item	BT116_SRVO_IT_SRVMON	BTQSrvOrdItmMon
Service confirmation	BT117_SRVC	BTQSrvCfmMon
Service confirmation item	BT117_SRVC_IT_SRVMON	BTQSrvCfmItmMon
Complaint	BT120_CPL	BTQComplMon
Complaint item	BT120_CPL_IT_SRVMON	BTQComplItmMon
In-house repair	BT120_IHR	BTQIhrMon
In-house repair item	BT120_IHR_IT_SRVMON	BTQIhrItmMon
Return	BT120_RET	BTQRetMon
Return item	BT120_RET_IT_SRVMON	BTQRetItmMon

BT120_RET_IT_SRVMON

• Select the Defaultradio button to determine which object is displayed by default in the business object dropdown box of the service monitor.

• To prevent an object from being offered in the business object dropdown box, select the Inactive checkbox.

If you want to add a new business object to the service monitor, you need to do the following:

Make Customizing Entries

• Enter the dynamic query objects that you created as described in the section Prerequisites above.

Note that each query object can only be used once so that, in case of a saved search, the correct business object type can be determined.

The key (BO Type field) can be freely defined. For simplicity, in the standard system the UI object type name used.

• In the field Alias for OTR Singular, enter the OTR text for the search result message (describes the number of results) for the case that only one result is found, for example, Result List: 1 Service Order Found.

• In the field Alias for OTR Plural, enter the OTR text for the search result message (describes the number of results) for the case that multiple results are found, for example, Result List: 55 Service Orders Found.

• In the field Alias for OTR Title, enter the OTR text for the title of the service monitor page (for example Search: Service Orders in Service Monitor).

Enhance the Service Monitor UI

Note: You must have experience with the WebClient UI Framework in order to complete the steps described below.

For information about the UI Framework functions, see SAP Library for SAP CRM on SAP Help Portal at http:/help.sap.com/crm -> Application Help -> SAP Customer Relationship Management -> WebClient UI Framework.

1. Enhance the UI component BTSRVMON.
2. Create a new empty view for search parameters in the enhanced UI component BTSRVMON.
3. Exchange the superclass of the superclass of the view controller with CL_BTSRVMON_SEARCH_PARAMS_IMPL.
4. Keep the redefinitions.
1. Ensure that the class constructor does the following:

- Passes the business object type to the superclass.

- Sets the parameter gv_object_type to an existing transaction type (to enable the standard input help to work).

If the standard input help does not meet your requirements, you need to redefine the input help methods to implement your own determination logic.

1. In the superclass of the view controller method DO_HANDLE_EVENT, delegate this call to the superclass.

Exchange the superclass of the context class with CL_BTSRVMON_SEARCH_PARAMS_CTXT.

Create the context node BTQuery (the name must be BTQUERY) with the dynamic query object that you entered in Customizing.

1. Change the superclass to CL_CRM_UIU_BT_ADVS_CN.
2. Bind CREATE_BTQUERY of the view context to the component controller, and provide the node to the view controller (if you want to make the standard input helps available).

For an example, see class CL_BTSRVMON_SERVICEORDERS_CTXT, method CREATE_BTQUERY.

1. Adapt the view.htm coding with the advanced search tag (for an example, see ServiceOrderSP.htm of view BTSRVMON/ServiceOrderSP).
2. Create a design layer object for the dynamic query object that you specified in Customizing, and assign it to the BTQUERY node.

The design layer object must be dependent on the UI object type.

1. Configure a search view.
2. In the runtime repository editor, add the search view to the view set BTSRVMON/SearchTypeViewSet, view area Search.
3. Create a navigational link using the naming pattern To<BOTYPE>Search from the BTSRVMON/SearchType view to the new view and the relevant search result view.

For an example, see navigational link ToBT117_SRVCSearch or ToBT117_SRVC_IT_SRVMONSearch.

1. Create a navigational link using the naming pattern SavedSearch<BOType> from the MainWindow view to the search result view (the first target must be the search result view) and to the search criteria view.

For an example, see navigational link SavedSearchBT116_SRVO or SavedSearchBT116_SRVO_IT_SRVMON.

1. Create a design layer object for the result object, dependent on the UI object type, and assign it to the result node (this is only possible for a table view).
2. If necessary, create your own configuration for the result view, dependent on the UI object type.

BT120_RET_IT_SRVMON

General Data in Customer Master   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 12456 Date: 20240523 Time: 153813     sap01-206 ( 132 ms )