This happens in the following scenario. You open filed based procedure, chosen a connection in the connections chooser (otherwise, the run action is not active), and then hit Run (or Debug). The message informs you that there is no such procedure in the database, so you are advised to compile it.
Behind the scenes SQLDev executes the query
SELECT OBJECT_ID, PIPELINED
WHERE OWNER = ? AND OBJECT_NAME = ?
which you can witness in the statements log. Can you please execute this statement manually and inform what is going on?
P.S. Of course you can just expand the navigator, open the db-based pl/sql module and run it without any chance of hitting this snag.
A slightly different case, for a non-public function in a package body, turned up in a web search:
The error message you posted references <Procedure Name> rather than <Package Name>, so Vadim's response seems more relevant.
Gary,It is the procedure that I am trying to run.And for Vadim's query no rows are returned.I am using Version 3.0.04.
Sounds like you do not have the correct privileges. What should have been granted to you by the QA user, or some other user with appropriate privileges, is...
grant EXECUTE on "QA"."<PROCEDURE_OF_INTEREST>" to "<YOUR_USERID>" ;
Note that a grant of execute on a procedure has nothing to do with grants of select on some or all of QA's tables and views.
So, as Vadim suggests, from your connection node in SQL Developer's Connections view, if you expand the Other Users node, then expand QA and look in the Procedures node, do you see the procedure of interest? If not, you cannot expect to be able to execute it from your userid's connection. And even if you do see it, you may have some other privilege that permits viewing but not executing, like...
The role SELECT_CATALOG_ROLE
The system privilege SELECT ANY DICTIONARY
And even if you do not see it there, then having certain other privileges granted to you could permit executing it in general, like...
The role EXECUTE_CATALOG_ROLE
The system privilege EXECUTE ANY PROCEDURE
Also, note that the 3.0 release is a bit dated nowadays. Upgrading to 4.0.3 production or even the 4.1 EA2 (early adopter) release will, in general, give you a better experience.