Create Custom Run
To create a custom run, select Create Custom Run from the Action drop-down. You see the Create Custom Run pop-up with two pages - Item Selection and Results Parameters. Need more info about recommendations to create a run.
Use the Item Selection page to select the items to include in the results, including the level of the results and the hierarchy nodes to include.
Provide a meaningful name for the Run Name that can help identify the run.
The Results Level defines the level of the hierarchy that the data is created for. Lower levels can require lower thresholds on the Results Parameters page (in order to find results), while higher levels can include too many results if the settings are not increased on the Results Parameters page.
The Filter Data Level is used to define rules regarding how to filter data. For example, if the results are only required for specific departments, then select Departments as the level and then select the departments.
A Promotion value of Yes only includes results in which the If component was on a promotion. A value of No is used when there is no concern about whether a promotion was present or not.
After entering item criteria, click Add Item Selection. The bottom section of the screen is populated with the results of the selection. You can also see this information in the right panel.
The Results Parameters page, which is shown in Figure 7-19, is displayed in the right panel. The minimum value for transactions is used to prevent a situation in which there are too many results because so many transactions have been used in the calculations.
Table 7-21 explains how to interpret these values.
Table 7-21 Results Parameters
| Field | Description |
|---|---|
|
Minimum Support |
The minimum percent of total transactions required to have this rule expressed as a decimal value. (0 - 1 range) |
|
Minimum Confidence |
The minimum confidence ratio required for a rule expressed as a decimal value. (0 - 1 range) |
|
Minimum Reverse Confidence |
The minimum confidence ratio required for the reverse rule definition, expressed as a decimal value. (0 - 1 range) |
|
Minimum Lift |
The minimum lift value required for a rule. |
|
Minimum Transactions |
The minimum value for transactions are used to prevent a situation in which there are too many results because too many transactions have been used in the calculations. This value also helps ensure some consistency if the transaction volume varies enough for Minimum Support to be used. |
|
Maximum Number of Rules |
The limit on the top number of rules to be saved from the results. Used to reduce data volume and remove the less significant rules. |
|
Maximum Rule Size |
The number of components to be included in a rule. The value of 2 is only supported for rules that include promotion or item results; otherwise, the value of 3 is supported. The additional components are always on the If side of the rule. |
|
Dates From and To |
The date range for processing sales data. This value must not span an excessive length of time, as the amount of data processed can become too large to manage reasonably. |
|
Segments |
Select any customer segments that should be included when determining the sales transactions to process. |
|
Location |
Limit the locations that should be included when determining the sales transactions to process. This can be done by selecting any hierarchy level and then multi-selecting any locations at that level. |