APPS.PA_SCHEDULE_PUB dependencies on PA_SCHEDULES

Line 2565: l_change_id PA_SCHEDULES_HISTORY.change_id%type;

2561: l_I NUMBER;
2562: l_p_start_id NUMBER;
2563: l_p_end_id NUMBER;
2564: l_apply_schedule_changes BOOLEAN;
2565: l_change_id PA_SCHEDULES_HISTORY.change_id%type;
2566: l_temp_status_code PA_PROJECT_ASSIGNMENTS.status_code%type;
2567:
2568: l_save_to_hist VARCHAR2(1); -- Unilog
2569: l_record_version_number_wo_chg NUMBER; -- Unilog

Line 2977: -- Inserting the records in PA_SCHEDULES table

2973:
2974: END IF;
2975:
2976: IF ( l_x_return_status = FND_API.G_RET_STS_SUCCESS ) THEN
2977: -- Inserting the records in PA_SCHEDULES table
2978: PA_SCHEDULE_PKG.insert_rows(l_x_sch_record_tab,l_x_return_status,x_msg_count,x_msg_data);
2979:
2980: END IF;
2981: /** Added call to update_wp_calendar for all projects **/

Line 3310: DELETE FROM PA_SCHEDULES

3306: WHERE calendar_id=v_c1.calendar_id
3307: FOR UPDATE ;
3308:
3309: -- Deleting the existing schedule of the calendar and creating the new one
3310: DELETE FROM PA_SCHEDULES
3311: WHERE calendar_id = v_c1.calendar_id
3312: AND schedule_type_code = 'CALENDAR';
3313:
3314: -- Creating new schedule for the Calendar Id */