However, I was not able to reproduce this, so I am unsure as to why you would be getting that error. It may depend on the package definition(user vs definer's rights), or how the table privileges were granted(through roles vs directly to the user).
If you have a testcase that demonstrates it, then feel free to post it or file an SR.
It may well be worth stating that I am new to using Oracle Workspace Manager.
Here is some background of how the Tables/Database is set up.
Users are assigned to a role called 'ADVANCED_USER' which grants the ability to SELECT, INSERT, UPDATE and DELETE on all tables in the database and also applies to another schema created by a different user. A GRANT EXECUTE to the packages controlling the updates has also given to the 'ADVANCED_USER'
In addition to this individual users are also assigned WM_ADMIN_ROLE.
I am however unsure by what you mean when you say +‘package definition (user vs definer's rights)’+. I naively assume that it would be whatever the default would be as I have not knowingly changed or set anything when creating the package.
It may take some time for me to produce a test case, but I will try and post one ASAP.
Packages are by default definer's rights, which means the package runs with the privileges of the owner of the package, not necessarily the user running it. Typically, privileges granted through roles are not enabled within procedures/packages, and instead the privileges need to be granted directly.
If you do get a testcase, I could confirm whether or not this is the cause of the behavior you are seeing.