Oracle (and any other DBMS I know of) does not have the concept of macro variables. If you use explicit pass-through, you have to convert the code to Oracle standards first, and have macro variables resolved to Oracle-compatible formats.
Are you sure that the Oracle side will understand a SAS MACRO variable of form '21JAN19'd?
I don't use Oracle but have seen a number of questions here about passing macro values to Oracle that make me believe this may not be appropriate.
It would likely help those who know more about Oracle than I do to include your connection info and the code using this macro variable. XXXX out anything like user or password in the connection.
Oracle (and any other DBMS I know of) does not have the concept of macro variables. If you use explicit pass-through, you have to convert the code to Oracle standards first, and have macro variables resolved to Oracle-compatible formats.
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.