Skip to Content

This Business Add-In (BAdI) enables you to filter appraisal documents according to various search criteria in

the form of overview lists from all existing appraisal documents.

The BAdI is called after the function module GET_LIST_XXL has been run.

This function is used in the administrator function. The administrator create variants to define certain

selection criteria according to which appraisal documents can be filtered.

Useful BADI to change appraisal documents list but I didnot find such function in administrator (Transaction PHAP_ADMIN).

Search on SCN and google didnot clear this problem. So the last helper is debugging.

For transaction PHAP_ADMIN used program RHHAP_APP_DOCUMENT_ADMIN

* ADMINISTRATOR – search appraisal documents
   call function ‘HRHAP_SHOW_DOCUMENT_SEARCH’
     exporting
       user_mode                  = ‘A’    ” Administrator
*     S_SEL_CRITERIA             =
*     S_SEL_PARAMETER_HIDE       =
*     S_DOCUMENT_FILL            =
*     VIA_SELECTION_SCREEN       = ‘X’


Parameter S_SEL_CRITERIA is commented. 


To turn on BADI GET_LIST_XXL you need to copy program to Z* and write BADI filter value. After that implementation of BADI will work.


Also the same situation in portal appraisal applications. In feeder class CL_HRHAP00_STARTPG_POWL the parameter sel_filter is commented.


* Call method to fetch the documents.
         CALL METHOD cl_hap_wd_start_page_ui=>document_get_list
           EXPORTING
*           sel_filter            =
             add_on_application    = lv_add_on_application



If somebody knows where SAP use BADI HRHAP00_GET_LIST_FLT by default, please write.


To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Yes SAP Team

    Hi Yurri,

     

    It ┬áis called (at least) from t-code “PHAP_CHANGE_PA”.

    The problem I have is that there are 2 SAP-Standard implementations in, but it’s not stopping anywhere.

    I found that for some reason the call for this BADI does not send any Filter value, so these implementations (which are Filter-bound) are not called.

    I think that there is a Customization needed.

     

     

    Regards,

    Ayal Telem.

    (0) 

Leave a Reply