Desktop productivity for business analysts and programmers

Failure in running RFM in EG

Reply
Occasional Contributor
Posts: 6

Failure in running RFM in EG

I don't know why i fail to run the RFM analysis where i am successfully run it before.

May i know if anyone know why? Thanks

 

Error Log enclosed

 

1                                                          The SAS System                               17:44 Sunday, April 22, 2018

1          ;*';*";*/;quit;run;
2          OPTIONS PAGENO=MIN;
3          %LET _CLIENTTASKLABEL='Recency, Frequency, and Monetary Analysis (9)';
4          %LET _CLIENTPROCESSFLOWNAME='Process Flow';
5          %LET _CLIENTPROJECTPATH='G:\Data Mining Group Project\KKBox Churn Project.egp';
6          %LET _CLIENTPROJECTPATHHOST='DESKTOP-3A38KG7';
7          %LET _CLIENTPROJECTNAME='KKBox Churn Project.egp';
8          
9          ODS _ALL_ CLOSE;
10         ODS PROCTITLE;
11         OPTIONS DEV=PNG;
12         GOPTIONS XPIXELS=0 YPIXELS=0;
13         FILENAME EGSR TEMP;
14         ODS tagsets.sasreport13(ID=EGSR) FILE=EGSR
15             STYLE=HTMLBlue
16             STYLESHEET=(URL="file:///C:/Program%20Files/SASHome/SASEnterpriseGuide/7.1/Styles/HTMLBlue.css")
17             NOGTITLE
18             NOGFOOTNOTE
19             GPATH=&sasworklocation
20             ENCODING=UTF8
21             options(rolap="on")
22         ;
NOTE: Writing TAGSETS.SASREPORT13(EGSR) Body file: EGSR
23         FILENAME EGXLSSX TEMP;
24         ODS EXCEL(ID=EGXLSSX) FILE=EGXLSSX STYLE=Excel
25         OPTIONS (
26          EMBEDDED_TITLES="no" EMBEDDED_FOOTNOTES="no" SHEET_INTERVAL="None"
27         );
28         
29         GOPTIONS ACCESSIBLE;
30         
31         
32         %aaRFM;
NOTE:  Macro AARFM_EXEC has been processed.
33         %EM_RFM_CONTROL
34         (
35            Mode = T,
36            InData = WORK.TRANS_02_28_ALL,
37            CustomerID = msno,
38            N_R_Grp = 5,
39            N_F_Grp = 5,
40            N_M_Grp = 5,
41            BinMethod = N,
42            PurchaseDate = transaction_date,
43            PurchaseAmt = actual_amount_paid,
44            SetMiss = Y,
45            SummaryFunc = SUM,
46            MostRecentDate = ,
47            NPurchase = ,
48            TotPurchaseAmt = ,
49            MonetizationMap = Y,
50            BinChart = Y,
51            BinTable = Y,
52            OutData = LOCAL.RFM_TABLE_LT,
53            Recency_Score = recency_score_LT,
54            Frequency_Score = frequency_score_LT,
55            Monetary_Score = monetary_score_LT,
56            RFM_Score = rfm_score_LT
2                                                          The SAS System                               17:44 Sunday, April 22, 2018

57         );

NOTE: The data set WORK._RFM_INDATA_CONTENTS_ has 3 observations and 3 variables.
NOTE: PROCEDURE CONTENTS used (Total process time):
      real time           0.01 seconds
      cpu time            0.00 seconds
      


NOTE: There were 3 observations read from the data set WORK._RFM_INDATA_CONTENTS_.
NOTE: DATA statement used (Total process time):
      real time           0.00 seconds
      cpu time            0.00 seconds
      


NOTE: There were 21908933 observations read from the data set WORK.TRANS_02_28_ALL.
NOTE: The data set WORK._RFM_INDATA_COPY_ has 21908933 observations and 3 variables.
NOTE: DATA statement used (Total process time):
      real time           2.48 seconds
      cpu time            1.86 seconds
      


NOTE: There were 21908933 observations read from the data set WORK._RFM_INDATA_COPY_.
NOTE: The data set WORK._RFM_TEMP2_ has 21908933 observations and 3 variables.
NOTE: The data set WORK._RFM_TEMP3_ has 0 observations and 3 variables.
NOTE: DATA statement used (Total process time):
      real time           2.43 seconds
      cpu time            1.79 seconds
      


NOTE: There were 21908933 observations read from the data set WORK._RFM_TEMP2_.
NOTE: The data set WORK._RFM_OUTDATA_COPY_ has 2391675 observations and 4 variables.
NOTE: PROCEDURE SUMMARY used (Total process time):
      real time           8.01 seconds
      cpu time            12.37 seconds
      

