DBA Data[Home] [Help]

APPS.PA_STAFFED_ASSIGNMENT_PVT dependencies on PA_ASSIGNMENT_APPROVAL_PVT

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

1982: ,x_msg => 'Inserting into Assignment History.'
1983: ,x_log_level => 5);
1984: END IF;
1985:
1986: PA_ASSIGNMENT_APPROVAL_PVT.Insert_Into_Assignment_History ( p_assignment_id => l_assignment_rec.assignment_id
1987: ,x_change_id => l_change_id
1988: ,x_return_status => l_return_status);
1989: IF l_return_status <> FND_API.G_RET_STS_SUCCESS THEN
1990: PA_ASSIGNMENTS_PUB.g_error_exists := FND_API.G_TRUE;

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

2000: ,x_log_level => 5);
2001:
2002: END IF;
2003: -- Get the status code after action performed.
2004: PA_ASSIGNMENT_APPROVAL_PVT.Get_Next_Status_After_Action ( p_action_code => PA_ASSIGNMENT_APPROVAL_PUB.g_update_action
2005: ,p_status_code => l_assignment_rec.apprvl_status_code
2006: -- ,x_status_code => l_assignment_rec.apprvl_status_code * commented for Bug: 4537865
2007: ,x_status_code => l_new_status_code -- added for Bug: 4537865
2008: ,x_return_status => l_return_status);