Search - Fiori Authorizations

5/30/22, 1:05 PM search – Saptechnicalguru.
com
Saptechnicalguru.com
Blog for SAP technical guru's: SAP basis, SAP authorization, SAP ABAP
Tag: search
SE16S: generic table and value search
SE16 and SE16N can be used to search specific tables. FIORI search can be used by
end users to search business documents for predefined scenarios.
In some cases you might need to search multiple table for a certain value or string.
This can be needed from IT point of view or business point of view.
Then transaction SE16S can be your solution: generic table and value search.
Questions that will be answered in this blog are:
How does the generic table and value search transaction SE16S work?
Use of SE16S
As example we want to search for the string DE01 in T tables (customizing).
After starting transaction SE16S you are confronted with a big selection screen. In
the top part enter the search string:
https://www.saptechnicalguru.com/tag/search/ 1/22
5/30/22, 1:05 PM search – Saptechnicalguru.com
In the search type select Create Ad Hoc Search String. If you have to execute
repetitive searches, you can setup predefined searches with transaction
SE16S_CUST.
In the search section enter the search tables you want to search:
In the technical block make the technical settings:
Best to use parallel processing to speed up and also best to show only the tables with
hit.
Now start the query by pressing execute and wait a couple of minutes for this query
to end.
Results are shown:
Per item you can drill down to the details:
Transaction SE16SL and SE16H
Also transaction SE16SL exists for searching content. This one is bit faster, but less
accurate.
SE16H is the HANA based implementation of SE16N and has specific search
functions which might be very useful for your use case. More on SE16H in this blog.
Background
Master reference note: 2002588 – CO-OM Tools: Documentation for SE16S, SE16SL,
and SE16S_CUST. This note has a full explanation of all the options.
28 January 2022 / Table analysis / SE16S, search / Leave a comment
FIORI search setup
FIORI search is a very powerful tool for the end users. It enables a google like search
on the business data.
How does FIORI search work from the end user perspective?
How to set up FIORI search?
How to authorize search data?
FIORI search from end user perspective
From the end user perspective: open the search glass and key anything. Just like in
Google:
Now wait for the search engine to give results:
Now you can select a record, or select a related app (with the … you get more
options):
Set up of FIORI search
In the FIORI launchpad configuration parameters (see SAP help) make sure that the
enableSearch is set to true. Otherwise the search icon does not appear.
In case you run a FIORI hub, make sure to setup the web dispatcher rules properly to
the backend (see SAP help).
Next step is to activate the search models and the backend (see blog). The search
setup for FIORI launchpad is fully dependent on the backend search.
Some apps use related links. For these related links, the related FIORI app or FIORI
factsheet must be activated. See this blog on how to fast activate complete groups of
FIORI apps.
FIORI search authorizations
FIORI search relies on the authorizations of the end user. First make sure that the
general authorization for the search is active in this IMG node:
The setting Model Authorization must be set to Check:
In the search cockpit (transaction ESH_COCKPIT), make sure that the user
authorizations are indexed. In case of doubt run it under the Actions button, and
select Index User Authority:
If one end user gets results and the other one does not get the same result: the main
reason might be difference in authorizations.
Useful OSS notes
For specific use cases the following OSS notes might be relevant:
2227082 – Search fails in SAP Fiori Launchpad but is successful in ‘Enterprise

Search’
2513743 – Fiori Launchpad Search pad error
2693653 – Enable Enterprise Search for a subgroup of fiori users

2885249 – How to disable Enterprise Search in Fiori Launchpad
2898408 – How to disable specific search connector in Fiori launchpad
2999945 – Fiori search error “SY530: An exception was raised”
3007113 – Connector name in Fiori search shows word ‘Duplicate’
3061220 – OData service ESH_SEARCH_SRV/users allows reading details about
other users
3090096 – SAP Fiori UI – “Search – Show More – Define Condition” does not
work
3102861 – Slow search performance when using “All” search scope
11 December 2020 / FIORI / FIORI, search / Leave a comment
Activating search in S4HANA
This blog will describe the steps in activating search in S4HANA. We will explain
both new fresh installation and upgrade from system which has search already
activated.
How to activate search in S4HANA for an initial installation?

How to activate search in S4HANA after upgrade when search was already active?
Activating search in S4HANA new installation
To activate search goto transaction STC01 and select task list

SAP_ESH_INITIAL_SETUP_WRK_CLIENT:
Open the details:
Make sure that you set the TREX destination to SAP HANA DB:
Then select the search model. For most use cases this will be SAPAPPLH:
Now run the task list and be patient. This can take quite some time. If the task list
finishes correctly start transaction ESH_COCKPIT to check that all search
connectors are correctly activated.
Search after upgrade to S4HANA
If you upgrade your existing system and have search already active, you get this
message after launching ESH_COCKPIT:
Run report ESH_CDSABAP_ACTIVATION with default parameters:
This might be a long run:
If you run into issues, check that the following OSS notes are applied:
2806253 – ES: Set CDS-based search connectors active