NOTE: Table WORK._RFM_TEMP1_ created, with 0 rows and 1 columns.

NOTE: PROCEDURE SQL used (Total process time):
      real time           0.01 seconds
      cpu time            0.00 seconds
      


NOTE: There were 2391675 observations read from the data set WORK._RFM_OUTDATA_COPY_.
NOTE: The data set WORK._RFM_OUTDATA_COPY_ has 2391675 observations and 4 variables.
NOTE: PROCEDURE SORT used (Total process time):
      real time           0.35 seconds
      cpu time            0.71 seconds
      


NOTE: There were 2391675 observations read from the data set WORK._RFM_OUTDATA_COPY_.
NOTE: There were 0 observations read from the data set WORK._RFM_TEMP1_.
3                                                          The SAS System                               17:44 Sunday, April 22, 2018

NOTE: The data set WORK._RFM_OUTDATA_COPY_ has 2391675 observations and 4 variables.
NOTE: DATA statement used (Total process time):
      real time           0.34 seconds
      cpu time            0.34 seconds
      


NOTE: Deleting WORK._RFM_TEMP1_ (memtype=DATA).
NOTE: Deleting WORK._RFM_TEMP2_ (memtype=DATA).
NOTE: Deleting WORK._RFM_TEMP3_ (memtype=DATA).
NOTE: PROCEDURE DATASETS used (Total process time):
      real time           0.12 seconds
      cpu time            0.12 seconds
      


NOTE: There were 2391675 observations read from the data set WORK._RFM_OUTDATA_COPY_.
NOTE: The data set WORK._RFM_OUTDATA_COPY_ has 2391675 observations and 4 variables.
NOTE: DATA statement used (Total process time):
      real time           0.26 seconds
      cpu time            0.26 seconds
      


NOTE: There were 2391675 observations read from the data set WORK._RFM_OUTDATA_COPY_.
NOTE: The data set WORK._RFM_OUTDATA_COPY_ has 2391675 observations and 4 variables.
NOTE: PROCEDURE SORT used (Total process time):
      real time           0.34 seconds
      cpu time            0.75 seconds
      

NOTE: Table WORK._RFM_TEMP2_ created, with 790 rows and 3 columns.

NOTE: PROCEDURE SQL used (Total process time):
      real time           0.51 seconds
      cpu time            0.98 seconds
      


NOTE: There were 790 observations read from the data set WORK._RFM_TEMP2_.
NOTE: The data set WORK._RFM_TEMP3_ has 790 observations and 3 variables.
NOTE: DATA statement used (Total process time):
      real time           0.01 seconds
      cpu time            0.01 seconds
      

NOTE: Table WORK._RFM_SCORE_ created, with 2391675 rows and 5 columns.

NOTE: PROCEDURE SQL used (Total process time):
      real time           0.79 seconds
      cpu time            1.35 seconds
      

NOTE: Table WORK._RFM_TEMP2_ created, with 316 rows and 4 columns.

NOTE: PROCEDURE SQL used (Total process time):
      real time           0.76 seconds
      cpu time            1.07 seconds
4                                                          The SAS System                               17:44 Sunday, April 22, 2018

      


NOTE: There were 316 observations read from the data set WORK._RFM_TEMP2_.
NOTE: The data set WORK._RFM_TEMP3_ has 316 observations and 4 variables.
NOTE: DATA statement used (Total process time):
      real time           0.01 seconds
      cpu time            0.00 seconds
      

NOTE: Table WORK._RFM_TEMP1_ created, with 2391675 rows and 6 columns.

NOTE: PROCEDURE SQL used (Total process time):
      real time           1.00 seconds
      cpu time            1.31 seconds
      

NOTE: Table WORK._RFM_TEMP2_ created, with 30652 rows and 5 columns.

NOTE: PROCEDURE SQL used (Total process time):
      real time           0.70 seconds
      cpu time            1.11 seconds
      


NOTE: There were 30652 observations read from the data set WORK._RFM_TEMP2_.
NOTE: The data set WORK._RFM_TEMP3_ has 30652 observations and 5 variables.
NOTE: DATA statement used (Total process time):
      real time           0.01 seconds
      cpu time            0.03 seconds
      

NOTE: Table WORK._RFM_SCORE_ created, with 2391675 rows and 7 columns.

NOTE: PROCEDURE SQL used (Total process time):
      real time           1.29 seconds
      cpu time            1.45 seconds
      


