Oracle Fusion HCM Knowledge Hub

  Introduction Data loading is a critical activity for every Oracle HCM implementation. Whether onboarding new employees, updating worker information, managing organizational changes, or performing mass data corrections, organizations rely heavily on HCM Spreadsheet Data Loader (HSDL) to efficiently process large volumes of HR data. While HSDL has long been a powerful data management tool, users often face challenges such as selecting the correct template, mapping columns accurately, validating file structures, and troubleshooting upload errors. These tasks can be complex, especially for occasional users or organizations with numerous business objects and templates. To simplify and modernize the data loading experience, Oracle HCM Cloud 26C introduces the AI-Powered Spreadsheet Data Loader Advisor , an intelligent assistant that guides users through the entire HSDL process using natural language interactions and automated file processing capabilities. What is the Spreadsheet Data L...

  Introduction Managing data security in Oracle Fusion HCM is a critical responsibility for IT Security Managers and HCM Administrators. Whether it's investigating why a manager cannot access employee records, determining which role grants a specific quick action, or resolving access control issues, security troubleshooting can often involve navigating multiple pages, roles, security profiles, and data security policies. To address these challenges, Oracle HCM Cloud 26C introduces the HCM Data Security Assistant , an AI-powered assistant designed to help security administrators quickly understand, analyze, and resolve user access issues through natural language conversations. By leveraging artificial intelligence, the HCM Data Security Assistant provides contextual insights into roles, security profiles, data access permissions, and access control lists (ACLs), significantly reducing the time required to troubleshoot security-related issues. What is the HCM Data Security Assistant?...

✅    Document Lifecycle The standard document lifecycle is: Draft → Ready to Publish → Process Agent Documents → Published ⚙️  Behavior Change After 26B ✅  Before 26B ·  Upload a file ·  Set status to Ready to Publish ·  Manually run ESS Job: Process Agent Documents ·  Status updates to Published ✅  After 26B (New Flow – Automatic Publishing) The ESS job is no longer required . Publishing is now handled automatically. ✅    Step-by-Step Process 1.  Upload File 2.  Click Save as Draft 3.  Close the Tool 4.  Re-open the tool 5.  Change status to Ready to Publish 6.  Close the Tool again 7.  Wait a few minutes 8.  Re-open the tool → ✅  Status will be Published ⚙️  What Happens Behind the Scenes Once marked as Ready to Publish , the platform automatically: ·  Uploads documents ·  Parses and chunks the content ·  Generates vector embeddings ·  Stores embeddings in the F...

✅  Overview When you modify a person name format, the changes are not automatically applied to existing records. ✅  To reflect the updated format, you must run the job set: Apply Name Formats to Person Names, Keywords, and LDAP ✅  Job Set Components This is a parent job set that automatically executes the following child processes: 1.  Apply Name Formats to Person Names 2.  Update Search Person Keywords 3.  Send Personal Data for Multiple Users to LDAP ✅  You only need to run the parent job set ❌  Do NOT run child processes separately ⚙️  How the Process Works ✅  Execution Flow 1.  Step 1 (Sequential) o  Runs: §  ✅  Apply Name Formats to Person Names 2.  Step 2 (Parallel Execution) o  Runs: §  ✅  Update Search Person Keywords §  ✅  Send Personal Data for Multiple Users to LDAP ⚠️  Failure Behavior ·  If Step 1 succeeds but any process in Step 2 fails: o  ✔  Successful ...

  ✅  Update Person Search Keywords – Process Guide ��  Overview Person search keywords are derived from key attributes of: ·  Person records ·  Employment records ·  Profile records These keyword values are stored in the table: ·  PER_KEYWORDS ��  This table is indexed to optimize search performance across the application. ��  How Keywords Are Updated ✅  Automatic Updates ·  When a keyword-related attribute changes (e.g., phone number, language skill): o  An event is triggered o  System services automatically update PER_KEYWORDS ·  When a new person is created: o  Keywords are populated automatically ⚠️  Why You Must Run the Process Even though updates are automatic, the process must still be run periodically because: 1.  Future-dated changes are NOT processed automatically 2.  Ensures recovery from: o  Temporary failures o  Missed event triggers 3.  Guarantees data consistency in PE...