eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.PA_FP_ROLLUP_PKG dependencies on PA_FP_ROLLUP_TMP

Line 460: FROM PA_FP_ROLLUP_TMP

456: ,sum(nvl(projfunc_raw_cost,0) - nvl(old_projfunc_raw_cost,0)) projfunc_raw_cost_diff
457: ,sum(nvl(projfunc_burdened_cost,0) - nvl(old_projfunc_burdened_cost,0)) projfunc_burdened_cost_diff
458: ,sum(nvl(projfunc_revenue,0) - nvl(old_projfunc_revenue,0)) projfunc_revenue_diff
459: ,sum(nvl(quantity,0) - nvl(old_quantity,0)) quantity_diff
460: FROM PA_FP_ROLLUP_TMP
461: GROUP BY resource_assignment_id;
462:
463: BEGIN
464:

Line 625: --Update the amounts for the resource assignments available in pa_fp_rollup_tmp . Bug 3489929

621: -- End, Bug 3362316, 08-JAN-2004: Added Conditional Logic for ORG_FORECAST ------------------
622: ELSIF p_entire_version = 'N' THEN
623:
624:
625: --Update the amounts for the resource assignments available in pa_fp_rollup_tmp . Bug 3489929
626: OPEN c_res_amt_diffs;
627: FETCH c_res_amt_diffs BULK COLLECT INTO
628: l_ra_id_tbl
629: ,l_proj_raw_cost_tbl

Line 3340: ROLLUP_RES_ASSIGNMENT_AMOUNTS: This API will take input from PA_FP_ROLLUP_TMP table

3336: raise FND_API.G_EXC_UNEXPECTED_ERROR;
3337: END INSERT_MISSING_RES_PARENTS;
3338:
3339: /***********************************************************************************************
3340: ROLLUP_RES_ASSIGNMENT_AMOUNTS: This API will take input from PA_FP_ROLLUP_TMP table
3341: and will update rollup amount for each level in pa_resource_assignments table.
3342: Before this API is called, INSERT_MISSING_RES_PARENTS would have created parents for all the
3343: records affected in PA_RESOURCE_ASSIGNMENTS. This API will just rollup the amounts.
3344: Pre-requisite: For an existing element users should have populated old and new amount fields

Line 3345: into the temp table PA_FP_ROLLUP_TMP before calling this API.

3341: and will update rollup amount for each level in pa_resource_assignments table.
3342: Before this API is called, INSERT_MISSING_RES_PARENTS would have created parents for all the
3343: records affected in PA_RESOURCE_ASSIGNMENTS. This API will just rollup the amounts.
3344: Pre-requisite: For an existing element users should have populated old and new amount fields
3345: into the temp table PA_FP_ROLLUP_TMP before calling this API.
3346: For a new element (thru excel sheets) users will populate old as null and new
3347: as the current value.
3348: ***********************************************************************************************/
3349:

Line 3355: /* Cursor to Select all data from PA_FP_ROLLUP_TMP table, grouped by resource_assignment_id

3351: ,x_return_status OUT NOCOPY VARCHAR2 --File.Sql.39 bug 4440895
3352: ,x_msg_count OUT NOCOPY NUMBER --File.Sql.39 bug 4440895
3353: ,x_msg_data OUT NOCOPY VARCHAR2) IS --File.Sql.39 bug 4440895
3354:
3355: /* Cursor to Select all data from PA_FP_ROLLUP_TMP table, grouped by resource_assignment_id
3356: and take sum of amount diffs (use nvl for new and old amounts) in project and project
3357: functional currencies. */
3358:
3359: CURSOR c_res_amt_diffs IS

Line 3368: FROM PA_FP_ROLLUP_TMP

3364: ,sum(nvl(projfunc_raw_cost,0) - nvl(old_projfunc_raw_cost,0)) projfunc_raw_cost_diff
3365: ,sum(nvl(projfunc_burdened_cost,0) - nvl(old_projfunc_burdened_cost,0)) projfunc_burdened_cost_diff
3366: ,sum(nvl(projfunc_revenue,0) - nvl(old_projfunc_revenue,0)) projfunc_revenue_diff
3367: ,sum(nvl(quantity,0) - nvl(old_quantity,0)) quantity_diff
3368: FROM PA_FP_ROLLUP_TMP
3369: GROUP BY resource_assignment_id;
3370:
3371: l_proj_raw_cost_tbl l_proj_raw_cost_tbl_typ;
3372: l_proj_burd_cost_tbl l_proj_burd_cost_tbl_typ;

Line 4009: from Resource_Assignments and those that are present in the pa_fp_rollup_tmp

