Keeping up with EPM Cloud

Recently, while implementing Oracle Planning Cloud for a new client, we experienced an issue where attribute dimensions were not being deployed successfully to the underlying Essbase cube – which was definitely not ideal! As we had never experienced this issue before, we opened an SR with Oracle, and (long story short) the issue was occurring because we had unknowingly used a restricted word as a member name and also had trailing spaces in a couple of aliases. Once we removed the restricted member names/aliases, the attribute dimensions were successfully deployed during the refresh. Unfortunately, these restricted members do not show as an error when refreshing the database, even if used in the outline, so hopefully this is something Oracle can add either as an error or as a warning on the Activity Report. In the meantime, it’s worth double checking the naming restrictions, especially if you seem to be experiencing some strange behaviour with Essbase. Some of the main restrictio...

When using additional Accounting Scenarios in your ERP GL Essbase cube to hold non-Actuals data (e.g. Budget or Forecast data from PBCS), it is occasionally necessary to clear out an entire Accounting Scenario in ERP, for example: ·          The data is incorrect and must be cleared out ·          The data pushed from PBCS was mapped to the wrong version ·          The data needs to be overwritten completely e.g. a “Latest Forecast” scenario which is updated monthly When pushing Budget or Forecast data from Planning (PBCS) to a defined Accounting Scenario in ERP, the data will only be overwritten for combinations which have non-zero data in the push. This means that if data has been cleared to #missing in the PBCS source data, then existing values in ERP will not be overwritten.  See my previous blog for more on pushing from Planning to ERP: https:...