Didn't work is awful vague.
Are there errors in the log?: Post the code and log in a code box opened with the "<>" to maintain formatting of error messages.
No output? Post any log in a code box.
Unexpected output? Provide input data in the form of data step code pasted into a code box, the actual results and the expected results. Instructions here: https://communities.sas.com/t5/SAS-Communities-Library/How-to-create-a-data-step-version-of-your-dat... will show how to turn an existing SAS data set into data step code that can be pasted into a forum code box using the "<>" icon or attached as text to show exactly what you have and that we can test code against.
Quite often when using macros the first debug option is to set OPTIONS MPRINT before code that executes macro to se what the macro generates. The error messages, if any, will also then appear in closer proximity to code generating them.
Just to confirm you did compile the macro in the current session before running the code, didn't you?
Your code is sending a litteral dt to the macro where you highlight it. There is nothing that supplies values to the variable dt (on the right of the = sign) as you have no SET or similar statement to reference a data set to provide them. You are not using a macro variable as shown. You would have to show the actual value of the macro variable to have a chance of this working.
If your
id = dt ;/* note you did not have a ; to end the statement*/
was supposed to be
id = &dt;
why does that statement exist? If your &dt macro variable contains multiple values that you intend to use one at a time then you need to get stuff from the macro and split it up, not copy it.
Maybe something along these lines (depends a LOT on actual value of the not shown macro variable dt.
data Junk;
length longstr $ 200;
Do i= 1 to countw("&dt.");
dttemp = scan("&dt.",i);
longstr = cats('%creating_data_tables(out_tbl = abc , in_file = bnk_mkt_scr_',dttemp,'.xlsx);');
output;
call execute(longstr);
end;
run;
Suggestion would be to run the above with the CALL Execute commented out so that it does not execute and examine the values of the LONGSTR variable to see if the code for the macro call is correct. If so, then uncomment the call execute. The test without call execute takes so little time you lose not much time compared to trying to figure out why all the executes you create are throwing errors.
HINT: Your code as designed is very useless as the apparent output is reused and the result will only be the version for the last value of the dt variable. This is based on a macro parameter named OUT_TBL which I expect to be the desired result. You overwrite it with each execution of the macro.
Click image to register for webinar