2806533 – ES: group labels not translated (CDS)
2811545 – ES: Getting a search trace from ABAP
2814227 – ES: Tracing for searches on CDS-based Connectors
For some search connectors based on CDS you might see this error message:
In this case you need to goto transaction SFW5 and activate the needed switch for
Enterprise Search for the specified object:
After the activation is done, rerun the search activation again.
Background: 2905864 – ESH_COCKPIT errors: ESH_DB037 – No activation of

CDS-entities for Enterprise Search ESH_DB027 – Mandatory Data Source is
missing.
More background information
More background on search can be found in the Search section of this blog. Also read
OSS note 2626107 – How to execute task list
SAP_ESH_INITIAL_SETUP_WRK_CLIENT.
Relevant OSS notes:
3102861 – Slow search performance when using “All” search scope

3122697 – Equivalence between CDS views and classical search models
4 October 2019 / Search / S4HANA, search / 1 Comment
SAP TREX and HANA embedded

search technical tips and tricks
This blog will give technical tips & tricks on embedded search. Embedded search can
run on both HANA directly or on separate TREX server. It is assumed you know how
to set up search in ESH_COCKPIT and know how the end user transaction
ESH_SEARCH work.
How do I set HANA default connection as embedded search location?

What to do after a system copy with embedded search?
How to reset the complete embedded search to initial state?
How to reset the embedded search buffer?
How to recreate the embedded search joins?
How to influence the package size of the search extraction?
How to check backend part of search?
How to deal with full text search issues?
How to deal with authority index issues?
Activating search in S4HANA
If you are running S4HANA, you can use an STC01 task list to fully setup the search
function. Read this blog for full instructions. The remainder of the blog below can be
used in case of issues.
Setting the search connection to use HANA default database

connection
If you are running HANA database for ECC you can use the HANA default primary
database connection for search setup. This is easier in maintenance: no extra TREX
needed, no extra secondary DB connection. Search will consume extra memory and
CPU off course on the HANA database.
To set this up run program ESH_ADM_SET_TREX_DESTINATION and select the

Use HANA Primary DB connection option.
Task list to run after system copy
After you copy a system the search will not immediately work. In client 000 start
transaction STC01 and run task list SAP_ESH_ADJUST_AFTER_COPY. See also OSS
note 2479611 – Error message: “Current system is a copy of another system”.
Resetting all settings to initial
When things gone really beyond repair, you can log on to client 000 and start
transaction STC01 and run task list SAP_ESH_RESET.
Important: write down (or make screen shots) on the connectors and settings
that were active before running this task list. It will really wipe out all
connectors and settings.
More information can be found in OSS note 2626143 – How to execute

SAP_ESH_RESET.
Resetting the buffer
Run program ESH_REFRESH_RUNTIME_BUFFER in the working client to reset the

trex buffer.
Bug fix note: 2947055 – CDS activation: Runtime error in report

ESH_REFRESH_RUNTIME_BUFFER.
Recreation of join indexes
Run program ESH_RECREATE_ALL_JOIN_INDICES in the working client to

recreate the join indexes. See also OSS note 2112153 – How to recreate ESH join
indexes which are corrupted in TREX.
Influencing package sizing per object
With program ESH_SET_INDEXING_PACKAGESIZE you can set the package size

for indexing per object. You can lower the size for large objects to avoid memory
issues while indexing. Also see OSS notes 2758222 – Runtime Error:
SYSTEM_NO_SHM_MEMORY with Except. CX_SHM_OUT_OF_MEMORY when

indexing connectors and 2540240 – High Memory and Indexing problems in TREX.
Check backend part of search
To check if a search issue is related to application coding or is related to search

setup, you can run program ESH_TEST_SEARCH (with same transaction code
ESH_TEST_SEARCH). This program gives you options to test the search
independent of any programming of search front end.
Bug fix OSS note: 2972790 – ESH_TEST_SEARCH – value help for attribute search:
Values are not transferred case-sensitively.
Full text search issues
If you are having issues with full text search, please check OSS note 2280372 – How
to check Full Text search issues. This note is focusing on full text search issues in
relation to solution manager CHARM, but the methods described can be used as well
for analyzing other full text search issues.
Setting the extraction user ID
Use program ESH_EX_SET_EXTRACTION_USER or transaction ESH_EXTR_USER

