DBA Data[Home] [Help]

APPS.AME_ATTRIBUTE_API dependencies on AME_ATU_UPD

Line 527: ame_atu_upd.upd(p_effective_date => l_effective_date

523: -- Set the effective date to the sysdate
524: l_effective_date := sysdate;
525: l_atu_object_version_number := p_object_version_number;
526: -- update the row in ame_attribute_usages. Parent row locking not needed.
527: ame_atu_upd.upd(p_effective_date => l_effective_date
528: ,p_datetrack_mode => 'UPDATE'
529: ,p_attribute_id => p_attribute_id
530: ,p_application_id => p_application_id
531: ,p_object_version_number=> l_atu_object_version_number

Line 884: ame_atu_upd.upd(p_attribute_id => p_attribute_id

880: begin
881: l_atu_object_version_number := p_atu_object_version_number;
882: useCount := calculateUseCount(attributeIdIn => p_attribute_id
883: ,applicationIdIn => p_application_id);
884: ame_atu_upd.upd(p_attribute_id => p_attribute_id
885: ,p_datetrack_mode => hr_api.g_correction
886: ,p_application_id => p_application_id
887: ,p_use_count => useCount
888: ,p_effective_date => sysdate