Introduction

Oracle Fusion Applications M&S (Maintenance and Support) is a critical aspect of managing a successful Oracle Cloud implementation. In real-world projects, most failures don’t happen during implementation—they happen after go-live due to poor monitoring, lack of governance, or weak support processes.

In Oracle Fusion Cloud (26A and beyond), Maintenance & Support is not just about fixing issues. It involves proactive monitoring, quarterly update management, performance tuning, security governance, and continuous improvement.

From my consulting experience, organizations that invest properly in M&S reduce production issues by nearly 40% and improve user adoption significantly.

What is Oracle Fusion Applications M&S?

Oracle Fusion Applications M&S refers to the ongoing operational support, maintenance, monitoring, and optimization of Oracle Cloud applications after implementation.

It includes:

• Application Support (HCM, ERP, SCM modules)
• Technical Support (integrations, reports, data loads)
• Quarterly Update Management (26A, 26B, etc.)
• Security & Compliance Monitoring
• Performance Optimization
• Incident and Change Management

Unlike legacy systems, Oracle Fusion is SaaS-based, meaning:

• No infrastructure maintenance
• Automatic updates from Oracle
• Continuous innovation model

However, this also introduces challenges:

• Frequent updates require validation
• Limited backend access
• Dependency on Oracle support channels

Key Features of Oracle Fusion M&S

1. Quarterly Update Model (26A and beyond)

Oracle delivers updates every quarter:

• 26A (January)
• 26B (April)
• 26C (July)
• 26D (October)

Each update includes:

• New features
• Bug fixes
• Security enhancements

2. Environment Strategy

Typical environments:

• Production (PROD)
• Test (TEST)
• Development (DEV)

Updates are first applied to TEST, allowing validation before PROD.

3. Oracle Support (SRs)

Support Requests (SRs) are raised via Oracle Support for:

• Critical issues
• Bugs
• Performance concerns

4. Built-in Monitoring Tools

• Transaction Console (HCM)
• Scheduled Processes
• ESS Job monitoring
• OTBI usage tracking

5. Security & Audit

• Role-based access control
• Audit reports
• Data security policies

Real-World Business Use Cases

Use Case 1: Payroll Failure After Update

A client experienced payroll calculation issues after a 26B update.

Root Cause:
A fast formula behavior changed.

Solution:

• Tested formulas in TEST environment
• Updated logic before PROD rollout
• Created regression test cases

Use Case 2: Integration Failure in OIC Gen 3

An ERP-to-bank integration failed.

Root Cause:
API payload structure changed after update.

Resolution:

• Reviewed integration logs in OIC Gen 3
• Updated mapping
• Re-tested using Postman

Use Case 3: Performance Issue in OTBI Reports

Users reported slow dashboards.

Solution:

• Optimized OTBI queries
• Reduced unnecessary joins
• Scheduled reports instead of real-time execution

Configuration Overview

Before setting up M&S processes, ensure:

Step-by-Step Maintenance & Support Setup

Step 1 – Access Monitoring Tools

Navigation:

Navigator → Tools → Scheduled Processes

Purpose:

• Monitor jobs
• Check failures
• Resubmit processes

Step 2 – Configure Alerts

Navigation:

Navigator → Tools → Alerts Composer

Example:

• Alert when payroll fails
• Alert when integration errors occur

Step 3 – Monitor Transactions

Navigation (HCM):

Navigator → Tools → Transaction Console

Use:

• Track approvals
• Identify stuck workflows

Step 4 – Manage Security

Navigation:

Navigator → Tools → Security Console

Tasks:

• Assign roles
• Review user access
• Audit permissions

Step 5 – Update Testing Setup

Navigation:

Navigator → Setup and Maintenance → Manage Update Configuration

Activities:

• Enable test environment updates
• Review readiness reports
• Identify impacted features

Step 6 – Integration Monitoring (OIC Gen 3)

Navigation:

