SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 57909: Counts are incorrect when you import SAS® Customer Intelligence Response definitions using SPK files

DetailsHotfixAboutRate It

Importing SAS Customer Intelligence response definitions by using SPK files might result in incorrect counts on the Response. Consider the following scenario:

  • You create a response definition in one environment (for example, your test environment).
  • You use an SPK file to import that response definition to another environment (for example, the production environment).
  • In the production environment, you use this imported response definition and create values in the CI_RESPONSE table.
  • Then you change the response definition in the test environment, and you re-import the SPK file again to the production environment.

When the counts on the Response node are updated, the node returns 0 counts.

This issue happens because re-importing the SPK file creates a new RESPONSE_SK value in the CI_RESPONSE table. However, it keeps the same RESPONSE_CD and RESPONSE_NM values, as shown below:

image label

When you then update the counts on the Response node in the production environment, the node returns 0 counts because the macro code does not factor in that a new RESPONSE_SK is available. This incorrect count results from having two RESPONSE_SK values (91 and 96) for the same response, as shown in the previous display. When this occurs, the SASCustIntelCore6.x.log file looks similar to the following:

MPRINT(MARESPEX): proc sql noprint; MPRINT(MARESPEX): create table cellpackagesk as select * from CIDB.CI_RESPONSE_HISTORY where CELL_PACKAGE_SK in (select CELL_PACKAGE_SK FROM CIDB.CI_CELL_PACKAGE where Campaign_CD="CAMP1735" and Communication_CD="COMM2857"); NOTE: Table WORK.CELLPACKAGESK created, with 22149 rows and 14 columns. MPRINT(MARESPEX): quit; NOTE: PROCEDURE SQL used (Total process time): real time 0.45 seconds cpu time 0.21 seconds MPRINT(MARESPEX): data MATables.THFEF3ZEUDRA5QI2Esasdemo(keep=INDIVID) counts(keep=Count); MPRINT(MARESPEX): retain Count 0; MPRINT(MARESPEX): set cellpackagesk end=done; MPRINT(MARESPEX): where response_sk= MPRINT(LEFT): 91 MPRINT(MARESPEX): ; MPRINT(MARESPEX): Count + 1; MPRINT(MARESPEX): output MATables.THFEF3ZEUDRA5QI2Esasdemo; MPRINT(MARESPEX): if done then output Counts; MPRINT(MARESPEX): run; NOTE: There were 0 observations read from the data set WORK.CELLPACKAGESK. WHERE response_sk=91; NOTE: The data set MATABLES.THFEF3ZEUDRA5QI2ESASDEMO has 0 observations and 1 variables.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Customer Intelligence StudioMicrosoft Windows 8.1 Enterprise x646.36.59.4 TS1M3
Microsoft Windows 8.1 Enterprise 32-bit6.36.59.4 TS1M3
Microsoft Windows 8 Pro x646.36.59.4 TS1M3
Microsoft Windows 8 Pro 32-bit6.36.59.4 TS1M3
Microsoft Windows 8 Enterprise x646.36.59.4 TS1M3
Microsoft Windows 8 Enterprise 32-bit6.36.59.4 TS1M3
Microsoft® Windows® for x646.36.59.4 TS1M3
Microsoft Windows 8.1 Pro 32-bit6.36.59.4 TS1M3
Microsoft Windows 8.1 Pro x646.36.59.4 TS1M3
Microsoft Windows 106.36.59.4 TS1M3
Microsoft Windows Server 20086.36.59.4 TS1M3
Microsoft Windows Server 2008 R26.36.59.4 TS1M3
Microsoft Windows Server 2008 for x646.36.59.4 TS1M3
Microsoft Windows Server 2012 Datacenter6.36.59.4 TS1M3
Microsoft Windows Server 2012 R2 Datacenter6.36.59.4 TS1M3
Microsoft Windows Server 2012 R2 Std6.36.59.4 TS1M3
Microsoft Windows Server 2012 Std6.36.59.4 TS1M3
Windows 7 Enterprise 32 bit6.36.59.4 TS1M3
Windows 7 Enterprise x646.36.59.4 TS1M3
Windows 7 Home Premium 32 bit6.36.59.4 TS1M3
Windows 7 Home Premium x646.36.59.4 TS1M3
Windows 7 Professional 32 bit6.36.59.4 TS1M3
Windows 7 Professional x646.36.59.4 TS1M3
Windows 7 Ultimate 32 bit6.36.59.4 TS1M3
Windows 7 Ultimate x646.36.59.4 TS1M3
64-bit Enabled AIX6.36.59.4 TS1M3
64-bit Enabled Solaris6.36.59.4 TS1M3
HP-UX IPF6.36.59.4 TS1M3
Linux for x646.36.59.4 TS1M3
Solaris for x646.36.59.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.