AX2565

Plan Files tab

On the Plan Files tab, specify the plan files that you want to process. There are three different options that you can use to specify the plan files: Choose from list, Use filter, and All. You should use the option that corresponds to how many plan files you want to process—all plan files, or a subset of plan files. If you want to process a subset of plan files, you can select individual files to process or you can use a filter to define the subset.

Process all plan files

To process all plan files, select All. The list of all plan files is generated each time the Scheduler task is executed, so that if new plan files have been added then those new plan files will be included in the processing (the reverse is also true if any plan files have been removed).

Alternatively, you can select Choose from list and then select the check box in the column header, causing all current plan codes to be selected. However, in this case the list of selected plan codes is fixed and therefore will not automatically adjust for any future changes.

Process selected plan files

To process certain plan files, select Choose from list, and then select the check boxes for the plan files that you want to process. When the Scheduler task is executed, Axiom Budget Planning and Performance Reporting will process only the selected plan files.

To find the plan files you are looking for, you can sort, filter, and group the list using standard Axiom grid features. You can show additional columns and hide columns by right-clicking in the column header. If you have filtered the list, you can select the check box in the header to select only the plan files that currently display in the dialog.

NOTE: This option is not available if the file group for the task is an alias. This is because the list of plan files could change when the alias target changes.

Process a filtered set of plan files

To use a filter to process a subset of plan files, select Use Filter. When the Scheduler task is executed, Axiom Budget Planning and Performance Reporting will process only the plan files that meet the filter.

You can use the Filter Wizard to create the filter, or you can manually type a filter criteria statement into the filter box. The filter must use the plan code table or a lookup table. For example: DEPT.Region='US West' where Dept is the plan code table.

Once you have entered a filter, you can click Refresh plan file list to show the plan files that currently match the filter. The refresh feature is intended to help you determine whether you have defined the filter correctly.

You can also use a job variable for the filter. For example, you can define a job variable named "filter" and then place the text {filter} in the filter box. This is intended for use when running Scheduler jobs via RunEvent. If a variable value is specified when the event is triggered, such as the value dept.region='west', then that filter statement will replace the {filter} variable and will be used to determine the list of plan files to be processed.

NOTE: If you use a variable, and you leave the default value for that variable blank within the Job Variables tab, then all plan codes will be processed if no value is passed by the RunEvent function. You may want to define a default filter that results in no values (such as 1=0), so that plan files are only processed if a valid filter value is passed.

Axiom queries

On the Axiom Queries tab, select the queries that you want to run in the plan files. By default, all listed queries are selected. This tab only applies when using Normal Processing mode.

If you do not want to run a particular query, you can clear the check box. You can select or clear individual check boxes, or you can use the check box in the header to select or clear all queries currently displayed in the list. You can sort, filter, and group the list using standard Axiom grid functionality.

Example Axiom Queries tab

The list of Axiom queries is based on the source templates that were used to create the plan files. Only Axiom queries that meet the following criteria are eligible for selection:

• Active is set to On, or the setting uses a formula.
• Refresh during document processing is set to On.

If a query uses a formula for the Active setting, this means the query is dynamic and may or may not be run, depending on how the formula resolves in each plan file to be processed. When a particular plan file is processed, each selected query will be evaluated based on the current settings in that plan file. If both Active and Refresh during document processing are On for that plan file, then the query will be run. If either or both settings are Off for that plan file, the query will not be run. You can tell whether a query is dynamic or not by looking at the Dynamic column in the query list.

If a query is not selected on this tab, then that query will not be run in any plan files during processing, regardless of whether Active or Refresh during document processing are enabled in the plan file.

The plan file selection on the Plan Files tab affects the Axiom query list as follows:

• If you have selected individual plan files, then only the eligible queries for the source templates of the selected plan files are shown.
• If you have selected All or Use Filter, then all eligible queries for all used templates are shown. If the file group has templates that have not been used to create any plan files, then those templates are not included in the list.

The listed queries are identified by template, worksheet, and query name. The following additional properties are also listed for each query:

• Refresh On Open: Indicates whether the Axiom query is configured to refresh automatically when the file is opened. This is for information purposes only, to help you determine whether the query needs to be included in the processing. The Refresh on Open status is ignored by Process Plan Files—if the query is selected it will be run along with the other selected queries, and if it is not selected it will not be run.

• Dynamic: Indicates whether the query is dynamically enabled. True means that the query uses a formula for the Active setting.

NOTE: If a query is listed on this tab but it is grayed out and unavailable for selection, that means that although the query is active (either directly or dynamically), the query is not eligible to be run using Process Plan Files (because the setting Refresh during document processing is set to Off). This query is listed for your information only, so that you understand the query cannot be run as part of the process.

