[Home] [Help]
337: CURSOR validate_impacts_csr (p_ci_type_id pa_ci_types_b.CI_TYPE_ID%type) is
338: select pc.impact_type_code,
339: luk.meaning impact_type_name
340: from pa_control_items pci,
341: pa_ci_impacts pc,
342: pa_lookups luk
343: where pci.ci_type_id = p_ci_type_id
344: and pci.ci_id = pc.ci_id
345: and pc.impact_type_code = luk.lookup_code
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:
412: Also notice that this list is expected to be very small. So no performance concern for the implementation
413: 1. delete * from pa_ci_impact_type_usage where ci_type_id = p_ci_type;
504: ***/
505: -- pre-req: UI has already take care of the FINPLAN exists in p_impact_tbl
506: -- so no additional check needed here.
507: --
508: -- note: In order to sync with pa_ci_impacts budget cost and revenue implementation logic
509: -- modify the code logic as below:
510: -- 1. remove add additional new lookup codes for direct cost and supplier region
511: -- 2. in case if it's direct cost or/and supplier cost region user selected, add
512: -- 'FINPLAN_COST' as a lookup code for both -- only one lookup code