Search screen in SRM UI Add-On returns no result

[laurent_burtaire]

Hi all,

we made all the basic customizing for SRM UI Add-On regarding the Enhanced Search and Cross-Catalog Search settings (settings for Embedded Search, extract data, indexing data).

We use only SRM Product Master Data.

By using the search screen (we disabled Product Category based Search), we do no get any result with any search term.

But, using ESH_TEST_SEARCH report for template ID SRMNXP01~STANDARD~SRMNXP02_CATALOG~ with a freestyle search term being the same as the one used on the search screen, i've got a result...

Does any body have a idea about this issue?

Regards.

Laurent.

[danilo_adam]

Hi Laurent,

i'm faced to the same problem right now. Did you solved your issue?

Best regards,

Danilo

[laurent_burtaire]

Hello Danilo,

i am sorry, but i did not manage to solve this issue.

As it was on a sandbox system, i did not push it...

Regards.

Laurent.

[former_member217429]

Hi Danilo, is the search from se38 -> esh_test_search works for you but not from SRM WUI? If this is the case I would like to recommend to open an OSS incident for this case. Best regards, Mikhail

[danilo_adam]

Hi Laurent,

thx for your reply. I have this issue also on a sandbox system.

Best regards

Danilo

[danilo_adam]

Hello Mikhail,

yes this is the case and the OSS incident is in progress. As soon as i have a solution i will share it.

Best regards,

Danilo

[robin_janke]

Hi all,

I had the same issue on a test system. On development it worked just fine. What finally fixed it for me was running the program ESH_ADM_INDEX_ALL_SC (after I deleted all indexes in trexadmin, which was probably not a wise thing to do ).

Regards,

Robin

[laurent_burtaire]

Hi,

result is obtained using GET_SEARCH_RESULT method from /SRMNXP/CL_SRV_TREX_SRCH class, but i cannot determine why i have no result...

I am implementing all OSS notes dealing with this class.

Our software components are:

- SAP_BASIS (SAPKB73106)

- SRM_SERVER (SAPK-70206INSRMSRV)

- SRMNXP01 (SAPK-10008INSRMNXP01)

Regards.

Laurent.

[ricardo_cavedini]

Hello,

Check if CAT attribute is maintained for the user who is performing the search.
Check also if CAT_VIEW is maintained as '*' or not maintained at all.
Product categories assigned to the catalog items should be maintained in extended attribute tab for end user.

After GET_SEARCH_RESULT method is called and results are there, see if items are still visible in method GET_ENTITYSET, class /SRMNXP/CL_SRH_CTLG_DATA_PRVDR.
Here an additional filter is applied.

Regards,
Ricardo

[former_member217429]

Hi Laurent, do you see any error messages in the TrexIndexServer trace when executing the search (f.e. attribute unknown)? Could you please activate the python trace for IndexServer (search calls only) , reproduce the issue , switch off the trace and attach this here. Thanks and best regards, Mikhail

[laurent_burtaire]

Hello Ricardo,

thank you for your help.

All attributes customizing is OK for my user.

After GET_SEARCH_RESULT method call, no data are retrieved.

The request type HIGH is used with connector ID XXXXXX~SRMNXP02_CATALOG~ (which is based on search template SRMNXP02_CATALOG) in GET_RESPONSE method.

I will check this catalog model: issue should come from here.

Regards.

Laurent.

[laurent_burtaire]

Hello Mikhail,

in the "Trace" tab, which file is the one dedicated to IndexServer?

Regarding Python trace, when i click over the button, there is no data. How can i activate this trace?

Regards.

Laurent.

[laurent_burtaire]

Hello Mikhail,

i just noticed the "Search" tab in TREXADMIN transaction allows you to simulate the search query.

Here also, i have no result with same attributes used during transactional process.

One stange thing is attributes for the model request are not the same with the ones in ESH_COCKPIT (for request 'HIGH').

In TREXADMIN:

In ESH_COCKPIT:

Is this could be the reason?

Regards.

Laurent.

[former_member217429]

Hi Laurent, you can look into the TrexIndexServerAlert_.trc file for checking , if there are any errors . For the Python Trace could you please use the note 1533891. Best regards, Mikhail

[former_member217429]

Hi Laurent, the TREXADMIN  isn't the best way to investigate the issues with the search in SRM/ESH scenario . If you start the search on Join and keep the default value (*) in the requested attributes field you usually don't get any results, but run into out of memory. The application request only very limited number of attributes pre-defined in the data model. For the tests on application level we use the esh_test_search report. As we probably need to activate a lot of addditional traces , is it possible for you probably to open the OSS incident? Thanks and best regards, Mikhail

[laurent_burtaire]

Hello Mikhail,

thank you for your help !

you will find Python trace file:

If you have any idea...

Regards.

Laurent.

[former_member217429]

Hi Laurent, it seems to be a problem with data model or corruption of some indexes. Unfortunately I don't see how to help here without to check your system directly. You can try to recreate the connector, but I doubt it help here. I would like to ask you to create a OSS incident for this issue. Best regards, Mikhail

[laurent_burtaire]

Hello Mikhail,

i recreated all connectors and did a full indexing: i still have the issue.

I opened an OSS message.

Regards.

Laurent.