Problem Note 54816: The CI_CONTACT_HISTORY table might contain incorrect RESPONSE_TRACKING_CD values under some circumstances in SAS® Marketing Automation
When you use multiple cells with same input node (for example, the Limit node or the Split node) upstream as input to the same communication node, the CI_CONTACT_HISTORY table might contain incorrect RESPONSE_TRACKING_CD values.
This problem happens when the input link from the node that is upstream from the cells is disconnected and then reconnected. The following display shows an example of how such a campaign might look:
When the campaign shown above is published, the CI_CELL_PACKAGE table has four CELL_PACKAGE_SK values:
However, in the CI_CONTACT_HISTORY table, only the first four rows have the correct RESPONSE_TRACKING_CD values, which are 1161 02 10 (CELL_PACKAGE_SK+BCID+SubjectID).
The next twelve rows have incorrect RESPONSE_TRACKING_CD values:
- 1162 02 00
- 1163 02 00
- 1164 02 00
In these rows, the value for the subject-level ID is 0, which results in incorrect reporting data.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Marketing Automation | Microsoft® Windows® for x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows 8 Enterprise x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows 8 Pro x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows 8.1 Enterprise 32-bit | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows 8.1 Enterprise x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows 8.1 Pro | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows 8.1 Pro 32-bit | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows Server 2008 R2 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows Server 2008 for x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows Server 2012 Datacenter | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows Server 2012 R2 Datacenter | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows Server 2012 R2 Std | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Microsoft Windows Server 2012 Std | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Windows 7 Enterprise x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Windows 7 Professional x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
64-bit Enabled AIX | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
64-bit Enabled Solaris | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
HP-UX IPF | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Linux for x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
Solaris for x64 | 6.1_M1 | 6.4 | 9.3 TS1M2 | 9.4 TS1M0 |
*
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: | 2014-12-15 10:23:24 |
Date Created: | 2014-12-10 09:10:27 |