Problem Note 43870: Base forecast partition table duplication error might cause estimation to fail
You might encounter a base forecast partition table duplication error when running calibration in SAS® Promotion Optimization and SAS® Regular Price Optimization. This might occur when a category does not have sufficient sales in every single store. The error will look similar to the following:
ERROR: duplicates for p_bf.partition_52_65349_1_2 Check work._dupout for details
ERROR: A fatal error was encountered while executing macro DI_DM_PARTITION_WRITE. Please contact your system administrator.
There is no workaround for this issue.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Regular Price Optimization | Microsoft Windows Server 2003 Standard Edition | 4.2_M1 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Enterprise Edition | 4.2_M1 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Datacenter Edition | 4.2_M1 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
64-bit Enabled AIX | 4.2_M1 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2008 for x64 | 4.2_M1 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2008 | 4.2_M1 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 for x64 | 4.2_M1 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
SAS System | SAS Promotion Optimization | 64-bit Enabled AIX | 4.2_M1 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2008 for x64 | 4.2_M1 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2008 | 4.2_M1 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 for x64 | 4.2_M1 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Standard Edition | 4.2_M1 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Enterprise Edition | 4.2_M1 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Datacenter Edition | 4.2_M1 | 5.2 | 9.2 TS2M3 | 9.3 TS1M1 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | alert |
Date Modified: | 2012-11-01 12:43:55 |
Date Created: | 2011-08-01 09:45:29 |