Concurrent Program Quarries..
How to find out Responsibility name based on Con Program Name?
SELECT responsibility_name , frg.request_group_name,
fcpv.user_concurrent_program_name, fcpv.description , fcpv.CONCURRENT_PROGRAM_ID
FROM apps.fnd_request_groups frg,
apps.fnd_request_group_units frgu,
apps.fnd_concurrent_programs_vl fcpv,
apps.fnd_responsibility_vl frv
WHERE frgu.request_unit_type = 'P'
AND frgu.request_group_id = frg.request_group_id
AND frgu.request_unit_id = fcpv.concurrent_program_id
AND frv.request_group_id = frg.request_group_id
--AND responsibility_name like '%Inv%'
--AND request_group_name = 'All inclusive'
AND user_concurrent_program_name like 'Con Program Name%'
ORDER BY responsibility_name;
How to find out Request Set name based on Con Program Name?
SELECT DISTINCT user_request_set_name
FROM FND_REQUEST_SETS_TL
WHERE request_set_id IN
(SELECT request_set_id
FROM FND_REQUEST_SET_PROGRAMS
WHERE concurrent_program_id =
(SELECT CONCURRENT_PROGRAM_ID
FROM fnd_concurrent_programs_tl
WHERE upper(USER_CONCURRENT_PROGRAM_NAME) = upper( '&Enter_Prog_name')));
How to find out Responsibility name based on Request set Name?
select frt.responsibility_name, frg.request_group_name,
frgu.request_unit_type,frgu.request_unit_id,
fcpt.user_request_set_name
From apps.fnd_Responsibility fr, apps.fnd_responsibility_tl frt,
apps.fnd_request_groups frg, apps.fnd_request_group_units frgu,
apps.fnd_request_Sets_tl fcpt
where frt.responsibility_id = fr.responsibility_id
and frg.request_group_id = fr.request_group_id
and frgu.request_group_id = frg.request_group_id
and fcpt.request_set_id = frgu.request_unit_id
and frt.language = USERENV('LANG')
and fcpt.language = USERENV('LANG')
and fcpt.user_request_set_name = :request_set_name
order by 1,2,3,4;
How to find out Responsibility Name based on Request ID
SELECT request_id, responsibility_name
FROM fnd_concurrent_requests fcr, fnd_responsibility_tl frt
WHERE fcr.responsibility_id = frt.responsibility_id
AND request_id = :request_id;
/* Pls provide your valuable suggestions and feed backs */
No comments:
Post a Comment