headershadow

How to improve search in transactions PA30 and PA20 or PPOSE/PPOME by removing hit list in Object Manager

Print Friendly

 

When transactions such as PA30 and PA20 or PPOSE/PPOME are run for a long hit list of employees, it will cause significant delays. Search history should be reset or delete and thus quicken the loading of the transaction.

To hide the selected hit list and avoid the problem you could follow the steps below:

1. Open PA30/PA20

2_1_PA20

  1. Then go to Search Term in Object manager of the screen

2_2_search

If there are any entries they have to be deleted.

In the screenshot below we have (*) in search term.

2_3_all

(*) means ‘’all’’ and when transaction is run with such a selection and in case of a huge organization this should cause load with delay.

Press Enter after entries are deleted.

  1. Open any PN and after that exit from the transaction

2_4_PA30

When the transaction is run again, the search will not produce any hits. You can select a shorter list of employees, using Collective Search help.

If a large hit list is collected again, you can remove it in advance before closing the transaction. In this way you will avoid waiting the next time you run PA30/PA20.

  1. If a consultant have to reset or delete the search history and thus quicken the loading of the transaction, follow the steps below:

Go to SE38 and run report RH_DELETE_OM_USER_SETTINGS, where first of all read the documentation:

2_5_ABAP

Then execute the program, select a user, choose desired options and run:

2_6_Usettings

To clear only the Hit List select just the upper option – Delete search variants.

A message confirming the settings have been deleted will be displayed.

2_7_Note

SAP HR consultant with extensive experiences in SAP HR implementation and support in PA, OM, PT, PD, TM, ESS, MSS, E-Recruitment modules.
More about

0 thoughts on “How to improve search in transactions PA30 and PA20 or PPOSE/PPOME by removing hit list in Object Manager

Leave a Reply


*