Administering Cloud EPM: The Platform Beneath the Business Processes · Module 5 · Business Processes and Migration
Lab: create, migrate, and write the plan
Lesson 61 of 201 · 3 min
An hour and a half, and three of the seven deliverables are written rather than built — which is what makes it work on the follow-along path. A business process created in at least one Northwind environment — or, on the follow-along path, an annotated creation plan for each environment in the estate. An application type created within a business process, demonstrating the Lesson 1 distinction. A snapshot taken, downloaded and imported into a second environment, with import results reviewed and verified. A written verification note: what you CHECKED in the target, and how you confirmed it works. A written migration plan for Northwind's Planning estate: source, target, sequence, compatibility check, user step, integration step, rollback position. A written answer to "can we move our old Profitability and Cost Management application into Enterprise Profitability and Cost Management?" — with the correct caveats. And a note on the EDM record ceiling:…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.
In this module: Module 5 · Business Processes and Migration
- 1One environment, one business process
- 2Creating from the Standard landing page
- 3Creating from the Enterprise landing page
- 4Switching business processes
- 5Migration: the concepts
- 6Migration paths by business process
- 7Performing a migration
- 8Transitioning the data management business process to standalone
- 9Essbase in Cloud EPM
- 10What breaks
- 11Lab: create, migrate, and write the plan