[Home] [Help]
9237: END IF;
9238:
9239: END LOOP;*/
9240: --log1('PBL 9 '||to_char(sysdate,'DD-MON-YYYY HH24:MI:SS'));
9241: PA_FP_CALC_PLAN_PKG.calculate(
9242: p_project_id => p_version_info_rec.x_project_id
9243: ,p_budget_version_id => p_budget_version_id
9244: ,p_rollup_required_flag => 'N'
9245: ,p_source_context => l_calc_calling_context
9262: --log1('PBL 10 '||to_char(sysdate,'DD-MON-YYYY HH24:MI:SS'));
9263: IF x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
9264:
9265: IF l_debug_mode = 'Y' THEN
9266: pa_debug.g_err_stage:='Called API PA_FP_CALC_PLAN_PKG.calculate returned error';
9267: pa_debug.write(l_module_name,pa_debug.g_err_stage, l_debug_level3);
9268: END IF;
9269: RAISE PA_FP_CONSTANTS_PKG.Invalid_Arg_Exc;
9270: END IF;
10489: the WEB ADI related procedures will populate PA_FP_WEBADI_UPLOAD_INF table and does not commit
10490:
10491: 2. Switcher API will be invoked after WEB ADI related code flow is completed.
10492:
10493: 3. Swicher API internally invokes PA_FP_CALC_PLAN_PKG.CALCULATE which inturn
10494: invokes the actual budget client extension
10495:
10496: 4. In client extension, as part of bug fix 3736220 added code to Stamp client extension errors
10497: in xface table (we stamp the val_error_code and val_error_flag of
10497: in xface table (we stamp the val_error_code and val_error_flag of
10498: PA_FP_WEBADI_UPLOAD_INF table)
10499:
10500: 5. But the client extension is designed in such a way that when any error occurs in
10501: client extension we roll back to the calling API PA_FP_CALC_PLAN_PKG. So the stamped data
10502: gets rolled back. Ulimately the customers customized errors cannot be displayed in excel
10503: due to this rollback.
10504:
10505: 6. Hence in order to preserve the stamped val_error_code and val_error_flag