NOTE: Deleting WORK._RFM_TEMP1_ (memtype=DATA).
NOTE: Deleting WORK._RFM_TEMP2_ (memtype=DATA).
NOTE: Deleting WORK._RFM_TEMP3_ (memtype=DATA).
NOTE: PROCEDURE DATASETS used (Total process time):
      real time           0.03 seconds
      cpu time            0.03 seconds
      


NOTE: There were 2391675 observations read from the data set WORK._RFM_SCORE_.
NOTE: The data set WORK._RFM_SCORE_ has 2391675 observations and 4 variables.
NOTE: DATA statement used (Total process time):
      real time           0.25 seconds
      cpu time            0.25 seconds
      


NOTE: Input data set is already sorted, no sorting done.
5                                                          The SAS System                               17:44 Sunday, April 22, 2018

NOTE: PROCEDURE SORT used (Total process time):
      real time           0.00 seconds
      cpu time            0.00 seconds
      


NOTE: There were 2391675 observations read from the data set WORK._RFM_SCORE_.
NOTE: The data set WORK._RFM_SCORE_ has 2391675 observations and 4 variables.
NOTE: PROCEDURE SORT used (Total process time):
      real time           0.71 seconds
      cpu time            1.42 seconds
      


NOTE: There were 2391675 observations read from the data set WORK._RFM_OUTDATA_COPY_.
NOTE: There were 2391675 observations read from the data set WORK._RFM_SCORE_.
NOTE: The data set WORK._RFM_OUTDATA_COPY_ has 2391675 observations and 8 variables.
NOTE: DATA statement used (Total process time):
      real time           0.57 seconds
      cpu time            0.56 seconds
      

NOTE: Format RECENCY_FMT is already on the library WORK.FORMATS.
NOTE: Format RECENCY_FMT has been output.
NOTE: Format FREQUENCY_FMT is already on the library WORK.FORMATS.
NOTE: Format FREQUENCY_FMT has been output.
NOTE: Format MONETARY_FMT is already on the library WORK.FORMATS.
NOTE: Format MONETARY_FMT has been output.
NOTE: Format RFM_FMT is already on the library WORK.FORMATS.
NOTE: Format RFM_FMT has been output.

NOTE: PROCEDURE FORMAT used (Total process time):
      real time           0.00 seconds
      cpu time            0.00 seconds
      


NOTE: There were 3 observations read from the data set SASHELP.VTITLE.
NOTE: DATA statement used (Total process time):
      real time           0.01 seconds
      cpu time            0.01 seconds
      

NOTE: There were 2391675 observations read from the data set WORK._RFM_OUTDATA_COPY_.
NOTE: PROCEDURE TABULATE used (Total process time):
      real time           0.56 seconds
      cpu time            0.96 seconds
      

NOTE: PROCEDURE SGPLOT used (Total process time):
      real time           0.59 seconds
      cpu time            0.40 seconds
      
NOTE: There were 2391675 observations read from the data set WORK._RFM_OUTDATA_COPY_.

NOTE: PROCEDURE SGPLOT used (Total process time):
      real time           3.14 seconds
      cpu time            2.95 seconds
6                                                          The SAS System                               17:44 Sunday, April 22, 2018

      
NOTE: The column format YYMMDD10 is replaced by an auto-generated format on the axis.
NOTE: The column format YYMMDD10 is replaced by an auto-generated format on the axis.
NOTE: There were 2391675 observations read from the data set WORK._RFM_OUTDATA_COPY_.

NOTE: PROCEDURE SGPANEL used (Total process time):
      real time           7.25 seconds
      cpu time            6.95 seconds
      
NOTE: There were 2391675 observations read from the data set WORK._RFM_OUTDATA_COPY_.

NOTE: PROCEDURE SGPANEL used (Total process time):
      real time           13.04 seconds
      cpu time            11.60 seconds
      
NOTE: Marker and line antialiasing has been disabled for at least one plot because the threshold has been reached. You can set
      ANTIALIASMAX=15400 in the ODS GRAPHICS statement to enable antialiasing for all plots.
NOTE: Marker and line antialiasing has been disabled for at least one plot because the threshold has been reached. You can set
      ANTIALIASMAX=15400 in the ODS GRAPHICS statement to enable antialiasing for all plots.
NOTE: There were 2391675 observations read from the data set WORK._RFM_OUTDATA_COPY_.

NOTE: Since no format is assigned, the numeric category variable will use the default of BEST6.
NOTE: PROCEDURE SGPANEL used (Total process time):
      real time           8.00 seconds
      cpu time            7.57 seconds
      
NOTE: There were 2391675 observations read from the data set WORK._RFM_OUTDATA_COPY_.

