Advanced Report Settings
You can add more flexibility to an Advanced Report by using the settings in the Advanced Rules and Advanced Profiles.
Effective Date Behavior
The dates used as the basis for running Advanced Report Profiles depend upon certain conditions. In some cases, the Advanced Report Profile date has precedence, and in other cases, the underlying Report Profile dates take precedence. Since there is a date setting at each level of the Advanced Report, this makes Advanced Reports more flexible, particularly when a package of reports is run.
The following table illustrates which date is being used in the Advanced Report Profile. There is no distinction on the Advanced Report Profile side between using an internal and user-defined date rule.
Advanced Report | PACE Profile Date | Resulting Date |
07/02/2010 | 06/22/2012 | 06/22/2012 |
Current Month (date rule) | 12/31/2012 | 12/31/2012 |
06/30/2012 | Previous Month (internal date rule) | Previous Month-Dates used are based on today’s dates. If today is 6/4/12, dates=5/1/12-5/31/12 |
Previous Month (internal date rule) | Previous Month (internal date rule) | Previous Month-Dates used are based on today’s dates. If today is 6/4/12, dates=5/1/12-5/31/12 |
06/30/2011 | Prior Year End (user‑defined date rule) | 12/31/2012 |
06/30/2012 | Prior Month (user-defined date rule) | 05/01/2012-05/31/2012 |
Prior Month | Prior Month (user‑defined date rule) | Based on today’s date, go back a month and then another month. Ex: today is 3/19/12. Date run is for 01/01/12-01/31/12. |
Current Month | Prior Month (user‑defined date rule) | Based on this month, go back to last month (dates work together). So if today is 3/19/12, dates used are 02/01/12-02/28/12. |
Select Force Dates Settings
The Advanced Reporting date override function includes a Force Datessetting. This setting allows the Advanced Report profile date to replace, rather than override, the date setting in the underlying PACE Report Profile. Set the Force Dates at the PACE Profile level in the Advanced Report Rule.
When Force Dates is not activated:
The Advanced Report Profile has a fixed Date and the underlying PACE Profile has a fixed Date. The Report runs for the Date in the PACE Report Profile.
The Advanced Report Profile has a Date Rule and the PACE Profile has a fixed Date. The report runs for the fixed Date specified in the PACE Profile.
Advanced Report and PACE Profile have Date Rules. First, the Date gets evaluated to the Date rule in the Advanced Report. Then, the Date gets evaluated with PACE Profile Date Rule based on the Date from Advanced Report.
The examples in the following sections illustrate the Force Dates function for date overrides in Advanced Reporting.
Example Run Date 1
The data in the following table provides an example of run date.
AR Date Setting | Flag | PACE Profile Date Setting | PACE Profile Runtime Date |
1/30/2012 | NO | 5/30/2011 | 5/30/2011 |
1/30/2012 | NO | 2 Months Ago | 11/30/2011 |
Last Month | NO | 5/30/2012 | 5/30/2012 |
Last Month | NO | 2 Months Ago | 4/31/2012 |
When Force Dates is activated:
The Advanced Report Profile and the underlying PACE Profile have fixed Dates. The Report runs for the Date in the Advanced Report Profile.
The Advanced Report Profile has a fixed Date and the PACE Report Profile has a Date Rule. The report runs for the date specified in the Advanced Profile.
The Advanced Report has a Date Rule and the PACE Profile has a fixed Date. The report runs for the Date evaluated based on Date Rule in Advanced Profile.
Advanced Report and PACE Profile have Date Rules. The report runs for the Date evaluated based on Date Rule in Advanced Profile.
Example Run Date 2
The data listed in the following table provides another example of run date.
AR Date Setting | Flag | PACE Profile Date Setting | PACE Profile Runtime Date |
1/30/2012 | YES | 5/30/2003 | 1/30/2012 |
1/30/2012 | YES | 2 Months Ago | 1/30/2012 |
Last Month | YES | 5/30/2009 | 6/30/2012 |
Last Month | YES | 2 Months Ago | 6/30/2012 |