PUBLIC Document Version: 1H 2022 – 2022-05-20 © 2022 SAP SE or an SAP affiliate company. All rights reserved. Implementing People Search THE BEST RUN Content 1 Change History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2 People Search Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3 People Search Terminologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4 Enabling People Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 5 Setting Up People Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.1 Enabling Fuzzy Search in People Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.2 Hiding Job Title in People Search and Organization Charts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 5.3 Showing External Users in People Search Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.4 Showing Inactive Employees in People Search Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.5 Showing Latest Employee Photos in People Search Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 6 Universal People Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 6.1 Autocomplete Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Supported Modules for Autocomplete Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Search Criteria for Autocomplete Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Configuring Role-Based Permissions to Allow Logged in User to View Certain Employee Information in Autocomplete Search Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Deactivating Autocomplete Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 6.2 Advanced Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Supported Modules for Advanced Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Configuring Search Criteria for Advanced Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Configuring Role-Based Permissions to Allow Logged In User to View Certain Employee Information in Advanced Search Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 7 Global Header People Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 7.1 Prerequisites and Limitations of People Search in the Global Header. . . . . . . . . . . . . . . . . . . . . . . . . . . 43 7.2 Configuring People Search in Global Header. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Configuring People Search in the Global Header to Allow Searching by Additional Keywords. . . . . . . . 44 Configuring People Search in the Global Header to Hide Information About Multiple Employments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Configuring People Search in the Global Header to Open Quickcard from Search Results. . . . . . . . . . 47 2 PUBLIC Implementing People Search Content 1 Change History Learn about changes to the documentation for People Search in recent releases. 1H 2022 Type of Change Description More Info Added We added a new topic to tell administra­ tors how to enable People Search. Enabling People Search [page 8] Added We added a new topic to list all terminol­ People Search Terminologies [page 7] ogies about the People Search that you might feel useful when reading this guide. Changed Autocomplete Search [page 15] We updated this topic to add the infor­ mation about the keyword limit of Auto­ complete Search. It now supports searching for an employee name with at most four keywords. (The keywords here refer to names such as first name, middle name, last name, etc.) The user query that contains more than four words is re­ garded as invalid input, thus no search results is returned. Changed We also updated this topic to add the in­ formation about the four keywords limit of Advanced Search. Advanced Search [page 30] Changed We also updated this topic to add the in­ formation about the four keywords limit of Global Header People Search. Global Header People Search [page 42] Description More Info We added Proxy Now to the list of sup­ ported module pages that have adopted Autocomplete Search. Supported Modules for Autocomplete Search [page 17] 2H 2021 Type of Change December 24, 2021 Added October 8, 2021 Changed Implementing People Search Change History We updated the brief introduction of Peo­ People Search Overview [page 5] ple Search features to the latest. PUBLIC 3 Type of Change Description More Info Changed We added a new bullet to demonstrate the logic for showing formal name. Autocomplete Search [page 15] Changed We updated the pages that have newly adopted Autocomplete Search in this re­ lease. Supported Modules for Autocomplete Search [page 17] Added We added a new topic to briefly introduce Advanced Search [page 30] the Advanced Search. Added We added a new topic to list all the mod­ ules that have adopted the Advanced Search. Supported Modules for Advanced Search [page 31] Added We added a new topic to list all the sup­ ported search criteria on the search widget of Advanced Search. Configuring Search Criteria for Advanced Search [page 32] Added We added a new topic to tell administra­ tors about how to set up corresponding role-based permissions to help users see the wanted employee information in a search result of the Advanced Search. Configuring Role-Based Permissions to Allow Logged In User to View Certain Em­ ployee Information in Advanced Search Results [page 38] Added We added a new topic to tell administra­ tor how to display customizable fields on the search widget of the Advanced Search. Configuring Customizable Fields on Ad­ vanced Search Widget [page 37] Changed We added a new bullet to demonstrate the latest logic change for showing for­ mal name and formatted name. Global Header People Search [page 42] 4 PUBLIC Implementing People Search Change History 2 People Search Overview SAP SuccessFactors builds a complete set of people search features to improve your search experience. Highlights of People Search People Search allows users to find employees across the organization. Currently, you can: ● search for employees in the search box that has adopted Autocomplete Search on certain module pages. ● search for employees with the search widget of Advanced Search. ● search for employees in the search box at the global header. Remember Some other modules have also invented distinct people search features, such as Candidate Search, Directory Search, and Talent Search, to help users find target employees based on their own module logics. Apart from People Search, you can also trigger specific tasks by typing relevant actions in the search box at the global header. Find more details in Action Search. Related Information Universal People Search [page 15] Implementing People Search People Search Overview PUBLIC 5 Global Header People Search [page 42] 6 PUBLIC Implementing People Search People Search Overview 3 People Search Terminologies List all frequently used search terminologies to help you better understand the work logic of People Search. Term Abbreviation Definition Employee Central user EC user EC user represents an employee who has access to Employee Central service. non-Employee Central user non-EC user Non-EC user represents an employee who doesn’t have access to Employee Central service. Search criteria N/A Search criteria mean that the search fields or filters leveraged by users to search for target employees. Implementing People Search People Search Terminologies PUBLIC 7 4 Enabling People Search The administrator can grant the role-based permission to the target users to let them search for certain employees with People Search. Prerequisites ● Enable Solr People Search (requires Role-based Permission) is enabled in Provisioning. Remember As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your implementation partner or Account Executive. For any non-implementation tasks, contact Product Support. ● You can manage role-based permissions. Procedure 1. Go to Admin Center Tools and search for Manage Permission Groups. Create a permission group for the users that need to use People Search. Assuming that you've created a permission group named "People Search". Then, all the users listed under this group can search for other employees after you grant the correct role-based permission to the group. Tip For more details about how to create a permission group, you can refer to Permission Groups. 2. Go to Admin Center Tools and search for Manage Permission Roles. Create new permission roles or select existing ones for your People Search users. Provided you want to create a new permission role, choose Create New and open Permission Role Detail screen. Tip For more details about how to create a permission role, you can refer to Permission Roles. 3. In Permission Role Detail screen, choose Permission... and open Permission settings dialogue box. 4. Grant the permission Choose Done. User Permissions General User Permission User Search to the permission role. 5. Still in Permission Role Detail screen, choose Grant this role to... Add... and grant this permission role to the permission group you've configured for People Search users in Step 1. In our example, the group is "People Search". Choose Done. 8 PUBLIC Implementing People Search Enabling People Search After being granted with this permission, the employees who are allocated to the permission group "People Search" can search for certain employees with People Search or other common search functions. 6. Save changes. To find out how long it takes for your above changes to take effect, see details in How Do Permissions Update When User Information Changes? And if the changes don’t take effect within 10 minutes, you could manually refresh the permissions according to Refreshing RBP after Changes in Provisioning Configuration. Results People Search is now ready for you to use. Related Information What Are Role-Based Permissions? List of Role-Based Permissions Implementing People Search Enabling People Search PUBLIC 9 5 Setting Up People Search The administrator can manage the recommended role-based permissions and switches below to configure Universal People Search and the People Search in the global header. Enabling Fuzzy Search in People Search [page 10] The administrator can enable the fuzzy search to let users search for employees with relevant employee names instead of exact matches in People Search. Hiding Job Title in People Search and Organization Charts [page 11] Hide the job title information in People Search results and organization charts if you don't want it to be displayed. Showing External Users in People Search Results [page 12] The administrator can display external users in a search result after relevant switch is configured. Showing Inactive Employees in People Search Results [page 13] The administrator can configure users' role-based permission and let them see inactive employees in a search result. Showing Latest Employee Photos in People Search Results [page 14] The administrator can keep the employee photos in a search result to the newest versions. 5.1 Enabling Fuzzy Search in People Search The administrator can enable the fuzzy search to let users search for employees with relevant employee names instead of exact matches in People Search. Prerequisites ● User Search permission is granted to the users. ● Enable Solr People Search (requires Role-based Permission) is enabled in Provisioning. Remember As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your implementation partner or Account Executive. For any non-implementation tasks, contact Product Support. 10 PUBLIC Implementing People Search Setting Up People Search Context Fuzzy search allows users to find an employee by a search term that has one-character difference from the target employee name. This feature applies to the following scenarios: ● One missing or redundant character. If you search for "Joerg", the results also return "Jörg", and vice versa. ● One misspelled character. If you search for "Justen", the search results also return "Justin", and vice versa. Procedure 1. Go to Admin Center Tools and search for Company System and Logo Settings. 2. Select Enable fuzzy search function for People Search. 3. Choose Save Company System Setting to save your change. Results Previously, People Search only returned exact matches of the search terms. With fuzzy search enabled, users can search for employees with relevant results. 5.2 Hiding Job Title in People Search and Organization Charts Hide the job title information in People Search results and organization charts if you don't want it to be displayed. Prerequisites You have the Administrator Manage System Properties Company System and Logo Settings permission. Context You can use option Hide job title in People Search and org charts (Company Org Chart, Calibration Org Chart, and Succession Org Chart) under Admin Center for People Search and organization charts. Company System and Logo Settings to hide job title information Note This option doesn't impact Position Organization Chart. Implementing People Search Setting Up People Search PUBLIC 11 Procedure 1. Go to Admin Center Company System and Logo Settings . 2. In the Company System Settings section, check option Hide job title in People Search and org charts (Company Org Chart, Calibration Org Chart, and Succession Org Chart). 3. Save your change. Results The job title field is hidden in People Search results, Company Organization Chart, Calibration Organization Chart, and Succession Organization Chart. 5.3 Showing External Users in People Search Results The administrator can display external users in a search result after relevant switch is configured. Prerequisites ● Enable Solr People Search (requires Role-based Permission) is enabled in Provisioning. Remember As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your implementation partner or Account Executive. For any non-implementation tasks, contact Product Support. Context Generally, external users can be displayed in a People Search result after the administrator deselects a switch named Hide External Users from search results in the Admin Center. To use this feature in the module search boxes that have adopted Universal People Search, the target module pages should support returning external users. Procedure 1. Go to 12 PUBLIC Admin Center Tools and search for Company System and Logo Settings. Implementing People Search Setting Up People Search 2. Deselect Hide External Users from search results. 3. Choose Save Company System Setting to save your change. Results Users can now find external users in a search result. 5.4 Showing Inactive Employees in People Search Results The administrator can configure users' role-based permission and let them see inactive employees in a search result. Context As an administrator, you can configure users' role-based permission to display inactive employees in a search result. To use this feature in the module search boxes that have adopted Universal People Search, the target module pages should support returning inactive employees. Remember Future hires are also recognized as inactive employees. Procedure 1. Go to Admin Center Tools and search for Manage Permission Roles. 2. In Permission Role List screen, create new permission roles or select existing ones for your target users. 3. In Permission Role Detail screen, choose Permission... and open Permission settings dialogue box. 4. In Permission settings screen, grant the permission Inactive Employees in the search Administrator Permissions Manage Hires Include to the permission roles you chose. Choose Done. 5. Still in Permission Role Detail screen, choose Grant this role to... Add... and grant this permission role to the permission group you've configured for People Search users. Choose Done. 6. Save changes. To find out how long it takes for your above changes to take effect, see details in How Do Permissions Update When User Information Changes? And if the changes don’t take effect within 10 minutes, you could manually refresh the permissions according to Refreshing RBP after Changes in Provisioning Configuration. Implementing People Search Setting Up People Search PUBLIC 13 Results Users now can see inactive employees in a search result. 5.5 Showing Latest Employee Photos in People Search Results The administrator can keep the employee photos in a search result to the newest versions. Context Once users update their profile photos, it generally takes a while to sync the changes. However, the administrator can contact implementation partner or Product Support to deactivate the photo cache and show the new photos in a search result immediately. Procedure Turn on Company Settings Disable Browser Photo Caching in Provisioning. Results The employee photos are now updated to the latest. 14 PUBLIC Implementing People Search Setting Up People Search 6 Universal People Search As part of People Search, Universal People Search (UPS) helps users find relevant employees across your organization with people search features adopted in modules pages. Highlights of Universal People Search ● Supports searching for employees in module search boxes that have adopted Autocomplete Search. ● Supports searching for employees with certain search criteria by using the search widget of Advanced Search. Autocomplete Search [page 15] As part of Universal People Search, Autocomplete Search is enabled by default in your instance, helping users search for and find relevant employees within your organization by using the search boxes in module pages. Advanced Search [page 30] As part of Universal People Search, Advanced Search helps users search for and find relevant employees within organizations by using the search widget of Advanced Search. 6.1 Autocomplete Search As part of Universal People Search, Autocomplete Search is enabled by default in your instance, helping users search for and find relevant employees within your organization by using the search boxes in module pages. Example For example, you can search for and add people as email recipients by using the search box in this Recruiting page. Implementing People Search Universal People Search PUBLIC 15 Highlights of Autocomplete Search ● Supports finding non-EC (Employee Central) employees with their basic employee info in module search boxes that adopted Autocomplete Search. ● Supports finding EC employees with their alternative names. ● Supports one-character search for the users logged in with simplified Chinese, traditional Chinese, Japanese, and Korean locales. When you sign in with such locales and search for employees with one character in module search boxes that adopted Autocomplete Search, the search results find relevant users automatically. ● Supports for fuzzy search, allowing you to find an employee by a search term that has one-character difference from the target employee name. ● Supports searching for an employee name with at most four keywords. (The keywords here refer to names such as first name, middle name, last name, etc.) The user query that contains more than four words is regarded as invalid input, thus no search results is returned. ● Supports searching for employee names that contain characters with accents, umlauts, diereses, etc. ● Supports showing users' employee info in a search result based on their user types and corresponding data resources. ● Supports displaying multiple employments of an employee. Each employment type has a different indicator. ● Supports displaying searched contingent workers with indicators in a search result by default if the logged-in user has permission to view. ● Supports finding external users as well as internal employees. ● Supports displaying target employee's formal name by default in a search result when user searches for an employee. If no formal name is configured for the target employee, a combination of first name, middle name, and last name is returned. The middle name may not be shown in the result in case no information is maintained for this field. Supported Modules for Autocomplete Search [page 17] List all the module pages that now have adopted Autocomplete Search. Search Criteria for Autocomplete Search [page 20] Users can search for employees with certain search criteria in the Autocomplete Search. Configuring Role-Based Permissions to Allow Logged in User to View Certain Employee Information in Autocomplete Search Results [page 23] 16 PUBLIC Implementing People Search Universal People Search The administrator can configure users' role-based permissions to control the visibility of certain employee information for your target employee in a search result. Deactivating Autocomplete Search [page 29] Autocomplete Search can be deactivated from Provisioning. Parent topic: Universal People Search [page 15] Related Information Advanced Search [page 30] People Search Terminologies [page 7] 6.1.1 Supported Modules for Autocomplete Search List all the module pages that now have adopted Autocomplete Search. Module 360 Reviews - SAP Fiori version Calibration Career Development Planning Continuous Performance Management Data Protection and Privacy Employee Central Implementing People Search Universal People Search Detailed Module Page ● Add Approver ● All new UI pages ● Internal and External Rater Search ● Send Copy ● 360 Executive Review Calibration session ● All CDP People Picker UI5 version pages ● Mentoring > Participant Invitations Request/give Feedback ● Change Audit Reports ● Read Audit Reports ● Subject Information ● Company Structure Overview ● Employment Info ● Job Info ● Job Relationships ● Position Org Chart ● Termination Screen ● Workflow PUBLIC 17 Module Onboarding Org Chart People Profile Performance and Goals Presentations 18 PUBLIC Detailed Module Page ● Buddy Assignment ● Recommended People Assignment Search box ● People Picker in People Profile ● User info block > Live Profile Manager Fields ● Add Modifier ● Ask for Feedback ● Change Document Date ● Delete Document ● Document Transfer with EX option on ● Form Inbox 1.0 ● Get Feedback ● Goal list page ● Goal Management People Picker UI5 Version ● Launch Form ● Manage Document Visibility ● Manage Route Map > "User" Role Configure ● Modify Form Route Map ● Restore Deleted Document ● Route Completed Form ● Route Document ● Route Signature Stage Document All pages Implementing People Search Universal People Search Module Recruiting Management Detailed Module Page ● Admin Center > Manage Onboarding Templates > Add/ edit New Email Template: CC/bcc ● Admin Center > Manage Recruiting Email Templates > Edit Email Template ● Admin Center > Manage Recruiting Groups ● Admin Center > Manage Recruiting Settings > Applicant ● Admin Center > Manage Recruiting Settings > Recruiting Profile Settings > Email Correspondence (Job Owner) Subscriber Settings ● Admin Center > Manage Recruiting Settings > Return ● Admin Center > Mass Delete of Job Requisitions ● Admin Center > Reassign Job Requisitions ● Admin Center > Reassign Offer Approvals ● Admin Center > Recruiting Email Triggers > Select an Email Address Information > Job Owner Email Trigger > Forward as Applicant ● Admin Center > Recruiting Email Triggers > Select an Email Trigger > Online Offer Cancelled by Sender ● Admin Center > Restore Deleted Job Requisitions ● Application > Interviewers Portlet > Set up Interviewers > ● Candidates > Select Candidate > Contact Candidates > Add Interviewer Cc and bcc ● Candidate > Select Candidate in Offer > Take Action > For­ ward > Forward as Applicant ● Candidate > Select Candidate in Offer > Take Action > Of­ fer Letter > ● ○ Send Online Offer ○ Send Email as PDF ○ Send Online Offer with E-signature Enabled Candidate Summary > Forward > Forward to Job Requisi­ tions ● Events > Create New Event > Copy Existing Event ● Events > Create New Event > Create New Event from Blank Template / Families and Roles ● Interview Scheduling > Select Candidate > Assigned to (interviewer) ● Interview Scheduling > Select Candidate > Start Schedul­ ing > Add Interviewer ● ● Offer > Offer Approval > Add Approver Preferences > My Recruiting Team Preferences > Addi­ tional Users ● Preferences > My Recruiting Team Preferences > Default Operator Implementing People Search Universal People Search PUBLIC 19 Module Detailed Module Page ● Requisition > Job Req Summary > Create New > Create from Blank Template ● Requisition > Job Req Summary > Create New > Copy Ex­ isting Job Requisition ● Requisition > Job Req Summary > Create New > Edit Ex­ isting Requisition ● Requisition > Job Req Summary > Edit Existing Requisi­ tion > Add Additional Users (Team Recruiting) ● Requisition > Job Req Summary > Filter Options > User Fields for Operators Rewarding Role-Based Permission ● Benefits ● Rewards and Recognition > Nomination ● Data Privacy Statement > Search External User ● Manage Permission Groups > Team View field ● Set DPCS Statement Status > Search External User Succession All pages User ProxyUser Proxy Proxy Now user search Restriction Some module pages still run with old search behavior, pending for UX redesign and the adoption of Autocomplete Search. 6.1.2 Search Criteria for Autocomplete Search Users can search for employees with certain search criteria in the Autocomplete Search. In the Autocomplete Search, you can search for employees with certain search criteria across your organization. For customers that have enabled the Employee Central, some additional criteria can be used when looking for target employees. Search Criteria Checklist Criteria Type Basic employee info 20 PUBLIC Detailed Criteria Name ● First Name ● Last Name ● Middle Name ● Nick Name ● User Name ● Email Note Default search criteria of Autocomplete Search. Implementing People Search Universal People Search Criteria Type Employee Central names & Person ID Ex­ ternal Detailed Criteria Name ● ● Employee Central names Note These search criteria are only available ○ Display Name for the companies that have enabled the ○ Display Name Alt1 Employee Central. ○ Display Name Alt2 ○ First Name Alt1 ○ First Name Alt2 ○ Formal Name ○ Formal Name Alt1 ○ Formal Name Alt2 ○ Last Name Alt1 ○ Last Name Alt2 ○ Middle Name Alt1 ○ Middle Name Alt2 ○ Partner Name ○ Partner Name Prefix ○ Preferred Name ○ Second Last Name Tip For more details on how to search for employees with Employee Central names, administrators can read Ena­ bling Employee Central Name Fields of Autocomplete Search [page 22]. Person ID External Remember The prerequisite of using the listed search criteria in Autocomplete Search is that administrators have configured these criteria in Succession Data Model. Related Information Configuring Role-Based Permissions to Allow Logged in User to View Certain Employee Information in Autocomplete Search Results [page 23] Implementing People Search Universal People Search PUBLIC 21 6.1.2.1 Enabling Employee Central Name Fields of Autocomplete Search The administrator can allow users to search for employees by their alternative name fields with a new Admin Center switch enabled. Prerequisites ● You've enabled Employee Central in your instance. ● Enable Solr People Search (requires Role-based Permission) is enabled in Provisioning. Remember As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your implementation partner or Account Executive. For any non-implementation tasks, contact Product Support. ● You've configured Employee Central name fields in Succession Data Model. Context As an administrator, you can allow users to search for employees by the following alternative name fields in addition to basic name fields in Autocomplete Search: ● Display Name ● Display Name Alt1 ● Display Name Alt2 ● First Name Alt1 ● First Name Alt2 ● Formal Name ● Formal Name Alt1 ● Formal Name Alt2 ● Last Name Alt1 ● Last Name Alt2 ● Middle Name Alt1 ● Middle Name Alt2 ● Partner Name ● Partner Name Prefix ● Preferred Name ● Second Last Name 22 PUBLIC Implementing People Search Universal People Search Procedure 1. Go to Admin Center Tools and search for Company System and Logo Settings. 2. Enable Search People by Employee Central Name Fields. Choose Save Company System Setting. Results Users now can find employees by using their alternative names. Next Steps If users still cannot find employees with their alternative names, you can contact your implementation partner or Product Support to rebuild the employee search index. 6.1.3 Configuring Role-Based Permissions to Allow Logged in User to View Certain Employee Information in Autocomplete Search Results The administrator can configure users' role-based permissions to control the visibility of certain employee information for your target employee in a search result. Context As an administrator, you can allow the logged in user to see certain employee information by granting their corresponding role-based permissions. A search criterion may have two different role-based permissions. One is for Employee Central users, and another is for the users that have no Employee Central enabled in their instances. Basically, we firstly display the search criteria applicable for Employee Central. For now, users can see the following employee information in an Autocomplete Search result: ● Email ● Job Title/Title ● Location ● Middle Name Note Make sure that your searched employee has the corresponding data for the above fields. If no relevant data maintained, no information is returned in a search result. Implementing People Search Universal People Search PUBLIC 23 Procedure 1. Go to Admin Center Tools and search for Manage Permission Roles. 2. Create new or select existing permission roles for your users. Provided you want to create a new permission role to grant the role-based permission, choose Create New and open Permission Role Detail screen. Tip For more details about how to create a permission role, you can refer to Permission Roles. 3. In Permission Role Detail screen, choose Permission... and open Permission settings dialogue box. 4. In Permission settings screen, grant the role-based permissions listed below to the permission role and control the corresponding employee information the logged in user can see. Employee Information Email Employee Information Data Source ○ Employee Central ○ User Management ○ Remember Role-Based Permission Grant the following permissions to the logged in user: ○ View retrieve the data of users from there, then we retrieve the data from User Management. ○ For the company without the HR Information Business Email Address Employee Central, we firstly Employee Central. If no email User Permissions Employee Data For the company that has the information is maintained in EC instance: ○ . Non-EC instance: Permissions Employee Data Employee Profile View User Email . Employee Central, we directly use the employee data stored in User Management. 24 PUBLIC Implementing People Search Universal People Search Employee Information Job Title/Title Employee Information Data Source ○ Job Title - Employee Central ○ Title - User Management Role-Based Permission Grant the following permissions to the logged in user: ○ EC instance: User Permissions Employee Central Effective Dated Entities Title ○ Job Information View Non-EC instance: Permissions User Employee Data Employee Profile Job Title View Tip See details in Display Logic of Job Title and Title [page 26]. Location ○ Employee Central ○ User Management Grant the following permissions to the logged in user: ○ EC instance: User Permissions Employee Central Effective Dated Entities Location ○ Job Information View Non-EC instance: Permissions User Employee Data Employee Profile View . Location . Tip See details in Display Logic of Loca­ tion [page 28]. Middle Name User Management Grant the permission Permissions Employee Data Employee Profile View User Middle Name to the logged in user. 5. Choose Done. Save changes. Results Users now can see configured employee information in an Autocomplete Search result. Implementing People Search Universal People Search PUBLIC 25 Related Information Search Criteria for Autocomplete Search [page 20] 6.1.3.1 Display Logic of Job Title and Title Learn the display logic behind Job Title and Title fields in the Universal People Search. When you use Universal People Search in Org Chart or on other module pages, the Job Title or Title information is included in the search results. And this title-related information is determined by the following factors: ● Permissions granted to the logged in user to view the title-related information. ○ Permission to view EC job title information under Information Job Title Employee Central Effective Dated Entities Job (only for the companies that use SAP Employee Central). ○ Permission to view title information under Employee Data Employee Profile Title . ● Job Title and Title data is maintained for the searched user. Display Logic The display logic differs between the companies that have the SAP Employee Central or not. For the company that has the EC product, it has two kinds of users, such as the EC user and non-EC user. EC user has the EC authorizations and displays the Job Title by default. And the non-EC user is the user who doesn’t have the EC authorizations and displays the Title info. While for the company without the EC product, only Title info is displayed. 26 PUBLIC Implementing People Search Universal People Search You can refer to the following flow charts for logic details: Logic for the Company with the EC Product - EC User Logic for the Company with the EC Product - Non-EC User Note The logic for the company without the EC product is same as the non-EC case in the second figure. If unexpected information is displayed in the search result, we kindly recommend checking your data model in case you mapped the Job Title or Title information of the user you search into other elements. Implementing People Search Universal People Search PUBLIC 27 6.1.3.2 Display Logic of Location Learn the display logic of Location fields in the Universal People Search. When you use Universal People Search in Org Chart or on other module pages, the Location information is included in the search results and is determined by the following factors: ● Permissions granted to the logged in user to view the location information. ○ Permission to view EC location information under Information Location Employee Central Effective Dated Entities Job (only for the companies that use SAP Employee Central). ○ Permission to view location information under Employee Data Employee Profile Location . ● Location data is maintained for the searched user. Display Logic The display logic differs between the companies that have the SAP Employee Central or not. For the company that has the EC product, it has two kinds of users, such as the EC user and non-EC user. EC user has the EC authorizations and displays the Locationinfo under Employee Central Effective Dated Entities by default. And the non-EC user is the user who doesn’t have the EC authorizations and displays the Location info under Employee Data. While for the company without the EC product, the Location info under Employee Data is displayed. You can refer to the following flow charts for logic details: Logic for the Company with the EC Product - EC User 28 PUBLIC Implementing People Search Universal People Search Logic for the Company with the EC Product - Non-EC User Note The logic for the company without the EC product is same as the non-EC case in the second figure. If unexpected information is displayed in the search result, we kindly recommend checking your data model in case you mapped the Location information of the user you search into wrong elements. 6.1.4 Deactivating Autocomplete Search Autocomplete Search can be deactivated from Provisioning. Context Autocomplete Search is installed in your instance by default after the administrator enables SAP SuccessFactors. If you no longer need to use Autocomplete Search, it can be deactivated in Provisioning. Remember As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your implementation partner or Account Executive. For any non-implementation tasks, contact Product Support. Implementing People Search Universal People Search PUBLIC 29 Procedure Turn on Company Settings Disable Universal Person Auto-Complete Search in Provisioning. Results Autocomplete Search is now deactivated in your instance. 6.2 Advanced Search As part of Universal People Search, Advanced Search helps users search for and find relevant employees within organizations by using the search widget of Advanced Search. Users can use Advanced Search to search for employees on certain module pages if SAP SuccessFactors module teams have enabled this search feature on the target pages. Example For example, you can search for and add people as offer approvers by using the search widget in this Recruiting page. 30 PUBLIC Implementing People Search Universal People Search Highlights of Advanced Search ● Supports finding EC (Employee Central) and non-EC employees with certain advanced criteria in module search widgets that adopted Advanced Search. ● Supports showing users' employee info in a search result based on their user types and corresponding data resources. ● Supports for fuzzy search, allowing you to find an employee by a search term that has one-character difference from the target employee name. ● Supports searching for an employee name with at most four keywords. (The keywords here refer to names such as first name, middle name, last name, etc.) The user query that contains more than four words is regarded as invalid input, thus no search results is returned. ● Supports searching for employee names that contain characters with accents, umlauts, diereses, etc. ● Supports displaying searched contingent workers with indicators in a search result by default if the logged-in user has permission to view. ● Supports finding external users as well as internal employees. Supported Modules for Advanced Search [page 31] List all the module pages that now have adopted Advanced Search. Configuring Search Criteria for Advanced Search [page 32] The administrator can configure users' role-based permissions to make certain search criteria visible on the Advanced Search widget. Configuring Role-Based Permissions to Allow Logged In User to View Certain Employee Information in Advanced Search Results [page 38] The administrator can configure users' role-based permissions to control the visibility of certain employee information for your target employee in a search result. Parent topic: Universal People Search [page 15] Related Information Autocomplete Search [page 15] People Search Terminologies [page 7] 6.2.1 Supported Modules for Advanced Search List all the module pages that now have adopted Advanced Search. Product Detailed Module Page Employee Profile ● Directory Search Performance and Goals ● Route Completed Document Implementing People Search Universal People Search PUBLIC 31 Product Detailed Module Page Platform ● GDPR (General Data Protection Regulation) pages Recruiting ● Admin Center > Manage Recruiting Settings > Recruiting Subscriber Settings ● Business Rules ● Events > Create New Event > Copy Existing Event ● Events > Create New Event > Create New Event from Blank Template / Families and Roles ● Events > Edit Existing Events ● Offer > Offer Approval > Add Approver ● Requisition > Job Req Summary > Create new > Copy Ex­ ● Requisition > Job Req Summary > Create new > Create isting Job Req from Blank Template ● Requisition > Job Req Summary > Create new > Edit Exist­ ing Requisition 360 Reviews - SAP Fiori version ● Send Copy ● Add Participant ● 360 Executive Review 6.2.2 Configuring Search Criteria for Advanced Search The administrator can configure users' role-based permissions to make certain search criteria visible on the Advanced Search widget. Context As an administrator, you can allow the logged in users to see certain search criteria by granting their corresponding role-based permissions. A search criterion may have two different role-based permissions. One is for Employee Central users, and another is for the users that have no Employee Central enabled in their instances. Basically, we firstly display the search criteria applicable for Employee Central. Procedure 1. Go to Admin Center Tools and search for Manage Permission Roles. 2. Create new or select existing permission roles for your users. Provided you want to create a new permission role to grant the role-based permission, choose Create New and open Permission Role Detail screen. 32 PUBLIC Implementing People Search Universal People Search Tip For more details about how to create a permission role, you can refer to Permission Roles. 3. In Permission Role Detail screen, choose Permission... and open Permission settings dialogue box. 4. In Permission settings screen, grant the role-based permissions listed below to the permission role and control the corresponding search criteria the logged in users can see. Search Criteria Type Search Criteria Name Customer Instance Type Basic search criteria First Name This criterion is displayed by Both types. This criterion is default and needs no more displayed on the Advanced Search widget in the instance configuration. that has enabled or without Employee Central. Middle Name Both types This criterion is displayed by default and needs no more configuration. Last Name Both types This criterion is displayed by default and needs no more configuration. Person ID EC instance only, which means this criterion can only be displayed on the Ad­ vanced Search widget in the instance that has enabled Employee Central. This criterion is displayed by default in EC instance and needs no more configuration. Username Both types Grant the permission Role-Based Permission Permissions Data Employee Employee Profile Username View logged in user. Preferred Name/Nickname Both types ○ Preferred Name - EC in­ stance only ○ User to the Grant the following permis­ sions to the logged in user: ○ EC instance: User Nickname - Non-EC in­ Permissions stance, which means Employee Central this criterion can be dis­ Effective Dated Entities played on the Advanced Personal Information Search widget in the in­ Preferred Name stance without Em­ ployee Central. View ○ . Non-EC instance: User Permissions Employee Data Employee Profile Nickname Implementing People Search Universal People Search View PUBLIC . 33 Search Criteria Type Search Criteria Name Customer Instance Type Role-Based Permission Formal Name EC instance only Grant the permission User Permissions Employee Central Effective Dated Personal Entities Information View user. Email Both types Formal Name to the logged in Grant the following permis­ sions to the logged in user: ○ EC instance: User Permissions Employee Data Information HR Business View Email Address ○ . Non-EC instance: User Permissions Employee Data Employee Profile Email Hire Date From/Hire Date To Both types View . Grant the permission Permissions User Employee Data Hire Date View to the logged in user. Advanced search criteria Division Both types Grant the following permis­ sions to the logged in user: ○ EC instance: User Permissions Employee Central Effective Dated Entities Job Information Division ○ View . Non-EC instance: User Permissions Employee Data Employee Profile Division 34 PUBLIC View . Implementing People Search Universal People Search Search Criteria Type Search Criteria Name Customer Instance Type Role-Based Permission Location Both types Grant the following permis­ sions to the logged in user: ○ EC instance: User Permissions Employee Central Effective Dated Entities Job Information Location ○ View . Non-EC instance: User Permissions Employee Data Employee Profile Location Department Both types View . Grant the following permis­ sions to the logged in user: ○ EC instance: User Permissions Employee Central Effective Dated Entities Job Information Department ○ View . Non-EC instance: User Permissions Employee Data Employee Profile Department View User Role Both types This criterion is displayed by default and needs no more configuration. National ID EC instance only Grant the permission Permissions Data User Employee HR Information National Id Card View the logged in user. Implementing People Search Universal People Search . PUBLIC to 35 Search Criteria Type Search Criteria Name Customer Instance Type Role-Based Permission Groups Both types Grant all the following per­ missions to the logged in user: Tip ○ The administrator can consult implementation Administrator Manage Permissions partner or Product Sup­ Manage User port to avoid security is­ Employee Dynamic sues before using this Groups criterion. ○ . Administrator Manage Permissions Recruiting Manage . Recruiting Groups ○ Administrator Manage Permissions Workflows Manage Workflow Groups Job Code Both types . Grant the following permis­ sions to the logged in user: ○ EC instance: User Permissions Employee Central Effective Dated Entities Job Information Classification ○ Job View . Non-EC instance: User Permissions Employee Data Employee Profile Code Company EC instance only View Job . Grant the permission User Permissions Employee Central Effective Dated Entities Job Information Company View logged in user. Customizable Field 1–15 Both types to the See details in Configuring Customizable Fields on Ad­ vanced Search Widget [page 37]. 5. Choose Done. Save changes. 36 PUBLIC Implementing People Search Universal People Search Results Users now can search for target employees with configured search criteria. Related Information Configuring Role-Based Permissions to Allow Logged In User to View Certain Employee Information in Advanced Search Results [page 38] 6.2.2.1 Configuring Customizable Fields on Advanced Search Widget The administrator can display customizable fields as search criteria on the search widget of Advanced Search. Prerequisites ● You've configured customizable fields in Succession Data Model. Example If you want to display two customizable fields, add the following sample code in your data model. Sample Code <custom-filters> <filter-module id="default"> <standard-element-ref refid="custom01"/> <standard-element-ref refid="custom02"/> </filter-module> </custom-filters> Context You can customize up to 15 additional search fields on the widget of Advanced Search after correct configuration. Implementing People Search Universal People Search PUBLIC 37 Procedure 1. Go to Admin Center Tools and search for Manage Permission Roles. 2. In Permission Role List screen, create new or select existing permission roles for your users. Provided you want to create a new permission role to grant the role-based permission, choose Create New and open Permission Role Detail screen. Tip For more details about how to create a permission role, you can refer to Permission Roles. 3. In Permission Role Detail screen, choose Permission... and open Permission settings dialogue box. 4. In Permission settings screen, grant the permission 1-15 User Permissions Employee Data Customizable Field to the permission role. Choose Done. 5. Save changes. Results The customizable fields are now displayed on the Advanced Search widget. 6.2.3 Configuring Role-Based Permissions to Allow Logged In User to View Certain Employee Information in Advanced Search Results The administrator can configure users' role-based permissions to control the visibility of certain employee information for your target employee in a search result. Context As an administrator, you can allow the logged in users to see certain employee information by granting their corresponding role-based permissions. A search criterion may have two different role-based permissions. One is for Employee Central users, and another is for the users that have no Employee Central enabled in their instances. Basically, we firstly display the search criteria applicable for Employee Central. For now, users can see the following employee information in an Advanced Search result: ● Job Title/Title ● Division ● Department ● Location 38 PUBLIC Implementing People Search Universal People Search ● Status Remember Make sure that your searched employee has the corresponding data for the above fields. If no relevant data maintained, no information is returned in a search result. Procedure 1. Go to Admin Center Tools and search for Manage Permission Roles. 2. Create new or select existing permission roles for your users. Provided you want to create a new permission role to grant the role-based permission, choose Create New and open Permission Role Detail screen. Tip For more details about how to create a permission role, you can refer to Permission Roles. 3. In Permission Role Detail screen, choose Permission... and open Permission settings dialogue box. 4. In Permission settings screen, grant the permission User Search General User Permission Company Info Access to the permission role. 5. Still in Permission settings screen, grant the role-based permissions listed below to the permission role and control the corresponding employee information the logged in user can see. Employee Information Employee Information Data Source Role-Based Permission Job Title/Title Both sources Grant the following permissions to the logged in user: ○ Job Title - EC instance only, which means this employee information EC instance: User Permissions can only be displayed in an Ad­ Employee Central Effective Dated vanced Search result in the in­ Entities stance that has enabled Employee Title Central. ○ ○ Title - Non-EC instance, which ○ Job Information View Non-EC instance: Permissions can be displayed in an Advanced Employee Profile out Employee Central. User Employee Data means this employee information Search result in the instance with­ Job Title View Tip See details in Display Logic of Job Title and Title [page 26]. Autocom­ plete Search and Advanced Search share the same backend logic for these two criteria. Implementing People Search Universal People Search PUBLIC 39 Employee Information Employee Information Data Source Role-Based Permission Division Both sources Grant the following permissions to the logged in user: ○ EC instance: User Permissions Employee Central Effective Dated ○ Entities Job Information Division View . Non-EC instance: Permissions User Employee Data Employee Profile View Department Both sources. This employee informa­ tion can be displayed in an Advanced Search result in the instance that has enabled or without Employee Central. Division . Grant the following permissions to the logged in user: ○ EC instance: User Permissions Employee Central Effective Dated Entities Job Information Department ○ View Non-EC instance: Permissions User Employee Data Employee Profile View Location Both sources . Department . Grant the following permissions to the logged in user: ○ EC instance: User Permissions Employee Central Effective Dated Entities Location ○ Job Information View Non-EC instance: Permissions User Employee Data Employee Profile View . Location . Tip See details in Display Logic of Loca­ tion [page 28]. Autocomplete Search and Advanced Search share the same backend logic for this cri­ terion. 40 PUBLIC Implementing People Search Universal People Search Employee Information Employee Information Data Source Role-Based Permission Status Both sources To display this field in a search result, you can follow the steps listed in Show­ ing Inactive Employees in People Search Results [page 13]. 6. Choose Done. Save changes. Results Users now can see configured employee information in an Advanced Search result. Related Information Configuring Search Criteria for Advanced Search [page 32] Implementing People Search Universal People Search PUBLIC 41 7 Global Header People Search People Search in the global header enables users to search for and find employees across the organization. People Search in the Global Header As part of People Search, Global Header People Search helps users search for and find relevant employees across the organization. Users can click on the search icon located in the page header to expand the search box and do the search. And from search results, users can view searched employees' Quickcards or go to their Employee Profiles for more details. Highlights of Global Header People Search ● Supports finding non-EC (Employee Central) employees with their basic employee info. ● Supports finding EC employees with their alternative names. ● Supports for fuzzy search, allowing you to find an employee by a search term that has one-character difference from the target employee name. ● Supports searching for an employee name with at most four keywords. (The keywords here refer to names such as first name, middle name, last name, etc.) The user query that contains more than four words is regarded as invalid input, thus no search results is returned. ● Supports searching for employee names that contain characters with accents, umlauts, diereses, etc. ● Supports showing users' employee info in a search result based on their user types and corresponding data resources. ● Supports displaying target employee's formal name, instead of formatted name, by default in a search result when user searches for an employee. If no formal name is configured for the target employee, a combination of first name, middle name, and last name is returned. The middle name may not be shown in the result in case no information is maintained for this field. In addition to searching for target employees, you can also trigger specific tasks by typing relevant actions in the Global Header Search box. Find more details in Action Search. Related Information People Search Terminologies [page 7] 42 PUBLIC Implementing People Search Global Header People Search 7.1 Prerequisites and Limitations of People Search in the Global Header Learn about the prerequisite features and current limitations of People Search to determine if it can be used in your system. People Search is enabled by default in all SAP SuccessFactors instances. However, limitations apply to instances under certain conditions. If any of the following conditions apply to your instance, take the appropriate action. ● If you're using SAP Data Encryption by CipherCloud, you shouldn't use the latest version of People Search. Contact Product Support or your implementation partner to have the latest version disabled. You can still use People Search to find people in the global page header but some newer functionality isn't compatible with the older version and can't be used in your instance. ● If you are not using role-based permissions, you can still use People Search to find people in the global page header, but some newer configuration options, such as the ability to search by keywords like job title or location, are not available in your instance. ● If you're using any locale other than traditional Chinese, simplified Chinese, Korean, and Japanese, you need to type two or more characters in order to search a person. Single-character search is possible only in the mentioned four languages. 7.2 Configuring People Search in Global Header Use the configuration guides listed below to manage your People Search features in the Global Header. Configuring People Search in the Global Header to Allow Searching by Additional Keywords [page 44] Change the default behavior of the global People Search so that you can search for people using additional keywords, such as job title, location, department, or division. Configuring People Search in the Global Header to Hide Information About Multiple Employments [page 46] Disable the display of multiple employment information on the organization chart, employee quickcard, and global search results where required for data privacy reasons. If this is considered confidential information in your organization, you can now hide it and only display the person's home or primary employment in the user interface. Otherwise, by default, if you are using Global Assignments or Concurrent Employments in Employee Central, you can view a person's multiple employment records in the user interface. Configuring People Search in the Global Header to Open Quickcard from Search Results [page 47] Change the default behavior of the global People Search so that it opens the employee quickcard when you select a user in search results. Implementing People Search Global Header People Search PUBLIC 43 7.2.1 Configuring People Search in the Global Header to Allow Searching by Additional Keywords Change the default behavior of the global People Search so that you can search for people using additional keywords, such as job title, location, department, or division. Prerequisites ● Role-based permissions are enabled. ● You have the role-based permission Company System and Logo Settings. Context By default, you can only search for people by name (first, middle, last, username). Use this configuration option to allow search by the following characteristics: ● job title ● location ● department ● division Caution This is a company-level setting that applies to all users of People Search, in all roles. People Search does not consider role-based permissions to view this employee data for a target population. Therefore, if you restrict the visibility of this data to certain roles in your system, you should not enable this option for People Search. Procedure 1. Go to Admin Center Tools Company System and Logo Settings . 2. Select the option Search for people by additional keywords such as job title, location, department, or division (requires Role-based Permissions). 3. Click Save Company System Setting to save the change. Results All users with access to People Search can now search for people using other search keywords, such as job title, location, department, or division. 44 PUBLIC Implementing People Search Global Header People Search Example People Search by Job Title People Search by Location Implementing People Search Global Header People Search PUBLIC 45 People Search by Department 7.2.2 Configuring People Search in the Global Header to Hide Information About Multiple Employments Disable the display of multiple employment information on the organization chart, employee quickcard, and global search results where required for data privacy reasons. If this is considered confidential information in your organization, you can now hide it and only display the person's home or primary employment in the user interface. Otherwise, by default, if you are using Global Assignments or Concurrent Employments in Employee Central, you can view a person's multiple employment records in the user interface. Prerequisites ● Global assignments and concurrent employment for Employee Central must be enabled in your system. ● You have the role-based permission for Company System and Logo Settings. Procedure 1. Navigate to the Admin Center Company System and Logo Settings . 2. Deselect the option Show all active employments (for Global Assignment and Concurrent Employment) on Quickcard, Organization Chart, and Global Search results. 46 PUBLIC Implementing People Search Global Header People Search 3. Save your settings. People Search with Multiple Employment Records [page 47] You can use search to find people as well as their employments. 7.2.2.1 People Search with Multiple Employment Records You can use search to find people as well as their employments. Search results show you when a person has multiple assignments in Employee Central. There are icons that indicate whether a person has a concurrent employment or is on a global assignment. From the search result, you can take action on either the person or the employment, as needed. The search also includes contingent workers. For People Profile, the search widget is available for the following UIs: ● Company Structure Overview ● Position Organization Chart ● Fields in Termination Screen ● My Workflow Requests ● Job Info Supervisor field (New Hire, Action UI and Job History) ● Job Relationship "User" field (Search in Job Relationships, New Hire and Job Relationship History) Note For customers with Employee Central, field permissions for the Job Title and Location fields in Job Information must be set to visible for them to be displayed in the search results. For customers without Employee Central, only field permissions for Job Title must be set to visible for them to be displayed in the search results. Parent topic: Configuring People Search in the Global Header to Hide Information About Multiple Employments [page 46] 7.2.3 Configuring People Search in the Global Header to Open Quickcard from Search Results Change the default behavior of the global People Search so that it opens the employee quickcard when you select a user in search results. Prerequisites You have the Company System and Logo Settings permission. Implementing People Search Global Header People Search PUBLIC 47 Context By default, selecting a user in search results navigates to that person's employee profile. Use this configuration option to change the default behavior so that it opens the quickcard instead. Procedure 1. Go to Admin Center Tools Company System and Logo Settings . 2. Select the option Selecting a user from global header search will show the quickcard. 3. Click Save Company System Setting to save the change. Results The behavior of the global People Search changes immediately so that clicking a search result opens the quickcard. To navigate to the employee profile from the quickcard, click the person's name. 48 PUBLIC Implementing People Search Global Header People Search Important Disclaimers and Legal Information Hyperlinks Some links are classified by an icon and/or a mouseover text. These links provide additional information. About the icons: ● ● Links with the icon with SAP) to this: : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements ● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information. ● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct. Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information. Videos Hosted on External Platforms Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP. Beta and Other Experimental Features Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up. The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP. Example Code Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct. Bias-Free Language SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders, and abilities. Implementing People Search Important Disclaimers and Legal Information PUBLIC 49 www.sap.com/contactsap © 2022 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices. THE BEST RUN
