The other day a client was having trouble setting up a bursting definition in Narrative Reporting. They needed to use a targeted distribution file so the report would go to specified users for selected cost centers. Normally, setting up a bursting like this is fairly straightforward. But we couldn’t figure out why the file was failing. Let’s go thru the whole process of setting up the bursting definition and resolve the issue.
We created a simple report with some POV selections, accounts in the rows, and periods in the columns. Members for Provider and Scenario are selectable. Note: We used a Freeform application as our datasource.
The bursting definition is set up with Provider as the Bursting POV Dimension and Scenario as the Global Dimension.
Edit Provider to include the members to be bursted and Scenario to be the single member for the reports.
Create a CSV file with the Provider members that are in the Bursting POV Dimension selection. For each member, assign the user name and email for the recipient. If a user is to receive reports for multiple members, add lines for each additional member. The members need to be available in the selection in Bursting POV Dimension.
Save the file as a regular CSV. This is critical, other CSV types will cause an error and the bursting definition will not work. This was the mistake our client was making, they were saving the CSV as ‘CSV UTF-8’ and it needed to be just ‘CSV‘.
Upload the CSV file to the bursting definition.
Select PDF or Excel for Distribution Format.
Add recipients for Success and/or Failure notifications if desired.
Check the Email selection and uncheck the selection on “Send all generated reports to all recipients in a single email”. The bursted reports can also be saved to a Library folder if desired, just check the Library selection and update the parameters.
Add a name for the attachment and compose the email.
Save the bursting definition.
To test the bursting, click on the gear icon and select Execute.
A confirmation window will open stating that the bursting is running.
Recipients will receive one email for each of the assignments in the targeted file. The success email is sent with details of the bursting.
Once a bursting definition has been configured and tested, it can be either executed on-demand or scheduled using EPM Automate. Bursting can be used on individual reports like in this example, or on books and report packages. Review Oracle documentation for more details https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/dmepr/bursting_chapter_designer_guide.html
As always, happy EPM’ng!