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.FII_EA_UTIL_PKG dependencies on FII_PMV_AGGRT_GT

Line 16: -- par_comp_id_aggrt_plsql depicts the plsql table for storing parent company id while inserting in fii_pmv_aggrt_gt

12: fin_cat_table PL1; -- table of records for category
13: fud1_table PL1; -- table of records for fud1
14: fud2_table PL1; -- table of records for fud2
15: par_comp_id_aggrt_plsql plsqltable;
16: -- par_comp_id_aggrt_plsql depicts the plsql table for storing parent company id while inserting in fii_pmv_aggrt_gt
17: --table. similar explanation for other plsql variables
18:
19: /* various plsql table's declaration */
20:

Line 1148: EXECUTE IMMEDIATE 'truncate table '||l_schema_name||'.fii_pmv_aggrt_gt';

1144:
1145: BEGIN
1146:
1147: l_schema_name := FII_UTIL.get_schema_name('FII');
1148: EXECUTE IMMEDIATE 'truncate table '||l_schema_name||'.fii_pmv_aggrt_gt';
1149: EXECUTE IMMEDIATE 'truncate table '||l_schema_name||'.fii_pmv_non_aggrt_gt';
1150:
1151: /* We set this variable to yes, (whenever current procedure is invoked from EA page portlets) OR
1152: (view by <> UD1/UD2 AND param values for Fin category, UD1, UD2, ledger are 'All' */

Line 1190: /* bug 4337351. For non-viewby fin category scenarios, while inserting records into fii_pmv_aggrt_gt table,

1186: /* fix for bug 4127077. If we any top node which is also a leaf, then we pick up the
1187: records with OM as parent category and top node as child from fii_gl_agrt_sum_mv ELSE we pick up
1188: records with top nodes as parent categories and their next level children as child categories */
1189:
1190: /* bug 4337351. For non-viewby fin category scenarios, while inserting records into fii_pmv_aggrt_gt table,
1191: we earlier picked up top node as parent fin category id and its next-level children as child fin category ids.
1192: This resulted in more NUMBER of records being inserted in gt tables which degraded performance. Instead, now,
1193: for non-viewby category cases, we pick up the combination of Operating Margin-Top node(s) which results in significant perf improvement */
1194:

