SAP Analytics
Thought Leadership

BPC owners often seek to implement automation to make manual administration the exception wherever possible, in order to lower TCO and increase uptime.  For dimension automation, new members added to source systems (accounts, product names, etc.) would be automatically inserted into the BPC master data tables.  Automating this task could save quite a bit of manual effort over time, and increase system uptime.  If your BPC deployment requires manual dimension maintenance, this solution may be of great interest to you.

This is part two of a blog on utilizing the BPC Restore Journal and Export Journal Data Manager Packages.  In the first installment we covered how to setup BPC to use the packages and a few of the reasons why a business team might utilize mass journal updates.  In the second installment, we will walk through a working example of how a team might use the packages to seed budget journals from actuals.  See part 1 for a refresher on how to setup BPC for importing and exporting journals.

Has your team ever had the need to consolidate history, including journals, when moving to a new consolidation solution?  How about detailed consolidated budgets that use journals?  Or detailed reporting on journal activity?   What about the need to move journals between development, quality, and production environments?  All of this can be accomplished using BPC’s Restore Journals and Export Journals package that comes standard with BPC. Today’s discussion will outline some of the key concepts with using BPC Restore Journal and Export Journal Data Manager Packages.   In the second installment, the discussion will continue with a couple of use cases explaining the different ways to use the functionality.  As a primer, it’s important to review the standard BPC EPM documentation on how to use Journals and Data Manager Packages.