TREX for MDG

[Former Member]

Hi Gurus,

I am configuring TREX for MDG Material (Set up of search) . I performed following steps 1 thru 3 and please let me know whether I will have to create MATERIAL Template as well and if yes, what parameters I should fill and execute?

Step 1: I did not find the MATERIAL and MDG_MATERIAL templates in Open Administration Cockpit under SPRO->SAP Netweaver->Search and Operational Analytics->SAP NetWeaverEnterprise Search-> Modeling, Administration, and Monitoring.

Step 2: Executed create search object connector template under MDGIMG->General Settings->Data Qualityand Search->Search and Duplicate Check. Please see the attached screen shot for parameters.

Steps 3:  Now the tempate MDG_MATERIAL shows up in SPRO. Please see Step 1 for the exact path.

Thanks.

Regards,

Ramesh

[former_member603451 · Accepted solution]

Hi Ramesh,

You can locate the information regarding this in the MAterial master data governance link. However to locate the relevant templates faster, I am pasting the related content for your ready reference.

The template MATERIAL is part of the PLMWUI software component (PLMWUI/EA_APPL/SAP_APPL/LO/LO-MD/LO_MD_MM/MATERIAL). The template MDG_MATERIAL is part of the MDG_APPL software component (MDG_APPL/CA/CA-MDG/CA-MDG-APP/CA-MDG-APP-MM/MDG_MATERIAL).

https://help.sap.com/erp_mdg_addon61/helpdata/en/5b/362c74ba324597ace35c6422370afe/content.htm

You need to locate this under ESH_COCKPIT  transaction by following the help document. Post it is located, create Enterprise search connectors and perform indexing.

Thanks

Rahul

[Former Member]

Hi Ramesh,

I want to configure TREX for MDG. please help me with configuration steps.

Regards

Deeru

[Former Member]

Please just follow the below steps:

Embedded Search

If you want to use Embedded Search, run the following activity in Customizing for SAP NetWeaver under Search Embedded Search .

SAP delivers the following two standard templates for MDG for material. You need to activate these templates and prepare them for indexing.

o Material (MATERIAL) – for the active data residing on the standard tables MA* and related objects

o Material Template for MDG (MDG_MATERIAL) – for the inactive material data linked to the MDG change requests

If you are not familiar with TREX or TREX is not yet activated, proceed as follows to make the basic settings:

5. Create TREX_RFC user.

If the TREX_RFC user is not available, create it with the required roles as mentioned in the SAP note 766516 for the target system.

6. Connect to the TREX installation.

During TREX installation, you created an RFC-destination for the TREX. Run transaction SM59 in the TCP/IP connections section to verify that it exists and can be linked. Link the ABAP system to this TREX destination.

For more information, see Customizing for SAP NetWeaver under Search and Operational Analytics SAP NetWeaver Enterprise Search TREX Set TREX Destination .

Alternatively, you can run report ESH_ADM_SET_TREX_DESTINATION.

7. Create and index the connectors.

Open the Connector Administration Cockpit in Customizing for SAP NetWeaver under Search and Operational Analytics SAP NetWeaver Enterprise Search Modeling, Administration, and Monitoring Open Administration Cockpit . Alternatively, you can run the transaction ESH_COCKPIT. Make the following settings:

1. To open the Modeler, select the Modeler link.

2. In the Software Components menu choose Maintain Software Components and choose Create. Enter the name for the new software component and assign a package. Choose Create. Enter a description for the new software component and choose Save. Select a workbench request.

3. Mark your new software component and choose in the Software Component menu select Include Software Components. Include the component MDG_APPL. Choose Save and select Workbench

Transport. Repeat this process for the highest software component for the connector MATERIAL. For example, if the software layer hierarchy is PLMWUI > EA-APPL > SAP-APPL use the software component PLMWUI but if the software layer hierarchy is EA-APPL > SAP-APPL then use the software component EA-APPL.

