EPBCS - Migrating on-prem planning as custom planning cube in EPBCS (Lesson Learned)
SummaryMy client migrated a on-prem planning app as a custom plan type to EPBCS with the intention of enabling features post migration.
My client migrated a on-prem planning app as a custom plan type to EPBCS with the intention of enabling features post migration to Cloud EPM EPBCS. This post is a lesson learned from this effort. We've logged the following SR with Oracle Support.
SR Issue: Migration from on prem to Cloud EPM EPBCS as custom plan type
SR Description: Enabling EPBCS features after migration from on-prem to Cloud EPM EPBCS requires modification to all EPBCS generated planning artifacts because generated artifacts assume existing on-prem planning application outline aligns with required top-most members in EPBCS outline design. This assumption is not valid when on-prem planning application is migrated as a custom plan type in Cloud EPM EPBCS with the intention of enabling EPBCS post migration. Figure 1 below of pre-configured EPBCS dashboard highlights this issue. Custom plan type does not use required EPBCS top most dimension for custom Center dimension (See Figure 2).