Ever have the need to produce a subset of Oracle Enterprise Planning and Budgeting Cloud Service (EPBCS) or Planning and Budgeting Cloud Service (PBCS) reports based on multiple characteristics in a timely fashion? Perhaps you need to provide multiple departments with snapshot of PDF P&L reports, and within your Department hierarchy, you are looking to quickly produce reports only for members identified as “Open,” as opposed to those that are “Closed”. Alternatively, maybe you are looking to distribute reports to a select group of Entities that are responsible for making “Product A” as opposed to “Product B”.
Fortunately, Oracle EPBCS and PBCS Financial Reporting capabilities can meet those requirements! In this blog, we’ll discuss Batch Bursting of financial reports as a methodology for producing multiple report snapshots quickly and efficiently. In particular, we will address the nuance of producing reports for a sub-section of intersections, as constrained by a set of parameters. We will discuss each topic through an example.
What is Batch Bursting?
“Batch Bursting” is a functionality that allows you to run (“burst”) a predefined “batch” of reports (and/or related items) across a set of parameters (for example – a set of members, e.g., reports for all lowest-level departments in the Department dimension). Multiple Financial Reports (as well as FR “Books” and other items) can be added within a designated “batch”, and that “batch” can then be bursted via a schedule or in an ad-hoc fashion. The snapshots commonly have an output format of PDF – and that output can be produced within Oracle Cloud and then downloaded (for example, from the Inbox/Outbox Explorer), and/or, emailed to designated recipients. Batch Bursting is beneficial in multiple business contexts because it:
- Allows for time saving – no need to run report member-by-member
- Allows for distribution (e.g., emailing the output to recipient(s))
- Allows for convenient means of snapshot archival (e.g., through Inbox/Outbox Explorer)
Walk-through: Batch Bursting Execution
Let’s discuss Batch Bursting within the context of Oracle EPBCS and PBCS in more detail by going through an example.
Assume we are responsible for producing EPBCS or PBCS Income Statement report snapshots for departments in the “Department” dimension that are “open”. Also, assume that we are a new user and not as familiar with the Department hierarchy and another admin has tagged these specific (highlighted) departments with the UDA “Open”:
Clearly, the UDA is associated with members across multiple levels within this hierarchy. Is it possible to produce report snapshots dynamically in this context for these departments without having to drill in to identify those tagged with the UDA? Yes, it is! Let’s continue.
Begin by accessing EPBCS or PBCS. In our example, our application is called “PLNtstc1”:
Access the reports repository:
We will create a batch containing our report template. Go to “File” -> “New” -> “Document”:
“Batch Reports for Scheduling”:
Select the report template for which we want to run these Income Statement reports – this is “Income Statement_Example”:
Click “Finish” on the lower right. We are then brought to this screen:
Where we can save our batch:
Now that we have our batch, we can “burst” it for our departments of interest.
Go to “Edit” -> “Schedule Batch”
Input the Batch Job Name and detail and click “Next”:
Select the batch of interest and click “Next”:
Input credentials used to login to EPBCS or PBCS:
Let’s assume we don’t want to schedule this burst, but that we want to run it now. Leave top settings as-is within the “Start Time” section.
Nuance: Bursting Across Specific Property/Properties
This screen might be the most critical in the batch burst process in our particular case. We know we want to run the batch for “multiple members in the dimension “Department” so we would select it as such:
Then, use the magnifying glass on the right to select more constraints:
We know we only want to run this process for the multiple Departments tagged with UDA “Open”, and, as such, we need to designate those parameters in this screen. At first glance, a way to begin to do that might be to choose the descendants of “All_Departments”.
However, this would get us all the Departments under “All_Departments” as opposed to only those Department members tagged with UDA “Open”.
So instead, to capture those specific departments, go to “Functions”:
And identify the function that is “Property”. Move to the right-hand side of the selection box:
Upon doing so, you will see the options to select “Property” parameters. In our case, we can select such that the logic aligns with ‘departments with UDA-equal-to-“Open”’:
After clicking “OK”, our selection screen looks like:
And after clicking “OK” again, we have:
Side Note: We can add multiple functions to further constrain the set for which we run the reports. For example, if we were to add a “Property” function again and this time add attribute “Northern” within “Territory” attribute hierarchy:
We could run the process only for departments that are “Open” (UDA) and in “Northern” territory (attribute).
After clicking “Next” again, we can choose output destinations, label conventions, and detail-related options on the following screens. For example:
Once we click “Finish” at the bottom, the process will run:
And our output should yield what we expect – the snapshot reports for the designated departments:
Batch Bursting is a very useful method for producing report snapshots in EPBCS and PBCS for specific members in a hierarchy. That said, the “Property” function within that method is especially useful as it allows you to quickly confine your set of members by leveraging properties such as UDA and/or attribute associations! We hope you can use Batch Bursting and the “Property” function to save time and improve efficiency in your next reporting cycle.
Blog Post by Noah Neal of Key Performance Ideas.