Generate Aggregate Report Tabulations

Learn how to set up aggregate reports and generate report tables.

Note Beginning with 24R1 in April 2024 and for all subsequent releases, Vault Safety General Release Help content is moving to a new site. Test the new site using Limited Release content.

Note Depending on your Admin's configuration, object, field, and section labels, lifecycle states, and workflows may differ from the general information on this page. Refer to your organization's business processes for guidance.

Trigger Table Generation

Once the Aggregate Report (DSUR, PSUR, PBRER, or PADER) has been created, trigger table generation through the Generate Aggregate Report Tabulations action. This action may be available as a user action from the All Actions (All Actions) menu on the Aggregate Report, or may be initiated automatically as part of the Aggregate Report workflow.

The table generation process duration depends on the size of the vault and the number of Cases. Once table generation is complete, the user who initiated the report generation is notified with an email and vault notification.

In the standard Vault Safety template, table generation occurs after you complete the Review Report Record task. Once complete, the Aggregate Report record enters the Authorship stage and the system starts generating the tables.

Note This page describes the Review Report Record task in the default configuration. If your organization has a custom workflow, follow the recommendations in your business standard operating procedure for generating aggregate report tables.

Regenerate Report Tabulations

To regenerate and update the report tabulations prior to submission, once the aggregate report is approved, select Regenerate Report Tabulations when you complete the Review & Author Report task.

Generate Next Aggregate Report

Vault Safety enables you to automatically generate subsequent reports and assign tasks according to the aggregate reporting period.

The Generate Next Aggregate Report Record action automatically generates the next aggregate report, using the reporting period defined on the Reporting Family, and the Start Date and End Date defined on the Aggregate Report record. This action may be available as a user action or may be triggered automatically as part of workflows in your vault.

When the Generate Next Aggregate Report action is triggered, the system creates a new Aggregate Report (DSUR, PSUR, PBRER, or PADER) with the following settings:

Field Value
Product Family The same Reporting Family specified on the initial Aggregate Report.
States to Include The same States to Include specified on the initial Aggregate Report
Data Period Start The Data Period End on the initial Aggregate Report, plus 1 day.
Data Period End The Data Period Start on the initial Aggregate Report, plus the Reporting Period (Months) specified on the Reporting Family, minus 1 day.
*The initial Aggregate Report refers to the Aggregate Report (DSUR, PSUR, PBRER, or PADER) from which the Generate Next Aggregate Report action is triggered.

The following diagram shows an example of how the Generate Next Aggregate Report action sets the report time period:

Generate Next Aggregate Report Action Date Calculation
Generate Next Aggregate Report Action Date Calculation

How Aggregate Reports Filter by Data Period
Generated Masked Aggregate Tabulations (CIOMS II, PBRER and DSUR)
Feedback?