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.FEM_WEBADI_FACT_TAB_UTILS_PVT dependencies on FEM_FACTOR_TABLES

Line 70: --- Entering data into fem_factor_tables and fem_factor_table_dims. This block is executed for only once first time the PLSQL API is invoked.

66:
67: ------------------------------------------------------ PART 1 ENDS ----------------------------------------------------------------------------
68:
69: --------------------------------------------------------- PART 2 ------------------------------------------------------------------------------
70: --- Entering data into fem_factor_tables and fem_factor_table_dims. This block is executed for only once first time the PLSQL API is invoked.
71: -----------------------------------------------------------------------------------------------------------------------------------------------
72:
73: POPULATE_FACTOR_TABLE_DIMS(P_VERSION_NAME,P_FACTOR_TYPE,P_MATCHING_DIM1,P_HIERARCHY1,P_HIER1_VER,P_LEVEL1,P_HIERARCHY_REL1,P_MATCHING_DIM2,
74: P_HIERARCHY2,P_HIER2_VER,P_LEVEL2,P_HIERARCHY_REL2,P_MATCHING_DIM3,P_HIERARCHY3,P_HIER3_VER,P_LEVEL3,P_HIERARCHY_REL3,P_DISTRIBUTION_DIM,P_FORCE_TO_HUNDRED);

Line 233: --- Entering data into fem_factor_tables and fem_factor_table_dims. This block is executed for only once first time the PLSQL API is invoked.

229:
230: ------------------------------------------------------ PART 1 ENDS ----------------------------------------------------------------------------
231:
232: --------------------------------------------------------- PART 2 ------------------------------------------------------------------------------
233: --- Entering data into fem_factor_tables and fem_factor_table_dims. This block is executed for only once first time the PLSQL API is invoked.
234: -----------------------------------------------------------------------------------------------------------------------------------------------
235:
236: POPULATE_FACTOR_TABLE_DIMS(P_VERSION_NAME,P_FACTOR_TYPE,P_MATCHING_DIM1,P_HIERARCHY1,P_HIER1_VER,P_LEVEL1,P_HIERARCHY_REL1,P_MATCHING_DIM2,
237: P_HIERARCHY2,P_HIER2_VER,P_LEVEL2,P_HIERARCHY_REL2,P_MATCHING_DIM3,P_HIERARCHY3,P_HIER3_VER,P_LEVEL3,P_HIERARCHY_REL3,NULL,P_FORCE_TO_HUNDRED);

Line 372: --- Entering data into fem_factor_tables and fem_factor_table_dims. This block is executed for only once first time the PLSQL API is invoked.

368:
369: ------------------------------------------------------ PART 1 ENDS ----------------------------------------------------------------------------
370:
371: --------------------------------------------------------- PART 2 ------------------------------------------------------------------------------
372: --- Entering data into fem_factor_tables and fem_factor_table_dims. This block is executed for only once first time the PLSQL API is invoked.
373: -----------------------------------------------------------------------------------------------------------------------------------------------
374:
375: POPULATE_FACTOR_TABLE_DIMS(P_VERSION_NAME,P_FACTOR_TYPE,NULL,NULL,NULL,NULL,NULL,NULL,
376: NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,P_DISTRIBUTION_DIM,P_FORCE_TO_HUNDRED);

Line 510: insert into FEM_FACTOR_TABLES(OBJECT_DEFINITION_ID,

506: select lookup_code into l_factor_type_code from fem_lookups where lookup_type = 'FEM_FACTOR_TABLE_TYPES_DSC' and meaning = p_factor_type;
507:
508: if(G_ENTER_IN_DIMS = 'Y') THEN
509:
510: insert into FEM_FACTOR_TABLES(OBJECT_DEFINITION_ID,
511: FACTOR_TYPE,
512: CREATION_DATE,
513: CREATED_BY,
514: LAST_UPDATED_BY,