[Home] [Help]
867: , G_etype_cr
868: , G_etype_cost_rate_flag
869: FROM
870: pa_expenditure_cost_rates ecr
871: , pa_expenditure_types et
872: WHERE
873: et.expenditure_type = ecr.expenditure_type (+)
874: AND X_date BETWEEN ecr.start_date_active (+)
875: AND nvl(ecr.end_date_active (+), X_date)
1307: nvl(sl.start_date_active, p_exp_item_date) sl_start_date,
1308: nvl(sl.end_date_active, p_exp_item_date) sl_end_date
1309: from pa_projects_all p,
1310: pa_tasks t,
1311: pa_expenditure_types et,
1312: pa_expend_typ_sys_links sl
1313: where p.project_id = p_project_id
1314: and t.project_id = p_project_id
1315: and t.task_id = p_task_id
2664: pa_cc_utils.reset_curr_function;
2665: RETURN;
2666: END IF;
2667:
2668: -- Check pa_expenditure_types table for for existence and activeness of
2669: -- the given exp_type combination
2670: IF PG_DEBUG = 'Y' THEN
2671: pa_debug.G_err_stage := 'Calling GetEtypeInfo';
2672: log_message('log_message: ' || pa_debug.G_err_Stage);
2683:
2684: -- Based on project journal design a transaction source can have more than one system_linkage
2685: -- So the validation of system_linkage of source with expenditure type is no more valid.
2686: -- The validation should be between the system_linkage of the record and the system_linkage of
2687: -- expenditure type of the same record. At present the system linkage is in pa_expenditure_types
2688: -- table. But once the new table for expenditure type and system_linkage is created, the given
2689: -- record's system linkage should be checked for existence in the new table.
2690: -- Selva 03/07/97
2691: