@Manol_Jovani wrote: Yes, the code above the macro works fine, there is no problem there. Is that what you are asking? No. I am asking if the part inside the macro, when tested without any macro coding, ran. The question about whether quotes are needed or not should have been resolved at that time before adding macros.   Messages about "conversion" Numeric values have been converted to character values at the places given by: (Line):(Column). is a warning that you are writing code incorrectly. That message says that you are doing something that treats a numeric variable as character. You may not know this yet, but numeric variables when converted to character typically do not create a value that works as you may expect. Here is a very simple example of the incompatible "where" clause. data example;; /* character value with digits*/ x='123'; /* numeric value*/ y=123; run; data result; set example; where x=y; run; Caution:  Writing macros without RUN statements ending Procedures or Data steps is also a "gotcha" just waiting to happen. You can write macro code quite easily that incorrectly by-passes an "implied" run and have lines from a following procedure or data step thought as part of the current one running. This is extremely easy if one macro calls another. You can spend a LOT of time tracing down such odd seeming problems caused by this small bit. Ask me how I know😓   Which is why code you attempt to create inside a macro has to be made without macros and run correctly before ever adding a %macro/ %mend. around it.   ... View more