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 188: PA_CALENDAR_UTILS.Check_Calendar_Name_Or_Id(

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

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

3428: -- storing the status success to track the error
3429: l_x_return_status := FND_API.G_RET_STS_SUCCESS ;
3430:
3431: -- Calling the Calendar API that will give the shift assign to the calendar*/
3432: PA_CALENDAR_UTILS.get_calendar_shifts(p_calendar_id,l_x_cal_record_tab,l_x_return_status,x_msg_count,x_msg_data);
3433:
3434: IF ( l_x_return_status = FND_API.G_RET_STS_SUCCESS ) THEN
3435: PA_CALENDAR_UTILS.gen_calendar_sch(p_calendar_id,l_x_cal_record_tab,l_schedule_rec_tab,l_x_return_status,
3436: x_msg_count,x_msg_data);

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

3431: -- Calling the Calendar API that will give the shift assign to the calendar*/
3432: PA_CALENDAR_UTILS.get_calendar_shifts(p_calendar_id,l_x_cal_record_tab,l_x_return_status,x_msg_count,x_msg_data);
3433:
3434: IF ( l_x_return_status = FND_API.G_RET_STS_SUCCESS ) THEN
3435: PA_CALENDAR_UTILS.gen_calendar_sch(p_calendar_id,l_x_cal_record_tab,l_schedule_rec_tab,l_x_return_status,
3436: x_msg_count,x_msg_data);
3437:
3438: END IF;
3439:

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

3438: END IF;
3439:
3440: PA_SCHEDULE_UTILS.log_message(1,'GEN SCH ',l_schedule_rec_tab);
3441: IF ( l_x_return_status = FND_API.G_RET_STS_SUCCESS ) THEN
3442: -- Calling the PA_CALENDAR_UTILS API that will take the exception associated with the calendar
3443: PA_CALENDAR_UTILS.get_calendar_except(p_calendar_id,l_x_cal_except_record_tab,l_x_return_status,
3444: x_msg_count,x_msg_data);
3445:
3446: END IF;

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

3439:
3440: PA_SCHEDULE_UTILS.log_message(1,'GEN SCH ',l_schedule_rec_tab);
3441: IF ( l_x_return_status = FND_API.G_RET_STS_SUCCESS ) THEN
3442: -- Calling the PA_CALENDAR_UTILS API that will take the exception associated with the calendar
3443: PA_CALENDAR_UTILS.get_calendar_except(p_calendar_id,l_x_cal_except_record_tab,l_x_return_status,
3444: x_msg_count,x_msg_data);
3445:
3446: END IF;
3447:

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

3446: END IF;
3447:
3448: IF ( l_x_return_status = FND_API.G_RET_STS_SUCCESS ) THEN
3449:
3450: -- Calling the PA_CALENDAR_UTILS API that will generate the calendar schedule after applying the exception
3451: PA_CALENDAR_UTILS.apply_calendar_except(p_calendar_id,l_x_cal_except_record_tab,l_schedule_rec_tab,
3452: l_x_sch_record_tab,l_x_return_status,x_msg_count,x_msg_data);
3453:
3454: END IF;

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

3447:
3448: IF ( l_x_return_status = FND_API.G_RET_STS_SUCCESS ) THEN
3449:
3450: -- Calling the PA_CALENDAR_UTILS API that will generate the calendar schedule after applying the exception
3451: PA_CALENDAR_UTILS.apply_calendar_except(p_calendar_id,l_x_cal_except_record_tab,l_schedule_rec_tab,
3452: l_x_sch_record_tab,l_x_return_status,x_msg_count,x_msg_data);
3453:
3454: END IF;
3455: