[Home] [Help]
342: IS
343: SELECT 'Y'
344: FROM DUAL
345: WHERE EXISTS (SELECT 1
346: FROM pa_budget_lines pbl
347: WHERE pbl.budget_version_id = p_budget_version_id
348: AND( pbl.cost_rejection_code IS NOT NULL
349: OR pbl.revenue_rejection_code IS NOT NULL
350: OR pbl.burden_rejection_code IS NOT NULL
904: PA_UTILS.Add_Message(p_app_short_name => 'PA',
905: p_msg_name => 'PA_BU_NO_PROJ_END_DATE');
906: end if;
907:
908: update pa_budget_lines
909: set start_date= v_project_start_date,
910: end_date = v_project_completion_date
911: where resource_assignment_id in
912: (select resource_assignment_id
941: if (bl_rec.start_date is null) or (bl_rec.completion_date is null) then
942: PA_UTILS.Add_Message(p_app_short_name => 'PA',
943: p_msg_name => 'PA_BU_NO_TASK_PROJ_DATE');
944: else
945: update pa_budget_lines
946: set start_date = bl_rec.start_date,
947: end_date = bl_rec.completion_date
948: where resource_assignment_id = bl_rec.resource_assignment_id and
949: ((start_date <> bl_rec.start_date) or (end_date <> bl_rec.completion_date));
2905: END CREATE_DRAFT;
2906:
2907: /*
2908: This procedure would use the input budget_line_tbl to insert records into
2909: pa_resource_assignments, pa_budget_lines, pa_mc_budget_lines and also takes
2910: care of rolling up the resource assignments and maintaining the denorm table.
2911: */
2912: PROCEDURE CREATE_FINPLAN_LINES
2913: ( -- Bug Fix: 4569365. Removed MRC code.
3337: END IF;
3338:
3339: */
3340: --Bug # 3507156-
3341: --Replaced PA_FP_EDIT_LINE_PKG.PROCESS_MODIFIED_LINES with an insert to pa_budget_lines
3342:
3343: -- Bug 3825873 17-JUL-2004 Do not insert amounts as calculate first checks existing values
3344: -- and the input values are different and then only acts on the record.
3345:
3352: * Bug 4221590: commenting out the following code to avoid creation of budget lines
3353: * with null quantities, instead population pa_fp_spread_calc_tmp1, so that calculate
3354: * api can use that to insert/spread the budget lines passed from AMG/MSP
3355: *----------------------------------------------------------------------------------------
3356: INSERT INTO pa_budget_lines(
3357: RESOURCE_ASSIGNMENT_ID
3358: ,BUDGET_LINE_ID
3359: ,BUDGET_VERSION_ID
3360: ,START_DATE
3421: ,PM_BUDGET_LINE_REFERENCE ) -- Added for bug 3833724
3422:
3423: (SELECT
3424: RESOURCE_ASSIGNMENT_ID
3425: ,pa_budget_lines_s.nextval
3426: ,p_fin_plan_version_id
3427: ,START_DATE
3428: ,SYSDATE
3429: ,FND_GLOBAL.USER_ID
3657: -- To avoid this planning_start_date is updated with original value if the original
3658: -- planning_start_date is least.
3659: IF(p_calling_context = PA_FP_CONSTANTS_PKG.G_AMG_API) THEN
3660: -- For scenario if actuals exist then planning start date for resource assignment
3661: -- should be least of the value presnt in pa_fp_spread_calc_tmp1 and pa_budget_lines
3662: -- else it should be least of value present in pa_fp_spread_calc_tmp1.
3663:
3664: --bug#8854015 Added condition to directly update the planning_start_date and planning_end_date
3665: -- if the updation is for non-time based.
3691: nvl(min(tmp.start_date), planning_start_date),
3692: least(nvl(min(tmp.start_date), planning_start_date),
3693: nvl(min(pbl.start_date), planning_start_date))),
3694: greatest(nvl(max(tmp.end_date), planning_end_date), planning_end_date) -- bug#10376078
3695: from pa_fp_spread_calc_tmp1 tmp, pa_budget_lines pbl
3696: where tmp.resource_assignment_id = pra.resource_assignment_id
3697: and pbl.resource_assignment_id (+)= tmp.resource_assignment_id)
3698: where pra.budget_version_id = p_fin_plan_version_id;
3699: END IF;