Minimum provisioned role for FDMEE load into Hyperion Planning

Hi all,

My client has asked me about a way to avoid accidental data loads into Hyperion Planning. In this scenario we don't want an FDMEE data load to accidentally overwrite past, closed periods.

We are using version 11.1.2.4(.0.79). The user account we set up in FDMEE (let's call it FDM_Loader) inherits the EssbaseCluster-1 admin role as well as the Essbase Write Access role for the target Planning application from the "ESSBASE_ADMIN_FOR_PLANNING_DS" group. The idea is to apply security to periods and years so we can restrict which ones can FDM_Loader write on when launching data loads from FDMEE.