Kontakt

Ansicht
Dokumentation

CRMV_IU_IR_PDS - Maintain Predefined Searches for Interaction Records

CRMV_IU_IR_PDS - Maintain Predefined Searches for Interaction Records

Addresses (Business Address Services)   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you maintain predefined searches that are used in the overview page of the Interaction Center (IC) application.

Each predefined search must have its key defined in a Business Add-In (BAdI) implementation for the BAdI definition CRM_ISU_IREC_PDS (Enhancement Spot CRM_ISU_IREC_ENHSPOT). The key is used as a filter in a BAdI implementation.

The BAdI definition CRM_ISU_IREC_PDS contains only one method, IF_CRM_ISU_IREC_SELECTION ~ LOAD_SELECTION_PARAMETERS, which must be implemented. The objective of this implementation is to prepare the selection criteria to be executed by the interaction records search. To do so, the selection criteria, along with the condition, must be filled in the parameter table ET_SELECTION_PARAMS.

The attribute names to be used as selection criteria must be valid selection fields which exist in the structure CRMS_ISU_IREC_ADVS_FILTER.

The option to be used as selection criteria must be a valid operator for the corresponding selection field. To check for valid operators for each search field, do the following:

  1. Use transaction SM34and display the view cluster CRMVC_DQ.
  2. Select the line with Component =BT and DQuery Object Name = BTQIrecFilter.
  3. Double-click the folder Exceptions per Attribute from the left panel. All operators for each selection field used for the interaction records search are listed.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab page in the BAdI Builder (transaction SE18).

Perform the following steps:

  1. Create a new BAdI implementation for BAdI definition CRM_ISU_IREC_PDS (Enhancement Spot CRM_ISU_IREC_ENHSPOT).
  2. Specify a filter for it and implement the method IF_CRM_ISU_IREC_SELECTION ~ LOAD_SELECTION_PARAMETERS.
  3. Maintain predefined searches by defining the following parameters for all predefined searches:
    1. PDS Key
Unique key for a predefined search. This key is used as a filter in a BAdI implementation for BAdI definition CRM_ISU_IREC_PDS (Enhancement Spot CRM_ISU_IREC_ENHSPOT).
  1. Seq.
Sequence of the display order for the predefined searches list.
  1. Hidden
Flag to hide the predefined search. If it is set, the predefined search is unavailable in the predefined search drop-down list on the user interface.
  1. Description
Description of the predefined search (language dependent). The description is displayed in the predefined search drop-down list on the user interface.

There are several delivered predefined searches that can serve as examples. To view them, use transaction SE18, display enhancement spot CRM_ISU_IREC_ENHSPOT and look for the implementation of BAdI definition CRM_ISU_IREC_PDS.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View→ Application Server→.Application Server ABAP→ Application Development on AS ABAP → ABAP Customer Development→ Enhancement Framework.






CPI1466 during Backup   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 5288 Date: 20240523 Time: 170558     sap01-206 ( 83 ms )