[Home] [Help]
9069: END IF;
9070:
9071: END LOOP;*/
9072: --log1('PBL 9 '||to_char(sysdate,'DD-MON-YYYY HH24:MI:SS'));
9073: PA_FP_CALC_PLAN_PKG.calculate(
9074: p_project_id => p_version_info_rec.x_project_id
9075: ,p_budget_version_id => p_budget_version_id
9076: ,p_rollup_required_flag => 'N'
9077: ,p_source_context => l_calc_calling_context
9094: --log1('PBL 10 '||to_char(sysdate,'DD-MON-YYYY HH24:MI:SS'));
9095: IF x_return_status <> FND_API.G_RET_STS_SUCCESS THEN
9096:
9097: IF l_debug_mode = 'Y' THEN
9098: pa_debug.g_err_stage:='Called API PA_FP_CALC_PLAN_PKG.calculate returned error';
9099: pa_debug.write(l_module_name,pa_debug.g_err_stage, l_debug_level3);
9100: END IF;
9101: RAISE PA_FP_CONSTANTS_PKG.Invalid_Arg_Exc;
9102: END IF;
10308: the WEB ADI related procedures will populate PA_FP_WEBADI_UPLOAD_INF table and does not commit
10309:
10310: 2. Switcher API will be invoked after WEB ADI related code flow is completed.
10311:
10312: 3. Swicher API internally invokes PA_FP_CALC_PLAN_PKG.CALCULATE which inturn
10313: invokes the actual budget client extension
10314:
10315: 4. In client extension, as part of bug fix 3736220 added code to Stamp client extension errors
10316: in xface table (we stamp the val_error_code and val_error_flag of
10316: in xface table (we stamp the val_error_code and val_error_flag of
10317: PA_FP_WEBADI_UPLOAD_INF table)
10318:
10319: 5. But the client extension is designed in such a way that when any error occurs in
10320: client extension we roll back to the calling API PA_FP_CALC_PLAN_PKG. So the stamped data
10321: gets rolled back. Ulimately the customers customized errors cannot be displayed in excel
10322: due to this rollback.
10323:
10324: 6. Hence in order to preserve the stamped val_error_code and val_error_flag