HI, Can you post your version of SAS Marketing Automation, the operating system you are using for the SAS Servers, and which SAS/Access engine you are using (SAS/Access to SQL Server or SAS/Access to ODBC). Thanks James ... View more

Hi Simon, Take a look at the RTDM User guide (Pg 95 of the current user guide for RTDM6.5) - you will need to create a SAS Process which is done in the Definitions workspace in the Decision Definitions section within CI Studio. When you get to the "SAS Code" part of the process definition you copy the code starting from the "package" key word i.e. you don't need to wrap the code in PROC DS2. Once you have created the process definition you can then add the process you created as a node in the diagram within a decision campaign - which means that when RTDM executes the decision campaign it will execute the DS2 code and run your model. Cheers James ... View more

The IF-THEN-ELSE are the same as normal DS, but the code that wraps around them in DS2 is different to DATA step - I've included a mock up below. As for the Lookups, for very small table we can use the Cross Table node inside a diagram, but for the size you mention its too large. We can lookup data from a table stored in a data set or database using a Data Process inside the diagram. This is a high performing query and can use a very large table (based on the database). But for this I would probably go with coded rules. Cheers James   package GBM_Model/overwrite=yes; /* declare a logger */ declare package logger m_logger('morglum.GMB_Model'); /* set logging methods */ method trace(varchar(32767) msg); m_logger.log(2, msg); end; method debug(varchar(32767) msg); m_logger.log(3, msg); end; method err(varchar(32767) msg); m_logger.log(6, msg); end; method isTraceEnabled() returns int; return m_logger.islevelactive(2); end; method isDebugEnabled() returns int; return m_logger.islevelactive(3); end; /* execute method which gets called by RTDM - the inputs here need to be defined in the RTDM Activity and values passed from the decision flow */ method execute( char gender , char education , int age_years , in_out double predicted_wages ); /* log messages */ if isDebugEnabled() then debug('Entered Execute Method'); /* optional trace messages - maybe not great if there are 100s of inputs */ if isTraceEnabled() then do; trace('Input gender:' gender); trace('Input education:' education); trace('Input age_years:' age_years); end; /* Model IF-THEN-ELSE rules */ if (gender EQ 'Male' and education = 'university' and age_years > 50) then /* if only one output variable the wont need a do block, just set the variable after then on the line above */ do; /* set outputs */ predicted_wages = 45001.10 ; end; else if (gender EQ 'Female' and education = 'university' and age_years > 50) then do; /* set outputs */ predicted_wages = 45001.10 ; end; else /* final block */ do; predicted_wages = 0.0; end; /* End of Model IF-THEN-ELSE rules */ /* log messages */ if isDebugEnabled() then debug('Finished Execute Method'); if isTraceEnabled() then do; trace('Output predicted_wages:' predicted_wages); end; end; end; endpackage;   ... View more

For Option 1, you are still going to need to do some DS2/Jython/Groovy programming to create the necessary web services calls from RTDM -> R Server. There are examples of this on the net to make it easy, but might not be something you want to entertain. Option 3 is embedding your R code inside a Java/Groovy program, and then calling that program inside RTDM. Im not familiar with the R tools that facilitate this, but suffice to say there would be a bunch of Java/Groovy programming involved. However from what I can tell this allows you to use your R model directly ("cut and paste" the code) inside Java, and hence doesn't require an R server at execution time. Option 4 is probably the one that requires the lest amount of "foreign" programming, but will need you to learn a little bit of SAS DS2 to be the wrapper around your exported code. Presumably your exported/converted code uses CASE statements in SQL - in order to use these in DS2 inside RTDM you would need to change these to IF-THEN-ELSE - so perhaps a find replace macro can automate this for you so you can paste the code into RTDM. Certainly doable. Regarding the lookup table, how big is it (rows and columns) and what version of RTDM are you using ? HTH, James ... View more

Hi Lucifer, Some notes and examples below. Cheers James RTDMTable The RTDMTable (com.sas.analytics.ph.common.RTDMTable) type corresponds to a datagrid. It has many useful features for manipulation & traversal. It is required to include the EventInfo object on many RTDMTable methods Create, Write, Read, Delete Here are the basic CRUD operations to work with the RTDMTable object from Python. It also illustrates when the builtin EventInfo object will also be needed inside your activities (for handling WHERE expressions). Example: import java.util.Collections as Collections import java.lang.Long as Long import com.sas.analytics.ph.common.RTDMTable as RTDMTable import com.sas.analytics.ph.common.exp.SymbolTable as SymbolTable import com.sas.analytics.ph.common.jaxb.DataTypes as DataTypes newTable = RTDMTable() # Defining columns newTable.columnAdd("MY_STRING_COLUMN", DataTypes.STRING, Collections.emptyList()); newTable.columnAdd("MY_INT_COLUMN", DataTypes.INT, Collections.emptyList()); # Adding a new row newRow = newTable.rowAdd() newRow.columnDataSet("MY_STRING_COLUMN", "A String value.") newRow.columnDataSet("MY_INT_COLUMN", Long(52)); # Iterating over the table & reading values it = newTable.iterator() while it.hasNext(): row = it.next() value = row.columnDataGet("MY_STRING_COLUMN") num_value = row.columnDataGet("MY_INT_COLUMN") # Deleting all rows with MY_INT_COLUMN greater than 5 newTable.delete(SymbolTable(), "newTable", eventInfo, "newTable.MY_INT_COLUMN GT 5", None); SELECT from existing datagrids To sub-select from an existing datagrid, you use the select() method. The parameters should be familiar to anyone who has used the TableSelect function within a calculated variable. Here is an example: ("fordCars" is an "Output Variable","cars" is a "Input Variable"): import com.sas.analytics.ph.common.exp.SymbolTable as SymbolTable fordCars=cars.select(SymbolTable(), "myTable", eventInfo, "Model", "myTable.Make EQ 'Ford'", None) Join Tables Joining tables is a bit more complicated. RTDM supports only INNER joins between in-memory tables. The syntax should be familiar to those using the TableInnerJoin functionality within calculated items. Here is an example: ("joinedTable" is an "Output Variable", "tableA" and "tableB" are "Input Variables") import com.sas.analytics.ph.common.exp.SymbolTable as SymbolTable joinedTable = tableA.innerJoin( SymbolTable(), "A", # Name for the customer table for use in the columns & WHERE tableB, # The right hand side table "B", # Name for the right hand side table eventInfo, # The event info object (in case of date math) "*", # The columns to retain in the joined table, all in this case "A.Product_code EQ B.Product_number", # The WHERE clause for the JOIN None ) Sorting On the RTDMTable object, there is a direct sort method. This sorts the table in place. You can sort on one or more columns. Example: ("inputTable" is an "Input Variable", "outputTable" is an "Output Variable") inputTable.sort("Color ASCENDING") outputTable=inputTable ... View more

Hi,   Does your random number really need to be that long ? SAS will handle an integer up to 16 digits (doc).   If you can work with that, the the following approach will find your nth digit and has the added benefit of generating Pass Thru SQL from PROC SQL (which is what CI Studio will do)  for most RDBMS:                MOD({your integer variable}, 10) – this returns the last digit              MOD(FLOOR({your integer variable}/10),10) – this returns the 2 nd last digit              MOD(FLOOR({your integer variable}/100),10) – this returns the 3 rd last digit              MOD(FLOOR({your integer variable}/1000),10) – this returns the 4 th last digit   keep adding a zero to the divisor to get the next "digit".   Regards James   ... View more