Thank you again Ray. Unfortunately I am now a little more confused: My SAS Code node is between my original data file and my Text Parsing node. Below is a picture of the original variables I have: And the following is what my path looks like: The variables that reside within my Text Parsing node are: So it seems all it brought over was the text field. But the following shows what variables occur in the Text Filter node: So it does have the new ordinal variable that I created with your guidance: proc format;   value F_TOTALRESERVES_B                           0 -< 300 = 1                           300 -< 1500 = 2                           1500 -< 10000 = 3                           10000 - high = 4; run; data &em_export_train;   set &em_import_data;   TOTALRESERVES_B = put(TOTALRESERVES, F_TOTALRESERVES_B.); run; %EM_METACHANGE(   NAME = TOTALRESERVES_B,   LEVEL = ORDINAL,   ROLE = TARGET                  ); I did have to make one change or addition. I not only said LEVEL = ORDINAL but I also included ROLE = TARGET. Is that possibly eliminating the other variables? Overall I think it would be best to bring over all of the variables. But I am also concerned that when I originally ran the Text Rule Builder it did not converge after one hour. As background I have about 100,000 text documents, the three Train parameters in the Text Rule Builder node were set to Very Low, and the Minimum Number of Documents in the Text Filter node was set at 20. The next time I run it I think I should set things at Medium with the minimum number of documents set to 200. Any other suggestions are welcome. I am enjoying learning all of this. Thank you again. ... View more

Thank you so much for the answer. I was sort of barking up the right tree but did not have the %EM_METACHANGE part. I will be using this with a Text Rule Builder Node. My question is after I run the Code Node I want to see my variables but it is not there. Will it be there by the time I get past a few other nodes (Text Parsing, Text Filter) to get to the Text Rule Builder Node? I guess I am a little worried because I do not see it in my variable listing. ... View more

Thank you MIguel. You are the first to respond to my query. Thank you - it helped. Onto the last-minute question I tacked-on at the end... "is there a way to specify where I would like the SAS data file (.sas7bdat) to be placed and named?" Thanks. ... View more

Thanks a bunch. Is a little comforting knowing that. ... View more

Thank you very much, again. I am working from home today (kind of sick) but will make some meeetings with the IT folks when I get back into the office. Can you recommend a good site to make the distinction between date and date-time variables? ... View more

Thank you very much. It was able to precisely isolate the year I was looking for. Yay! But now I am worried about how I have been pulling in the data and date ranges all of this time. Below is the code I use to generally pull in the data when working with our IT deparment: proc sql; CONNECT TO oracle( user=sas_app orapw="{sas002}F47DB14D49A3125D1A77A9662758292C10070A844C83FEB8424BEBA7" path="@test" ); EXECUTE ( execute uw_predict.fill_in_data(to_date('01/01/2004', 'MM/DD/YYYY'), to_date('12/31/2013', 'MM/DD/YYYY')) ) by oracle; DISCONNECT FROM oracle; But then I have been kick-starting my more targeted code with the following: DATA POLICY;   SET OraRef.SAS_POLICY;   where (EFFECTIVE_DATE >= "01Jan2004"d and EFFECTIVE_DATE <= "31Dec2013"d) and (MULTI_STATE_FLAG = "N"); RUN; Does that mean that I have been incorrectly pulling in dates? I know I am at the very least in the ballpark. You are correct in that EFFECTIVE_DATE is DATETIME20. ... View more

Trying all of your suggestions, thank you again. At the bottom is a picture of my data if I comment out the date selection- maybe you see something in my code below. You will also notice the new way I did it by putting ED in the middle of the range: data POLICY;   set L_P1.PolicyData2012 (keep = pol_phr_code pol_code pol_cmp_code MULTI_STATE_FLAG EFFECTIVE_DATE EXPIRE_DATE);   /* where ('01JAN2012'd <= EFFECTIVE_DATE <= '02JAN2012'd) and (MULTI_STATE_FLAG = "N"); */ run; Also, thank you for introducing me to proc compare. I am also inserting another screen image of how I tried to calculate the year off of the EFFECTIVE_DATE variable. You can see with all of the notes that I was not very successful. Sorry that this one is dragging on. But thank you. I clearly need more help. ... View more

Thank you very much for the suggestion. Unfortunately it does not appear to be the culprit. But something is weird about my end date of <= "31Dec2012"d. If I thrown in the first date everything is ok. But having that 2nd date is somehow throwing things off? I even substituted the variable name for the beginning date into the 2nd one in case if I had any hidden characters. Nothing is working, so far. ... View more

Thank you Sanjay. My chart is similar to yours - but my boxes do not show up at all given the quality of the data I am working with. ... View more

That is great information from both of you guys! Thank you so much. Now the problem I am dealing with is my scatterplots are skewed in a major way. Wihin each of the 10 categories the majority of the points are zero - no longer thinking boxplots would be terribly conducive to understanding such a skewed distribution. Any other suggestions to graphically see what is going on in a snapshot? If I were to just send out my percentiles an example for one of my categories could be: P1 0 P5 0 P10 0 P25 0 P50 0 P75 6 P90 22 P95 47 P99 128 Can anyone think of a way to adjust such scatterplots in these situations? Perhaps put a condition in that the value needs to be > 0 - but then I am steering away from the original question. Thank you. ... View more