TAGS

Recent Posts

Archives

How to Burst Reports in Oracle EPM Planning Cloud
Posted on May 7, 2019
Author: The Performance Architects Team, Performance Architects

Oracle EPM Planning Cloud “batch-bursting” allows you to bundle reports so that they can be scheduled and delivered via email or deposited in the repository. Job bursting allows you to execute these reports multiple times for different members of a chosen dimension.

In this blog post, we walk through setting up a monthly export of a budget report that will be emailed out to multiple department heads using Oracle Planning and Budgeting Cloud Service (PBCS). Using burst reporting, we can ensure that each department head receives a report only for the department they are responsible for.

From the main menu in PBCS, click the “Navigate” icon and select “Explore Repository” under the “Reporting” heading. This brings up the “EPM Cloud Repository” window. The first thing you’ll need create is a batch file containing the report you want to “burst” out.

Using the navigation pane on the left, go to the directory you’d like to store the batch file in. From there, select “File > New > Document” from the navigation pane. In the “New Document” tab that opens, select “Batch Reports for Scheduling” and click “Next.”

This is where you’ll select the report that you want to send out. Navigate to the directory where the report is stored, highlight it, and click the arrow to move that report to the “Selected Items” pane.

Once this is done, click “Finish” and you should be brought to a “New Document” tab for your batch file.

From here, you can name the file by clicking “File > Save.” After the batch is saved, you can close this tab and move back to the previous tab, where you should see your newly created batch file in the repository window.

With the “Batch File” saved, you can now begin the scheduling process. Start by selecting “Batch Scheduler” from the “Tools” menu.

This will open the “Batch Scheduler” tab. From here you should select “New Scheduled Batch” from the “File” menu.

Enter a name and, optionally, a description for this process. If this is meant to be a one-time execution, you can check the “Delete Scheduled Batch Entry from Scheduler if Completed Successfully” checkbox to prevent this job from cluttering up the repository. Otherwise, leave the box unchecked so we can continue to run this job in the future.

Next, select the “Batch” that we created earlier in the process.

Before we begin setting up the schedule, you’ll be prompted for login credentials to the server and database.

The next step will be to choose the frequency of your schedule. For this demonstration, you’ll perform the batch once using the “Perform Now” option, but an automated schedule can be set up easily using the other options.

Next, you’ll select the “Point of View” (POV) for the report. For this report, the POV consists of the Period, Years, and Department dimensions. You can leave the “Department” selector alone, since that’s what you’ll be “bursting” on in the next step.

Check the “Run batch for multiple members in the dimension” checkbox and select the appropriate member from the drop-down, then click on the “Member Selector” icon to the right to select the departments you want to see in the report.

The member selector allows us to pick individual members, using predefined lists, or functions such as Children, Siblings, and Character Matching. For this example, we’ve manually selected some members.

Once the members are selected, they should show up in the “Select Members” box.

Clicking “Preview Bursting List” will bring up the list of members that have been selected for reports, along with other options that will be set in the following steps.

On the next screen, you’ll choose your output options. You can either save the files to the repository or have them mailed out as PDFs. For this example, you’ll email the reports as PDFs. Note that the options for exporting as HTML and MHTML are greyed out. These options are not available when using the burst feature.

After configuring the “Destination” settings, the next step is to generate output labels for the files and, if appropriate, the destination folder those files will be placed into in the “Repository.” Plain text can be used as well as variable values to personalize the reports based on the member or report name. For a full list of which values can be used see the official Oracle documentation.

On the next screen, you’ll set up a recipient list for your reports.

The subsequent screen sets up the automated email that will be used to send the reports. Note that while there is a function button for the “Message Subject” and “Message Body” fields, the only available field in this section is to include the date that the files are being generated.

The final screen gives you the option of receiving notification emails about whether the batch completed successfully or not. You can choose to send a notification only on success, failure, both, or neither and you can customize the subject line of the notification email.

Clicking “Finish” will close the window and run the batch. The “Status” value for the batch in the “Batch Scheduler” tab will change to “Running” while the job is running and then “Successful” when it is completed. Note that closing and reopening the tab may be required to see the changes.

Have any questions about this process?  Send the Performance Architects team a note at communications@performancearchitects.com or leave a note below and we’ll be in touch shortly with a response.

Share
© Performance Architects, Inc. and Performance Architects Blog, 2006 - present. Unauthorized use and/or duplication of this material without express and written permission from this blog's author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Performance Architects, Inc. and Performance Architects Blog with appropriate and specific direction to the original content.

Leave a Reply

Your email address will not be published. Required fields are marked *