Kontakt

Ansicht
Dokumentation

CRM_IOBJECT_NAV_BADI - BAdI: Settings for Locator for Individual Objects

CRM_IOBJECT_NAV_BADI - BAdI: Settings for Locator for Individual Objects

CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

This Add-In is used to enhance the individual object locator of the Interaction Center (IC). The different methods are called from within function group CRM_IOBJECT_CIC_NAV_UI.

The Add-In contains the following methods:

  • DETERMINE_DEFAULT_SETUP: Setting the default setup for the locator
This method has the following parameters:
  • EV_ONLY_ONE_OBJECT_FAMILY
    If this flag is set to true ('X') this object family is used inside the program (for example to find the alternative IDs).

  • EV_ONLY_ONE_OBJECT_FAMILY
    Specifies that only the default object family will be used in the locator. This means that the dropdown list of the object family on the screen for the search type "individual object" is hidden and object family EV_OBJECT_FAMILY of BADI CRM_ISAM_COMMON is used internally.

  • EV_OUTPUT_STRUCTURE
    Structure used for the ALV that displays the search result. As a default, the structure CRMT_IOBJ_NAV_OUT_S is used. As you can define your own attributes and set types for the individual object you can specify your own output structure here . This structure will be filled with your customer-specific attributes.

  • EV_OUTPUT_TABLE
    Table used for the ALV that displays the search result. As a default, the table type CRMT_IOBJ_NAV_OUT_T is used. The table type should have the line type that is used in EV_OUTPUT_STRUCTURE.

  • EV_PARTNER_DETERM_PROCEDURE
    Partner determination procedure used to get the list of the partner functions fyou want to search for in the business partner search type.

  • CV_DEFAULT_SEARCH_TYPE
    Default search type that will appear when you open the locator. It can either be 1 (partner) or 2 (individual object).

  • DETERMINE_FIELDCATALOG: Manipulating the field catalog of the search result ALV in the IC individual object locator
    This method has the following parameters:
  • IV_LIST_KIND
    Type of search that was carried out. Based on the search type, you can manipulate the field catalog. The possible search types are P (Partner), O (Individual Object) and A (Alternative Identifier).

  • IV_ALTID_TYPE
    Alternative ID that the user has used within an alternative ID search. You need this information to search for the texts of the alternative ID. See the automotive example implementation in IOBJ_NAV_ISA_EX_IMPL.

  • EV_BADI_USED
    Specifies that the Add-In was run through. Set this flag to true ('X') to prevent the program from overwriting your field catalog manipulation with the standard field catalog manipulation.

  • CT_FIELDCATALOG
    Field catalog. You can modify all of its fields. See the automotive example implementation in IOBJ_NAV_ISA_EX_IMPL.

  • DETERMINE_SEARCH_TYPES: Specifying customer-specific texts for the search types
    The standard texts are Partner (1) and Individual Object (2). This method has the following parameter:
  • CT_LISTBOX_DATA
    Listbox data (key and short text). See the automotive example implementation in IOBJ_NAV_ISA_EX_IMPL.

  • MANIPULATE_OUTPUT_TABLE: Manipulating the search result that is displayed in the output table
    For example, you can filter out individual objects using specific criteria (partner function, individual object attribute).
This method has the following parameters:
  • IV_LIST_KIND
    Type of search that the user has executed.
    P = partner Search; O = individual object Search; A = search by alternative ID

  • CT_OUTTAB
    Output data. You can filter out certain lines, sort it or even add lines or manipulate certain attributes.

  • FILTER_PRDBP_DATA: Manipulating the contents of table CT_PRDBP_DATA
    This makes sense if you want to delete certain records that seem to be duplicates in your business context. For example, there might be several more or less similar relationships between a business partner and an individual object, resulting in the identical individual object being displayed several times in the search result for the end user in the IC. The user will see that some attributes of the relationships are different (for example, partner function, valid from/to date, and so on), but the identical individual object will be displayed several times all the same. All these relationships are stored in table CT_PRDBP_DATA. This method enables you to filter these pseudo duplicates out.
This method has the following parameters:
  • CT_PRDBP_DATA
    Interlinkage data of relationship type PRDBP (link between business partner and product/individual object).

  • IV_PARTNER_DETERM_PROCEDURE
    Current partner determination procedure that is used in the individual object locator. You can use this variable to find out the partner functions and use this information as an additional filter in case the user selected any of the partner functions as search criteria.

  • MANIPULATE_CONFIRMED_BP: Transferring the partner function from the confirmed business partner to the partner search screen of the locator
    If this method is not used no partner function will be passed on to the partner function of the partner search screen. The partner function is not passed on as a default because it might not be part of the partner determination procedure defined.

The BAdI is filter-dependent. The filter type is CCMPROF (CIC Profile).






General Data in Customer Master   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 6511 Date: 20240523 Time: 152928     sap01-206 ( 95 ms )