Copy Job needs more functionality

Here's another issue: I spun up a simple Copy Job to bring in ONE table from an ODBC source because the original mechanism responsible for loading the data wasn't doing its job. To protect from hosing up the table in question (in a Warehouse) I decided that I would append the table name with "_CopyJob" to differentiate between the two. The original source AND destination table are named [PUB].[oeeh]. So I set the new destination table name as [oeeh_CopyJob]. But what I ended up with was a table in the dbo schema named, ["PUB"."oeeh_CopyJob"]. I didn't look closely enough at the Destination Mapping, which DEFAULTED by table to the [dbo] schema, with a table name of "Pub"."oeeh". Come ON, Microsoft. PLEASE READ THE SOURCE SCHEMA!!! There is a Destination Schema OF THE SAME NAME. Figure it out and use it by default!