Line 1477: INSERT INTO fii_pmv_aggrt_gt VALUES ( par_comp_id_aggrt_plsql(y),comp_id_aggrt_plsql(y),par_cc_id_aggrt_plsql(y),

1473:
1474: END LOOP;
1475: END LOOP;
1476: FORALL y in 1..g_aggrt_gt_record_count
1477: INSERT INTO fii_pmv_aggrt_gt VALUES ( par_comp_id_aggrt_plsql(y),comp_id_aggrt_plsql(y),par_cc_id_aggrt_plsql(y),
1478: cc_id_aggrt_plsql(y),par_fin_cat_id_aggrt_plsql(y),fin_cat_id_aggrt_plsql(y),
1479: par_fud1_id_aggrt_plsql(y),fud1_id_aggrt_plsql(y),fud2_id_aggrt_plsql(y),
1480: aggrt_viewbydescription(y), sort_order_aggrt_plsql(y));
1481: FORALL z in 1..g_non_aggrt_gt_record_count

Line 1510: INSERT INTO fii_pmv_aggrt_gt VALUES ( par_comp_id_aggrt_plsql(y),comp_id_aggrt_plsql(y),par_cc_id_aggrt_plsql(y),

1506: other_misc_stuff(i.agg_flag, l_cc_aggregate_flag, p_aggrt_gt_is_empty, p_non_aggrt_gt_is_empty);
1507:
1508: END LOOP;
1509: FORALL y in 1..g_aggrt_gt_record_count
1510: INSERT INTO fii_pmv_aggrt_gt VALUES ( par_comp_id_aggrt_plsql(y),comp_id_aggrt_plsql(y),par_cc_id_aggrt_plsql(y),
1511: cc_id_aggrt_plsql(y),par_fin_cat_id_aggrt_plsql(y),fin_cat_id_aggrt_plsql(y),
1512: par_fud1_id_aggrt_plsql(y),fud1_id_aggrt_plsql(y),fud2_id_aggrt_plsql(y),
1513: aggrt_viewbydescription(y), sort_order_aggrt_plsql(y));
1514: FORALL z in 1..g_non_aggrt_gt_record_count

Line 1551: INSERT INTO fii_pmv_aggrt_gt VALUES ( par_comp_id_aggrt_plsql(y),comp_id_aggrt_plsql(y),par_cc_id_aggrt_plsql(y),

1547: other_misc_stuff(l_company_aggregate_flag, j.agg_flag, p_aggrt_gt_is_empty, p_non_aggrt_gt_is_empty);
1548:
1549: END LOOP;
1550: FORALL y in 1..g_aggrt_gt_record_count
1551: INSERT INTO fii_pmv_aggrt_gt VALUES ( par_comp_id_aggrt_plsql(y),comp_id_aggrt_plsql(y),par_cc_id_aggrt_plsql(y),
1552: cc_id_aggrt_plsql(y),par_fin_cat_id_aggrt_plsql(y),fin_cat_id_aggrt_plsql(y),
1553: par_fud1_id_aggrt_plsql(y),fud1_id_aggrt_plsql(y),fud2_id_aggrt_plsql(y),
1554: aggrt_viewbydescription(y), sort_order_aggrt_plsql(y));
1555: FORALL i in 1..g_non_aggrt_gt_record_count

Line 1594: INSERT INTO fii_pmv_aggrt_gt VALUES ( par_comp_id_aggrt_plsql(y),comp_id_aggrt_plsql(y),par_cc_id_aggrt_plsql(y),

1590: form_specific_cc_join(l_company_aggregate_flag, l_cc_aggregate_flag);
1591: other_misc_stuff(l_company_aggregate_flag, l_cc_aggregate_flag, p_aggrt_gt_is_empty, p_non_aggrt_gt_is_empty);
1592:
1593: FORALL y in 1..g_aggrt_gt_record_count
1594: INSERT INTO fii_pmv_aggrt_gt VALUES ( par_comp_id_aggrt_plsql(y),comp_id_aggrt_plsql(y),par_cc_id_aggrt_plsql(y),
1595: cc_id_aggrt_plsql(y),par_fin_cat_id_aggrt_plsql(y),fin_cat_id_aggrt_plsql(y),
1596: par_fud1_id_aggrt_plsql(y),fud1_id_aggrt_plsql(y),fud2_id_aggrt_plsql(y),
1597: aggrt_viewbydescription(y), sort_order_aggrt_plsql(y));
1598: FORALL i in 1..g_non_aggrt_gt_record_count

Line 1629: -- g_aggrt_gt_record_count and g_non_aggrt_gt_record_count are the number of records in fii_pmv_aggrt_gt and fii_pmv_non_aggrt_gt tables respectively

1625: l_non_agrt_table_count NUMBER := 0;
1626: l_schema_name VARCHAR2(10) := FII_UTIL.get_schema_name('FII');
1627:
1628: BEGIN
1629: -- g_aggrt_gt_record_count and g_non_aggrt_gt_record_count are the number of records in fii_pmv_aggrt_gt and fii_pmv_non_aggrt_gt tables respectively
1630:
1631: IF g_aggrt_gt_record_count > 0 THEN -- it means that fii_pmv_aggrt_gt has been populated so only now, we should insert records into fii_debug_agrt table
1632:
1633: BEGIN

Line 1631: IF g_aggrt_gt_record_count > 0 THEN -- it means that fii_pmv_aggrt_gt has been populated so only now, we should insert records into fii_debug_agrt table

1627:
1628: BEGIN
1629: -- g_aggrt_gt_record_count and g_non_aggrt_gt_record_count are the number of records in fii_pmv_aggrt_gt and fii_pmv_non_aggrt_gt tables respectively
1630:
1631: IF g_aggrt_gt_record_count > 0 THEN -- it means that fii_pmv_aggrt_gt has been populated so only now, we should insert records into fii_debug_agrt table
1632:
1633: BEGIN
1634:
1635: SELECT 1 INTO l_agrt_table_count

Line 1691: FROM fii_pmv_aggrt_gt gt';

1687: gt.FUD2_ID,
1688: gt.VIEWBY,
1689: gt.SORT_ORDER,
1690: '||g_session_id||','''||g_region_code||'''
1691: FROM fii_pmv_aggrt_gt gt';
1692: END IF;
1693:
1694: IF g_non_aggrt_gt_record_count > 0 THEN -- it means that fii_pmv_non_aggrt_gt has been populated so only now, we should insert records into fii_debug_non_agrt table
1695: