eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.OKL_VP_SYNC_CR_PVT dependencies on OKL_K_HEADERS

Line 53: FROM okl_k_headers

49: -- cursor to find out the agreement id that was created for the change request. this agreement id
50: -- is not the parent agreement id, but the one that was created using the copy api
51: CURSOR c_get_creq_chr_id (cp_change_request_id okl_vp_change_requests.id%TYPE)IS
52: SELECT id
53: FROM okl_k_headers
54: WHERE crs_id = cp_change_request_id;
55:
56: cv_get_cr_details c_get_cr_details_csr%ROWTYPE;
57: lv_vcrv_rec okl_vcr_pvt.vcrv_rec_type;

Line 107: -- get the agreement associated with the change request. this is achieved by getting the id from okl_k_headers

103: -- store the value of the original agreement id here. this would be useful in calling the sync procedures
104: lv_orig_chr_id := cv_get_cr_details.orig_agr_chr_id;
105: -- now fork based on change request type
106: IF(G_ARGREEMENT_TYPE_CODE = cv_get_cr_details.change_type_code)THEN
107: -- get the agreement associated with the change request. this is achieved by getting the id from okl_k_headers
108: -- that has the supplied change request in the crs_id column, this cursor results in a full table scan of okl_k_headers
109: -- the agreement associated with the change request is the agreement that was created from the parent agreement by calling the copy api
110: OPEN c_get_creq_chr_id (p_change_request_id); FETCH c_get_creq_chr_id INTO lv_creq_chr_id;
111: CLOSE c_get_creq_chr_id;

Line 108: -- that has the supplied change request in the crs_id column, this cursor results in a full table scan of okl_k_headers

104: lv_orig_chr_id := cv_get_cr_details.orig_agr_chr_id;
105: -- now fork based on change request type
106: IF(G_ARGREEMENT_TYPE_CODE = cv_get_cr_details.change_type_code)THEN
107: -- get the agreement associated with the change request. this is achieved by getting the id from okl_k_headers
108: -- that has the supplied change request in the crs_id column, this cursor results in a full table scan of okl_k_headers
109: -- the agreement associated with the change request is the agreement that was created from the parent agreement by calling the copy api
110: OPEN c_get_creq_chr_id (p_change_request_id); FETCH c_get_creq_chr_id INTO lv_creq_chr_id;
111: CLOSE c_get_creq_chr_id;
112:

Line 456: ,okl_k_headers khr

452: ,khr.attribute14
453: ,khr.attribute15
454: FROM okc_k_headers_v chr
455: ,okc_governances gov
456: ,okl_k_headers khr
457: WHERE chr.id = cp_chr_id
458: AND chr.id = khr.id
459: AND gov.dnz_chr_id(+) = chr.id;
460: cv_hdr_attribs_orig c_hdr_attribs_csr%ROWTYPE;

Line 1410: ,okl_k_headers khr

1406: ,rul_lapmth.id lapmth_rul_id
1407: ,rul_lapmth.object1_id1 rul_lapmth_o1id1
1408: ,rul_lapmth.object1_id2 rul_lapmth_o1id2
1409: FROM okc_k_headers_b chr
1410: ,okl_k_headers khr
1411: ,okc_rule_groups_b rgp_lavenb
1412: ,okc_rules_b rul_lainpr
1413: ,okc_rules_b rul_lainvd
1414: ,okc_rules_b rul_labacc