Concurrent program details from backend
Do we
really login to EBS always to check what the concurrent program definition is,
and what is executable type and parameters?
To do this we have to access to either application developer or system
administrator and also we have to navigate two screens, concurrent program
-> Define and Concurrent Program -> executable to avoid this I wrote
small script to view from backend
/*--------------Script
to view concurrent program details ---------------*/
SELECT (SELECT basepath
FROM fnd_application
WHERE application_id = cp.application_id)
cp_application
,(SELECT basepath
FROM fnd_application
WHERE application_id = FE.application_id)
ex_application
,cp.concurrent_program_id program_id
,user_concurrent_program_name
,executable_name
,execution_file_name
,DECODE(fe.execution_method_code
,'P', 'Oracle Reports'
,'H', 'Host'
,'S', 'Immidate'
,'J', 'Java Stored Procedure'
,'K', 'Java Concurrent Program'
,'M', 'Multi Language Function'
,'I', 'PL/SQL Stored Procedures'
,'B', 'Request Set Stage Function'
,'A', 'Spwaned'
,'L', 'SQL*Loader'
,'Q', 'SQL*Plus'
,'E', 'Perl Concurrent Program'
,'Not Listed')
execution_method
,dfcu.End_user_column_name
,dfcu.enabled_flag
,dfcu.REquired_flag
,dfcu.display_flag
,dfcu.default_type
,dfcu.DEFAULT_VALUE
FROM fnd_concurrent_programs cp
,fnd_concurrent_programs_tl cpt
,fnd_executables fe
,fnd_descr_flex_column_usages dfcu
WHERE user_concurrent_program_name = 'ANIL: Links Loader Program'
AND cp.concurrent_program_id
= cpt.concurrent_program_id
AND fe.executable_id
= cp.executable_id
AND dfcu.application_id
= cp.application_id
AND descriptive_flexfield_name = '$SRS$.' || concurrent_program_name
AND descriptive_flex_context_code = 'Global Data Elements'
AND dfcu.enabled_flag
= 'Y'
ORDER BY column_seq_num;
No comments:
Post a Comment