[Home] [Help]
797: , G_etype_cr
798: , G_etype_cost_rate_flag
799: FROM
800: pa_expenditure_cost_rates ecr
801: , pa_expenditure_types et
802: WHERE
803: et.expenditure_type = ecr.expenditure_type (+)
804: AND X_date BETWEEN ecr.start_date_active (+)
805: AND nvl(ecr.end_date_active (+), X_date)
1216: nvl(sl.start_date_active, p_exp_item_date) sl_start_date,
1217: nvl(sl.end_date_active, p_exp_item_date) sl_end_date
1218: from pa_projects_all p,
1219: pa_tasks t,
1220: pa_expenditure_types et,
1221: pa_expend_typ_sys_links sl
1222: where p.project_id = p_project_id
1223: and t.project_id = p_project_id
1224: and t.task_id = p_task_id
2401: pa_cc_utils.reset_curr_function;
2402: RETURN;
2403: END IF;
2404:
2405: -- Check pa_expenditure_types table for for existence and activeness of
2406: -- the given exp_type combination
2407: IF PG_DEBUG = 'Y' THEN
2408: pa_debug.G_err_stage := 'Calling GetEtypeInfo';
2409: log_message('log_message: ' || pa_debug.G_err_Stage);
2420:
2421: -- Based on project journal design a transaction source can have more than one system_linkage
2422: -- So the validation of system_linkage of source with expenditure type is no more valid.
2423: -- The validation should be between the system_linkage of the record and the system_linkage of
2424: -- expenditure type of the same record. At present the system linkage is in pa_expenditure_types
2425: -- table. But once the new table for expenditure type and system_linkage is created, the given
2426: -- record's system linkage should be checked for existence in the new table.
2427: -- Selva 03/07/97
2428: