APPS.OKL_SUBSIDY_POOL_TRX_PVT dependencies on OKL_SUBSIDY_POOL_PVT

Line 128: okl_subsidy_pool_pvt.expire_sub_pool(p_api_version => p_api_version

124: lv_pool_expired := OKL_API.G_TRUE;
125: IF(cv_pool_details.decision_status_code <> 'EXPIRED')THEN
126: -- pool though expired by dates, is not set to status EXPIRED. set the status and do not permit this transaction
127: -- THE EXPIRATION IS AN AUTONOMOUS TRANSACTION, see okl_subsidy_pools_pvt for more details
128: okl_subsidy_pool_pvt.expire_sub_pool(p_api_version => p_api_version
129: ,p_init_msg_list => p_init_msg_list
130: ,x_return_status => x_return_status
131: ,x_msg_count => x_msg_count
132: ,x_msg_data => x_msg_data

Line 286: okl_subsidy_pool_pvt.update_subsidy_amount(p_api_version => p_api_version

282: END IF;
283: -- note that (total budget - subsidy amount) = remaining balance
284: -- based on the transaction type, the subsidy amount is increased (in case of REDUCTION transaction or reducing pool balance)
285: -- or subsidy amount is decreased (in case of ADDITION transaction or adding back to pool balance)
286: okl_subsidy_pool_pvt.update_subsidy_amount(p_api_version => p_api_version
287: ,p_init_msg_list => p_init_msg_list
288: ,x_return_status => x_return_status
289: ,x_msg_count => x_msg_count
290: ,x_msg_data => x_msg_data