cancel
Showing results for 
Search instead for 
Did you mean: 

HANA embedded search limitations

Former Member
0 Kudos

Dear all

For the ESH included in the HANA platform, is there any restrictions on the usage for searching in SAP Applications (use for CAR etc)?

Is there any additional licensing or is this included in the HANA License?

Regards

Andreas

Accepted Solutions (0)

Answers (3)

Answers (3)

aifrim
Explorer
0 Kudos

Hi all.

Note 2222735 does not appear in the new version of SAP For Me service portal, and neither the note 1865540 , which is still included in the documentation bellow :

https://help.sap.com/doc/saphelp_nw74/7.4.16/en-us/48/037ac8c4914d65861c9816f9fd6c0e/content.htm?no_...

Also as the lines above were written in 2016, is not clear if those limitations are still in place. Do you know if there is other note specifying the current limitations of Embedded Search?


Thank you,

Alina

dmitry_sharshatkin
Active Participant
0 Kudos

Hi Andreas,

There is a note: 2222735 - "Limitations Note SAP Enterprise Search on HANA" which is now being worked on. It says:

The following limitations exist for SAP Enterprise Search on HANA:

- A fulltext search runs on data of all available languages, however the search results will only be displayed in the logon language.

- Search models leveraging classification features cannot be used. Specific advanced search queries for classification characteristics are not supported. Measure conversion is not supported for search terms.

- For search models including KPRO documents, only document metadata (not content) can be searched.

- Flagging a table column as fulltext relevant in a search model will not automatically trigger the creation of a fulltext index for this table. Solution: create fulltext index manually via se11.

- For templates based directly on database tables changes of authorizations are not effective immediately. Solution: schedule indexing of authorization data.

- In a scenario containing a TREX or BWA, real-time indexing and delta indexing is not supported for templates that are based directly on database tables.

- NW 7.40 based systems running Enterprise Search must not be connected (content relocation) to SAP NetWeaver Enterprise Search 7.20 or 7.30.
Any search backend systems that have already been relocated must not be upgraded to 7.40

- If an already running  Enterprise Search system (based on a non-HANA DB with a TREX or BWA connected) is switched to a HANA-based DB (but the TREX/BWA is still being used), then the prefix :RFC: must be added before stating.the TREX rfc destination in the table ESH_ADM_TREX. (Example: :RFC:TREX_LD8893)

- The Enterprise Search HTML5 UI only runs on a limited set of browser versions (Internet Explorer 9 or higher, latest Firefox, latest Chrome). It does not support the full set of globalization and accessibility characteristics.

- If a system has existing connectors, it is not possible to switch from HANA to TREX (or vice versa). In such a case, please delete all connectors first, then switch, then recreate them.

So, as long as it is not released, I'm not sure if these limitations are still valid, but at least this is something.

Regards, Dima

Mithun_K
Advisor
Advisor
0 Kudos

Hi Andreas,

Embedded Search is a solution which is available within the Business Suite solutions. There should be no extra pricing to use the solution.

Regards,

Mithun