3760915 - The system return unexpected Japanese name ranking without space after enabling Enhance People Search

• After enabling “Enable Enhanced People Search in the Global Header and the Directory Search”, Japanese name search results differ from previous behavior.
• Searching a two‑kanji full name without a half‑width space may not rank the exact full name at the top.
• Entries with only one of the queried kanji in the last name can appear above expected combined matches.
• Adding a half‑width space between family and given name changes the result order.

SAP SuccessFactors HCM Core

1. Enable “Enable Enhanced People Search in the Global Header and the Directory Search”.
2. The first issue is in Global Header or Directory Search, enter a Japanese name as a single two‑kanji string (no space).=>Observe that the exact full name does not rank first and results prioritize entries matching a single kanji in the last name.
3. The second issue is in Global Header or Directory Search, enter a Japanese full name without space).=>the exact full name won't return at the top 

As confirmed with our engineering team, the first issue is caused by ES tokenization, while the second issue is caused by ES scoring configuration. 

For the first issue, an enhancement has been included in the 2611 Release. After this enhancement, when user search with Japanese name as a single two‑kanji string (no space),the exact full name will returns at the top.

For the second issue, our engineering team has confirmed this is a defect and plan to deliver the fix in 4th June.

• refer to: KBA 2475303 - Change Display Language

enhanced people search, directory search, japanese, kanji, tokenization, scoring, ranking, no space, half‑width space, full name, global header search, rebuild company index, scheduled job manager, search index, elasticsearch , KBA , LOD-SF-PLT-SRH , Search , Known Error