| How to Trap FND_REQUEST.SUBMIT_REQUEST ERROR IN Database procedure [message #265523] |
Thu, 06 September 2007 10:06 |
sauami
Messages: 54
Registered: October 2005
Location: india
|
Member |
|
|
Dear Sir,
I have a procedure which firing another concurrent by using
v_purge_errors := FND_REQUEST.SUBMIT_REQUEST(c_application_short_name, -- APPLICATION SHORT NAME
c_poxpierr, -- CONC PROGRAM NAME
NULL,
NULL,
FALSE,
'SOME PROG NAME', -- Source Program
'Y' -- Purge Data
);
IF v_purge_errors = 0 THEN
g_error_code := g_conc_prog_err;
FND_MESSAGE.set_name('GEWEFND',g_error_code);
FND_MESSAGE.set_token ('CONTEXT','Purge Interface errors process was not submitted successfully');
g_message := FND_MESSAGE.get;
In above code I have mentioned predefine error g_conc_prog_err; it will be save in my error table what ever error is coming. But I want to know or trap the actual error which is occurred during the execution of my fnd_request program.
I had try to use fnd_message.error for getting the error but its given undefine PLS-00302: component 'ERROR' must be declared while compiling the code.
Because this is my database procedure.
Pls. help me how can I trap this error and save the real error in my error table.
Thanks,
Saurabh
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
