Problem Note 61200: Communications with percent-based holdouts that have a small number of offers might fail in a campaign group in SAS® Customer Intelligence
In SAS Customer Intelligence, communications with percent-based control groups that have a small number of offers might fail in a campaign group during the optimization process. When this failure occurs, you might see the following error message in the SASCustIntelCore6.x.log file:
2017-07-21 13:57:20,994 ERROR [CIAsyncExec-67]
[192859aa2e32a1ec:-1ee28524:15d60e7f46a:-4448] [SAS MAMO User] s.crm.custdata.ejb.MAMOConsumeResultData - handleResults - Unmatched CCC results
returned from stored process! CCC=CAMP_XXX:CCOM_XXX:CELLXXX
This problem happens when the following criteria are true:
- You use a percentage-based (auto) control group.
- A small number of offers is selected by a Communication node.
- All offers end up in the control group.
Because SAS Marketing Optimization is a large-scale optimization application, it is not a good practice to have communications with only one (or no) eligible customer because those values cannot be optimized.
If you encounter this problem, contact SAS Technical Support to obtain a fix for this issue.
Operating System and Release Information
SAS System | SAS Customer Intelligence Studio | Microsoft Windows 10 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8.1 Pro x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8.1 Pro 32-bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8.1 Enterprise x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8.1 Enterprise 32-bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8 Pro x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8 Pro 32-bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8 Enterprise x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows 8 Enterprise 32-bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft® Windows® for x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows Server 2008 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows Server 2008 R2 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows Server 2008 for x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows Server 2012 Datacenter | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows Server 2012 R2 Datacenter | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows Server 2012 R2 Std | 6.3 | 6.5 | | 9.4 TS1M3 |
Microsoft Windows Server 2012 Std | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Enterprise 32 bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Enterprise x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Home Premium 32 bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Home Premium x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Professional 32 bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Professional x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Ultimate 32 bit | 6.3 | 6.5 | | 9.4 TS1M3 |
Windows 7 Ultimate x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
64-bit Enabled AIX | 6.3 | 6.5 | | 9.4 TS1M3 |
64-bit Enabled Solaris | 6.3 | 6.5 | | 9.4 TS1M3 |
HP-UX IPF | 6.3 | 6.5 | | 9.4 TS1M3 |
Linux for x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
Solaris for x64 | 6.3 | 6.5 | | 9.4 TS1M3 |
*
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: | high |
Date Modified: | 2017-10-16 07:39:21 |
Date Created: | 2017-10-06 10:49:41 |