4005: RAISE PA_FP_ROLLUP_PKG.Invalid_Arg_Exc;
4006: END IF;
4007:
4008: /* Inserting the parent level records that need to be updated into pa_fp_ra_map_tmp
4009: from Resource_Assignments and those that are present in the pa_fp_rollup_tmp
4010: (i.e. records that have got updated).*/
4011:
4012: DELETE from pa_fp_ra_map_tmp;
4013:

Line 4021: FROM pa_fp_rollup_tmp tmp);

4017: END IF;
4018:
4019: INSERT into pa_fp_ra_map_tmp(resource_assignment_id)
4020: (SELECT DISTINCT tmp.parent_assignment_id
4021: FROM pa_fp_rollup_tmp tmp);
4022:
4023: pa_debug.g_err_stage := 'inserted ' || sql%rowcount || ' records';
4024: IF P_PA_DEBUG_MODE = 'Y' THEN
4025: pa_debug.write('ROLLUP_DENORM_AMOUNTS: ' || l_module_name,pa_debug.g_err_stage,3);

Line 4533: DELETE FROM pa_fp_rollup_tmp; /* M20-AUG: delete from rollup_tmp should be unconditional */

4529: IF P_PA_DEBUG_MODE = 'Y' THEN
4530: pa_debug.write('DELETE_ELEMENT: ' || l_module_name,pa_debug.g_err_stage,3);
4531: END IF;
4532:
4533: DELETE FROM pa_fp_rollup_tmp; /* M20-AUG: delete from rollup_tmp should be unconditional */
4534:
4535: /* At this point, l_parent_assginment_id contains the assignment id of an impacted
4536: parent under which some other (undeleted) children exist. Hence Rollup has to be
4537: done for the parent level records. */

Line 4539: /* For the Parent Assignment ID, populating the Rollup Table PA_FP_ROLLUP_TMP, with

4535: /* At this point, l_parent_assginment_id contains the assignment id of an impacted
4536: parent under which some other (undeleted) children exist. Hence Rollup has to be
4537: done for the parent level records. */
4538:
4539: /* For the Parent Assignment ID, populating the Rollup Table PA_FP_ROLLUP_TMP, with
4540: the old and new amounts. Call Rollup_Resource_Assignment_Amounts to roll up the
4541: Resource Assignments data and Rollup_Denorm_Amounts to roll up the Denorm data.*/
4542:
4543: pa_debug.g_err_stage := 'Insert records into Rollup Temp Table with the amounts';

Line 4550: INSERT INTO PA_FP_ROLLUP_TMP

4546: END IF;
4547:
4548: /* M20-AUG: we have to insert all the records for the deleted resource assignment */
4549:
4550: INSERT INTO PA_FP_ROLLUP_TMP
4551: ( BUDGET_LINE_ID /* FPB2 */
4552: ,OLD_START_DATE /* FPB2 */
4553: ,START_DATE /* FPB2 */
4554: ,RESOURCE_ASSIGNMENT_ID

Line 4626: /* First, delete the records from pa_fp_rollup_tmp if any. */

4622: /* Since the details of the records being deleted are required for rolling
4623: up data, we need to get the amounts from the Budget Lines table for the
4624: resource assignment that is being deleted. */
4625:
4626: /* First, delete the records from pa_fp_rollup_tmp if any. */
4627:
4628: DELETE FROM pa_fp_rollup_tmp;
4629:
4630: pa_debug.g_err_stage := 'Insert Records into Rollup Temp Table for txn currency';

Line 4628: DELETE FROM pa_fp_rollup_tmp;

4624: resource assignment that is being deleted. */
4625:
4626: /* First, delete the records from pa_fp_rollup_tmp if any. */
4627:
4628: DELETE FROM pa_fp_rollup_tmp;
4629:
4630: pa_debug.g_err_stage := 'Insert Records into Rollup Temp Table for txn currency';
4631: IF P_PA_DEBUG_MODE = 'Y' THEN
4632: pa_debug.write('DELETE_ELEMENT: ' || l_module_name,pa_debug.g_err_stage,3);

Line 4635: INSERT INTO pa_fp_rollup_tmp

4631: IF P_PA_DEBUG_MODE = 'Y' THEN
4632: pa_debug.write('DELETE_ELEMENT: ' || l_module_name,pa_debug.g_err_stage,3);
4633: END IF;
4634:
4635: INSERT INTO pa_fp_rollup_tmp
4636: ( budget_line_id /* FPB2 */
4637: ,old_start_date /* FPB2 */
4638: ,start_date /* FPB2 */
4639: ,resource_assignment_id