B3R006 |
SAS Revenue Optimization 5.4 |
Issue(s) Addressed: | Introduced: |
60576 | There is no option to select "Include if selected by the TS component" for the PS_1 to PS_n REG component in the Configuration Editor |
B3R001 |
61675 | ALERT - An "ORA-00913: too many values.." error might occur after opening the Pack Optimization Products view when using custom attributes |
B3R001 |
61817 | ALERT - A mixed case misspelling of a user ID might log a user on as an "Unauthorized User" in SAS® Merchandise Intelligence |
B3R001 |
62485 | The dialog box to exclude style-colors might fail to open in SAS® Size Profiling |
B3R001 |
55330 | SAS® Pack Optimization middle-tier log size might be excessive due to recurring message "No size set specified for product ######..." |
B3R001 |
60951 | Overrides to Profiling Project Properties for Prepare Size Sets and Generate Profiles might not be saved in SAS® Size Profiling |
B3R001 |
61020 | ALERT - Optimization results might be incorrect when using Default Pack Settings with delivery overrides and bulk sizes in SAS® Pack Optimization |
B3R001 |
61202 | Selecting bulk size pack values greater than one within inner packs might yield undesired results in SAS® Pack Optimization |
B3R001 |
61697 | ALERT - An "ORA-01745: invalid host/bind variable name in LONG PSQL" error might occur during a Purchase Order Plan Delete operation |
B3R001 |
63403 | In SAS® Size Profiling, check boxes in the filtered Product Root hierarchy might incorrectly be dimmed |
B3R001 |
61649 | The %DI_JOB_SO MODEL_GP_STATUS task might eliminate large amounts of sales data when sales occur in only one week |
B3R001 |
62969 | The SAS® Size Profiling Load_STG2DM_Product_attr_lookup job does not provide the ability to delete attributes |
B3R001 |
63333 | ALERT - The SAS® Merchandise Intelligence update_datamart.sas script might generate "ERROR: The macro DI_UTIL_RENAME_PK will stop executing" |
B3R001 |
63571 | ALERT - SOAP requests might have poor performance in SAS® Pack Optimization |
B3R001 |
64020 | The PERIOD_IN_STOCK value in the SAS® Size Profiling report viewed in SAS® Visual Analytics Administration and Reporting might incorrectly be negative |
B3R001 |
64202 | SZPK_PACK_BY_DC_.NUM_OUTERS values might be incorrect |
B3R001 |
61166 | ALERT - %TKMI_JOB_RO etl_end_service generates "ORA-01652: unable to extend temp segment by 128 in tablespace TEMP" |
B3R002 |
61171 | %TKMI_JOB_RO etl_end_service generates "ORA-00001: unique constraint (DI_DM.RPP_PLAN_PROD_METRICS_PK) violated" |
B3R002 |
61212 | A "java.sql.SQLException: ORA-01000: maximum open cursors exceeded" exception might occur when you open the Promotion List view |
B3R002 |
61215 | The SASMerchIntelMidTier5.41.log file might not contain DEBUG lines as expected |
B3R003 |
62245 | ALERT - A "Failed to connect to server" error might occur after logging in to the SAS® Merchandise Solutions Configuration Workbench |
B3R003 |
62349 | %TKMI_JOB_RO etl_end_service generates 'Record : Rejected - Error on table DI_DM.RPP_PLAN_PROD_METRICS_PART.' |
B3R003 |
62350 | ALERT - Migrated promotion missing KPIs |
B3R003 |
62377 | SAS® Promotion Optimization Tentatively Approved and Approved plans are out of date after re-evaluation |
B3R003 |
62267 | ALERT - ETL jobs in the SAS® Merchandise Intelligence Suite might fail with "ERROR: File does not exist" and "Statement not executed due to NOEXEC option" |
B3R003 |
61602 | ALERT - In SAS® Pack Optimization, using the Request API for allocations with DC Splits might miscalculate pack quantities for stores |
B3R004 |
62805 | %TKMI_JOB_RO etl_end_service task generates "Caused by: java.sql.SQLSyntaxErrorException: ORA-01795: maximum number of expressions in a list is 1000" |
B3R004 |
62930 | The Baseline metrics in the Promotion Performance table might be blank |
B3R004 |
62932 | A promotion plan that is migrated from a previous release might incorrectly have a status of "Out of date" |
B3R004 |
62931 | The Units Expected with Override metric might be incorrect |
B3R004 |
60640 | SAS® Size Optimization fails when publishing profiles with "ERROR: ORACLE prepare error: ORA-01795: maximum number of expressions in a list is 1000" |
B3R004 |
61308 | SAS Merchandise Solutions Configuration Workbench generates 'ORA-12899: value to large for column "<SCHEMA>"."<TABLE>","CREATED_BY"...' |
B3R004 |
61424 | Sort order might be incorrect in SAS® Size Profiling reports viewed in SAS® Visual Analytics Administration and Reporting |
B3R004 |
61595 | The %TKMI_JOB_RO job generates "ERROR: is not licensed or is expired for this SAS installation" |
B3R004 |
62014 | SAS® Pack Optimization reports viewed in SAS® Visual Analytics Administration and Reporting might not be generated for plans with model members |
B3R004 |
62697 | ALERT - The Load_STG2DM_Size_translation job might fail with "ERROR: Insufficient authorization to access BL_SIZE_TRANSLATION_0.ctl" |
B3R004 |
61378 | Regular Price Grids might not be properly inherited at child nodes in the Pricing Rules view |
B3R005 |
61422 | Price Endings might not be properly applied during optimization |
B3R005 |
63206 | An exception might occur when you save price grids |
B3R005 |
61721 | You might be unable to change the description in existing product relationship rules |
B3R005 |
62866 | The pricing rules graph might not display pricing rules as expected |
B3R005 |
62890 | The Fix Price check box remains selected after a product is unapproved |
B3R005 |
62895 | An "ORA-01795: maximum number of expressions in a list is 1000" might occur when you create a new regular price plan from the Alerts List view |
B3R005 |
57637 | ALERT - Optimization results might not be optimal when the current prices for plan members are really large in SAS® Regular Price Optimization |
B3R005 |
61156 | Optimization fails with "ERROR: TKTException code = 6 (Access violation)" |
B3R005 |
62169 | Price Grid rules might not be applied correctly |
B3R005 |
62702 | The recommended price might not be as expected when there are more than 4000 grid points |
B3R005 |
63072 | The recommended prices might not be as expected for a uniform pricing location level |
B3R005 |
63089 | Recommended prices might not be as expected when the same price rule is defined |
B3R005 |
62022 | Markdown spend might not be reported in the correct week in the Plan Weekly Details view |
B3R006 |
62026 | Price and Effective Price in the Plan Weekly Details view might be different in a week with no promotions |
B3R006 |
63832 | The %TKMI_JOB_RO etl_end_service task might generate an "ORA-00600: internal error code, arguments: [KGL-heap-size-exceeded]" error |
B3R006 |
64487 | Promotion copy is slow |
B3R006 |
64503 | Markdown plans might not be optimized during the %TKMI_JOB_RO etl_end_service job |
B3R006 |
64944 | You might not be able to change the status of an approved promotion after a product reclassification |
B3R006 |
65155 | %TKMI_JOB_RO etl_end_service generates "There was some problem during Aggregation during Batch." |
B3R006 |
58343 | You cannot override vendor deal support to remove the support if the vendor deal is at the promotion level |
B3R006 |
61714 | The location filter in the Markdown Approvals view might not contain all necessary location levels |
B3R006 |
64683 | A promotion created from a copy might not include calendar vehicles at the master level from the original promotion |
B3R006 |
64724 | Price changes cannot be made on the master promotion |
B3R006 |
64837 | An exception might be generated when you create a regional promotion in SAS® Promotion Optimization |
B3R006 |
56544 | The KPIs generated when you specify the Minimize Price Rule Violations optimization goal might not be optimal |
B3R006 |
61331 | Estimation or model analysis might fail with "ERROR: Assertion failed: reg_md_frame->ts_trend_offset != 0..." |
B3R006 |
62178 | %TKMI_JOB_RO fcst_export generates 'ERROR: TKTException code = 6 (Access violation)' |
B3R006 |
63641 | Forecasts in promotions might not be as expected |
B3R006 |
63694 | Optimization might be slow for buy-get promotions |
B3R006 |
64296 | Estimation fails with "Error: invalid status grid detected during model data aggregation for prod/geo/date_sk..." |
B3R006 |
64321 | Case cost, effective cost, and regular cost might be incorrect in approved promotions |
B3R006 |
64348 | %TKMI_JOB_RO est_start_service generates "ERROR: ERROR: ERROR: ORACLE execute error: ORA-00001: unique constraint (DI_DM.COVERAGE_OUTPUT_PK) violated" |
B3R006 |
60978 | DATA_LVL.DATA_LVL_NM might not be updated after you rebuild the analytical hierarchy |
B3R006 |
62146 | %TKMI_JOB_RO fcst_export generates "ERROR: Update/delete failed. The observation may have been changed or deleted since the time it was read" |
B3R006 |
64530 | %DI_MAINTAIN_JOB generates "ERROR: Data set D_PATH.GEO_PROD does not contain the index specified by the KEY= option, PRIM_KEY." for every partition |
B3R006 |
65101 | ALERT - The %TKMI_JOB_RO job macro produces "WARNING 1-322: Assuming the symbol WEBAUTHDOMAIN was misspelled as webdomain." |
B3R006 |
|
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |