DBA Data[Home] [Help]

APPS.FEM_DIMENSION_UTIL_PKG dependencies on FEM_GLOBAL_VS_COMBOS_PKG

Line 62: | Insert statement for FEM_GLOBAL_VS_COMBOS_PKG

58: | New_Global_VS_Combo
59: |
60: | 26-JAN-05 tmoore Bug 4145122 - added New_Encumbrance_Type
61: | 21-APR-05 RFlippo Bug#4303380 Add Global_vs_combo_display_code to the
62: | Insert statement for FEM_GLOBAL_VS_COMBOS_PKG
63: | -- this fix will preserve the original signature
64: | for this API so that it is backward compatible
65: | with OGL by employing a default for the
66: | global combo display_code. If the user passes

Line 8528: Insert statement for FEM_GLOBAL_VS_COMBOS_PKG

8524:
8525: New_Global_VS_Combo
8526:
8527: 4/20/2005 RobFlippo Bug#4303380 Add Global_vs_combo_display_code to the
8528: Insert statement for FEM_GLOBAL_VS_COMBOS_PKG
8529: -- this fix will preserve the original signature
8530: for this API so that it is backward compatible
8531: with OGL by employing a default for the
8532: global combo display_code. If the user passes

Line 8614: FEM_GLOBAL_VS_COMBOS_PKG.INSERT_ROW(

8610: ---------------------------------------
8611: -- Insert New Global VS Combo Member --
8612: ---------------------------------------
8613: BEGIN
8614: FEM_GLOBAL_VS_COMBOS_PKG.INSERT_ROW(
8615: x_rowid => v_row_id,
8616: x_global_vs_combo_id => v_gvsc_id,
8617: x_global_vs_combo_display_code => v_global_vs_combo_dc,
8618: x_enabled_flag => p_enabled_flag,