Utilities tab

On the Utilities tab, select the ProcessPlanFileUtilities data source to use during processing. This data source determines which utility files are processed and the processing order. This tab only applies when using Process with Utilities mode.

Example Utilities tab

For each template listed, use the Utilities Data Source field to select the data source to use for plan files created from that template.

• If the template only has one data source, that data source is selected.
• If the template has multiple data sources, then the data source marked as the default data source is selected by default. If preferred, you can use the dropdown to select a different data source.

When plan files are processed, Axiom Budget Planning and Performance Reporting reads the specified data source in each plan file to determine the utilities to be processed for that plan file.

The plan file selection on the Plan Files tab affects the Utilities list as follows:

• If you have selected individual plan files, then only the templates used to create the selected plan files are shown.
• If you have selected All or Use Filter, then all used templates are shown. If the file group has templates that have not been used to create any plan files, then those templates are not included in the list.

Processing variables

This tab can be used to define variables to pass into plan files before processing begins, and to pass variables back to the Scheduler job after processing has been performed. This tab is optional and is only used in special situations.

Pre-processing document variables

This section can be used to pass document variables into plan files before processing. This can impact the processing of plan files if the files are configured to use the variable values in some way.

For each pre-processing document variable, you can specify a variable name and a variable value. The plan files must be set up with GetDocumentInfo functions that return the values for the specified variables.

To edit the variable settings, double-click the applicable cell to make the cell contents editable. When you are finished editing, you can press the Enter key or Tab key to exit the cell, or click outside of the cell.

Item	Description
Variable Name	The name of the variable. Do not enclose the variable name in curly brackets (you are not using the variable here, you are defining its value).
Variable Value	The value of the variable. The value can be a "hard-coded" value, or it can be a job variable that will be resolved at time of processing. If you use a job variable to define the value, the job variable must be enclosed in curly brackets.

Pre-processing workbook variables

This section can be used to pass values into plan files before processing. This can impact the processing of plan files if the files are configured to use the values in some way.

For each pre-processing variable, you can specify a workbook location to place the value, and the value to be placed.

Item	Description
Workbook Location	The location in the workbook for the value to be placed. Any existing value in this location will be overwritten for the duration of the processing. If the file is saved as part of the processing, then the value will be saved in the file. The location can be specified using SheetName!CellRef syntax (for example: Report!A13), or by using a named location in the file.
Formula	The value to be placed in the specified workbook location. The value can be a "hard-coded" value, or a formula, or a job variable that will be resolved at time of processing. If the value is a formula, the formula is placed into the target cell and calculated in the plan file. The formula can be any formula that would be valid within a spreadsheet in the Axiom client. This includes using Excel functions and Axiom functions. The formula can also use job variables, which will be resolved before placing the formula in the target cell.

The specified location and value will apply to all plan files being processed by the task. If you are going to use pre-processing variables, the location should be predefined in the template and therefore available to all plan files built using that template. If the plan files will be built using multiple templates, then all templates should be set up with the same designated location, or you should set up separate processing tasks based on template type.

Post-processing workbook variables

This section can be used to pass a value from plan files back to the Scheduler job after processing has been performed. This can impact the processing of subsequent tasks in the job if those tasks are configured to use the value in some way.

For each post-processing variable, you can specify the location in the workbook to find the value, and the job variable to use that value.

NOTE: If this task processes multiple plan files, the resulting variable value will be from the last file that was processed.

Item	Description
Workbook Location	The location in the workbook to find the value to be passed to Scheduler. This value will become the value for the assigned job variable for the duration of executing the current job (unless a later process within the same job overwrites the value for the same job variable). The location can be specified using SheetName!CellRef syntax (for example: Report!A13), or by using a named location in the file.
Job Variable	The job variable that you want to use the value in the specified workbook location. Do not enclose the variable name in curly brackets (you are not using the variable here, you are referencing the variable name). If the job variable does not already exist in the job (on the Job Variables tab), then it will be created. However, in most cases you will want the variable to be already set up with a default value, so that the job does not have validation errors that prevent saving.

The specified location and job variable will apply to all plan files being processed by the task. If you are going to use post-processing variables, the location should be predefined in the template and therefore available to all plan files built using that template. If the plan files will be built using multiple templates, then all templates should be set up with the same designated location, or you should set up separate processing tasks based on template type.

Even though the task may process many plan files, only the job variable value from the last-processed plan file will be used. The plan files must be set up so that all plan files result in the same value after processing, or else your results will vary depending on which plan file was the last file to be processed.