APPS.MSC_DEMANTRA_PKG dependencies on MSD_DEM_SCN_ENTRIES_V

Line 121: from msd_dem_scn_entries_v k1,

117: k1.zone_id,
118: k1.inventory_item_id,
119: k1.demand_class,
120: k2.start_date
121: from msd_dem_scn_entries_v k1,
122: (select distinct start_date
123: from msd_dem_scn_entries_v
124: where scenario_id=p_plan_id) k2
125: where k1.scenario_id=p_plan_id) k,

Line 123: from msd_dem_scn_entries_v

119: k1.demand_class,
120: k2.start_date
121: from msd_dem_scn_entries_v k1,
122: (select distinct start_date
123: from msd_dem_scn_entries_v
124: where scenario_id=p_plan_id) k2
125: where k1.scenario_id=p_plan_id) k,
126: msd_dem_scn_entries_v f
127: where k.scenario_id = f.scenario_id(+)

Line 126: msd_dem_scn_entries_v f

122: (select distinct start_date
123: from msd_dem_scn_entries_v
124: where scenario_id=p_plan_id) k2
125: where k1.scenario_id=p_plan_id) k,
126: msd_dem_scn_entries_v f
127: where k.scenario_id = f.scenario_id(+)
128: and k.sr_instance_id = f.sr_instance_id(+)
129: and k.organization_id = f.organization_id(+)
130: and k.customer_id = f.customer_id(+)