Collective search does not contain any search help

[laurad2]

Dear All,

At the moment I want to display a preventive maintenance plan or measurement document I get the following error:

Please give me detailed advise on how to solve this issue.

I know already the table DDSHDEFSH and checked the collective search help for MPLA and there is an entry...

Kr,

Laura

[Former Member · Accepted solution]

Hello Laura,

the collective search help that is behind this field is MPLA_ES (Structure EAMS_S_SP_MPLAN_ID -> Field EAMS_WARPL).

This error means that none of the elementary search helps ( MPLA_ES_SIMPLE_E nor MPLA_ES_ADVANCED_E) are working.

Both of this elementary search helps read the data from the enterprise search, and in order to make them work, the enterprise search connector for maintenance plan should be active in your system.

Depending on your release, this search connector will be MAINTENANCE_PLAN_H, if you are using HANA or BUS1020 if you are using TREX.

Creating the search connector will repair your problem.

Best regards,

Julián

[laurad2 · Accepted solution]

Hi Julian,

The search connector for maintenance_plan_h is active.

Is there a category missing to your knowledge?

Kr,

Laura

[Former Member · Accepted solution]

Hello Laura,

the search helps MPLA_ES_SIMPLE_E and MPLA_ES_ADVANCED_E do not use any category as a reference to the search model, but the search model itself.

We have here two different scenarios:

1.- (I guess this is your case): Your system has installed the component SAP_APPL 617 or 618 and there the search helps still are expecting the replicated search models (TREX based). In this release both kind of search models are still supported, but the search helps only support the TREX based.

In this case BUS1020

2.- Your system has installed the component S4CORE: There, only the HANA based search models are supported, and the search helps were changed accordingly.

In case you are in the scenario 1, you have then the option to schedule the search connector BUS1020 or to modify both search help in order to make it work for the HANA search connector MAINTENANCE_PLAN_H.

Best regards,

Julián

[laurad2 · Accepted solution]

Dear Julian,

Indeed scenario 1 is applicable for me.

Can you guide me through the steps that I need to do?

Thanks in advance.

Kr,

Laura

[Former Member · Accepted solution]

Hello Laura,

you have the option to modify both elementary search helps accordingly as in the second image on my previous reply (change the parameter value OBJECT_TYPE_ID from 'BUS1020' to 'MAINTENANCE_PLAN_H' and the parameter name from WARPL_EXT to WARPL.

Afterwards you have to adapt the collective search help MPLA_ES so that the parameter mapping also matches:

Replace WARPL_EXT by WARPL:

If you do not want to make a modification, you will have to schedule the search connector for BUS1020.

The option of replacing the search help in the customizing does not exist, since the only possibility would be to use the search help MPLA or MPLAL, and both tries to open a dynpro in the Web UI, what will give a short dump.

I hope this helps you.

Best regards,

Julián

[laurad2 · Accepted solution]

Hi Julian,

Thanks for your reply.

So I can do the following:

* (Developer key is needed):

• Replace the WARPL_EXT by WARPL
• Replace BUS1020 by MAINTENANCE_PLAN_H
• Replace MDOCM by ?
• Replace BUS2092 by MEASUREMENT_DOC_H?

* Schedule the search connector for BUS1020? => Please explain how this is done? (in the ESH_Cockpit?)

Can this be done without developer key?

Thanks,

Laura

[Former Member · Accepted solution]

Hello Laura,

If you do not want to make a modification in the search helps or you do not want to schedule the connector for the TREX search models, you can also create Z* search helps and use the customizing to replace the existing search helps.

In this case you can copy the existing search helps (MPLA_ES, MPLA_ES_SIMPLE_E, MPLA_ES_ADVANCE_E, and the IMRM_ES...) and change the parameters as you mentioned above.

The field MDOCM is the same in both BUS2092 and MEASUREMENT_DOC_H search models, you can check it using the transaction ESH_TEST_SEARCH or opening the search model directly in the transaction ESH_MODELER.

This might be, in my opininon, the easiest way. You can of course just schedule the TREX search connectors from the transaction ESH_COCKPIT, but this might be your decission.

Best regards,

Julián

[laurad2]

Hi all,

Incident 2287944 - EHP7: Correction of search model for PM in component SAPAPPLH (EAMS) can also solve a lot of issues.

Kr,

Laura

[Former Member]

HI Laura,

Please check whether there is elementry seach help mapped with your search help MPLAL.

Just double click on MPLAL & Check & if possible please share screenshot.

Regards,

AMol

[laurad2]

Hi Amol,

See screenshot of MPLAL. How can I see if it's mapped?

Kr,

Laura

[Former Member]

Hi Laura,

Looks okay. I think this is standard behavior.

Can you try to search with following method & execute. It works.

Regards,

Amol

[laurad2]

Dear Amol,

In the GUI I have no problem to search a preventive maintenance plan or measurement document. It's in the NWBC that the error occurs.

Kr,

Laura

[Former Member]

Hi Laura,

Ok. Can you please check if entries for MPLA & WARPL with search help assignment exist in following Maintenance tables.

EAMS_SHLP_CONFIG

V_EAMSC_UI_SHLP

V_EAMS_UI_SHLP.

Also I am not sure if this is relevant but please have a look at below note.

2274409 - Creation of categories for Enterprise Search search model and connectors

Regards,
Amol

[laurad2]

Hi Amol,

The note is not relevant.

It's not advisable to change in the table V_EAMS_UI_SHLP.

In both other tables the following is present:

This makes sure that a different search help is possible but does not prevent the error on measurement document and preventive maintenance plan.

Kr,

Laura

[MTerence]

Hi Laura,

May be you try posting your request to below community

Regards

Terence

[Former Member]

Hi Laura,

In table EAMS_SHLP_CONFIG & V_EAMSC_UI_SHLP do you have following entry? f no please try to add & check. If still it does not help then I think its better to go for OSS support or raise your query in a space mentioned by Maria.

Regards,

Amol

[Former Member]

Hi Laura,

I am not sure whether this helps or not. Perhaps you must have gone through this document already.

But can you check through chapter 3 of this document & also raise OSS for this issue.

EAM Web UI Implementation Guide EHP7 | SCN

Regards,

Amol