APPS.PA_SCHEDULE_PUB dependencies on PA_FORECAST_ITEMS

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

4682:
4683: -- Now all parameters for calling API's are determined. Now start calling them
4684:
4685: -- Returning the person_id back to the calling environment so that it does not have to fetch
4686: --x_person_id := PA_FORECAST_ITEMS_UTILS.get_person_id(p_resource_id);
4687:
4688:
4689: -- Initialize the monday..sinday hours table with 0 if data is not populated already
4690: -- Note that in First set of hours at least one day will have at least one non -99 value

Line 5182: FROM pa_forecast_items

5178: -- 'N', decode(sign(capacity_quantity-overcommitment_quantity), 1, 0, overcommitment_quantity))) quantity,
5179: resource_id,
5180: forecast_item_type,
5181: -1 assignment_id
5182: FROM pa_forecast_items
5183: WHERE resource_id = l_res_id
5184: AND forecast_item_type = 'U'
5185: AND item_date between l_actual_display_start_date and l_actual_display_start_date+14
5186: AND delete_flag = 'N'

Line 5195: pa_forecast_items fi

5191: fi.resource_id,
5192: fi.forecast_item_type,
5193: asgn.assignment_id
5194: FROM pa_project_assignments asgn,
5195: pa_forecast_items fi
5196: WHERE asgn.resource_id = l_res_id
5197: AND fi.resource_id = l_res_id
5198: AND fi.delete_flag = 'N'
5199: AND fi.item_date between l_actual_display_start_date and l_actual_display_start_date+13