APPS.PA_ASSIGNMENT_APPROVAL_PUB dependencies on PA_SCHEDULE_PVT

Line 239: PA_SCHEDULE_PVT.Check_overcommitment_single

235: --------------------------------------------------------------------------------------------------------
236: -- Overcommitment checking
237: --------------------------------------------------------------------------------------------------------
238: IF (p_check_overcommitment_flag IS NOT NULL AND p_check_overcommitment_flag='Y') THEN
239: PA_SCHEDULE_PVT.Check_overcommitment_single
240: ( p_assignment_id => p_assignment_id
241: ,p_resolve_conflict_action_code => p_resolve_con_action_code
242: ,x_overcommitment_flag => l_overcommitment_flag
243: ,x_conflict_group_id => l_conflict_group_id

Line 436: PA_SCHEDULE_PVT.RESOLVE_CONFLICTS (p_conflict_group_id => l_conflict_group_id

432: -- Resolve Overcommitment conflict for Approve case
433: --------------------------------------------------------------------------------------------------------
434: IF (l_conflict_group_id IS NOT NULL AND l_action_code=PA_ASSIGNMENT_APPROVAL_PUB.g_approve_action) THEN
435: -- resolve remaining conflicts by taking action chosen by user
436: PA_SCHEDULE_PVT.RESOLVE_CONFLICTS (p_conflict_group_id => l_conflict_group_id
437: ,p_assignment_id => p_assignment_id
438: ,x_return_status => l_return_status
439: ,x_msg_count => l_msg_count
440: ,x_msg_data => l_msg_data);

Line 446: PA_SCHEDULE_PVT.OVERCOM_POST_APRVL_PROCESSING

442: RAISE FND_API.G_EXC_ERROR;
443: END IF;
444:
445: -- complete post overcommitment processing
446: PA_SCHEDULE_PVT.OVERCOM_POST_APRVL_PROCESSING
447: (p_conflict_group_id => l_conflict_group_id
448: ,p_fnd_user_name => FND_GLOBAL.USER_NAME
449: ,x_return_status => l_return_status
450: ,x_msg_count => l_msg_count

Line 1032: PA_SCHEDULE_PVT.Revert_To_Last_Approved ( p_assignment_id => p_assignment_id

1028: END IF;
1029: --
1030: --Revert the schedule records also.
1031: --
1032: PA_SCHEDULE_PVT.Revert_To_Last_Approved ( p_assignment_id => p_assignment_id
1033: ,p_change_id => l_change_id
1034: ,x_return_status => l_return_status
1035: ,x_msg_count => l_msg_count
1036: ,x_msg_data => l_msg_data);

Line 1526: PA_SCHEDULE_PVT.update_asgmt_changed_items_tab (

1522: ---------------------------------------------------------------------------
1523: -- get change_id just to check, it will pass -1 if the history table has no record for this asmt
1524: l_change_id := PA_ASSIGNMENT_APPROVAL_PVT.Get_Change_Id (p_assignment_id);
1525:
1526: PA_SCHEDULE_PVT.update_asgmt_changed_items_tab (
1527: p_assignment_id => p_assignment_id
1528: ,p_populate_mode => p_populate_mode
1529: ,p_change_id => l_change_id
1530: ,p_exception_type_code => p_exception_type_code

Line 3238: PA_SCHEDULE_PVT.resolve_conflicts (p_conflict_group_id => p_conflict_group_id

3234: RAISE PROCESS_ASSIGNMENT_EXCEPTION;
3235: END IF;
3236:
3237: -- resolve remaining conflicts by taking action chosen by user
3238: PA_SCHEDULE_PVT.resolve_conflicts (p_conflict_group_id => p_conflict_group_id
3239: ,p_assignment_id => l_assignment_id_tbl(i)
3240: ,x_return_status => l_return_status
3241: ,x_msg_count => l_msg_count
3242: ,x_msg_data => l_msg_data);

Line 3640: PA_SCHEDULE_PVT.overcom_post_aprvl_processing

3636:
3637: ------------------------------------------------------------------
3638: --This API is called to send notifications to conflicting managers
3639: ------------------------------------------------------------------
3640: PA_SCHEDULE_PVT.overcom_post_aprvl_processing
3641: ( p_conflict_group_id => p_conflict_group_id
3642: ,p_fnd_user_name => l_submitter_user_name
3643: ,x_return_status => l_return_status
3644: ,x_msg_count => l_msg_count