Results for “vendor_program_number”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_C_V_RULES_UV is a read-only reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKL (Lease and Finance Management) product family. The view consolidates vendor program data with the lease and loan contracts generated under those programs, exposing the rule sets attached to each vendor program alongside the vendor and contract identifiers. Its design supports the common OAF and concurrent program reporting requirement of returning vendor, vendor program, contract, and rule information in a single denormalized result set, avoiding multi-step navigation through the OKC and OKL contract tables. The suffix "_UV" indicates a user-facing validation or lookup view intended primarily to back value sets, LOVs, and diagnostic reporting rather than to store data. Because it is a view, it holds no data of its own; it resolves entirely from its underlying base objects at query time.

Underlying Base Objects

The view is defined over six documented referenced objects: OKC_K_HEADERS_V (VIEW), OKC_K_PARTY_ROLES_B (SYNONYM), OKC_RULES_B (SYNONYM), OKC_UTIL (PACKAGE), OKL_K_HEADERS (SYNONYM), and OKX_VENDORS_V (VIEW). Two aliases of OKC_K_HEADERS_V supply the program record (PROG) and the lease contract record (LEASE), joined through OKL_K_HEADERS (KHR), where KHR.KHR_ID equals the program header and KHR.ID equals the lease header. Vendor identity is resolved from OKX_VENDORS_V (VND) by matching OKC_K_PARTY_ROLES_B.OBJECT1_ID1 and OBJECT1_ID2 to VND.ID1 and VND.ID2, restricted to party role code OKL_VENDOR. Rules are joined from OKC_RULES_B (RUL) on DNZ_CHR_ID equal to the program header ID. Program rows are filtered by SCS_CODE = 'PROGRAM' and contract rows by SCS_CODE IN ('LEASE','LOAN'). The inclusion of OKC_UTIL (PACKAGE) is documented in the metadata and typically reflects a helper function referenced within view-level logic.

Key Columns

The view exposes 24 columns. VENDOR_ID and VENDOR_NAME identify the vendor party. VENDOR_PROGRAM_ID, VENDOR_PROGRAM_NUMBER, and VENDOR_PROGRAM_NAME describe the program contract header. CONTRACT_ID, CONTRACT_NUMBER, and CONTRACT_DESCRIPTION identify the associated lease or loan contract. RULE_CODE carries the rule information category, while RULE_INFORMATION1 through RULE_INFORMATION15 hold the fifteen DFF-style rule attributes. A frequent reporting question concerns vendor_program_id, which is the program header primary key (PROG.ID) and serves as the join key linking vendor, program, contract, and rule rows in a single result. This column is the principal filter for isolating all contracts and rules belonging to one vendor program.

Common Use Cases and Queries

Typical uses include validating vendor program rule setups, driving value sets keyed on a vendor program, and extracting audit-ready rule listings per contract.

• List all contracts and rules for a specific program: SELECT vendor_program_id, contract_number, rule_code, rule_information1 FROM okl_c_v_rules_uv WHERE vendor_program_id = :p_program_id;
• Report all programs for a vendor: SELECT vendor_name, vendor_program_number, vendor_program_name FROM okl_c_v_rules_uv WHERE vendor_id = :p_vendor_id GROUP BY vendor_name, vendor_program_number, vendor_program_name;
• Inspect rule attributes for lease contracts: SELECT contract_number, rule_code, rule_information1, rule_information2 FROM okl_c_v_rules_uv WHERE rule_code = :p_rule_code ORDER BY contract_number;

Because the view filters on SCS_CODE values 'PROGRAM', 'LEASE', and 'LOAN', results are inherently scoped to active lease and finance constructs. Joins should always include vendor_program_id when correlating back to OKC_K_HEADERS or OKL_K_HEADERS, as multiple contracts can share a single program.