Won't say anything about what that code is supposed to do because you still have not included ALL the code between %Macro and %mend. All of it.
So far basically what I see is 1) a reference to data sets with a macro variable without definition anywhere:
set &transform_para;
set &relevant_tab;
That macro variable is not a parameter and not defined. So without a definition for these variables all this code will do is generate errors about no data set on a SET statement and then perhaps run or not if there is currently a data set named Transformation in the Work library (that may well not have any of the correct variables or expected values).
Don't see definitions for
&matchby
&intercept
either.
Another reason for suspecting not very familiar with the macro language is reading the same data set 10 times to populate 10 macro variables which can be done with a single pass:
proc sql noprint;
select sex,age into :SS separated by '/', :AA separated by ','
from sashelp.class
;
quit;
%put SS is: &ss. , AA is: &aa.;
This bit code tells me that that it is highly likely that only one of the macro conditions really should be set:
if &variable &condition9. then score=&i_score;
if &variable &conditioon8. then score=&h_score;
if &variable &conditioon7. then score=&g_score;
if &variable &conditioon6. then score=&f_score;
if &variable &conditioon5. then score=&e_score;
if &variable &conditioon4. then score=&d_score;
if &variable &conditioon3. then score=&c_score;
if &variable &conditioon2. then score=&b_score;
if &variable &conditioon1. then score=&Null_score;
Reason: Since there are multiple conditions that all assign values to the exact same variable then only the lowest numbered condition is actually kept in the result. So why bother setting more than 1???? Additionally NONE of those "conditioon" macro variables exist because the parameters defined are spelled with one o as in "condition" not "conditioon".
Except for &Condition9 which is spelled correctly those statements resolve to something like
if "variable" then score= <the assignment for that line>.
If the value passed into the macro for variable does not resolve to something that can be made numeric that will create an error for "Invalid numeric data
And lastly your shown example of the macro call:
%Generate_transformed_Scores (variables=LongestOverdueMonth,Has_Left=0,Has_Right=0,
condition1=>=3,
condition1=>=2,
condition1=>=1,
condition1=<1,
Meaningful_Null=0);
Will throw an error first because the macro defined name shown is GENERATE_TRANSFORMED_SCORED, not GENERATE_TRANSFORMED_SCORES If you get that fixed you have another set of errors because the parameter VARIABLES is not defined for the Macro, the variable name is VARIABLE.
And has multiple Condition1, so will throw a completely different set of errors
ERROR: The keyword parameter CONDITION1 passed to macro GENERATE_TRANSFORMED_SCORED was given a value twice.
Some one needs to check spelling frequently.
Most of the time when some one builds as many macro variables that code appears to do then there is a poor understanding of what the macro language should be used for (I know, I've been there). Pulling values out of data set, sticking them into macro variables just so they can be used in a formula means that someone didn't know how to combine data sets so the actual variables from the original data set could be used.
Without examples of the INPUT data sets complete and correct code can't say what it is supposed to do. What is shown is going to throw a number of errors.
