Not sure if you figured this out or not... But I don't see a response with the most obvious answer.

This is a simple mistake I make all too often

I suspect that you created the object without specifying which account you wanted it created under.

For example, in my databases we use a generic "dbo" account for all our objects. So our objects would be

[DatabaseName].dbo.[objectname]

I am guessing that you simply forgot to specify which account you wanted the object TRANSACTEDET created under.

i.e. you probably said something like

Create Table TRANSACTEDET blah blah blah.

When you should have used

Create Table dbo.TRANSACTEDET

So, I would assume that your account is the only account that has access to the table. So when you run the package locally through VS, the package inherits your permissions and can access the object; but Agent is unable to do so since it does not have access.

Recreate the table with the correct permissions and you should be golden.