EPM · Fusion · Intermediate
Administering Cloud EPM: The Platform Beneath the Business Processes
Nineteen modules on the platform layer almost nobody teaches — identity, security, recovery and the estate
A practical administration course for Cloud EPM service administrators, cloud and identity teams inheriting an EPM estate, Center of Excellence leads, and consultants who keep getting handed the platform work nobody scoped. IT DOES NOT TEACH HOW TO CONFIGURE PLANNING, FINANCIAL CONSOLIDATION AND CLOSE, ACCOUNT RECONCILIATION OR ANY OTHER INDIVIDUAL BUSINESS PROCESS — each of those is its own implementation and its own course. This teaches how to run the platform they live on: cloud accounts, identity domains and regions; creating, sizing and retiring environments; a role model that survives growth; single sign-on and directory synchronization; network perimeter, managed provider access and customer-managed encryption keys; clients and automation; backups, disaster recovery and the restore you have never actually performed; the operating calendar; monitoring and the evidence an auditor asks for; and the Center of Excellence that holds all of it. Every module ends with a failure segment and a diagnostic sequence.
Written by AbdAllah Mohamed
Live cohort · registration open
Live teaching starts 18 January 2027
One hour daily, Sunday to Thursday · 19:00 Riyadh, 18:00 Cairo · 10 weeks
Taught live by an Oracle consultant, with every session recorded for anyone who misses one. Places are limited — we teach these in small groups so questions get answered.
Your access starts the day you enrol, not the day the cohort starts. The written lessons, the quizzes and the final assessment open straight away, so you can come to the first session having already read the ground.
The sessions run online, and the joining details reach you by email before the first one.
Watch a free lesson
All free lessons in this course · 9 free lessons
EGP 15,900
201 lessons · 234 min
Buying for a team? See seat pricing.
Who this is for
- Cloud EPM service administrators, and cloud or identity teams who have inherited an EPM estate.
- Center of Excellence leads responsible for how the platform is run rather than what is modelled on it.
- Consultants who keep being handed the platform work nobody put in the scope.
- Not for you if you want to build a Planning application, a consolidation or a reconciliation. Each of those is its own implementation; this is the platform underneath them.
What you will be able to do
- Design the identity and infrastructure structure an EPM estate will live in for a decade — cloud account, identity domains, regions, compartments — and defend the parts you can never change
- Treat region selection as the legal decision it is, and get a residency constraint in writing before provisioning anything
- Create, name, document, hand over and retire environments, and read any EPM URL to say which environment it is before you act on it
- Put a business process into an environment and move one between environments, knowing what migrates and what does not
- Design a role model that works at five hundred users as well as at five — roles to groups, never to people
- Connect the estate to the corporate directory so joiners, movers and leavers happen once, in one place
- Federate the estate to a corporate identity provider without locking yourself out, and know what SSO does to Smart View and automation before your users find out
- Restrict the network perimeter, control what the provider itself can access, hold your own encryption keys, and answer a security questionnaire without guessing
- Choose the right automation tool for each task and build automation that reports its own failures
- Distinguish the three different things called "backup", restore an environment, and state how long it actually took
- Run the operating calendar — maintenance windows, patch readiness, appearance, email deliverability — so the platform runs quietly
- Build a monitoring routine that finds problems before users report them and an evidence pack that turns an audit from a week into an afternoon
- Assess an organization against the capability inventory of a Center of Excellence, and make the case for one to a sceptical sponsor
What you should know first
- General cloud and identity literacy. Nothing about Cloud EPM specifically is assumed.
- THIS COURSE DOES NOT TEACH BUSINESS PROCESS CONFIGURATION. If you want to learn how to build a Planning application, configure a consolidation, or set up reconciliations, this is not that course — those are separate implementations and separate courses. This is the platform underneath them.
- ACCESS: three levels, and which you have determines how much you can do hands-on. Service administrator on ONE environment is enough for the orientation, operations and enablement phases — most of the course. Building the estate and securing it needs CLOUD ACCOUNT AND IDENTITY DOMAIN ADMINISTRATION, which most learners will not have and should not request on a production tenant.
- Follow-along mode is a legitimate primary path here, not a consolation. Every privileged lesson is written out in full, and the labs assess your design reasoning — which is the part that is actually hard, and which is graded equally.
- NEVER practise identity, security or network perimeter configuration in a live tenant. Locking yourself out of a production EPM estate is possible, unglamorous and career-adjacent. Use a disposable or non-production tenant.
- This is the fastest-dating course in the catalogue — the platform layer changes monthly. Every module carries a recorded-against date, concepts are taught ahead of click paths, and the course teaches you to read release readiness notes yourself, which is the durable skill.
What you will cover
Watch a free lesson
1. Module 0 · Orientation
What this course is and — just as important — what it is not. The access levels each phase needs, so you know before you start which parts you can do hands-on. The shape of the platform administrator's job, which in most organizations nobody ever wrote a description for. And the three modules that carry the decisions worth taking slowly.
4 lessons7 min
2. Module 1 · The Cloud EPM and EDM Landscape
Cloud EPM names a family of about eleven business processes plus a data management capability — and an environment hosts exactly one of them. That single rule determines estate size and therefore workload, and it is why platform administration is a job. This module names every business process, groups them into families, and draws the platform layer underneath all of them that the rest of the course is about.
9 lessons18 min
3. Module 2 · Subscriptions and Licensing
Licensing looks like a procurement problem and is repeatedly an administrator problem, because the person who discovers the entitlement gap is almost always the one trying to create an environment or add a user. This module teaches you to read a client's subscription, say what it does and does not entitle them to, and raise the surprise in week one rather than month six.
8 lessons15 min
4. Module 3 · Cloud Account, Identity Domains and Regions
THE FIRST FLAGSHIP. Every environment lives inside an identity domain, inside a cloud account, in a region — and those three facts determine who can sign in, where the data physically resides, and what it costs to change your mind. Restructuring after environments exist is a migration with downtime, and region selection is a data residency commitment with legal weight. The module's argument: design the identity structure before you create anything, because the first environment you create fixes it. The build is ninety minutes; the design should take days.
19 lessons36 min
5. Module 4 · Creating and Managing Environments
Creating, naming, documenting, handing over and retiring environments — and giving users a URL they can actually remember. It also teaches the habit that prevents a category of bad afternoons: read any EPM URL before you act on it, and confirm which environment it actually is.
10 lessons19 min
6. Module 5 · Business Processes and Migration
Putting a business process into an environment, moving one between environments, and knowing what the migration paths are before somebody asks you to move something that cannot be moved. The rule to carry out of it: never plan a migration you have not tested, and the answer to "can we move this?" is never a flat yes.
11 lessons17 min
7. Module 6 · Users, Groups and the Role Model
THE SECOND FLAGSHIP, and the only one where the wrong decision does not feel like a decision at all. Nobody chooses per-user role assignment — they just start, and then they have five hundred users and five thousand individual grants, each of which must be created on joining, changed on moving and removed on leaving. The module's argument: assign roles to groups, never to people, and decide that before the eleventh user. This phase is roughly a quarter of the job and it is routinely scoped as half a day.
16 lessons27 min
8. Module 7 · Provisioning at Scale
Connecting the estate to the corporate directory so joiners, movers and leavers happen once, in one place, by people who already do it for a living. The group model makes provisioning survivable; synchronization makes it correct — and the division of labour it creates is the reason the group design mattered so much.
10 lessons16 min
9. Module 8 · Single Sign-On and Federation
Federating the estate to the corporate identity provider, handling the multi-domain and multi-account cases, and knowing what SSO does to your clients before your users find out. The security argument that carries it: without SSO, disabling someone's corporate account does nothing to their EPM access — with it, it does.
11 lessons16 min
10. Module 9 · Securing the Perimeter
Restricting who can reach the estate and from where, controlling what the provider itself can access, holding your own encryption keys, and answering a security questionnaire without guessing. The proportionality point runs through it: not every estate needs customer-managed keys and approval-gated provider access, and a perimeter so tight that legitimate users cannot work produces workarounds that are worse than the original risk.
12 lessons22 min
11. Module 10 · Clients and Tools
Users experience the platform through clients, which means a Smart View problem is your problem regardless of whose laptop it is. Which client every user needs, how to get it to them, how to connect it, and what to check before you change anything upstream that might break it. This phase describes the job as it is actually lived: the earlier phases happen once, and this happens every day.
10 lessons18 min
12. Module 11 · Automation
Automating the recurring work — backups, loads, refreshes, exports — with the right tool for each job, and building a runbook someone else could operate. Automation is not about saving time; it is about reliability, auditability and a task that runs correctly whether or not the person who normally does it is available. And the governance point that matters more than the tooling: automation nobody monitors is worse than manual work, because manual work fails visibly.
13 lessons23 min
13. Module 12 · Business Continuity and Recovery
THE THIRD FLAGSHIP, and a different kind of risk from the other two. Those are decisions you cannot undo; this is the one where being wrong is UNRECOVERABLE — and unlike the others the failure is invisible until the day it matters. Nothing tells you your recovery plan does not work. You find out. The module's argument: a backup you have never restored is not a backup, it is a belief. By the end of it you will have restored an environment and timed it.
15 lessons25 min
14. Module 13 · Running the Environment
The operating rhythm — maintenance windows, update handling, appearance, session timeout, email deliverability and announcements — set so the platform runs quietly and nobody has to think about it. A platform administrator without a calendar is a platform administrator reacting; the work is predictable, and the calendar is what makes it manageable.
10 lessons16 min
15. Module 14 · Monitoring the Estate
The reports exist, they are comprehensive, and almost nobody reads them until something has already gone wrong. This module builds the routine that finds problems before users report them and produces the evidence auditors ask for without a scramble. The routine is the deliverable, not the reports — and most of what matters is a trend rather than a value.
11 lessons20 min
16. Module 15 · User Enablement and Support
A platform administrator with two hundred users and no support model becomes a helpdesk, and everything else in this course stops happening. This module builds the tiers that keep a user base productive without consuming your week — guidance inside the product, a working feedback loop, and users who can help themselves.
8 lessons15 min
17. Module 16 · AI Agent Studio and EPM Assistants
What EPM Assistants actually are — downloadable, preconfigured TEMPLATES for creating agents, not agents you turn on — how to assemble the prerequisite stack they need, and how to give a client an honest assessment of whether it is worth it yet. This is the fastest-dating module in the course and everything in it must be verified against current documentation. It is worth learning anyway, because the prerequisite stack is identity work and identity work is durable.
9 lessons16 min
18. Module 17 · The EPM Center of Excellence
The module that assembles the course. The source material opens with this topic and this course closes with it deliberately, because governance is a set of capabilities and you cannot define capabilities you do not understand. A Center of Excellence is not a governance committee bolted onto a technology — it is the standing team that holds the capabilities the preceding sixteen modules taught.
9 lessons14 min
19. Module 18 · Full Platform Capstone
A brief and an estate to assess, secure, operate and recover. A manufacturing group whose EPM estate has grown without a plan across two cloud accounts and three identity domains, with 340 individual role assignments, no single sign-on, a residency violation confirmed in writing, a nightly load running from an analyst's laptop under her personal account, and three internal audit findings due in ninety days. Eight deliberate ambiguities to resolve and justify. The graded centrepiece is the recovery exercise, which has no partial credit for intent.
6 lessons13 min