4. Locate the two templates mentioned above. The template MATERIAL is part of the PLMWUI software component (PLMWUI/EA_APPL/SAP_APPL/LO/LO-MD/LO_MD_MM/MATERIAL). The template MDG_MATERIAL is part of the MDG_APPL software component (MDG_APPL/CA/CA-MDG/CA-MDG-APP/CA-MDG-APP-MM/MDG_MATERIAL). Once you have located the templates, create the connectors for the Enterprise Search. To create a search connector for the corresponding template, from the Actions menu select Create Connector. Create the connector using the MATERIAL template first and wait for the job to complete before creating the connector using the MDG_MATERIAL template.

5. Go back to the Administration Cockpit. The two connectors Material and Material Template for MDG are now visible with the status preparing and or prepared. Select the Material connector and from the Actions menu select Schedule Indexing. On the new screen choose Show Input Form. Next, choose the option for immediate indexing and the recurrence period. You can also activate real-time indexing if the sizing, parameters, and performance of the system allow for this. Select all object types and choose the Copy Settings button. This copies the default settings from the input form to all object types. The status of the connector is changed to Indexing.

6. Ensure authorization indexing. Enterprise Search requires its own authorizations. Authorizations for all MDG users must be indexed on the Enterprise Search system. The system writes every new or changed user as an entry into the table ESH_AU_USR_UPD that contains the user IDs that have been changed since the last indexing of the technical object type USER_AUTHORITY.

The object type USER_AUTHORITY needs to be regularly scheduled for indexing on the Enterprise Search system. The object type USER_AUTHORITY can be found in the connector Material or the connector MDG_MATERIAL. You cannot enable real-time indexing for USER_AUTHORITY.

7. Repeat step 4 for the Material Template for MDG connector.

Once indexing is complete the two connectors should have the status Active.

8. Use the report ESH_TEST_SEARCH to verify the search function. In the Search Scope section, enter a Connector ID. Next, enter Default in the Request field and execute the report.

§ The connector MATERIAL returns the active material master data.

§ The connector MDG_MATERIAL returns the inactive material master data. At least one active change request of type MAT* needs to exist with materials assigned to it, otherwise you will get a message that the search provider MDG_MATERIAL does not exist during the search and in the duplicate check of any change request where this is relevant.

[Former Member]

Hi Ramesh,

Thank you so much.

KR

Deeru

[former_member659619]

Hello Experts,

We are trying to create Search Object Connectors for Standard Material Master Model MM. We have followed your steps. At the time of creating the connectors, we receive following error messages. Also refer to the screenshot attached. Please suggest.

For Material

08/20/2014 03:01:34 Job started
08/20/2014 03:01:34 Step 001 started (program ESH_SE_CONNECTOR_MOD_BGD, variant &0000000000000, user ID SRAI)

08/20/2014 03:01:34 Process Step: Preparation
Information Messages (1)
08/20/2014 03:01:34 Environment Details: TREX Version 7.10.58.00, Destination: :RFC:TREX_DE1, SAP Release&#x20

08/20/2014 03:01:34 Process Step: Change inactive Connector Metadata
Warning Messages (6)
08/20/2014 03:02:04 Object type MATKL, node MATKL:
08/20/2014 03:02:04 There is a field with the same name as the alias MATKL
08/20/2014 03:02:04 Object type CLES_CLASS, node CLES_CLASS_LONGTEXT:
08/20/2014 03:02:04 Node CLES_CLASS_LONGTEXT has no response fields but is flagged for subquery
08/20/2014 03:02:04 Object type CLES_CLASS, node CLES_CLASS_NAME:
08/20/2014 03:02:04 Node CLES_CLASS_NAME has no response fields but is flagged for subquery
Error Messages (4)
08/20/2014 03:02:04 Rel. requests for object type CLES_CLASS, node CLES_CLASS:
08/20/2014 03:02:04 Navigation id 801CC4EFFE841DDEB7FE59BA4E4752F8 must start with $NAV_
08/20/2014 03:02:04 Rel. requests for object type CLES_CLASS, node CLES_CLASS:
08/20/2014 03:02:04 Navigation id 801CC4EFFE841DEEB7FE59BA4ED20D90 must start with $NAV_

