Function Mapping — SEND_ATTACH_VARCHAR2

utl_mail.send_attach_varchar2(...) — the UTL_MAIL.SEND_ATTACH_VARCHAR2 analogue, for one text attachment. Identical shape to SEND_ATTACH_RAW — same argument order, same reasoning for the attachment DEFAULT NULL deviation — with two differences:

	SEND_ATTACH_RAW	SEND_ATTACH_VARCHAR2
attachment type	RAW → bytea	VARCHAR2 → text (stored UTF-8)
att_mime_type default	'application/octet'	'text/plain; charset=us-ascii'

Oracle argument (in order)	Type / default	utl_mail.send_attach_varchar2
sender … priority	(as SEND)	Same mapping
attachment	VARCHAR2, required	attachment text — NULL degrades to a plain send with no attachment
att_inline	BOOLEAN DEFAULT TRUE	att_inline — same default
att_mime_type	DEFAULT 'text/plain; charset=us-ascii'	att_mime_type — same default
att_filename	VARCHAR2 DEFAULT NULL	att_filename — NULL falls back to a default filename
replyto	VARCHAR2 DEFAULT NULL	replyto → p_reply_to — at the end, same position as SEND_ATTACH_RAW

Both att_mime_type defaults were confirmed individually against Oracle's own Parameters table for each procedure, not assumed from their otherwise-near-identical shape — see Function Mapping — SEND_ATTACH_RAW for why that verification step mattered.

---