Oracle Apps Database Concepts [message #164571] |
Fri, 24 March 2006 00:46 |
Lachmi
Messages: 18 Registered: June 2004
|
Junior Member |
|
|
Hi,
My queries is :
If I create tables & packaged procedures (meant for Payables) in apps schema but register/define then as Concurrent Program under Payables as the application, will they work ?
I am facing problem while running a Concurrent Program. The scenario is as follows :
1. Created 2 staging tables in apps schema
2. Created a PL/SQL packaged procedure in apps schema which takes an IN parameter and is used by the main cursor to fetch data which is further validated. Most of the tables used are in apps schema & rest are either views or synonyms.
3. Executed the procedure from Sql*Plus successfully by logging under apps.
After registering the above packaged procedure as a Concurrent Program under the Application - Payables, the IN parameter takes a NULL value which is apparent from the message in the log. If I remove the IN parameter & run the program for all records it works fine from SRW.
The scripts files are attached
-
Attachment: pkg.txt
(Size: 9.75KB, Downloaded 2275 times)
|
|
|
Re: Oracle Apps Database Concepts [message #164736 is a reply to message #164571] |
Sat, 25 March 2006 05:12 |
kittu915
Messages: 51 Registered: February 2006 Location: Hyderabad,India
|
Member |
|
|
hi..
if you want to create concurent program for the package which uses some other schema's table ,first grant all previleges on the table to the payable, and try..i think it has to work.
i have seen ur package..i think u know the importance of errbuff and retcode parameters..right??
good luck..
kittu.
|
|
|
Re: Oracle Apps Database Concepts [message #164820 is a reply to message #164736] |
Sun, 26 March 2006 22:11 |
Lachmi
Messages: 18 Registered: June 2004
|
Junior Member |
|
|
Thanks Kittu.
What is standard practice ? Should we compile packages in apps schema or in the module specific schema ?
I will appreciate all inputs on errbuff and retcode parameters as I only know that they are used for sending execution status to the Concurrent Manager but am not very sure about their usage.
|
|
|
|
Re: Oracle Apps Database Concepts [message #164835 is a reply to message #164830] |
Mon, 27 March 2006 00:16 |
Lachmi
Messages: 18 Registered: June 2004
|
Junior Member |
|
|
Hi manwadka,
I don't need to register my staging tables because they are not being used by any front-end.
Providing grants of the apps object to ap worked fine. Moreover once I shifted the p_source IN patameter after the errbuff & retcode parameters even the parameter passing is taking palce successfully.
Thanks.
|
|
|
Re: Oracle Apps Database Concepts [message #164971 is a reply to message #164835] |
Mon, 27 March 2006 21:22 |
kittu915
Messages: 51 Registered: February 2006 Location: Hyderabad,India
|
Member |
|
|
hi lachmi...
Generally what people will do is create tables in the schema according to which module they use(here in AP) and will grant all privileges to apps(creating sysnonym is some times needed), by default oracle looks for apps schema only,so compile your package in apps only.
Regarding errbuff& retcode , defaulty they are out parameters and as you said they are used to execution status to concurrent manager as i know..try in metalink.
Kittu.
|
|
|
|
Re: Oracle Apps Database Concepts [message #176512 is a reply to message #164571] |
Thu, 08 June 2006 09:58 |
agostino_neto
Messages: 180 Registered: July 2005
|
Senior Member |
|
|
First, there is no parameter in your package.
You can set a value to errbuf or retcode when an error occurs.
These values will give the completion code (success, error, warning) and message.
In addition to what Kiran said, we generally create Concurrent Program under custom application (you can add your program to custom or standard request group).
|
|
|