11g with WF installed - Create Package issues.

Question

Hi All,
I have installed 11.2.0.1.0, and then installed the workflow server provided under the Products directory.
This is being used as a test environment.
I have logged into the environment as both SYS and OWF_MGR and also created a new user (XXR and applied some privileges) and am having some difficulty compiling a package.
My package contains the following:
p_result := wf_engine.eng_completed||':'||'Y';
I kept receiving compiling issues and am receiving the following error:
PLS-00201: identifier 'WF_ENGINE.ENG_COMPLETED' must be declared
Can anyone assist in finding out why i am receiving this issue? Am i assuming that the workflow engine doesn't exist, or i haven't applied correct privileges to either SYS, OWF_MGR or XXR?
Cheers,
Russell H.

Answer 1

Russell H. wrote:
I kept receiving compiling issues and am receiving the following error:
PLS-00201: identifier 'WF_ENGINE.ENG_COMPLETED' must be declared
Can anyone assist in finding out why i am receiving this issue? Am i assuming that the workflow engine doesn't exist, or i haven't applied correct privileges to either SYS, OWF_MGR or XXR?Logon as SYS. Run:
select * from dba_objects where object_name = 'WF_ENGINE'
This will tell you what objects there are with that name, their owners, and their types.
There are 2 ways to address an object in your PL/SQL code.
Explicitly. You provide explicit scope resolution to the PL/SQL engine by specifying the owner and object name. E.g.
p_result := schema_owner.wf_engine.eng_completed||':'||'Y'
Implicitly. You do not provide the name of the object's owner, or even the actual name of the object itself. Instead local and public synonyms are used by the PL/SQL engine to resolve the actual object being referenced. (your current statement uses implicit scope)
You need execute rights on the object also.
Last thing to do is make sure that the procedure/function call to that package, is done correctly. For example, not calling a function as a procedure, or vice versa. Getting the return and parameter data types correct. Etc.