APPS.PA_COMPETENCE_PVT dependencies on HR_COMPETENCE_ELEMENT_API

Line 163: hr_competence_element_api.create_competence_element

159: FOR I in 1..p_object_id.count LOOP
160: -- Now create the competency
161: l_element_id := NULL;
162:
163: hr_competence_element_api.create_competence_element
164: (
165: p_competence_element_id => l_element_id,
166: p_object_version_number => l_object_version_number,
167: p_type => p_object_name,

Line 339: hr_competence_element_api.update_competence_element

335: -- The HR api expects the effective_date as an input
336: -- Since we do not have a need to update the effective date
337: -- we will use the effective date fetched earlier for this purpose
338:
339: hr_competence_element_api.update_competence_element
340: (
341: p_competence_element_id => p_element_id,
342: p_object_version_number => l_object_version_number,
343: p_proficiency_level_id => p_rating_level_id,

Line 431: hr_competence_element_api.delete_competence_element

427: x_return_status := FND_API.G_RET_STS_SUCCESS;
428: pa_debug.reset_err_stack;
429: RETURN;
430: END IF;
431: hr_competence_element_api.delete_competence_element
432: (p_competence_element_id => p_element_id,
433: p_object_version_number => p_object_version_number );
434:
435: x_return_status := FND_API.G_RET_STS_SUCCESS;