APPS.PA_STAFFED_ASSIGNMENT_PVT dependencies on PA_ASSIGNMENT_APPROVAL_PVT

Line 2017: PA_ASSIGNMENT_APPROVAL_PVT.Insert_Into_Assignment_History ( p_assignment_id => l_assignment_rec.assignment_id

2013: ,x_msg => 'Inserting into Assignment History.'
2014: ,x_log_level => 5);
2015: END IF;
2016:
2017: PA_ASSIGNMENT_APPROVAL_PVT.Insert_Into_Assignment_History ( p_assignment_id => l_assignment_rec.assignment_id
2018: ,x_change_id => l_change_id
2019: ,x_return_status => l_return_status);
2020: IF l_return_status <> FND_API.G_RET_STS_SUCCESS THEN
2021: PA_ASSIGNMENTS_PUB.g_error_exists := FND_API.G_TRUE;

Line 2038: PA_ASSIGNMENT_APPROVAL_PVT.Get_Next_Status_After_Action ( p_action_code => PA_ASSIGNMENT_APPROVAL_PUB.g_update_action

2034: -- Get the status code after action performed.
2035: /* bug 8233045: GSI ER, skipping the following validation only when call is in bulk mode. This might need to be revisited later */
2036: -- bug#9441844
2037: -- if (PA_ASSIGNMENTS_PUB.G_update_assignment_bulk_call <> 'Y') then
2038: PA_ASSIGNMENT_APPROVAL_PVT.Get_Next_Status_After_Action ( p_action_code => PA_ASSIGNMENT_APPROVAL_PUB.g_update_action
2039: ,p_status_code => l_assignment_rec.apprvl_status_code
2040: -- ,x_status_code => l_assignment_rec.apprvl_status_code * commented for Bug: 4537865
2041: ,x_status_code => l_new_status_code -- added for Bug: 4537865
2042: ,x_return_status => l_return_status);