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.GL_CONS_SEGMENT_MAP_PKG dependencies on GL_CONS_FLEX_HIERARCHIES

Line 225: -- from gl_cons_flex_hierarchies table - This is introduced here

221: -- X_From_Value_Set_Id,
222: -- X_Segment_Map_Type );
223:
224: -- The following delete statement deletes orphaned detail rows
225: -- from gl_cons_flex_hierarchies table - This is introduced here
226: -- because the Consolidation program insert row into
227: -- GL_CONS_FLEX_HIERARCHIES table, and if the user changes the
228: -- segment rule type from Parent Rollup to Detail Rollup, the
229: -- corresponding rows in gl_cons_flex_hierarchies are hanging

Line 227: -- GL_CONS_FLEX_HIERARCHIES table, and if the user changes the

223:
224: -- The following delete statement deletes orphaned detail rows
225: -- from gl_cons_flex_hierarchies table - This is introduced here
226: -- because the Consolidation program insert row into
227: -- GL_CONS_FLEX_HIERARCHIES table, and if the user changes the
228: -- segment rule type from Parent Rollup to Detail Rollup, the
229: -- corresponding rows in gl_cons_flex_hierarchies are hanging
230: -- loose. Hence the delete.
231: -- IF ( X_Segment_Rule_Changed = 'Y' ) THEN

Line 229: -- corresponding rows in gl_cons_flex_hierarchies are hanging

225: -- from gl_cons_flex_hierarchies table - This is introduced here
226: -- because the Consolidation program insert row into
227: -- GL_CONS_FLEX_HIERARCHIES table, and if the user changes the
228: -- segment rule type from Parent Rollup to Detail Rollup, the
229: -- corresponding rows in gl_cons_flex_hierarchies are hanging
230: -- loose. Hence the delete.
231: -- IF ( X_Segment_Rule_Changed = 'Y' ) THEN
232: -- DELETE FROM GL_CONS_FLEX_HIERARCHIES
233: -- WHERE segment_map_id = X_Segment_Map_Id;

Line 232: -- DELETE FROM GL_CONS_FLEX_HIERARCHIES

228: -- segment rule type from Parent Rollup to Detail Rollup, the
229: -- corresponding rows in gl_cons_flex_hierarchies are hanging
230: -- loose. Hence the delete.
231: -- IF ( X_Segment_Rule_Changed = 'Y' ) THEN
232: -- DELETE FROM GL_CONS_FLEX_HIERARCHIES
233: -- WHERE segment_map_id = X_Segment_Map_Id;
234: -- END IF;
235:
236: UPDATE gl_cons_segment_map

Line 269: DELETE FROM GL_CONS_FLEX_HIERARCHIES

265: PROCEDURE Delete_Row(X_Rowid VARCHAR2, X_Segment_Map_Id NUMBER ) IS
266: BEGIN
267:
268: --Previously from Pre-Delete
269: DELETE FROM GL_CONS_FLEX_HIERARCHIES
270: WHERE SEGMENT_MAP_ID = X_Segment_Map_Id;
271:
272:
273: DELETE FROM gl_cons_segment_map

Line 341: from gl_cons_flex_hierarchies cfh,

337: fvh_new.child_flex_value_low and fvh_new.child_flex_value_high))
338: and (csm.rowid <> X_Rowid OR X_Rowid is NULL)
339: UNION
340: select 'x'
341: from gl_cons_flex_hierarchies cfh,
342: gl_cons_segment_map csm,
343: fnd_flex_value_hierarchies fvh
344: where csm.segment_map_id = cfh.segment_map_id
345: and csm.coa_mapping_id = X_Coa_Mapping_id

Line 400: from gl_cons_flex_hierarchies cfh,

396: fvh_new.child_flex_value_low and fvh_new.child_flex_value_high))
397: and (csm.rowid <> X_Rowid OR X_Rowid is NULL)
398: UNION
399: select 'x'
400: from gl_cons_flex_hierarchies cfh,
401: gl_cons_segment_map csm,
402: fnd_flex_value_hierarchies fvh
403: where csm.segment_map_id = cfh.segment_map_id
404: and csm.coa_mapping_id = X_Coa_Mapping_id