How I Identified 45 Configuration Gaps in an Oracle HCM Implementation — A Structured Approach

During a recent Oracle Fusion HCM implementation, I led a gap analysis that surfaced 45 configuration issues between the client's legacy system and Fusion. Here is the structured approach that made it possible to find all 45 — not just the obvious ones.

The Framework — Four Gap Categories

Category	Description	Gaps Found
Functional	Business process exists in legacy, not in Fusion	18
Configuration	Feature exists but not configured to match requirement	14
Data	Data cannot be migrated cleanly without transformation	9
Integration	Third-party system connection not supported out of the box	4

Step-by-Step Process

1. Workshop each module separately — do not try to cover all modules in one session. Absence alone can take half a day.
2. Use the Oracle Fusion standard process flow as your baseline, not the legacy system. Map legacy → Fusion, not Fusion → legacy.
3. Score each gap by impact (High / Medium / Low) and effort to resolve (Easy / Medium / Complex).
4. Document resolution options — not just "gap exists" but specifically: configure, extend, workaround, or accept.
5. Get sign-off on each gap resolution before build begins.

✦ The most commonly missed gaps are in Payroll element configurations and Absence accrual rules. Always run a dedicated session for each of these — they are deceptively complex.

Output Format

Maintain a living gap log in Excel with columns: Gap ID, Module, Description, Impact, Effort, Resolution Type, Owner, Status. Update it weekly during the build phase — gaps evolve as you configure.

Migrating to Oracle Redwood UI — A Practical Checklist from the Field

Oracle's Redwood UI is the new standard for Fusion HCM. If your organization is still on the classic UI, migration is inevitable. Here is the practical checklist I used — tested against a real implementation.

Phase 1 — Audit Your Current Configuration

• List every custom page layout and flexfield configuration
• Identify personalizations that will not carry over automatically
• Document all custom BIP reports that display within HCM pages
• Note any third-party integrations that depend on classic UI URLs

Phase 2 — Enable Redwood in Sandbox

Navigate to Setup and Maintenance → Manage Administrator Profile Values. Search for the profile option HCM_EXPERIENCE_DESIGN_MODE and set it to REDWOOD at the Site level — in Sandbox only first.

✦ Never enable Redwood in Production before completing a full regression test in Sandbox. Some workflows behave differently, especially absence and performance forms.

Phase 3 — Test High-Traffic Pages First

Page	Test Focus	Risk Level
My Team → Absence	Absence request flow end-to-end	High
Performance → Goal Setting	Goal creation and approval chain	High
Payslip view	Rendering and download	Medium
Learning → My Courses	Course launch and completion	Medium
Directory search	Search results and person card	Low

Phase 4 — Promote to Production

After sign-off in Sandbox: enable Redwood at Site level in Production during a low-traffic window. Prepare a rollback plan — you can revert the profile option if critical issues arise.

The Biggest Lesson

The technical switch takes minutes. The people side takes weeks. Invest in quick reference cards and short demo videos for end users — these reduce helpdesk tickets by more than any technical preparation.