Table of Contents

Master (Bring Back) Burst

A Master (Bring Back) Burst uses a primary report — the driver or master — that pulls, or "brings back," summarized values from one or more sub-reports and returns them as new columns on the master report. It is essentially a user-defined report lookup: much like a table lookup, except the returned data comes from another report rather than a table.

The Core Pattern

Each sub-report is attached to the master through a Burst calculation. Like a table lookup, every burst calculation returns one or more new columns into the master report — summarized, relevant values drawn from the rows the sub-report bursts back. The master and its sub-reports can be run manually or scheduled in Automator, and the sub-report values are gathered at the time the master is generated.

A Running Example

In the Distribution Burst section we pushed a voucher report out to each vendor. A Master (Bring Back) Burst reverses that flow — instead of distributing a report, it pulls summarized values back into a master report.

Throughout this section we follow a single example in that same A/P world: a Supplier Master (F0401) report that brings back summarized amount values from an AP Detail (F0411) sub-report.

The main (driver) report Brought back from the sub-report Matched on
A/P Supplier Master Information Total Gross Amount, Total Open Amount Vendor

Each returned value becomes a new column on the master report, summarized for the rows that match.

Before You Start

This page orients you to what a Master (Bring Back) Burst does; the pages that follow walk through designing one, adding the burst calculation, and testing it. The setup concepts shared by every burst type — Report Selection, Burst on Run, Which Rows to Burst, Activation Condition, Lookup Values, and Output Types — are covered in Concepts Common to Every Burst.

Note

Master (Bring Back) Bursts are the exception to one common rule: they run the burst for all rows in the data set whether the master report is queried by Run or by Get Sample Data. This is intentional, ensuring all returned values are populated on the master.