Name Type in Oracle Fusion HCM

Introduction

In Oracle Fusion HCM, Name Type is a foundational configuration that directly impacts how employee names are captured, displayed, and used across business processes. In real implementations, especially in global organizations, managing multiple name formats (legal, preferred, local language) becomes critical for compliance, reporting, and employee experience.

As a consultant, you will frequently encounter scenarios where clients want different name representations—for example, legal names for payroll and statutory reporting, and preferred names for internal communication tools. This is where Name Type in Oracle Fusion HCM plays a key role.

What is Name Type in Oracle Fusion HCM?

A Name Type defines different variations of a person’s name stored in the system. Oracle Fusion allows multiple name records per employee, each categorized by a name type.

Common Name Types:

• Global Name – Standard name used across applications
• Legal Name – Official name used for compliance and payroll
• Preferred Name – Informal name used in communication
• Local Name – Name in regional/language-specific format

Each person can have multiple name types, but one is typically marked as primary for system usage.

Key Features of Name Type

1. Multiple Name Storage

Oracle Fusion supports storing multiple names per employee, each with a defined purpose.

2. Legislative Support

Different countries require different name formats. Name Types help meet localization requirements.

3. Effective Dating

Name changes (e.g., after marriage) can be tracked using effective dates.

4. Integration Support

Name Types are used in:

• Payroll processing
• BI reports
• Integrations (OIC, HDL, REST APIs)

5. Flexible Display

Applications can be configured to display:

• Preferred name in UI
• Legal name in reports

Real-World Business Use Cases

Use Case 1: Global Organization with Multi-Country Employees

A US-based company operating in Japan needs:

• Legal name (English) for payroll
• Local name (Kanji) for local compliance

👉 Solution:

• Configure Legal Name and Local Name
• Assign appropriate legislative data group

Use Case 2: Employee Experience Enhancement

Employees prefer short names or nicknames internally.

👉 Example:

• Legal Name: Ramesh Kumar Reddy
• Preferred Name: Ramesh

👉 Solution:

• Enable Preferred Name
• Configure UI to display Preferred Name in directories

Use Case 3: Name Change Tracking

After marriage, an employee updates their legal name.

👉 Solution:

• Create a new Legal Name record with a future effective date
• Maintain history for audit

Configuration Overview

Before configuring Name Types, ensure the following setups are in place:

Step-by-Step Configuration in Oracle Fusion HCM

Step 1 – Navigate to Name Type Setup

Navigation Path:

Navigator → Setup and Maintenance → Search Task: Manage Person Name Types

Step 2 – Create Name Type

Click on Create

Enter the following details:

👉 Consultant Tip: Always align Name Types with business requirements and legislative needs.

Step 3 – Configure Name Formats

Navigation Path:

Navigator → Setup and Maintenance → Manage Person Name Formats

Define:

• Display order (First Name, Last Name)
• Format masks

Example:

Step 4 – Assign Name Type Usage

Ensure Name Types are:

• Available in Person Management
• Enabled in Hire/Manage Worker flows

Step 5 – Save Configuration

Click Save and Close

Testing the Setup

Scenario: Adding Preferred Name for Employee

Navigation:

My Client Groups → Person Management → Search Employee

Test Steps:

1. Open employee record
2. Go to Names section
3. Click Add Name
4. Select Name Type = Preferred Name
5. Enter:
   • First Name: Ramesh
   • Last Name: Reddy
6. Save

Expected Results:

• Preferred name appears in UI (if configured)
• Legal name remains unchanged
• Reports reflect correct name based on configuration

Validation Checks:

• Check Person Details UI
• Run OTBI report to verify name fields
• Validate integration payload (if applicable)

Architecture / Technical Flow

From a technical perspective, Name Types are stored in HCM tables and exposed through APIs.

Key Components:

• PER_PERSON_NAMES_F
• PER_ALL_PEOPLE_F

Integration Flow:

1. Name data created in UI or HDL
2. Stored in database tables
3. Exposed via:
   • REST APIs
   • OTBI
   • BIP reports

Example: HDL File for Name Type

👉 Consultant Insight: Always include NameType in HDL loads to avoid data inconsistency.

Common Implementation Challenges

1. Missing Name Type in UI

Cause:
Not enabled in configuration

Solution:
Verify setup in “Manage Person Name Types”

2. Incorrect Name Display

Cause:
Improper format configuration

Solution:
Review “Manage Person Name Formats”

3. Integration Issues

Cause:
NameType not mapped correctly

Solution:
Update mapping in OIC or middleware

4. Duplicate Name Records

Cause:
Improper HDL loads

Solution:
Use MERGE instead of INSERT

Best Practices

1. Standardize Name Types

Define clear usage:

• Legal → Payroll
• Preferred → UI
• Global → Default

2. Use Effective Dating Properly

Maintain history for:

• Compliance
• Audit

3. Align with Localization Requirements

Different countries have:

• Different name formats
• Different legal requirements

4. Validate in Reports

Always test:

• OTBI reports
• BIP outputs

5. Integration Readiness

Ensure:

• NameType is included in API payloads
• Mapping is consistent across systems

Frequently Asked Questions (FAQs)

1. Can an employee have multiple name types in Oracle Fusion?

Yes, an employee can have multiple name types such as Legal, Preferred, and Global. Each serves a different purpose.

2. Which name type is used in payroll processing?

Typically, Legal Name is used for payroll and statutory reporting.

3. Can we control which name appears in UI?

Yes, through configuration and personalization, you can display Preferred Name or Global Name in UI.

Summary

Name Type in Oracle Fusion HCM is not just a basic configuration—it is a critical component that impacts compliance, reporting, integrations, and user experience.

From a consultant’s perspective, proper design and configuration of Name Types can:

• Avoid compliance issues
• Improve employee experience
• Ensure accurate reporting
• Simplify integrations

In real implementations, overlooking Name Types often leads to downstream issues in payroll, reporting, and external systems. So always treat this setup as part of your core HCM data model design.

For deeper reference, always consult Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html