Document of Record in Fusion HCM

Document of Record in Oracle Fusion HCM – Complete Consultant Guide

When working on Document of Record in Oracle Fusion HCM, many consultants initially treat it as just a document storage feature. However, in real implementations, it plays a critical role in compliance, employee lifecycle tracking, and audit readiness. In modern HR systems powered by Oracle Corporation, this feature becomes a structured repository rather than a simple attachment tool.

In this detailed guide, we will break down Document of Record from a functional consultant perspective, including configuration, real-time scenarios, and practical tips from live projects.

What is Document of Record in Oracle Fusion HCM?

A Document of Record (DoR) is a structured way to store employee-related documents within Oracle Fusion HCM.

Unlike basic attachments, DoR provides:

• Categorization
• Controlled access
• Lifecycle tracking
• Association with HR transactions

Key Idea

Think of Document of Record as:

A compliance-ready digital employee file system, where each document is categorized, secured, and auditable.

Key Features of Document of Record

1. Categorized Document Storage

Documents are grouped into types such as:

• Educational Certificates
• Identity Proofs
• Contracts
• Medical Records

2. Role-Based Access Control

• HR can upload sensitive documents
• Employees can upload personal documents
• Managers may have limited visibility

3. Expiry Tracking

• Supports expiry date tracking (e.g., visa, passport)
• Alerts can be configured for renewals

4. Attachment Support

• Upload files (PDF, DOC, images)
• Multiple attachments per record

5. Workflow Integration

• Approval workflows can be attached
• Useful in regulated industries

Real-World Business Use Cases

Use Case 1 – Employee Onboarding (India IT Company)

During onboarding:

• PAN card
• Aadhaar
• Degree certificates

HR uploads these under predefined document types.

👉 Benefit: Ensures compliance with labor laws and audit readiness.

Use Case 2 – Visa and Work Permit Tracking (US/UK Projects)

Employees working onsite:

• Visa documents uploaded
• Expiry date tracked

👉 System sends alerts before expiration.

Use Case 3 – Employee Separation Documentation

During exit:

• Resignation letter
• Clearance forms
• Experience letter

👉 Stored as permanent record for audits.

Configuration Overview

Before using Document of Record, ensure the following setups are completed:

Step-by-Step Configuration in Oracle Fusion

Step 1 – Define Document Types

Navigation:

Navigator → Setup and Maintenance → Search Task →
Manage Document Types

Step 2 – Create Document Type

Enter details:

• Document Type Name: Educational Certificate
• Category: Qualification
• Country: India (optional)
• Enable Attachment: Yes

Important Fields Explained

👉 Tip: Always align document types with business policies.

Step 3 – Assign Security

Ensure correct roles:

• HR Specialist → Full access
• Employee → Limited upload/view
• Manager → Read-only (optional)

Step 4 – Enable Approval (Optional)

If required:

• Configure BPM workflow
• Define approval hierarchy

👉 Example: Background verification documents require approval.

Step 5 – Save Configuration

Click Save and Close

How to Create Document of Record (Transaction)

Navigation:

Navigator → Me → Personal Information →
Documents of Record

Step 1 – Add Document

Click Add

Step 2 – Enter Details

Example:

• Document Type: Passport
• Issue Date: 01-Jan-2022
• Expiry Date: 01-Jan-2032
• Description: Employee Passport Copy

Step 3 – Attach File

Upload:

• Passport PDF

Step 4 – Submit

If approval enabled → goes for approval
Else → auto-approved

Testing the Setup

Test Scenario

Employee uploads a passport document.

Steps:

1. Login as Employee
2. Navigate to Documents of Record
3. Upload passport with expiry date

Expected Results

• Document saved successfully
• Attachment visible
• Expiry date stored
• Notification triggered (if configured)

Validation Checks

• Correct document category
• Role-based visibility
• Approval workflow triggered

Architecture / Functional Flow

Here is how Document of Record works internally:

1. User creates document record
2. System validates document type
3. Attachment stored in content server
4. Workflow triggered (if enabled)
5. Data stored in HCM tables

👉 Key Tables (for reporting consultants):

• PER_DOCUMENTS_OF_RECORD
• PER_DOCUMENT_TYPES

Common Implementation Challenges

1. Incorrect Document Type Setup

Problem:

• Users confused due to poor naming

Solution:

• Use clear naming conventions
  Example: “India – Aadhaar Card”

2. Missing Security Configuration

Problem:

• Employees cannot view documents

Solution:

• Validate role privileges

3. No Expiry Tracking

Problem:

• Compliance issues

Solution:

• Enable expiry date field

4. Duplicate Document Entries

Problem:

• Multiple records for same document

Solution:

• Define governance policy

Best Practices from Real Projects

1. Use Structured Naming Convention

Example:

• Country – Document Type – Version
  👉 “US – Visa – H1B”

2. Enable Expiry Alerts for Compliance

Especially for:

• Visa
• Work permits
• Certifications

3. Restrict Sensitive Documents

• Medical records
• Legal documents

👉 Use role-based security

4. Avoid Overloading Document Types

Keep it manageable:

• 15–25 document types ideal

5. Use Approval Only Where Needed

Avoid unnecessary workflows
👉 Improves performance

Expert Consultant Tips

• Always gather HR policy requirements first
• Align document types with legal compliance
• Validate security during SIT phase
• Include DoR in data migration strategy
• Use BI Publisher reports for audit tracking

Frequently Asked Questions (FAQs)

1. What is the difference between Attachment and Document of Record?

Attachment:

• Simple file upload

Document of Record:

• Structured, categorized, auditable

2. Can employees upload their own documents?

Yes, based on role configuration.
Employees can upload:

• ID proofs
• Certificates

3. Can we track document expiry?

Yes.
You can:

• Enable expiry date
• Configure alerts

Summary

Document of Record in Oracle Fusion HCM is not just a storage feature—it is a compliance-driven document management system.

Key takeaways:

• Structured document categorization
• Secure access control
• Expiry tracking capability
• Integration with workflows

In real implementations, this feature becomes critical for:

• Audits
• Compliance
• Employee lifecycle management

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

This helps align your implementation with latest Fusion release (26A standards) and best practices.