[Home] [Help]
1383: ld_effective_start_date := l_current_date + 1;
1384:
1385: -- Check that an update to the end date of the largest object
1386: -- definition will not invalidate any dependent data.
1387: FEM_PL_PKG.effective_date_incl_rslt_data(
1388: p_object_definition_id => l_max_object_definition_id
1389: ,p_new_effective_start_date => l_max_effective_start_date
1390: ,p_new_effective_end_date => l_max_effective_end_date
1391: ,x_msg_count => l_msg_count
1509: ,p_module => G_BLOCK||'.'||l_api_name
1510: ,p_msg_text => 'Step 3.4.1: Check for Edit or Approval Lock'
1511: );
1512:
1513: FEM_PL_PKG.get_object_def_edit_locks(
1514: p_object_definition_id => ld_hier_obj_def_id
1515: ,x_approval_edit_lock_exists => l_approval_edit_lock_exists
1516: ,x_data_edit_lock_exists => l_data_edit_lock_exists
1517: );
4333: );
4334:
4335: savepoint register_process_execution_pub;
4336:
4337: -- Call the FEM_PL_PKG.Register_Request API procedure to register
4338: -- the concurrent request in FEM_PL_REQUESTS. For hierarchy loader process
4339: -- locks, we must pass hierarchy_object_name to make sure that specified
4340: -- hierarchy object can only be loaded by one user at a time. Do not pass
4341: -- dimension id, as the PL fwk uses that for dimension loader process locks.
4338: -- the concurrent request in FEM_PL_REQUESTS. For hierarchy loader process
4339: -- locks, we must pass hierarchy_object_name to make sure that specified
4340: -- hierarchy object can only be loaded by one user at a time. Do not pass
4341: -- dimension id, as the PL fwk uses that for dimension loader process locks.
4342: FEM_PL_PKG.register_request (
4343: p_api_version => 1.0
4344: ,p_request_id => p_request_id
4345: ,p_user_id => p_user_id
4346: ,p_last_update_login => p_login_id
4363: );
4364: raise e_pl_register_req_failed;
4365: end if;
4366:
4367: -- Call the FEM_PL_PKG.Register_Object_Execution API procedure to register
4368: -- the object execution in FEM_PL_OBJECT_EXECUTIONS to obtain an execution
4369: -- lock.
4370: FEM_PL_PKG.register_object_execution (
4371: p_api_version => 1.0
4366:
4367: -- Call the FEM_PL_PKG.Register_Object_Execution API procedure to register
4368: -- the object execution in FEM_PL_OBJECT_EXECUTIONS to obtain an execution
4369: -- lock.
4370: FEM_PL_PKG.register_object_execution (
4371: p_api_version => 1.0
4372: ,p_request_id => p_request_id
4373: ,p_object_id => p_object_id
4374: ,p_exec_object_definition_id => p_obj_def_id
4391: );
4392: raise e_pl_register_exec_failed;
4393: end if;
4394:
4395: FEM_PL_PKG.register_object_def (
4396: p_api_version => 1.0
4397: ,p_request_id => p_request_id
4398: ,p_object_id => p_object_id
4399: ,p_object_definition_id => p_obj_def_id
4555: if (p_exec_status_code <> g_exec_status_success) then
4556:
4557: -- Since a hierarchy load is an all or nothing process, the number
4558: -- of errors reported will be 1.
4559: FEM_PL_PKG.update_obj_exec_errors (
4560: p_api_version => 1.0
4561: ,p_request_id => p_request_id
4562: ,p_object_id => p_object_id
4563: ,p_errors_reported => 1
4582:
4583: ------------------------------------
4584: -- Update Object Execution Status --
4585: ------------------------------------
4586: FEM_PL_PKG.update_obj_exec_status (
4587: p_api_version => 1.0
4588: ,p_request_id => p_request_id
4589: ,p_object_id => p_object_id
4590: ,p_exec_status_code => p_exec_status_code
4606:
4607: ---------------------------
4608: -- Update Request Status --
4609: ---------------------------
4610: FEM_PL_PKG.update_request_status (
4611: p_api_version => 1.0
4612: ,p_request_id => p_request_id
4613: ,p_exec_status_code => p_exec_status_code
4614: ,p_user_id => p_user_id