Embedded Search - no delta Indexing

Hi Experts,
i want to configure Embedded Search in CRM 7.0. TREX is well configured and all Embedded Search configuration steps are done. I created all BO-Connectors in ESH_COCKPIT. But now I can`t start delta indexing (Actions-Schedule Indexing) because the Button is grey. The status of the connectors is new.
I also tried scheduling indexing with the report ESH_ADM_INDEX_ALL_SC, but it takes no effect.
What should i do?
Thanks,
Tobi

you mean on 7.0 and now you are on 7.1. Can you please be specific as i am also facing the same problem. i am on TREX 7.1 and tried report 'ESH_IX_PROCESS_CHANGE_POINTERS' but no any effact on trex search result. I created soem new data for job family and talent groups but its not coming up in HRTMC searches.
apprecite any help..
Mani

Similar Messages

Embedded Search delta indexing

Hello all,
i am trying to create delta indexing for EA-HRXXX component in SAP ECC 6 EH4 on TREX search 7.10 (standalone) but its not taking into account my changes.
I created some test data on ECC6 EH4 system related to talent group (new talent group) and job family (for talents) , now my HRTMC_Search_OBJECTS not retruning data related to those objects. i tried to run program 'ESH_IX_PROCESS_CHANGE_POINTERSESH_IX_PROCESS_CHANGE_POINTERS' as said in documentation (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/47/fb4c38469e59e8e10000000a421937/frameset.htm) but its not showing results.
any reply will be highly appreciateed.
Mani

Hi Mani,
yes, there are moderators in SDN.
But in the end the forums are community froums - they are not a support system with guaranteed answering times or anything of the like. So, if you have questions about mission critical errors, please do use SAP support.
If you are looking for answers to "how to..:" questions, SDN forums are a great channel, but - again - without any answering guarantee.
By the way, I understood you correctly that you have found an answer to your query, right?
Even if that may have been "not possible"...
Best, Karsten

Embedded Search Index AND Document Security?

I'm using Adobe Acrobat Standard 8.1.7.
It appears that I cannot have both an embedded search index and restricted security (e.g., password required to change document) on the same document.
Why is that?
If I start with security ON and then attempt to embed a search index, I get below error message:
A search index can not be embedded in this document because this document has restricted security permissions.
If I start with security OFF, successfully embed a search index, and then secure the document, Acrobat "strips off" the previously embedded search index. No warning message; no feedback to end-user; just kills it!
Why are those two functions mutually exclusive? Anyone know of a work-around?
Thank you in advance!

Hi,
As to "why", that might be floating out there in Adobe's devnet space or in one of the blogs maintained by Adobe's devnet crew.
Also good to know about use of embedded index - if used, cannot apply fast web view to the PDF. It is one or the other, but not both.
Work around? I've not come across one; but, that does not mean something isn't "out there" <g>.
Be well...

Indexing product data for embedded search for my shopping cart fiori app

Hello Experts
I'm doing indexing of product data records for SRM embedded search for My Shopping Cart Fiori app.
however the job being created by the system to accomplish the task is, as error message displayed, not defined properly.
any idea how to resolve this?
i have no idea what program is this, and job details cannot be displayed/changed because of incomplete job definition.
Appreciate any assistance pls.

Hi Dex,
Please check if there was a dump recorded in ST22. Also perform an authorization check SU53 for the background user that submits the job.
Thanks,
Vipin

Talent Management - TM - Trex 7.1 - Delta Indexing

luke.....are you out there??
congrats on your blog being featured right on the SDN homepage... very nice...
http://scn.sap.com/community/erp/hcm/blog/2010/09/20/setting-up-netweaver-embedded-search-trex-for-sap-ehp4-talent-management
and congrats to Chris on his first two excellent blogs....
http://scn.sap.com/people/chris.mcnarney/blog/2010/08/26/whats-included-with-the-predefined-performance-management-process
http://scn.sap.com/people/chris.mcnarney/blog/2010/09/09/whats-included-with-the-predefined-performance-management-process--part-2
all 3 blogs are very helpful since there is little information available out there on these topics...
so we've been testing the delta indexing program very heavily - ESH_IX_PROCESS_CHANGE_POINTERS
we have found that it does not appear to be able to index new hires (new central_person index does not pick up the new CP). The only way this data can be indexed is by running a full re-index. That is problematic for us, b/c we were hoping to only do full re-indexing 1 a week or even 1 a month. our indexes take 2-3 hrs to complete and trex searching is pretty much inoperable during that time.
Have you tested new hires with delta indexing? it seems as a gap in the change_pointers program. We opened up OSS message to SAP.
some additional thoughts working with the program, relative to your blog. I would highly recommend that anyone testing this makes sure the following notes are implemented in your system. The first one is the most recent and we ourselves did not have that implemented.
1. 0.350 BC-EIM-ESH 1441190 Error in model assignments to logical system 24.02.2010
2. 0.230 BC-EIM-ESH 1408655 Alerts in syntax check due to unused indexes 18.11.2009
3. 0.260 PA-TM 1395703 Positions and termination are missing for indexing 30.10.2009
4. 0.330 BC-EIM-ESH 1249482 Functional corrections for Enterprise Search 7.01 SP03 26.01.2009
Another area which we found from testing: SAP by default does not delta index structural authority view. What this means is that if a new talent specialist is added with 741 relationship there access to see that structure will not be available in TREX search by default delta indexing. This would also impact existing organizations and positions shifted under existing 741 relationships.
The information in spro is actually quite helpful, you can find it in: talent management and talent development > basic settings > search > BAdI: Activate Delta Indexing for Authorization Data
Activtate the BADI, than the program to "create the change pointers" must run periodically in your system. This is done with RPTMC_CREATE_CHANGEPOINT_AUTH. Once that program creates the change pointers the next time your scheduled delta program runs (ESH_IX_PROCESS_CHANGE_POINTERS) all of the structural auths will be created and indexed correctly.
If we can just now get new hires to work with ESH_IX_PROCESS_CHANGE_POINTERS we will probably only run the full re-index once a week or once a month.
Let me know your thoughts,
Michael
Message was edited by: Luke Marson
Message was edited by: Luke Marson

so if anyone is interested, from my previous post I mentioned that new hires were not getting picked up by the change pointers program.
after further testing though, we found that when the authorization recon program identifies the new hires and appropriately creates a change pointer.
conclusion: to avoid full re-indexing of trex indexes, perform the following steps:
1. implement / activate the BADI - HRTMC_AUTHORITY_VIEW - talent management -> basic settings -> search
2. Schedule program RPTMC_CREATE_CHANGEPOINT_AUTH - every 30 mins, or 1 or 2 hr. This program will capture whenever anything changes from an authorization data perspective. This would include identifiying new central persons (new hires) or new TMC specialist being setup with 741 relationship. This program "creates change pointers" which than feeds the main delta program - ESH_IX_PROCESS_CHANGE_POINTERS.
3. Use Luke's blog on the instructions for the delta program - ESH_IX_PROCESS_CHANGE_POINTERS - this program you can have run every 5 mins, 10 mins, 15 mins, based on your needs. this processes all delta changes, the first time the program runs after the RPTMC_CREATE_CHANGEPOINT_AUTH program finishes it will also processes the data authorization changes, otherwise every other time the program is running it will catch non-data authorization for all the other indexes (employee name change, new performance rating, new potential, position name change, new profiiciency scale, new career profile data, etc).
hope this helps somebody!
michael
Edited by: Michael L Pappis on Oct 7, 2010 12:05 AM

SES vs Embedded search

Hi All,
I have couple of questions..
1. What will be the main feature of embedded search over SES?
2. My requriement is , for example i have a document like sales order and want to index , after initial indexing of all documents.
for example if we change only item level data, then i want to index only that part of data, so that means delta indexing at really the node level not the entire document level.
In ses what i observed is we always have to do indexing for entire document,I think in Enterprise search indexing we can define nodes with relationsihp , seems to be we can achieve this , is that right? or by SES also we can achieve this? i do not see any examples like that in Netweaver 701 release.
Thanks and Regards,
Shiva.

Hi,
you wrote
"SES can be used ONLY for SAP ERP business object, whereas Embedded Search can be used by SAP ERP as well other SAP Business Suite applications. Is that the only one difference?"
well you can use SES and embedded search not only for ERP, you can as well use both for other SAP Business Suites like CRM. But only in ERP there are out-of-the-box some business objects defined for searching via SES. SES and embedded search are part of AS ABAP.
SES is available with NW 7.0 and Embedded Search is available with SAP Business Suite 7.0 (NW 7.01).
The most important part is:
The successor framework of SES is "Embedded Search".
see as well
Note 1254901 - SES for customer projects on TREX search
Best regards
Frank

Create new search object for simple/embedded search

Hi,
SAP CRM contains indexing and search functionalities based on SAP Netweaver Enterprise Search. SAP delivers search models, connectors and search abilities for a lot of CRM objects, like Accounts, Contacts, Opportunities, ...
However, some objects like "Service Requests" (BUS2000223) and "Tasks" (BUS2000125) are missing.
Has anyone tried to perform a complete extension of the whole process including template modeling, change pointers (for delta indexing), enhancing UI to provide search abilities for these objects, and so on?
I found different kind of information on how to create a new search object template, however, no further details about what comes after, e.g. how to index, how to handle change pointers for delta, what to do in the CRM web UI to provide search ability and result lists...
Many thanks & regards
Wolfgang

Hi Ralf,
there is a new Book avaliable "mySAP CRM Interaction Center" from Thorsten Wewers and Tim Bolte. Currently it is only avaliable in german. But as I've seen from your Business Card that should be OK. There is also a Chapter about extendig the Search in IC WinClient.
Regards
Gregor

Searching for Easy DMS documents using embedded search

Dear Experts,
we are using easy dms to manage documents. As far as I know it should be possible to index these documents using TREX.
-it is possible to perform a search for these documents using Embedded Search an get the search results as XML (a documentation would be very helpful)?
-how can the security be taken into account? Is there a method like AUTHORITHY_CHECK by SeS to perform security check?
thanks a lot for your help
kind regards
Nicolai

I found that authorization checks can be performed using the following authorization objects:
-Authorization Object C_DRAW_TCD (Activities for Documents)
-Authorization Object C_DRAW_TCS (Status Dependent Authorization)
-Authorization Object C_DRAW_STA (Document Status)
-Authorization Object C_DRAW_BGR (Authorization Group)
-Authorization Object C_DRAW_DOK (Document Access)
-Authorization Object C_DRAD_OBJ (Object Link)
I could not find any information regarding my first question

Integrate with SES: connector approach or embedded search approach

hi Experts:
According to the document, we have 2 options to integrate ECM11g with SES11g:
* SES connector approach
* embedded search approach
My customer needs to use a unified search engine to search ECM, internal web and file system, so SES should be used with ECM, question is which approach should be taken, what is the difference?
Best regards

Hi
SES connector approach
In this case SES and UCM have different DB schemas and for SES to search contents of UCM the feeds are created by SES Crawler Export component and placed in SES home location for it to read . It is a 2 stage approach viz 1. UCM creating the feeds 2. SES Crawling the feeds so that search can retrieve results .
Embedded search approach :
With this UCM schema is the same as SES one so that SES acts as the search indexer engine for UCM . Moment contents are checked in to UCM indexes are created on the common DB schema so that SES can directly search / display the contents from UCM .
In my view you should go for Embedded SES Search engine approach.
Thanks
Srinath

TREX - how to setup delta indexing?

Hi,
I have got TREX installed and I could search in Succession Planning.
However, when I changed some data (for e.g. assigning a new user id to a PERNR), that new ID couldn't perform a search on employee.
I have scheduled the program ESH_IX_PROCESS_CHANGE_POINTERS, and this program could be completed without error.
But still, I couldn't perform a search until I manually run program ESH_ADM_INDEX_ALL_SC.
FYI, I'm following Luke's guide to setup the TREX:
Setting up NetWeaver Embedded Search (TREX) for SAP HCM Talent Management EhP4, 5 and 6
Regards

The program ESH_IX_PROCESS_CHANGE_POINTERS is little bit different than regular background job.
It looks like a hang, but this program will keep calling SUBMIT of itself. It takes care of its own scheduling based on parameters you provide.
It will finish only after 'Exit processing after [hours]' you gave in selection screen.
Infact its not struck at 'Indexing object type: HRTMC_REL_S_JF_450'
It says that is the last index it worked on.
If it finds change pointers to any other object, it will index them and add a message at the end of job log saying 'Indexing object type: xxxxxx'. Make a change in org and monitor this job to validate this.
You see the job 'on hold', 'SLEEP' because it will wait for a while before it start checking for change pointers again. This duration is based on 'Delay[seconds]' parameter you specified in selection screen.
I thing your problem is that change pointers are not being generated properly which is the task of program RPTMC_CREATE_CHANGEPOINT_AUTH.
Thanks,
Nag

Search Material - No Results Found after Embedded Search is configured

Hello Experts,
We have configured Search connector for Material using Embedded Search . The Search connectors are active after indexing . We have created a material using the Create CR process and we could see the approved material in MM03/ MARA table . But when I search for the material in NWBC ,it is not showing the existing material . Let me know if there is anything we could have missed.
Thanks.

Yes the report ESH_TEST_SEARCH returns no material.
So should I suspend the indexing and reschedule with with real time indexing ? I am not sure whether we choose real time indexing in the first time.
What about the authorizations, I see USER_AUTHORITY object is activealready.
Thanks

TREX documentation - Embedded Search

Hi everyone,
We are implemeting TREX on SAP CRM 7.
I am looking for some customizing documents on SAP sites but cannot really understand what the difference between TREX, Embedded Search and Enterprise Search. Are those different functionnalities? Are they dependant of TREX implementation?
Any tips about TREX/CRM will be appreciated,
Regards,
Anaïs

Hi Anais,
SAP Enterprise Search provides unified, comprehensive, and secure real-time access to enterprise data and information from within and outside of a company.
the Enterprise Search enables a centralized search access to all sources, i.e. users can enter their search requests and receive the search results through a single browser-based user interface (Search UI).
In TREX search, each source has a separate user interface.
To configure TREX in SAP CRM or Solman please find below link.
Full-Text Search with TREX - SAP IT Service Management on SAP Solution Manager - SCN Wiki
If any concern in configuring Software Agent Framework (SAF), please let me know.
You can also refer below document:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80d3c626-b9f0-2d10-b3a5-e2e7582f3449?overridelayout=true&quicklink=index
Thanks,
Vikas.

Features of TREX embedded search

Hi Experts,
I would like to know if raking is possible in TREX Embedded search. and also can i do an alternate product search, by alternate Product search i mean if there are looking for some product say "XYZ", i might have some other product "ABC" not exactly similar in name but closer by some other parameter like say product type. ?
Thanks!!

we need to re create indexes from scratch again after deleing inconsistent entries.
Thanks
Mani

Delta Indexing

Hi All,
We have created a programme named RSRETDELTAINDEXING by refering SAP note 1003868 - KPRO Delta indexing report. Usually it indexes the delta indexing in search criteria. But presently it is not working.
If we do the full indexing through SAP standerd programme RSTIRIDX it is working. But the full indexing will take much time to index the same.
Can anyone help me out to solve this delta indexing issue..
Regards
Harshavardhan.G

If anyone has same problem in user search (who is who)...i found a solution, that works for me.
After a user changes his properties in his user profile i do the following
IIndexService indexService = (IIndexService)ResourceFactory.getInstance().getServiceFactory().getService(IServiceTypesConst.INDEX_SERVICE);
IIndex i = indexService.getIndex("ume");
IResourceFactory aResourceFactory = ResourceFactory.getInstance();
IResource rsrc = aResourceFactory.getResource(RID.getRID("/ume/users/" + user.getUniqueID() +".usr"), aResourceFactory.getServiceContext());
i.indexDocument(rsrc);
This way only the changed user is reindexed.
regards
Alex

Adding custom fields to Embedded Search

Hi All,
I have read the post [here|How to add custom fields to Embedded Search; about adding custom fields to Embedded Search. I am looking to add Employee Subgroup for use in Talent Management (specifically the STVN SuccessionPlanning component) and wanted to know if anyone can expand on the instructions in the link to add this field.
It appears to be part of the HRTMC_PERSON search object connector already and while I've done some IMG configuration the field is showing in SuccessionPlanning, but not displaying any data.
Additionally, I'd be interested in any tips to add information that is not from PA0002 should it be required in the future.
Many thanks,
Luke

Hi Luke,
I am assuming here that your search request fields are based on HRTCM_CENTRALPERSON search template. To enable your search to work on employee subgroup please do the following
1) Check if the HRTMC_PERSON Template extracts the data from Infotype 0001 via SPRO node 'Define Search Models and Change Pointer' Extraction Class is 'CL_HRTMC_SEARCH_READ_PA_INFTY'.
2) Via ESH_COCKPIT, goto Template Modeler and select your custom Software Component and press Edit. Goto roadmap step 5 - Define Requests - where all search request fields are defined. Its using these fields Talent search works.
3) Select the search request e.g. 'SAP_TALENT_NAKISA', it would then show list searchable attributes in below table. Using 'Add' button select path for PERSK so that it can searched.
It would look like this once selected
OBJID(REL_CP_P)->HRTMC_REL_CP_P_209.REL_CP_P(REL_CP)->HRTMC_PERSON.OBJID->HRTMC_PERSON.ORG_ASSIGNMENT
4) In step SPRO 'Define Search Requests and Search Field Names' , define Employee subgroup field with AliasSearchField = PERSK since thats what is defined in roadmap step 5.
Hope it helps!
Regards,
Ricky Shah

Embedded Search - no delta Indexing

Similar Messages

Maybe you are looking for