| W19025 |
| SAS Size Optimization 3.4 |
| Issue(s) Addressed: | Introduced: |
| 53535 | The Get Purchase Order Export method might erroneously generate duplicate pack configuration information |
W19001 |
| 56642 | The Profiles view in SAS® Size Profiling might become unresponsive |
W19001 |
| 57079 | ALERT - The status of a purchase order plan might be displayed incorrectly when you have selected multiple plans to optimize or disaggregate |
W19001 |
| 59325 | "Could not synchronize database state with..." error might occur when you attempt to delete a store grouping rule |
W19001 |
| 59850 | The %TKMI_JOB_SO batch job does not generate an error when you specify an invalid task name for the RUN_ONLY argument |
W19001 |
| 56761 | ALERT - The status of a purchase order plan might incorrectly be displayed as "Optimization Failed" or "Disaggregation Failed" |
W19003 |
| 57325 | The Imputation Removed Sales Units values in the Size Sets table in the Profiling Scenario details page might be incorrect |
W19003 |
| 56351 | ALERT - A "Failed to connect to server" error might be encountered after logging in to the SAS® Merchandise Solutions Configuration Workbench |
W19004 |
| 56640 | An "ORA-00936: missing expression..." error might occur in SAS® Pack Optimization |
W19005 |
| 53920 | "java.lang.NumberFormatException: For input string..." might be encountered when you attempt to view grouping assignment properties |
W19005 |
| 54022 | The Size Name column might not sort correctly in SAS® Size Profiling |
W19005 |
| 57592 | ALERT - Manually created store groups might be missing from the PROFILE_CLUSTER table |
W19005 |
| 58724 | SAS® Size Profiling might generate a large number of Imputation Added Sales Units when using Clustering (Cross-Store) Imputation Methods |
W19005 |
| 58786 | Custom size sets might be missing manual store groups in the PROFILE_CLUSTER table |
W19005 |
| 58902 | The plots for Sales Units and Demand Units might not be correct in the Sales versus Demand plot when there are no additional units added by imputation |
W19005 |
| 58910 | The %DI_JOB_SO DERIVE_STOCKOUT_GP_STATUS task treats initial inventory records with zero available quantity as start of active period |
W19005 |
| 56735 | The %DI_JOB_SO geo_synch task generates "ORA-00942: table or view does not exist" |
W19005 |
| 58939 | ALERT - The error "ORA-00060: deadlock detected while waiting for resource" might occur in SAS® Pack Optimization |
W19006 |
| 57778 | ALERT - An "ORA-00913: too many values.." error might occur after opening the Pack Optimization Products view |
W19007 |
| 58934 | ALERT - The %DI_JOB_SO geo_synch task might drop store groups when there is a new store within a store grouping rule |
W19007 |
| 58628 | Generating a VAAR report gives "an error occurred while generating the report" in SAS® Pack Optimization |
W19009 |
| 59555 | In SAS® Size Profiling, purging Inventory fact data might run longer than expected when many data partitions exist |
W19009 |
| 59610 | ALERT - The Pre-Pack Quantity and Bulk Pack Quantity units in the SAS® Pack Optimization Scorecard report in SAS® Visual Analytics might be incorrect |
W19010 |
| 59794 | A "java.util.ConcurrentModificationException" error might occur when you select the Project SKU Exclusions dialog box |
W19010 |
| 59560 | ALERT - Purging sales fact data might take longer than expected when many data partitions exist in SAS® Size Profiling |
W19010 |
| 59777 | The %DI_JOB_SO batch job does not generate an error when you specify an invalid task name for the RUN_ONLY argument |
W19010 |
| 60207 | ALERT - An exception might occur when you create a like product or a child product in SAS® Pack Optimization |
W19011 |
| 59842 | ALERT - SAS® Merchandise Intelligence ETL and purge jobs might generate "ERROR: A lock is not available for " before a success lock is obtained |
W19011 |
| 59978 | Filter preferences might not be honored |
W19012 |
| 60140 | The MINIMUM_ORDER_THRESHOLD and MAXIMUM_ORDER_THRESHOLD global setting values are not applied on the Purchase Order Plan Properties view |
W19012 |
| 60052 | You are able to incorrectly enter a maximum order threshold value that is greater than 100 in SAS® Pack Optimization |
W19012 |
| 59958 | "ERROR: ORACLE execute error: ORA-00001: unique constraint (DI_DM.SYS_XXXXXXX) violated" might occur when you generate store groups |
W19012 |
| 60089 | A profile lookup might return an incorrect profile when an attribute is used as both the filtering attribute and partitioning attribute |
W19012 |
| 60109 | SAS® Size Optimization reports viewed in the SAS® Visual Analytics Report Viewer might contain no data |
W19012 |
| 60282 | ALERT - The product and location permission hierarchies might not be populated in the Permissions dialog box in the SAS® Merchandise Intelligence Plug-in |
W19012 |
| 60477 | Attribute values might be duplicated in the Attribute List in the Exclude Store Attribute view in SAS® Size Profiling |
W19013 |
| 60724 | Deleting projects might take a long time in SAS® Size Optimization |
W19013 |
| 60640 | SAS® Size Optimization fails when publishing profiles with "ERROR: ORACLE prepare error: ORA-01795: maximum number of expressions in a list is 1000" |
W19013 |
| 60996 | The SAS® Pack Optimization Scorecard Report is not available in SAS® Pack Optimization 3.4 |
W19014 |
| 60839 | The Imputation Added Sales Units column in the Size Sets table might incorrectly display negative values |
W19014 |
| 60928 | Custom sort order is not honored in SAS® Size Optimization reports viewed in SAS® Visual Analytics Administration and Reporting |
W19014 |
| 61602 | ALERT - In SAS® Pack Optimization, using the Request API for allocations with DC Splits might miscalculate pack quantities for stores |
W19015 |
| 61565 | ALERT - Optimization might fail with a segmentation violation error when you specify Allow Pack from Prior Delivery for carry over packs |
W19016 |
| 61675 | ALERT - An "ORA-00913: too many values.." error might occur after opening the Pack Optimization Products view when using custom attributes |
W19016 |
| 61697 | ALERT - An "ORA-01745: invalid host/bind variable name in LONG PSQL" error might occur during a Purchase Order Plan Delete operation |
W19016 |
| 61817 | ALERT - A mixed case misspelling of a user ID might log a user on as an "Unauthorized User" in SAS® Merchandise Intelligence |
W19016 |
| 55330 | SAS® Pack Optimization middle-tier log size might be excessive due to recurring message "No size set specified for product ######..." |
W19016 |
| 60951 | Overrides to Profiling Project Properties for Prepare Size Sets and Generate Profiles might not be saved in SAS® Size Profiling |
W19016 |
| 61360 | "Error" might be displayed in the Profile Distribution table in the Profile view in SAS® Size Profiling |
W19016 |
| 61186 | The %DI_JOB_SO geo_synch task might take a long time to execute |
W19016 |
| 59200 | The %TKMI_JOB_RO etl_end_service task generates "c_product_hier_assoc_dm: Error: (prod_hier_assoc_cd = 1) cannot find a product for sk ..." |
W19016 |
| 61308 | SAS Merchandise Solutions Configuration Workbench generates 'ORA-12899: value to large for column "<SCHEMA>"."<TABLE>","CREATED_BY"...' |
W19016 |
| 61424 | Sort order might be incorrect in SAS® Size Profiling reports viewed in SAS® Visual Analytics Administration and Reporting |
W19016 |
| 62014 | SAS® Pack Optimization reports viewed in SAS® Visual Analytics Administration and Reporting might not be generated for plans with model members |
W19016 |
| 62245 | ALERT - A "Failed to connect to server" error might occur after logging in to the SAS® Merchandise Solutions Configuration Workbench |
W19017 |
| 62952 | The %DI_JOB_SO geo_synch task fails with "ERROR: The keyword parameter XXX passed to macro SZPF_PROFILE_SYNCH_GEO_IN_UNIT was given a value twice." |
W19018 |
| 63849 | SAS® Pack Optimization might recommend more packs than needed when USE_SHARED_PACK_CONFIGS is turned on |
W19019 |
| 63403 | In SAS® Size Profiling, check boxes in the filtered Product Root hierarchy might incorrectly be dimmed |
W19019 |
| 63571 | ALERT - SOAP requests might have poor performance in SAS® Pack Optimization |
W19019 |
| 63579 | The %DI_MAINTAIN_JOB might have poor performance when purging request data from all request and response tables in SAS® Pack Optimization |
W19020 |
| 64577 | ALERT - The SAS® Pack Optimization API calls for the Pack Recommendations & Optimization process fail with a segmentation violation |
W19020 |
| 57446 | Orphaned rows might occur in the APP_USER, APP_GROUP, and DATA_AUTHORIZATION tables |
W19020 |
| 57510 | An "ArrayIndexOutOfBoundsException" exception might occur after you remove authorization for SAS® Merchandise Intelligence for a user |
W19020 |
| 62485 | The dialog box to exclude style-colors might fail to open in SAS® Size Profiling |
W19020 |
| 64448 | Profile generation might eliminate lower-level profiles that should be retained in SAS® Size Optimization |
W19020 |
| 65042 | You might not be able to log on the SAS® Merchandise Intelligence client |
W19020 |
| 65396 | ALERT - Batch profile generation might generate errors after you install SAS® Size Profiling 3.4 Hot Fix W19020 |
W19020 |
| 61884 | The Standard Size Code column in the Pack configurations view and the Outer Pack Contents view is not sorted by default |
W19020 |
| 62284 | ALERT - SAS® Pack Optimization might generate "ERROR: Error in table REQ_PACK. SKU ID XXX found in PACK ID; XXX is not a valid sku in the request." |
W19020 |
| 63013 | ALERT - Disaggregated quantities might be incorrect in a purchase order plan |
W19020 |
| 64437 | ALERT - You might not be able to open or delete profiles in SAS® Size Profiling |
W19020 |
| 64807 | Profile clusters and store groups might not have distributions when store grouping attributes are used in SAS® Size Optimization |
W19020 |
| 62629 | ALERT - The DI_ETL_Geo_prod_purge_job ETL job might fail with "ERROR: File DI_TRANS.USER_TABLES.DATA does not exist" |
W19020 |
| 62697 | ALERT - The Load_STG2DM_Size_translation job might fail with "ERROR: Insufficient authorization to access BL_SIZE_TRANSLATION_0.ctl" |
W19020 |
| 62839 | Size name display order might be incorrect in SAS® Size Profiling reports viewed in SAS® Visual Analytics Administration and Reporting |
W19020 |
| 62969 | The SAS® Size Profiling Load_STG2DM_Product_attr_lookup job does not provide the ability to delete attributes |
W19020 |
| 65073 | The SAS® Size Profiling extract generation process for SAS® Visual Analytics Administration and Reporting might generate errors |
W19020 |
| 65846 | Publishing a profiling project in SAS® Size Profiling generates the message "ERROR: An error occurred updating profiles with new and closed stores" |
W19022 |
| 66543 | You cannot successfully paste numbers from Microsoft Excel into the profile distribution field in SAS® Size Optimization |
W19023 |
| 61649 | The %DI_JOB_SO MODEL_GP_STATUS task might eliminate large amounts of sales data when sales occur in only one week |
W19023 |
| 67186 | You cannot paste numbers from multiple cells in Microsoft Excel into the profile distribution fields in SAS® Size Optimization |
W19024 |
| 69762 | The maximum quantity of a style-color or SKU that can be ordered across all stores in the delivery might not be enforced |
W19025 |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
General Information about Hot Fixes