What is the GRANT or permission setting that allows viewing of package body

Question

For purposes of SOX and security/audit control, we log in under our network id's in our production environment. We have sourcecode compiled into Oracle seeded schemas ( APPS ) so that scheduled jobs are able to run with submitted from the Oracle Applications environment. We don't compile code into our personal network account areas.
I know how to GRANT EXECUTE privs so that we can execute a package in another schema, but what I want to do is to be able to view the sourcecode in another schema. Compile into APPS but be able to see the package body from my network id schema account.
I can't seem to find what the correct permission is anywhere. Granted I can look at DBA_SOURCE to get to it, but I want to use a tool like SQL Developer or TOAD to look at the code in a more presentable and easier to debug manner.
Any help ?

Answer 1

I guess you need GRANT DEBUG ON SCOTT.PKG TO U
SYS@LSC01> create or replace package scott.pk is procedure p; end pk;
  2  /
Package created.
SYS@LSC01> create or replace package body scott.pk is procedure p is begin null; end; end pk;
  2  /
Package body created.
SYS@LSC01> grant create session to u identified by u;
Grant succeeded.
SYS@LSC01> grant execute on scott.pk to u;
Grant succeeded.
SYS@LSC01> connect u/u
Connected.
U@LSC01> select text from all_source where name='PK';
TEXT
package       pk is procedure p; end pk;
U@LSC01> connect / as sysdba
Connected.
SYS@LSC01> grant debug on scott.pk to u;
Grant succeeded.
SYS@LSC01> connect u/u
Connected.
U@LSC01> select text from all_source where name='PK';
TEXT
package       pk is procedure p; end pk;
package body       pk is procedure p is begin null; end; end pk;