J3V007 |
SAS Size Optimization 3.41_M2 |
Issue(s) Addressed: | Introduced: |
66543 | You cannot successfully paste numbers from Microsoft Excel into the profile distribution field in SAS® Size Optimization |
J3V001 |
61649 | The %DI_JOB_SO MODEL_GP_STATUS task might eliminate large amounts of sales data when sales occur in only one week |
J3V001 |
66958 | The BATCH_PROFILING task in SAS® Size Profiling does not run batch profiling projects in parallel when the PARALLEL= parameter is set to 1 |
J3V001 |
67186 | You cannot paste numbers from multiple cells in Microsoft Excel into the profile distribution fields in SAS® Size Optimization |
J3V002 |
67295 | The GEO-SYNCH process in SAS® Size Optimization causes profile data errors |
J3V002 |
51776 | The error "Resource is write-locked by another user. File" occurs when you run the BATCH_PROFILING task in SAS® Size Profiling |
J3V003 |
69114 | A security vulnerability occurs in the SAS® Size Optimization Suite and the SAS® Revenue Optimization Suite because of Java application files |
J3V004 |
69055 | The message "ERROR: File GSY.ALLCLSTR_XXXXXX.DATA does not exist" is encountered with the GEO_SYNC task |
J3V004 |
69988 | SAMBA server mapping does not work when you deploy SAS® Merchandise Solutions Configuration Workbench in RHEL 8+ |
J3V006 |
70342 | The integrated Help window is no longer available in SAS® Revenue Optimization and SAS® Size Optimization |
J3V006 |
69211 | Stores that did not have any sales for the entire project duration should be classified into an existing store group |
J3V007 |
69590 | Store groups with significant sales might erroneously inherit the distribution% from the overall store group in SAS® Size Profiling |
J3V007 |
69762 | The maximum quantity of a style-color or SKU that can be ordered across all stores in the delivery might not be enforced |
J3V007 |
|
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |