Oracle EBS Support Partner in India: A Buyer's Guide

Many companies still run their finance, supply chain and HR on Oracle E-Business Suite (EBS). Oracle has extended Premier Support for EBS 12.2 well into the next decade. So for most EBS customers the question is not "how do we get off EBS next year?" It is "who will keep EBS stable, patched and useful while we plan what comes next?"

This guide is for IT and finance leaders choosing an EBS support partner in India. It covers what support should include, Oracle's own support timelines, engagement models, priority levels, how to evaluate partners and how to onboard one.

Where Oracle's own support stands

Oracle publishes support dates under its Lifetime Support policy. The policy has three levels. Premier Support gives full maintenance and updates. Extended Support adds further years for a fee where offered. Sustaining Support continues for as long as you use the software, but covers existing fixes rather than new ones.

For EBS, the current position on oracle.com is:

EBS 12.2 follows Oracle's Continuous Innovation model. Oracle treats the 2037 date as a minimum that it may extend, and says it has no current plans to end Premier Support for 12.2. Recheck the policy each year, as dates can change.

You still need an Oracle support contract. A partner does not replace Oracle Support. It works with it.

What EBS support should cover

Ask any partner to show how they handle each of these areas.

Functional support. User queries, setup changes, period-close issues and process fixes across modules such as General Ledger, Payables, Receivables, Fixed Assets, Purchasing, Inventory, Order Management and HRMS.

Technical and DBA support. Concurrent manager health, workflow, performance tuning, cloning, backups, user and responsibility administration, and database and application tier housekeeping.

Patching. Oracle releases Critical Patch Updates (CPUs) every quarter, on the third Tuesday of January, April, July and October. Your partner should review each release, test the EBS patches in a non-production instance and apply them to production on an agreed cycle.

12.2 online patching. EBS 12.2 uses a dual file system (run and patch) and the adop utility. A cycle moves through prepare, apply, finalize, cutover and cleanup. Users keep working during most of the cycle. Only cutover needs a short outage. A partner must know how to plan cutover windows, abort a cycle when needed and run fs_clone when a procedure requires it.

Code-level checks. Custom code on 12.2 must follow Oracle's online patching standards. Oracle provides readiness reports, a database standards checker and the Global Standards Compliance Checker (GSCC). A good partner runs these on every new or changed customisation before it reaches production.

Month-end and year-end support. Extra cover on close days, with named people who know your ledgers, interfaces and reconciliation steps.

Oracle SR handling. Logging and following up service requests in My Oracle Support, with the right severity, logs and steps to reproduce. Oracle sets severity by business impact, from Severity 1 (critical operations stopped) to Severity 4 (information requests).

Engagement models

• Dedicated team. Named functional and technical consultants assigned to you. Suits large or heavily customised estates.
• Shared pool with fixed hours. A monthly block of hours used across functional, technical and DBA work. Suits mid-sized estates with steady demand.
• Ticket-based. Pay per ticket or per band of tickets. Suits stable estates with low change.
• Hybrid. A small core team plus a flexible pool for month-end, CPU cycles and projects.

Whatever the model, ask which hours are covered. Many Indian partners serve customers in the GCC, UK, Europe, US and Australia, so the overlap with your working day matters.

A sample priority table

Agree priority definitions in the contract. Oracle's SR severity and your partner's priority are separate, but they should line up. A typical structure looks like this. The response and resolution targets are for you and your partner to agree.

How to evaluate an EBS support partner

1. Check Oracle credentials. Confirm the partner is listed in Oracle's partner directory and ask about their consultants' EBS experience by module.
2. Match release experience. Ask for 12.2 online patching experience, not only 12.1. Ask who will run your next adop cycle.
3. Review the patching process. Ask how they review each quarterly CPU, how long testing takes and who signs off before production.
4. Test custom code discipline. Ask how they run the readiness reports and GSCC, and how they review code before migration.
5. Ask about month-end. Who is on call during close, and do they know your ledgers?
6. Read the SR process. Ask for sample SR updates and how they escalate a slow SR with Oracle.
7. Check working hours and handovers. Confirm cover in your time zone and how shifts hand over open tickets.
8. Look at reporting. Ask for a sample monthly report: tickets, ageing, root causes, CPU status and open SRs.
9. Plan the exit. Make sure documentation, scripts and runbooks belong to you.

Partner selection checklist

• Oracle Partner status confirmed
• EBS 12.2 online patching experience shown
• Quarterly CPU process documented
• Custom code checks (readiness reports, GSCC) part of the process
• Month-end and year-end cover agreed
• My Oracle Support SR handling and escalation described
• Priority definitions and targets written into the contract
• Working hours match your business hours
• Monthly service report sample reviewed
• Knowledge transfer and exit terms agreed

Transition and onboarding plan

A clean handover takes roughly 60 to 90 days.

1. Weeks 1 to 2: discovery. Collect the environment list, customisation inventory, interfaces, open tickets, open SRs and patch history.
2. Weeks 3 to 6: shadowing. The new partner works alongside the outgoing team or in-house staff and writes runbooks.
3. Weeks 7 to 8: reverse shadowing. The new partner leads; the outgoing team watches. Include one month-end close.
4. Weeks 9 to 12: steady state. Full handover, first monthly report and first CPU cycle planned.

Give the partner My Oracle Support access under your support identifier early. SRs cannot wait for paperwork.

When to consider moving to Fusion

Good support keeps EBS running. It does not change the fact that EBS is software you host and patch. Consider Fusion Cloud ERP when you are still on 12.1, when hardware or database renewals fall due, or when the business wants quarterly updates without upgrade projects. Many companies move in phases and run EBS and Fusion side by side using Oracle's coexistence reference architecture. Our EBS to Fusion migration checklist covers the ten areas to plan. Oracle's EBS 12.2 documentation library is the place to check release notes and upgrade guides.

How Egisedge helps

Egisedge Technologies is an Oracle Partner, founded in 2019. Our directors bring 20+ and 16+ years of hands-on Oracle EBS and Fusion experience across finance and supply chain. We have delivered multiple Oracle projects, and we help EBS customers plan the move to Fusion and rebuild integrations on Oracle Integration Cloud (OIC). Our teams work from offices in Gurugram and Mahendergarh, India, and deliver offshore across GCC, UK/Europe, US and Australia/NZ working hours.

If you are weighing EBS support options or planning your route to Fusion, email info@egisedge.com to talk to our team.

Frequently asked questions