Re: PLS-00201 and ORA-00942 when creating a package
From a DBA standpoint:
The descriptions of these errors in the manual will explain that the schema
in which you're attempting to create the package does not have appropriate
permissions on the objects that your referencing. Note that these
permissions must be granted directly to the schema (not via a role)
Verify the permissions by checking the USER_TAB_PRIVS_ RECD data dictionary
view which, despite the name, lists the user's received privileges for all
types of database objects
Perhaps someone that has worked directly with Oracle Apps can give some
insight on what is and is not recommended when customizing the apps.
--
Mark C. Stock
mcstock -enquery(dot)com
www.enquery.com training & consulting
"Per Magnus L?vold" <pmlovold@broad park.nowrote in message
news:a0c31732.0 401050234.b1307 ba@posting.goog le.com...
| Hi,
| I am trying to create a package under the apps schema, and I keep
| getting PLS-00201 and ORA-00942 when refering to types from other
| apps-packages and other views / tables.
|
| I even get this error when calling a quite simple:
| MY_NUM := FND_PROFILE.VAL UE('MY_PROFILE_ NAME');
|
| Any ideas what I can be doing wrong?
| This same code was originally part of a trigger code, and worked just
| fine.
|
| -Per Magnus
PLS-00201 and ORA-00942 when creating a package
Collapse
This topic is closed.
X
X
-
Guest replied -
PLS-00201 and ORA-00942 when creating a package
Hi,
I am trying to create a package under the apps schema, and I keep
getting PLS-00201 and ORA-00942 when refering to types from other
apps-packages and other views / tables.
I even get this error when calling a quite simple:
MY_NUM := FND_PROFILE.VAL UE('MY_PROFILE_ NAME');
Any ideas what I can be doing wrong?
This same code was originally part of a trigger code, and worked just
fine.
-Per Magnus
Tags: None
Leave a comment: