Passing SAS Functions to Yellowbrick

SAS/ACCESS Interface to Yellowbrick passes the following SAS functions to Yellowbrick for processing. Where the Yellowbrick function name differs from the SAS function name, the Yellowbrick name appears in parentheses. For more information, see Passing Functions to the DBMS Using PROC SQL.

ABS LOG2 (LOG)
ARCOS (ACOS) LOWCASE (LOWER)
ARSIN (ASIN) MINUTE
ATAN MOD (see note)
ATAN2 MONTH
BYTE QTR
CEIL REPEAT
COALESCE SECOND
COS SIGN
COUNT SIN
DAY SQRT
DAYOFWEEK STD (STDDEV_SAMP)
EXP STRIP (BTRIM)
FLOOR SUBSTR
HOUR TAN
INDEX (POSITION, STRPOS) TRANWRD (REPLACE)
LENGTH TRIMN (RTRIM)
LENGTHC (CHARACTER_LENGTH) UPCASE (UPPER)
LENGTHN (LENGTH) VAR (VAR_SAMP)
LOG (LN) YEAR
LOG10 (LOG)
Note: SAS does not modify non-integer arguments to the MOD function. If your DBMS does truncate non-integer arguments to MOD, then DBMS results for this function might vary from SAS results. For more information, see Functions Where Results Might Vary: MOD Function.

SQL_FUNCTIONS=ALL allows for SAS functions that have slightly different behavior from corresponding database functions that are passed down to the database. Only when SQL_FUNCTIONS=ALL can the SAS/ACCESS engine also pass these SAS SQL functions to Yellowbrick. Because of incompatibility in date and time functions between Yellowbrick and SAS, Yellowbrick might not process them correctly. Check your results to determine whether these functions are working as expected.

COMPRESS ROUND
DATE (CURRENT_DATE) TIMEPART
DATEPART TODAY (CURRENT_DATE)
DATETIME (NOW) TRANSLATE
Last updated: February 3, 2026