When you run one of the SAS^® Merchandise Intelligence Revenue Optimization Suite products and you use an analytical product hierarchy, duplicate ATTR_PROD_DM.PROD_HIER_SK values can be generated incorrectly across partitions below the partition level. The specific products include SAS^® Markdown Optimization, SAS^® Promotion Optimization, SAS^® Regular Price Optimization, and SAS^® Retail Forecasting.

In most environments, there are no indications that this issue has occurred. However, in an environment where uncovered geo/prods exist (geo/prods that do not belong to a model group), the following error might be displayed. This error is displayed in one of the di_mc_mg_coverage_unit child logs when the %tkmi_job_ro est_start_service task runs.

In order to determine whether this issue has occurred in your environments(s), run the check_attr_prod.sas program found on the Downloads tab. The check_attr_prod.sas program must be run in a SAS session where the SAS^® Merchandise Intelligence libraries are allocated. There is one macro variable that must be customized and set to the location of your partition subdirectories. When the program runs, it places a message in the log stating whether duplicates across partitions were found. If duplicates are found, then a report of the duplicates is generated. If your environment contains duplicates, then contact SAS Technical Support to obtain a script to correct your data.

The workaround for this issue is to run the %tkmi_job_ro attr_hier_job task single-threaded. Running single-threaded prevents duplicate ATTR_PROD_DM.PROD_HIER_SK values from being generated in different partitions. The recommendation is to perform the following steps to run the %tkmi_job_ro attr_hier_job task:

1. Preserve the current value of the NUM_PARALLEL_EXECUTIONS global setting.
2. Set the value of the NUM_PARALLEL_EXECUTIONS global setting to 1 (to force single threading).
3. Run the %tkmi_job_ro attr_hier_job task.
4. Restore the value of the NUM_PARALLEL_EXECUTIONS global setting.

The Full Code tab contains sample code that you can use to perform the steps above.

Note: If you rebuild the analytical product hierarchy in the SAS^® Merchandise Solutions Configuration Workbench, then you must manually set the NUM_PARALLEL_EXECUTIONS global setting to 1. Change the global setting in the Global Settings Editor BEFORE you rebuild the analytical product hierarchy in order to ensure single-threading. Reset the NUM_PARALLEL_EXECUTIONS global setting afterward.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

proc sql noprint;
   select spec_value into :num_parallel_executions_orig
      from di_dm.global_setting
      where app = 'ALL' and spec_nm = 'NUM_PARALLEL_EXECUTIONS';
   update di_dm.global_setting
      set spec_value = '1'
      where app = 'ALL' and spec_nm = 'NUM_PARALLEL_EXECUTIONS';
   select spec_value into :num_parallel_executions
      from di_dm.global_setting
      where app = 'ALL' and spec_nm = 'NUM_PARALLEL_EXECUTIONS';
quit;

%put Original NUM_PARALLEL_EXECUTIONS = &num_parallel_executions_orig;
 
%put Before attr_hier_job task NUM_PARALLEL_EXECUTIONS = &num_parallel_executions;
 
%tkmi_job_ro(application=RPO,
             run_only=%bquote(attr_hier_job));
        
proc sql noprint;
   update di_dm.global_setting
      set spec_value = "&num_parallel_executions_orig"
      where app = 'ALL' and spec_nm = 'NUM_PARALLEL_EXECUTIONS';
   select spec_value into :num_parallel_executions
      from di_dm.global_setting
      where app = 'ALL' and spec_nm = 'NUM_PARALLEL_EXECUTIONS';
quit;
 
%put After attr_hier_job task NUM_PARALLEL_EXECUTIONS = &num_parallel_executions;

A fix for this issue for SAS Revenue Optimization 5.2_M4 is available at:

A fix for this issue for SAS Size Optimization 3.2_M4 is available at: