Summary of "Hiring New Employees in Oracle HCM Redwood - Step by Step | Future Proof Trainings"

Purpose / Main Ideas

Demonstrates how to hire a new employee in Oracle HCM Redwood UI and how to fall back to the Classic UI when needed.
Emphasizes required prerequisites and common configuration pitfalls that block hiring (most importantly: legislative data group (LDG) and salary basis/payroll setup).
Shows creation of basic enterprise objects used by hiring transactions: legal entity, legislative data group, business unit, department, job.
Walks through the Redwood “Hire an Employee” flow: what sections to include, which fields are mandatory vs optional, and how to verify the new hire in Person Spotlight.
Notes practical troubleshooting: Redwood can be unstable; admins can toggle Progressive Web App (PWA) settings or use Classic UI; approvals may need to be disabled for training/demo.

Key Concepts and Lessons

Legal entity = legal employer / payroll statutory unit. Create it and set legal address and employer ID if you plan to run payroll.
Legislative Data Group (LDG) = container for country-specific payroll/tax settings (currency, cost allocation structure). An LDG must be created and associated with the legal employer before hiring employees for payroll purposes.
Salary basis / payroll frequency / payroll statutory unit configuration must exist for the legal employer to populate payroll fields during hire. Missing salary basis prevents completing payroll-related hire steps.
Redwood vs Classic UI: some tasks or troubleshooting may require Classic UI. Admins can toggle PWA/profile options; end users usually see whatever UI the admin configures.
Approvals: hiring-related objects or job changes may trigger approval workflows. For training/demo, approvals can be disabled or bypassed to speed testing.
Verification: after hire, use Person Spotlight to review employee personal info, contact/address, manager, assignments, and to add/modify details.

Step-by-step Methodology (actions shown in the video)

Create a legal entity
- Navigate to Manage Legal Entity and create a new record.
- Enter name (example: Applegate Forms LLC), enable legal employer and payroll statutory unit flags.
- Select or create a legal address and enter employer identification number.
- Save and scope the legal entity to your implementation.
Create a Legislative Data Group (LDG)
- Go to Manage Legislative Data Group.
- Choose country (e.g., United States — currency defaults).
- Select the cost allocation structure (e.g., US cost allocation flex instance) as provided by finance.
- Submit and name the LDG (example: Hormel Foods US LDG).
Associate LDG to the legal entity
- Use Manage Legal Entity HCM Information (or Manage Legal Entity > HCM Info).
- Edit the legal employer / payroll statutory unit record and attach the LDG in the Payroll Statutory Unit tab.
- Save/submit.
- Result: avoids the “No legislative data group associated” error when hiring for that legal employer.
If necessary, switch UI or toggle PWA
- If Redwood pages aren’t working, disable PWA/profile option to open Classic UI for certain tasks, then re-enable later.
- Note: some navigation (e.g., New Person > Hire an employee) may route to Classic UI — use My Client Groups > Quick Actions > Hire an employee to access the Redwood hire flow.
Create organizational objects used in hires
- Business Unit (Manage Business Unit) — e.g., Food Service.
- Department (Manage Department) — e.g., Food Safety & Quality Assurance; assign location and manager if required.
- Job (Manage Job) — e.g., HCM Consultant or HCM Senior Consultant; set full-time/regular, standard hours, and legal employers that use the job.
- Watch for approval rules on jobs/departments; disable approvals or ensure approvers are configured for training/demo.
Hire an employee in Redwood UI (navigation)
- My Client Groups > Quick Actions > Hire an Employee (select the Redwood link).
- In “Information to include,” choose which sections to include (email/phone, addresses, legislative info, family/emergency, manager details, payroll relationship, compensation, attachments/comments, etc.), then Continue.
Complete the Redwood hire screens (common required fields and flow)
- When & Why: enter hire date and reason (e.g., hire to fill vacancy), select legal employer (must have LDG attached).
- Business Unit / Department / Job: choose the previously created business unit, department, and job. If using positions, select position (video skipped positions).
- Person details: enter name and national identifier (SSN in US — 9 digits). Save.
- Communication: enter phone and primary email. Save.
- Address: enter home address. Save.
- Legislative info: update marital status, citizenship, armed forces data if required (often optional).
- Assignment (Worker Assignment):
  - Assignment status: Active and payroll eligible.
  - Person type: Employee.
  - Business title, reporting establishment, working-at-home flag, job time basis (full-time), employment type (regular/permanent), salaried vs hourly, weekly hours.
  - Assign manager (line manager) and optionally matrix manager.
- Payroll/compensation:
  - Payroll frequency and salary basis must be present for the selected legal employer. If not configured, payroll fields will not populate.
  - If using a demo legal entity (e.g., US1) that already has salary basis configured, salary basis will appear and you can enter salary (e.g., $78,000 annually) and salary review date.
- Submit the final form to create the worker record.
Verify the hire
- Use Person Spotlight to search for the newly hired employee (example: Sheldon Cooper).
- Open the employee’s record to view personal information, contact details, address (and update if needed), manager and areas of responsibility.
- Use “Show more” to view sensitive fields such as national identifier and other personal info.

Troubleshooting and Practical Tips

“No legislative data group associated” error: create an LDG and attach it to the legal employer.
Missing payroll/salary fields: ensure salary basis and payroll frequency are configured and associated with the legal employer/LDG.
If Redwood UI is unstable, use Classic UI temporarily; admins can toggle PWA setting.
For training/demo: use a default demo legal entity (US1) or a legal entity with full payroll configuration to practice hires.
Disable or bypass approval workflows for jobs/hire transactions during practice to avoid waiting for approvals.
Remember that some navigation elements may route users to Classic UI even when Redwood is preferred.

Examples / Sample Data Used in the Demo

Client enterprise: Hormel Foods
Legal entities: Applegate Forms LLC (created in demo), Applegate Farms, Hormel Corporation
Demo legal entity with full config: US1
Business unit example: Food Service
Department example: Food Safety & Quality Assurance
Jobs: HCM Consultant, HCM Senior Consultant, Recruiter
Manager example: Curtis
Example hired person: Sheldon Cooper
Email/Phone: temporary/demo values used

Speakers / Sources Featured

Primary trainer: Future Proof Trainings instructor (main presenter; unnamed in transcript)
Participants/attendees: several unnamed attendees who provided short interjections (e.g., “Okay”)
Data/entities referenced (not speakers): Hormel Foods, Applegate Forms LLC, US1 demo legal entity, Sheldon Cooper, Curtis

Note: This summary condenses the demo best practices, required configuration items, and step-by-step hire workflow for Oracle HCM Redwood UI. Use it as a checklist when preparing environments for hires or training sessions.