Not sure, but you could export your table using V/I and chain it to an import job that sets the UDF's value.

Sweet i'll try that. 

One of the Source options is ODBC, so you can select the table from your SOTAMAS90 data source. I've never tried updating the table that's used as the source table though.  That would be interesting.

ah super clever.  I'll try that.  

hyanaga is right. You can indeed configure a VI Import job to query CI_Item, for example, and also update CI_Item. Just set the source to ODBC, select the DSN you want to use, and if you want to hardcode credentials which is fine if you only have one company, then click the "green key" button, enter the user and target company code separated by the vertical pipe ("|"), e.i. username|ABC and then enter the password.

If you have more than one company, i don't recommend saving the credentials because the last thing you might want to do is accidentally run the import under another company code other than the one hardcoded in the credentials causing you to end up pulling data from the hardcoded company code and creating records in the wrong company code.

After you select your ODBC data source, click the "Tables" button, you can then use each tab to step through building the SQL string for you.

If you decide you want to include a WHERE clause, you can go to the last tab and click "Modify SQL", click though the warning and then edit the SQL as needed.

Your suggestions worked, here is my process for the internets. 

new job > ODBC Data Source > Select the table > SQL Statement (tab); 

SELECT
CI_Item.ItemCode 
FROM
CI_Item
WHERE
CI_Item.UDF_ETA < {fn CURDATE()}

Setup the rest of the job like normal.