08/20/2014 03:02:04 Process Step: Rollback
Error Messages (1)
08/20/2014 03:02:05 An exception was raised
08/20/2014 03:02:05 Error(s) occurred during connector creation
08/20/2014 03:02:05 Job cancelled after system exception ERROR_MESSAGE

For MDG_MATERIAL

08/20/2014 03:19:27 Job started
08/20/2014 03:19:27 Step 001 started (program ESH_SE_CONNECTOR_MOD_BGD, variant &0000000000007, user ID RMISHRA&#x29

08/20/2014 03:19:27 Process Step: Preparation
Information Messages (1)
08/20/2014 03:19:27 Environment Details: TREX Version 7.10.58.00, Destination: :RFC:TREX_DE1, SAP Release&#x20

08/20/2014 03:19:27 Process Step: Change inactive Connector Metadata
Warning Messages (12)
08/20/2014 03:19:52 Object type CLES_CLASS, node CLES_CLASS_LONGTEXT:
08/20/2014 03:19:52 Node CLES_CLASS_LONGTEXT has no response fields but is flagged for subquery
08/20/2014 03:19:52 Object type CLES_CLASS, node CLES_CLASS_NAME:
08/20/2014 03:19:52 Node CLES_CLASS_NAME has no response fields but is flagged for subquery
08/20/2014 03:19:52 Object type MDG_MATERIAL, node MARAPURCH:
08/20/2014 03:19:52 Node MARAPURCH has no response fields but is flagged for subquery
08/20/2014 03:19:52 Object type MDG_MATERIAL, node MARASALES:
08/20/2014 03:19:52 Node MARASALES has no response fields but is flagged for subquery
08/20/2014 03:19:52 Object type MDG_MATERIAL, node MBEWACTNG:
08/20/2014 03:19:52 Node MBEWACTNG has no response fields but is flagged for subquery
08/20/2014 03:19:52 Object type MDG_MATERIAL, node MBEWVALUA:
08/20/2014 03:19:52 Node MBEWVALUA has no response fields but is flagged for subquery
Error Messages (12)
08/20/2014 03:19:52 Rel. requests for object type CLES_CLASS, node CLES_CLASS:
08/20/2014 03:19:52 Navigation id 801CC4EFFE841DDEB7FE59BA4E4752F8 must start with $NAV_
08/20/2014 03:19:52 Rel. requests for object type CLES_CLASS, node CLES_CLASS:
08/20/2014 03:19:52 Navigation id 801CC4EFFE841DEEB7FE59BA4ED20D90 must start with $NAV_
08/20/2014 03:19:52 Rel. requests for object type MDG_MATERIAL, node MATERIAL:
08/20/2014 03:19:52 Navigation id 48B31C5008C71E56E10000000A428CD4 must start with $NAV_
08/20/2014 03:19:52 Rel. requests for object type MDG_MATERIAL, node MATERIAL:
08/20/2014 03:19:52 Navigation id 49B31C5008C71E56E10000000A428CD4 must start with $NAV_
08/20/2014 03:19:52 Rel. requests for object type MDG_MATERIAL, node MATERIAL:
08/20/2014 03:19:52 Navigation id 4BB31C5008C71E56E10000000A428CD4 must start with $NAV_
08/20/2014 03:19:52 Rel. requests for object type MDG_MATERIAL, node MBEWVALUA:
08/20/2014 03:19:52 Navigation id 4AB31C5008C71E56E10000000A428CD4 must start with $NAV_

08/20/2014 03:19:52 Process Step: Rollback
Error Messages (1)
08/20/2014 03:19:52 An exception was raised
08/20/2014 03:19:52 Error(s) occurred during connector creation
08/20/2014 03:19:52 Job cancelled after system exception ERROR_MESSAGE

[Former Member]

Again, please open a new post as this is very old. If you think it is relevant, you can always post a link to it in your own post.

[Former Member]

Hi Rahul,

I see it under EA-APPL. Thanks for your help.

Ramesh