Problem Note 45949: SAS® Marketing Automation writes an extra observation to Common Data Model Treatment tables when you manually publish a scheduled campaign
When you use the menu item Action ► Publish Reporting Data in SAS® Customer Intelligence Studio, SAS Marketing Automation publishes reporting information to the Common Data Model. When you manually publish data in this way for a scheduled, recurring campaign, SAS Marketing Automation might write an extra observation to the following two tables:
- CI_PACKAGE_X_TREATMENT
- CI_CELL_PACKAGE_TREATMENT_CNT
The following scenario describes the steps that lead to the problem in further detail:
- A scheduled recurring campaign is executed at least once.
- A treatment for an associated package is modified.
- The campaign is manually published. The act of publishing manually writes future occurrence records to the tables CI_PACKAGE_X_TREATMENT and CI_CELL_PACKAGE_TREATMENT_CNT.
- The treatment is modified for a second time.
- The recurring campaign is executed again.
After the final step, above, the CI_PACKAGE_X_TREATMENT and CI_CELL_PACKAGE_TREATMENT_CNT tables have two sets of records for the latest campaign occurrence. The records written by the manual publish step and the records written when the campaign is re-executed are both present in the two tables mentioned above. Both sets of records that are written for this occurrence have counts associated with them. It is impossible to determine which treatment was associated with the package at the time that the occurrence was actually executed.
Operating System and Release Information
SAS System | SAS Marketing Automation | Microsoft® Windows® for 64-Bit Itanium-based Systems | 5.4 | 6.1 | | 9.3 TS1M0 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 5.4 | 6.1 | | 9.3 TS1M0 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 5.4 | 6.1 | | 9.3 TS1M0 |
Microsoft Windows XP 64-bit Edition | 5.4 | 6.1 | | 9.3 TS1M0 |
Microsoft Windows Server 2003 Datacenter Edition | 5.4 | 6.1 | | 9.3 TS1M0 |
Microsoft Windows Server 2003 Enterprise Edition | 5.4 | 6.1 | | 9.3 TS1M0 |
Microsoft Windows Server 2003 Standard Edition | 5.4 | 6.1 | | 9.3 TS1M0 |
Microsoft Windows Server 2003 for x64 | 5.4 | 6.1 | | 9.3 TS1M0 |
Microsoft Windows Server 2008 | 5.4 | 6.1 | | 9.3 TS1M0 |
Microsoft Windows Server 2008 for x64 | 5.4 | 6.1 | | 9.3 TS1M0 |
Microsoft Windows XP Professional | 5.4 | 6.1 | | 9.3 TS1M0 |
Windows 7 Enterprise 32 bit | 5.4 | 6.1 | | 9.3 TS1M0 |
Windows 7 Enterprise x64 | 5.4 | 6.1 | | 9.3 TS1M0 |
Windows 7 Home Premium 32 bit | 5.4 | 6.1 | | 9.3 TS1M0 |
Windows 7 Home Premium x64 | 5.4 | 6.1 | | 9.3 TS1M0 |
Windows 7 Professional 32 bit | 5.4 | 6.1 | | 9.3 TS1M0 |
Windows 7 Professional x64 | 5.4 | 6.1 | | 9.3 TS1M0 |
Windows 7 Ultimate 32 bit | 5.4 | 6.1 | | 9.3 TS1M0 |
Windows 7 Ultimate x64 | 5.4 | 6.1 | | 9.3 TS1M0 |
Windows Vista | 5.4 | 6.1 | | 9.3 TS1M0 |
Windows Vista for x64 | 5.4 | 6.1 | | 9.3 TS1M0 |
64-bit Enabled AIX | 5.4 | 6.1 | | 9.3 TS1M0 |
64-bit Enabled HP-UX | 5.4 | 6.1 | | 9.3 TS1M0 |
64-bit Enabled Solaris | 5.4 | 6.1 | | 9.3 TS1M0 |
HP-UX IPF | 5.4 | 6.1 | | 9.3 TS1M0 |
Linux | 5.4 | 6.1 | | 9.3 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: | 2012-06-29 09:43:42 |
Date Created: | 2012-03-07 10:52:23 |