APPS.OKL_VP_CR_WF dependencies on OKL_VP_SYNC_CR_PVT

Line 621: okl_vp_sync_cr_pvt.sync_change_request(p_api_version => 1.0

617: END IF;
618:
619: -- now start synchronization, the synchronization api will set the status of the change request
620: -- and the associated agreement accordingly
621: okl_vp_sync_cr_pvt.sync_change_request(p_api_version => 1.0
622: ,p_init_msg_list => OKL_API.G_TRUE
623: ,x_return_status => x_return_status
624: ,x_msg_count => x_msg_count
625: ,x_msg_data => x_msg_data

Line 632: 'okl_vp_sync_cr_pvt.sync_change_request on change request id '||lv_change_req_id||' returned with status '||x_return_status

628: -- write to log
629: IF(NVL(l_debug_enabled,'N')='Y') THEN
630: okl_debug_pub.log_debug(FND_LOG.LEVEL_STATEMENT,
631: l_module,
632: 'okl_vp_sync_cr_pvt.sync_change_request on change request id '||lv_change_req_id||' returned with status '||x_return_status
633: );
634: END IF; -- end of NVL(l_debug_enabled,'N')='Y'
635: IF(x_return_status = OKL_API.G_RET_STS_UNEXP_ERROR) THEN
636: RAISE OKL_API.G_EXCEPTION_UNEXPECTED_ERROR;