APPS.BEN_PLAN_DESIGN_WIZARD_API dependencies on BEN_PLAN_DESIGN_DELETE_API

Line 308: ben_plan_design_delete_api.call_delete_apis_for_hierarchy

304: savepoint VALIDATE_DELETE_API_CALLS;
305: -- make sure that parent is marked for delete
306: -- since the delete_entity does not mark the parent for delete as it is done in the java layer
307: update ben_copy_entity_results set dml_operation = 'DELETE',datetrack_mode ='DELETE' where copy_entity_result_id = p_parent_entity_result_id ;
308: ben_plan_design_delete_api.call_delete_apis_for_hierarchy
309: ( p_process_validate => l_validate
310: ,p_copy_entity_txn_id => p_copy_entity_txn_id
311: ,p_parent_entity_result_id => p_parent_entity_result_id
312: ,p_delete_failed => p_delete_failed

Line 432: ben_plan_design_delete_api.call_delete_apis

428: -- this may fail because these rows which we are trying to delete may be
429: -- present as foriegn keys before the submit api updates them.
430: BEGIN
431: savepoint DELETE_REQUEST;
432: ben_plan_design_delete_api.call_delete_apis
433: ( p_process_validate => p_process_validate
434: ,p_copy_entity_txn_id => p_copy_entity_txn_id
435: ,p_delete_failed => p_delete_failed
436: );

Line 468: ben_plan_design_delete_api.call_delete_apis

464:
465: /*-- call delete again if the delete failed previously
466: if(p_delete_failed ='Y') then
467: p_delete_failed:='N';
468: ben_plan_design_delete_api.call_delete_apis
469: ( p_process_validate => p_process_validate
470: ,p_copy_entity_txn_id => p_copy_entity_txn_id
471: ,p_delete_failed => p_delete_failed
472: );