APPS.PA_CI_TYPES_PVT dependencies on PA_CI_IMPACTS

Line 382: pa_ci_impacts pc

378: -- check if impacts exists for control item type
379: CURSOR validate_impacts_csr (p_ci_type_id pa_ci_types_b.CI_TYPE_ID%type) is
380: select 1
381: from pa_control_items pci,
382: pa_ci_impacts pc
383: where pci.ci_type_id = p_ci_type_id
384: and pci.ci_id = pc.ci_id;
385:
386: l_impacts_exists boolean := false;

Line 407: pa_ci_impacts pc,

403: p_impact_type_code varchar2) is
404: select pc.impact_type_code,
405: luk.meaning impact_type_name
406: from pa_control_items pci,
407: pa_ci_impacts pc,
408: pa_lookups luk
409: where pci.ci_type_id = p_ci_type_id
410: and pci.ci_id = pc.ci_id
411: and pc.impact_type_code = luk.lookup_code

Line 422: pa_ci_impacts pc,

418: p_impact_type_code varchar2) is
419: select pc.impact_type_code,
420: luk.meaning impact_type_name
421: from pa_control_items pci,
422: pa_ci_impacts pc,
423: pa_lookups luk,
424: pa_budget_versions pbv,
425: pa_resource_assignments pra
426: where pci.ci_type_id = p_ci_type_id

Line 447: pa_ci_impacts pc,

443: p_impact_type_code varchar2) is
444: select pc.impact_type_code,
445: luk.meaning impact_type_name
446: from pa_control_items pci,
447: pa_ci_impacts pc,
448: pa_lookups luk,
449: pa_budget_versions pbv,
450: pa_resource_assignments pra
451: where pci.ci_type_id = p_ci_type_id