NOTE: Since no format is assigned, the numeric category variable will use the default of BEST6.
NOTE: PROCEDURE SGPANEL used (Total process time):
      real time           20.32 seconds
      cpu time            13.65 seconds
      
NOTE: VIEWMIN=0.0 is invalid. The option expects positive value for a log axis. The default will be used.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
7                                                          The SAS System                               17:44 Sunday, April 22, 2018

NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: Marker and line antialiasing has been disabled for at least one plot because the threshold has been reached. You can set
      ANTIALIASMAX=9600 in the ODS GRAPHICS statement to enable antialiasing for all plots.
NOTE: Some of the tick values have been thinned.
NOTE: Some of the tick values have been thinned.
NOTE: Some of the tick values have been thinned.
NOTE: Some of the tick values have been thinned.
NOTE: Some of the tick values have been thinned.
NOTE: VIEWMIN=0.0 is invalid. The option expects positive value for a log axis. The default will be used.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: The log axis cannot support zero or negative values for the axis from plot data or due to default or assigned
      BASELINEINTERCEPT value. The axis type will be changed to LINEAR.
NOTE: Marker and line antialiasing has been disabled for at least one plot because the threshold has been reached. You can set
      ANTIALIASMAX=9600 in the ODS GRAPHICS statement to enable antialiasing for all plots.
NOTE: Some of the tick values have been thinned.
NOTE: Some of the tick values have been thinned.
NOTE: Some of the tick values have been thinned.
NOTE: Some of the tick values have been thinned.
NOTE: Some of the tick values have been thinned.
NOTE: There were 2391675 observations read from the data set WORK._RFM_OUTDATA_COPY_.

ERROR: Template 'MonetizationMap' was unable to write to template store!
8                                                          The SAS System                               17:44 Sunday, April 22, 2018

NOTE: PROCEDURE TEMPLATE used (Total process time):
      real time           0.00 seconds
      cpu time            0.00 seconds
      
WARNING: Errors were produced.
NOTE: The SAS System stopped processing this step because of errors.



NOTE: Deleting WORK._RFM_INDATA_CONTENTS_ (memtype=DATA).
NOTE: Deleting WORK._RFM_INDATA_COPY_ (memtype=DATA).
NOTE: Deleting WORK._RFM_OUTDATA_COPY_ (memtype=DATA).
NOTE: Deleting WORK._RFM_SCORE_ (memtype=DATA).
NOTE: PROCEDURE DATASETS used (Total process time):
      real time           0.18 seconds
      cpu time            0.18 seconds
      

ERROR:  (EM_RFM_CONTROL) Errors occurred in procedures while invoking this macro.  Please refer to the LOG for details.

NOTE: (EM_RFM_CONTROL) Elapsed Time = 0:01:14.88
58         
59         GOPTIONS NOACCESSIBLE;
60         %LET _CLIENTTASKLABEL=;
61         %LET _CLIENTPROCESSFLOWNAME=;
62         %LET _CLIENTPROJECTPATH=;
63         %LET _CLIENTPROJECTPATHHOST=;
64         %LET _CLIENTPROJECTNAME=;
65         
66         ;*';*";*/;quit;run;
67         ODS _ALL_ CLOSE;
NOTE: Writing EXCEL(EGXLSSX) file: C:\Users\Nicolas\AppData\Local\Temp\SEG2500\SAS Temporary
      Files\_TD14448_DESKTOP-3A38KG7_\#LN01524
68         
69         
70         QUIT; RUN;
71         

Super User
Posts: 13,889

Re: Failure in running RFM in EG

Posted in reply to nicolaskan

Proximate cause is what ever caused this:

ERROR: Template 'MonetizationMap' was unable to write to template store!

You might try turning on options mprint symbolgen; before running the code to see more details of what is going on. Macros generally only show the error after all of the code and not for each step in connection to what was attempted. Sometimes MPRINT reveals more of what was going on. In this case the creation of a template.

 

 

Some possible causes:

An update path from proc template was not run or successful, so not place to write the template.

The path to the template store is not set as writeable or update.

Permissions on the location not set.

Some other general failure to the template creation code.

 

If you have run this before I would look for changes in your configuration or perhaps options. If there was other code you ran prior to the previous success and you did not run it this time that could be a cause. Change of servers? Change in data structure-one or more of the data variables are missing from the data set, have all values missing, change of data type. Something changed in your environment so you'll have to check on what may have changed since the last time.

Ask a Question
Discussion stats
  • 1 reply
  • 153 views
  • 1 like
  • 2 in conversation