DBA Data[Home] [Help]

APPS.PA_SCHEDULE_PUB dependencies on PA_FORECAST_ITEMS

Line 4206: --x_person_id := PA_FORECAST_ITEMS_UTILS.get_person_id(p_resource_id);

4202:
4203: -- Now all parameters for calling API's are determined. Now start calling them
4204:
4205: -- Returning the person_id back to the calling environment so that it does not have to fetch
4206: --x_person_id := PA_FORECAST_ITEMS_UTILS.get_person_id(p_resource_id);
4207:
4208:
4209: -- Initialize the monday..sinday hours table with 0 if data is not populated already
4210: -- Note that in First set of hours at least one day will have at least one non -99 value

Line 4702: FROM pa_forecast_items

4698: -- 'N', decode(sign(capacity_quantity-overcommitment_quantity), 1, 0, overcommitment_quantity))) quantity,
4699: resource_id,
4700: forecast_item_type,
4701: -1 assignment_id
4702: FROM pa_forecast_items
4703: WHERE resource_id = l_res_id
4704: AND forecast_item_type = 'U'
4705: AND item_date between l_actual_display_start_date and l_actual_display_start_date+14
4706: AND delete_flag = 'N'

Line 4715: pa_forecast_items fi

4711: fi.resource_id,
4712: fi.forecast_item_type,
4713: asgn.assignment_id
4714: FROM pa_project_assignments asgn,
4715: pa_forecast_items fi
4716: WHERE asgn.resource_id = l_res_id
4717: AND fi.resource_id = l_res_id
4718: AND fi.delete_flag = 'N'
4719: AND fi.item_date between l_actual_display_start_date and l_actual_display_start_date+13