OIC Console → Integrations → Tracking

Actions:

• Check failed instances
• Replay integrations
• Analyze payload

Testing the Setup

Testing is the most critical part of M&S.

Example Test Case: Employee Hire

Steps:

1. Hire employee
2. Assign salary
3. Run payroll

Expected Results:

• Employee created successfully
• Salary processed
• Payroll completed

Example Test Case: Integration

Payload Example:

Expected Response:

• Status: Success
• Record created in target system

Validation Checklist

• No errors in Scheduled Processes
• Integration logs show success
• Data consistency verified

Common Implementation Challenges

1. Ignoring Quarterly Updates

Many teams skip testing updates, leading to production issues.

2. Lack of Proper Logging

Without logs:

• Issues are hard to diagnose
• Root cause analysis becomes slow

3. Poor Coordination Between Teams

Functional and technical teams must collaborate.

4. Over-Customization

Too many customizations increase maintenance effort.

5. Inefficient SR Handling

Raising incomplete SRs delays resolution.

Best Practices from Real Projects

1. Always Test in TEST Environment

Never directly rely on Oracle updates.

2. Maintain Regression Test Scripts

Include:

• Hire employee
• Create invoice
• Run payroll
• Submit expense

3. Use OIC Gen 3 Monitoring Effectively

• Enable tracking
• Use error handling frameworks

4. Maintain Documentation

Keep records of:

• Changes
• Fixes
• Known issues

5. Implement SLA-Based Support

Example:

6. Optimize Reports

• Avoid heavy joins
• Use filters
• Schedule batch jobs

7. Regular Security Audits

• Remove inactive users
• Review role assignments

Frequently Asked Interview Questions

1. What is Oracle Fusion M&S?

It is the process of maintaining, monitoring, and supporting Fusion applications post go-live.

2. What are quarterly updates?

Oracle releases updates (26A, 26B, etc.) every quarter with new features and fixes.

3. How do you test updates?

Using TEST environment and regression test cases.

4. What is Transaction Console?

A tool to monitor workflow transactions.

5. What is ESS Job Monitoring?

Monitoring Scheduled Processes in Fusion.

6. How do you handle integration failures?

Check OIC logs, analyze payload, fix mapping, and reprocess.

7. What is SR in Oracle?

Service Request raised to Oracle Support.

8. How do you manage security?

Using Security Console and role-based access control.

9. What is regression testing?

Testing existing functionality after updates.

10. How do you optimize performance?

Optimize queries, reduce data load, and use scheduling.

11. What are common M&S challenges?

Updates, integrations, performance issues.

12. What is environment strategy?

Using DEV, TEST, and PROD environments.

13. How do you monitor payroll issues?

Using Scheduled Processes and logs.

14. What is OIC Gen 3 role in M&S?

Integration monitoring and error handling.

15. What is SLA in support?

Defined response and resolution timelines.

Expert Tips from Oracle Consultants

• Never ignore update readiness reports
• Always maintain backup test cases
• Automate testing wherever possible
• Monitor integrations daily
• Keep communication channels clear between teams

FAQ Section

1. How often should we test Oracle Fusion updates?

Every quarter before production rollout. Ideally, perform testing immediately after TEST environment update.

2. What is the most critical part of M&S?

Regression testing and integration monitoring are the most critical areas.

3. Can we avoid issues after updates?

Not completely, but proper testing and monitoring reduce risks significantly.

Summary

Oracle Fusion Applications M&S is not just a support function—it is a continuous improvement process. In real-world implementations, organizations that invest in structured maintenance strategies see better system stability, improved user satisfaction, and fewer production issues.

With Oracle’s quarterly update model (26A and beyond), proactive testing, strong monitoring, and efficient support processes are essential.

If you approach M&S like a consultant—not just a support engineer—you will add real business value.

For deeper reference, always review Oracle’s official documentation:

https://docs.oracle.com/en/cloud/saas/index.html