EIT in Oracle Fusion HCM Guide

Introduction

EIT in Oracle Fusion HCM (Extra Information Types) is a commonly used feature in real-world implementations when standard fields are not sufficient to capture business-specific data. In almost every Oracle Fusion HCM project, clients come with unique requirements—such as storing visa details, employee certifications, asset allocations, or region-specific compliance data—that cannot be handled using seeded fields.

As a consultant, understanding how to design and configure EITs effectively is critical, especially when dealing with extensions in Core HR, Benefits, or Talent modules.

What is EIT in Oracle Fusion HCM?

Extra Information Types (EITs) are used to store additional, user-defined information that is not available in standard Oracle Fusion HCM data models.

Think of EIT as:

• A custom extension layer
• Used to capture non-standard attributes
• Attached to business objects like Person, Assignment, Job, Position, etc.

Example:

A company wants to store:

• Passport details
• Laptop serial number
• Medical insurance ID

These are not available as standard fields → EIT is used.

Key Features of EIT in Oracle Fusion HCM

1. Flexibility

• Allows adding custom fields without changing core tables
• Supports multiple data types (Text, Number, Date)

2. Context-Based Data Storage

• Data is stored using contexts
• Each context represents a logical grouping

3. UI Integration

• Appears directly in the Fusion UI under “Extra Information” sections

4. Secure Data Handling

• Controlled via role-based security

5. No Coding Required

• Configuration-based approach using Flexfields

Real-World Business Use Cases

Use Case 1: Employee Visa Details

A global company needs to track:

• Visa type
• Expiry date
• Country of issue

EIT is created under Person object.

Use Case 2: Asset Allocation Tracking

HR wants to track:

• Laptop ID
• Mobile device assigned
• Issue date

EIT attached to Assignment level

Use Case 3: Employee Certifications

A consulting company tracks:

• Certification name
• Validity
• Issuing authority

EIT used under Person Profile

Configuration Overview

Before creating EIT, ensure:

Step-by-Step Configuration in Oracle Fusion HCM

Step 1 – Navigate to Flexfield Setup

Navigation:

Navigator → Setup and Maintenance →
Search Task: Manage Descriptive Flexfields

Step 2 – Search for Relevant Object

Examples:

• Person EIT → PER_PERSON_EIT_EFF
• Assignment EIT → PER_ASG_EIT_EFF

Select the appropriate flexfield.

Step 3 – Create Context (EIT Structure)

• Click on Edit
• Go to Contexts
• Add new context

Example:

• Context Code: PASSPORT_DETAILS
• Name: Passport Details

Step 4 – Add Segments (Fields)

Add fields under the context:

Step 5 – Configure Display Properties

• Set display type (Text box, Date picker)
• Enable required fields if needed

Step 6 – Save and Deploy

Click:

• Save
• Deploy Flexfield

⚠️ Deployment is mandatory for UI visibility.

Testing the Setup

Step 1 – Navigate to Employee Record

Navigator → My Client Groups → Person Management

Step 2 – Search Employee

Open employee profile.

Step 3 – Access Extra Information Section

• Scroll to Extra Information
• Select your context (e.g., Passport Details)

Step 4 – Enter Test Data

Example:

• Passport Number: A1234567
• Expiry Date: 31-Dec-2030

Step 5 – Save and Validate

Check:

• Data saved successfully
• Fields visible correctly
• No validation errors

Architecture / Technical Flow

EIT is technically implemented using:

• Descriptive Flexfields (DFF)
• Stored in backend tables like:
  • PER_PERSON_EIT
  • PER_ASSIGNMENT_EIT

Flow:

1. Context created → Defines structure
2. Segments created → Defines fields
3. Data entered → Stored in EIT tables
4. Retrieved via UI / OTBI / BI Reports

Common Implementation Challenges

1. Wrong Object Selection

Choosing Person vs Assignment incorrectly leads to data inconsistency.

2. Missing Deployment

Changes won’t reflect until flexfield is deployed.

3. Performance Issues

Too many segments can slow UI performance.

4. Security Issues

Users unable to view EIT due to role restrictions.

5. Reporting Complexity

EIT data requires special joins in BI reports.

Best Practices from Real Projects

1. Always Validate Business Requirement

Don’t create EIT if:

• Standard field exists
• Could be handled via DFF already available

2. Use Meaningful Context Names

Avoid generic names like:

• CONTEXT1
  Use:
• VISA_DETAILS
• ASSET_TRACKING

3. Limit Number of Fields

Keep segments minimal to avoid UI clutter.

4. Plan Reporting Early

Ensure:

• BI team knows about EIT structure
• Proper joins are defined

5. Use Consistent Naming Convention

Example:

• XX_COMPANYNAME_FIELD

Frequently Asked Interview Questions

1. What is EIT in Oracle Fusion HCM?

EIT is used to store additional custom information not available in standard fields.

2. Difference between EIT and DFF?

EIT is implemented using DFF but specifically for extra information sections.

3. Where is EIT data stored?

In backend tables like PER_PERSON_EIT.

4. Can EIT be reported in OTBI?

Yes, but requires proper configuration.

5. What is a context in EIT?

A logical grouping of segments.

6. Can we make fields mandatory?

Yes, through segment configuration.

7. Is coding required for EIT?

No, it is configuration-based.

8. Can EIT be migrated?

Yes, using HDL or configuration packages.

9. Difference between EIT and KFF?

EIT is flexible user-defined data, while KFF is structured accounting framework.

10. Can EIT impact performance?

Yes, if overused or poorly designed.

Real Implementation Scenario

In one implementation for a Middle East client:

• Requirement: Track employee Iqama (residency permit)
• Solution:
  • Created EIT under Person
  • Fields:
    • Iqama Number
    • Expiry Date
    • Sponsor Name
• Integrated with alerts to notify before expiry

This reduced compliance risk significantly.

Expert Tips

• Always align EIT design with future integrations
• Avoid duplication across multiple EITs
• Document each EIT clearly for support teams
• Test with multiple roles for visibility issues

Summary

EIT in Oracle Fusion HCM is a powerful feature that allows organizations to extend the standard data model without customization. It plays a crucial role in handling real-world business requirements that vary across industries and geographies.

A well-designed EIT solution ensures:

• Clean data capture
• Better reporting
• Smooth user experience

However, improper design can lead to:

• Performance issues
• Reporting challenges
• Maintenance complexity

As a consultant, your focus should always be on minimal, meaningful, and scalable EIT design.

FAQs

1. When should I use EIT instead of standard fields?

Use EIT only when the requirement cannot be fulfilled using existing fields.

2. Can EIT be used in integrations?

Yes, EIT data can be extracted using BI, HDL, or APIs.

3. Is EIT available across all modules?

Primarily used in HCM, but conceptually similar structures exist in other modules.

Oracle Documentation

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