to set the user to be used for extraction. This includes the real time indexing. For
more information see OSS note 2340298 – User Types and required authorizations
for ESH extraction user. For issues see OSS note 2750997 – Error “Logon of user
XYZ in client xyz failed when starting a step” in ESH indexing job logs. And 2938916
– ESH extraction user – option “Generate User” – adjustment of password policy.
Bug fix OSS note: 2938916 – ESH extraction user – option “Generate User” –
adjustment of password policy.
Authorization indexing issues
While indexing you might get authorization indexing issues. First step is to repeat
with sufficient rights attached to your user ID. Then run program
ESH_ADM_RECALC_AUTHS to force the recalculation of the authorizations.
If it does not help, you can read the very extensive OSS note 2472239 – Error
message “Authorization indexing unsuccessful” when creating search connectors.
And OSS note 2729739 – Error indexing search connectors: “Authorization indexing
unsuccessful for object type USER_AUTHORITY”.
New option to partially skip the checks for indexing: 3088737 – Customizing option
for completely deactivating authorization indexing for individual ESH authorization
indexes.
Index preload
For some TREX issues index preload can be a solution. More information on index
preload can be found in OSS note 2115082 – ESH Index Preload.
Python check script
For detailed check on TREX embedded search there is a special Python check script,
which is not installed by default. The script can be downloaded as attachment from
OSS note 2227741 – TREX 710: check of the TREX settings for the
Enterprise/embedded Search scenario. Read OSS note 2344042 – How to execute
python script check_esh.py on how to install and run the script.
TREX memory issues
If you are seeing high memory consumption in TREX, please check OSS note
2540240 – High Memory and Indexing problems in TREX.
TrexViaDbsl Analysis Tool in ABAP
In newer versions this tool is available. Otherwise apply OSS note 2690982 –
TrexViaDbsl Analysis Tool in ABAP. Then in SA38 you can launch program
RHANA_TREXVIADBSL_ANALYZER for the analysis tool:
A more detailed explanation is given in OSS note 2800048 – FAQ: SAP HANA
TREXviaDBSL.
Special use cases
SAP solution manager documentation
If you have search issues with SAP solution manager documentation, there is a
special OSS note 2608454 – FAQ: How to handle issues with the (embedded) search
functionality in the context of Solution Documentation . This OSS note also contains
coding for special test program that will check all relevant settings for the solution
documentation search function to work properly.
16 March 2018 / Basis, Search / embedded search, enterprise search, search, trex / 2 Comments

Search - Fiori Authorizations

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Search - Fiori Authorizations

Uploaded by

Copyright:

Available Formats

5/30/22, 1:05 PM search – Saptechnicalguru.

SE16S: generic table and value search

Questions that will be answered in this blog are:

As example we want to search for the string DE01 in T tables (customizing).

In the technical block make the technical settings:

Results are shown:

Per item you can drill down to the details:

Transaction SE16SL and SE16H

28 January 2022 / Table analysis / SE16S, search / Leave a comment

FIORI search setup

Questions that will be answered in this blog are:

FIORI search from end user perspective

Now wait for the search engine to give results:

Set up of FIORI search

FIORI search authorizations

The setting Model Authorization must be set to Check:

Useful OSS notes

2227082 – Search fails in SAP Fiori Launchpad but is successful in ‘Enterprise

2693653 – Enable Enterprise Search for a subgroup of fiori users

11 December 2020 / FIORI / FIORI, search / Leave a comment

Activating search in S4HANA

Questions that will be answered in this blog are:

How to activate search in S4HANA for an initial installation?

Activating search in S4HANA new installation

To activate search goto transaction STC01 and select task list

Open the details:

Search after upgrade to S4HANA

Run report ESH_CDSABAP_ACTIVATION with default parameters:

This might be a long run:

2806253 – ES: Set CDS-based search connectors active

After the activation is done, rerun the search activation again.

Background: 2905864 – ESH_COCKPIT errors: ESH_DB037 – No activation of

More background information

Relevant OSS notes:

3102861 – Slow search performance when using “All” search scope

4 October 2019 / Search / S4HANA, search / 1 Comment

SAP TREX and HANA embedded

Questions that will be answered in this blog are:

How do I set HANA default connection as embedded search location?

Activating search in S4HANA

Setting the search connection to use HANA default database

To set this up run program ESH_ADM_SET_TREX_DESTINATION and select the

Task list to run after system copy

Resetting all settings to initial

More information can be found in OSS note 2626143 – How to execute

Resetting the buffer

Run program ESH_REFRESH_RUNTIME_BUFFER in the working client to reset the

Bug fix note: 2947055 – CDS activation: Runtime error in report

Recreation of join indexes

Run program ESH_RECREATE_ALL_JOIN_INDICES in the working client to

Influencing package sizing per object

With program ESH_SET_INDEXING_PACKAGESIZE you can set the package size

SYSTEM_NO_SHM_MEMORY with Except. CX_SHM_OUT_OF_MEMORY when

Check backend part of search

To check if a search issue is related to application coding or is related to search

Full text search issues

Setting the extraction user ID

Use program ESH_EX_SET_EXTRACTION_USER or transaction ESH_EXTR_USER

Authorization indexing issues

Python check script

TREX memory issues

TrexViaDbsl Analysis Tool in ABAP