eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.PA_CI_IMPACT_TYPE_USAGE_PVT dependencies on DUAL

Line 30: SELECT 'Y' FROM dual

26: )
27: IS
28: l_rowid VARCHAR2(30);
29: CURSOR check_exists is
30: SELECT 'Y' FROM dual
31: WHERE exists (SELECT ci_impact_type_usage_id FROM
32: pa_ci_impact_type_usage
33: -- WHERE ci_type_class_code = p_ci_type_class_code
34: WHERE nvl(ci_type_class_code, 1) = nvl(p_ci_type_class_code, 1) -- cklee

Line 204: SELECT 'Y' FROM dual

200: )
201: IS
202: l_temp VARCHAR2(1);
203: CURSOR check_exists is
204: SELECT 'Y' FROM dual
205: WHERE exists (SELECT ci_impact_type_usage_id FROM
206: pa_ci_impact_type_usage
207: WHERE ci_impact_type_usage_id = p_ci_impact_type_usage_id
208: );

Line 407: validation at last because we can by pass the TAPI to validate for each individual impact

403: x_msg_count := 0;
404: x_msg_data := '';
405: /*
406: This is the simplest way to implement the shuttle bean activities. The main reason we put the
407: validation at last because we can by pass the TAPI to validate for each individual impact
408: deletion and we validate after all database transactions (delete and insert new lists) are done;
409: if however, any list is missing from the pa_ci_impacts, we can list all missing list in once
410: so that user can fix on UI in once.
411: