eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.PA_SCHEDULE_PUB dependencies on PA_CALENDAR_UTILS

Line 184: PA_CALENDAR_UTILS.Check_Calendar_Name_Or_Id(

180: PA_UTILS.Add_Message ('PA', 'PA_OTHER_CALENDAR_NULL');
181: RAISE FND_API.G_EXC_ERROR;
182: END IF;
183:
184: PA_CALENDAR_UTILS.Check_Calendar_Name_Or_Id(
185: p_calendar_id => p_change_calendar_id
186: ,p_calendar_name => p_change_calendar_name
187: ,p_check_id_flag => 'N'
188: ,x_calendar_id => l_change_calendar_id

Line 2952: PA_CALENDAR_UTILS.get_calendar_shifts(p_calendar_id,l_x_cal_record_tab,l_x_return_status,x_msg_count,x_msg_data);

2948: -- storing the status success to track the error
2949: l_x_return_status := FND_API.G_RET_STS_SUCCESS ;
2950:
2951: -- Calling the Calendar API that will give the shift assign to the calendar*/
2952: PA_CALENDAR_UTILS.get_calendar_shifts(p_calendar_id,l_x_cal_record_tab,l_x_return_status,x_msg_count,x_msg_data);
2953:
2954: IF ( l_x_return_status = FND_API.G_RET_STS_SUCCESS ) THEN
2955: PA_CALENDAR_UTILS.gen_calendar_sch(p_calendar_id,l_x_cal_record_tab,l_schedule_rec_tab,l_x_return_status,
2956: x_msg_count,x_msg_data);

Line 2955: PA_CALENDAR_UTILS.gen_calendar_sch(p_calendar_id,l_x_cal_record_tab,l_schedule_rec_tab,l_x_return_status,

2951: -- Calling the Calendar API that will give the shift assign to the calendar*/
2952: PA_CALENDAR_UTILS.get_calendar_shifts(p_calendar_id,l_x_cal_record_tab,l_x_return_status,x_msg_count,x_msg_data);
2953:
2954: IF ( l_x_return_status = FND_API.G_RET_STS_SUCCESS ) THEN
2955: PA_CALENDAR_UTILS.gen_calendar_sch(p_calendar_id,l_x_cal_record_tab,l_schedule_rec_tab,l_x_return_status,
2956: x_msg_count,x_msg_data);
2957:
2958: END IF;
2959:

Line 2962: -- Calling the PA_CALENDAR_UTILS API that will take the exception associated with the calendar

2958: END IF;
2959:
2960: PA_SCHEDULE_UTILS.log_message(1,'GEN SCH ',l_schedule_rec_tab);
2961: IF ( l_x_return_status = FND_API.G_RET_STS_SUCCESS ) THEN
2962: -- Calling the PA_CALENDAR_UTILS API that will take the exception associated with the calendar
2963: PA_CALENDAR_UTILS.get_calendar_except(p_calendar_id,l_x_cal_except_record_tab,l_x_return_status,
2964: x_msg_count,x_msg_data);
2965:
2966: END IF;

Line 2963: PA_CALENDAR_UTILS.get_calendar_except(p_calendar_id,l_x_cal_except_record_tab,l_x_return_status,

2959:
2960: PA_SCHEDULE_UTILS.log_message(1,'GEN SCH ',l_schedule_rec_tab);
2961: IF ( l_x_return_status = FND_API.G_RET_STS_SUCCESS ) THEN
2962: -- Calling the PA_CALENDAR_UTILS API that will take the exception associated with the calendar
2963: PA_CALENDAR_UTILS.get_calendar_except(p_calendar_id,l_x_cal_except_record_tab,l_x_return_status,
2964: x_msg_count,x_msg_data);
2965:
2966: END IF;
2967:

Line 2970: -- Calling the PA_CALENDAR_UTILS API that will generate the calendar schedule after applying the exception

2966: END IF;
2967:
2968: IF ( l_x_return_status = FND_API.G_RET_STS_SUCCESS ) THEN
2969:
2970: -- Calling the PA_CALENDAR_UTILS API that will generate the calendar schedule after applying the exception
2971: PA_CALENDAR_UTILS.apply_calendar_except(p_calendar_id,l_x_cal_except_record_tab,l_schedule_rec_tab,
2972: l_x_sch_record_tab,l_x_return_status,x_msg_count,x_msg_data);
2973:
2974: END IF;

Line 2971: PA_CALENDAR_UTILS.apply_calendar_except(p_calendar_id,l_x_cal_except_record_tab,l_schedule_rec_tab,

2967:
2968: IF ( l_x_return_status = FND_API.G_RET_STS_SUCCESS ) THEN
2969:
2970: -- Calling the PA_CALENDAR_UTILS API that will generate the calendar schedule after applying the exception
2971: PA_CALENDAR_UTILS.apply_calendar_except(p_calendar_id,l_x_cal_except_record_tab,l_schedule_rec_tab,
2972: l_x_sch_record_tab,l_x_return_status,x_msg_count,x_msg_data);
2973:
2974: END IF;
2975: