Monday, September 9, 2013
SELECT p.profile_option_name
short_name,
n.user_profile_option_name NAME,
DECODE(v.level_id,
10001,'Site',
10002,'Application',
10003,'Responsibility',
10004,'User',
'UnDef'
) level_set,
v.level_value level_val,
v.profile_option_value VALUE
FROM fnd_profile_options p,
fnd_profile_option_values v,
fnd_profile_options_tl n
WHERE p.profile_option_id = v.profile_option_id(+)
AND p.profile_option_name = n.profile_option_name
AND
UPPER(n.user_profile_option_name)LIKEUPPER('%&ProfileName%');
Monday, September 9, 2013 by Team search · 3
1. Check
workflow mailer service current status
SELECT running_processes
SELECT running_processes
FROM fnd_concurrent_queues
WHERE concurrent_queue_name ='WFMLRSVC';
Note : Number of running processes > 0
2. Find current mailer status
2. Find current mailer status
SELECT component_status
FROM fnd_svc_components
WHERE component_id =(SELECT component_id
FROM fnd_svc_components
WHERE component_name ='Workflow Notification Mailer');
Possible statuses are :
RUNNING
STARTING
STOPPED_ERROR
DEACTIVATED_USER
DEACTIVATED_SYSTEM
3. Stop notification mailer
DECLARE
Possible statuses are :
RUNNING
STARTING
STOPPED_ERROR
DEACTIVATED_USER
DEACTIVATED_SYSTEM
3. Stop notification mailer
DECLARE
p_retcode
NUMBER;
p_errbuf
VARCHAR2(100);
m_mailerid
fnd_svc_components.component_id%TYPE;
BEGIN
SELECT component_id
INTO m_mailerid
FROM fnd_svc_components
WHERE component_name ='Workflow Notification Mailer';
fnd_svc_component.stop_component (m_mailerid,
p_retcode,
p_errbuf
);
COMMIT;
END;
/
4. Start notification mailer
DECLARE
4. Start notification mailer
DECLARE
p_retcode
NUMBER;
p_errbuf
VARCHAR2(100);
m_mailerid
fnd_svc_components.component_id%TYPE;
BEGIN
SELECT component_id
INTO m_mailerid
FROM fnd_svc_components
WHERE component_name ='Workflow Notification Mailer';
fnd_svc_component.start_component (m_mailerid,
p_retcode,
p_errbuf
);
COMMIT;
END;
/
by Team search · 0
The
concurrent request can be submitted via shell script. This can be done by a
standard utility named CONSUB. It can be used to schedule a request
too.
In
this post, I tried providing few details about it.
The syntax for CONCSUB is given below:
CONCSUB APPS username APPS password
responsibility application short name
responsibility name
username
[WAIT=N|Y|]
CONCURRENT
program application short name
program name
[PROGRAM_NAME=””]
[REPEAT_TIME=]
[REPEAT_INTERVAL=]
[REPEAT_INTERVAL_UNIT=< resubmission unit>]
[REPEAT_INTERVAL_TYPE=< resubmission type>]
[REPEAT_END=]
[START=]
[IMPLICIT=< type of concurrent request>
[ ... ]
The syntax for CONCSUB is given below:
CONCSUB APPS username APPS password
responsibility application short name
responsibility name
username
[WAIT=N|Y|
CONCURRENT
program application short name
program name
[PROGRAM_NAME=”
[REPEAT_TIME=
[REPEAT_INTERVAL=
[REPEAT_INTERVAL_UNIT=< resubmission unit>]
[REPEAT_INTERVAL_TYPE=< resubmission type>]
[REPEAT_END=
[START=
[IMPLICIT=< type of concurrent request>
[
These
are the compulsory Parameters:
PARAMETER
|
DESCRIPTION
|
ORACLE ID
|
Username and
Password of the ORACLE ID for Applications, separated by a slash (“/”). This
would be apps/appspass
|
Responsibility Application Short Name
|
Enter the short name of the application for your
responsibility. This name, along with your responsibility name, will be used
to select a responsibility for your request to run in. eg : SYSADMIN
|
Responsibility Name
|
This name, along with your responsibility
application short name, will be used to select a responsibility for your
concurrent request to run in.
eg : ”System Administrator” |
User name
|
Enter the name of your Application Object Library
user. This name will be used to update the Who information for any data your
concurrent manager changes.
eg : SYSADMIN |
CONCURRENT
|
A flag that separates the program–specific
parameters from the operating system parameters.
|
Program application short name
|
The application short name of your concurrent
program.
eg : FND |
Program name
|
The uppercase name of your program. It must be
the short name that you enter in the Concurrent Programs window when defining
a concurrent program.
|
by Team search · 0
Subscribe to:
Posts (Atom)
Disclaimer
The ideas, thoughts and concepts expressed here are my own. They, in no way reflect those of my employer or any other organization/client that I am associated. The articles presented doesn't imply to any particular organization or client and are meant only for knowledge Sharing purpose. The articles can't be reproduced or copied without the Owner's knowledge or permission.