Results for “okl_cure_vendor_program_uv”

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

Overview

The APPS.OKL_CURE_VENDOR_PROGRAM_UV view is a reporting and integration object within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. It exposes the relationship between vendors and lease programs by resolving the party-role assignments that link a vendor to a program contract. In OKL, a program is a contract header whose SCS code is 'PROGRAM' and which is governed by a rule group identifying the cure program logic. Vendors are attached to these programs through party roles. This view flattens that many-to-many association into a single denormalized result set containing the vendor identity, the program identity, and descriptive attributes suitable for lookups, LOVs, and downstream reporting.

The view exists to support user-interface validation and reporting where a consumer needs to know which vendors are associated with a given program, or conversely which programs a vendor participates in. Because it is an _UV (user view) object owned by APPS, it is intended for direct query by custom reports, concurrent programs, and integration extracts rather than for base-table updates. The status is VALID in the documented ETRM 12.2.2 metadata, and the object is equally referenced in 12.1.1 environments.

Underlying Base Objects

The view is defined over four referenced objects:

• OKC_K_HEADERS_V (VIEW) — supplies the program header record, aliased as PROG. It carries CONTRACT_NUMBER, SHORT_DESCRIPTION, and the SCS classification used to isolate programs.
• OKC_K_PARTY_ROLES_B (SYNONYM in APPS) — supplies the party-role rows, aliased as PTY. The join restricts to RLE_CODE = 'OKL_VENDOR' and matches the vendor through OBJECT1_ID1 and OBJECT1_ID2.
• OKX_VENDORS_V (VIEW) — supplies vendor identity and name, aliased as VND, joined on the two-part vendor ID.
• OKC_RULE_GROUPS_V (VIEW) — supplies the rule-group association, aliased as RGD, filtered to RGD_CODE = 'COCURP'.

An additional dependency, the OKC_UTIL package, is referenced by the view text, typically for internal helper logic used within the underlying OKC views (for example, deterministic ID resolution). The joins are inner joins throughout, so only vendor/program combinations that satisfy all four conditions appear in the result.

Key Columns

• VENDOR_ID — the internal vendor identifier (VND.ID1), used as the foreign key to supplier and vendor tables.
• VENDOR_NAME — the display name of the vendor from OKX_VENDORS_V.
• PROGRAM_ID — the contract header ID (PROG.ID) of the program record.
• PROGRAM_NUMBER — the program contract number (PROG.CONTRACT_NUMBER); this is the column most frequently searched by users querying "program_number".
• PROGRAM_NAME — the short description of the program (PROG.SHORT_DESCRIPTION).

Common Use Cases and Queries

Typical scenarios include validating that a vendor is eligible for a program, populating a vendor-by-program LOV, and generating reconciliation reports. A representative query returning all vendors for a known program number:

SELECT vendor_id, vendor_name, program_number, program_name
FROM   apps.okl_cure_vendor_program_uv
WHERE  program_number = :p_program_number
ORDER  BY vendor_name;

Conversely, listing all programs for a vendor:

SELECT program_number, program_name
FROM   apps.okl_cure_vendor_program_uv
WHERE  vendor_id = :p_vendor_id;

Because the view only returns fully joined rows, a vendor or program that lacks the required rule group or party role will not appear, and this should be considered when diagnosing missing associations.