Search Results okl_vp_change_requests

Overview

The OKL_VP_CHANGE_REQUESTS table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the OKL (Lease and Finance Management) product module. As documented, it serves as the primary change request table for Vendor Agreements. This table functions as the system of record for tracking and managing proposed modifications to vendor contract terms within the leasing and financing lifecycle. Its role is critical for maintaining an auditable history of agreement amendments, ensuring that all changes follow a formal request and approval workflow before being implemented in the active contract header.

Key Information Stored

The table's structure is designed to capture the essential details of a change request. While the full column list is not provided in the metadata, the documented primary key is the ID column, which uniquely identifies each change request record. A crucial foreign key relationship is established with the OKL_K_HEADERS table via the CRS_ID column in that table. This links each change request to the specific lease or finance contract (the "K" header) it intends to modify. Typically, such a table would also store columns for the request description, the specific terms being changed (e.g., payment schedule, asset details, pricing), the requestor, dates (creation, target effective), status (e.g., PENDING, APPROVED, REJECTED), and approval history.

Common Use Cases and Queries

The primary use case is managing the end-to-end process of amending a Vendor Agreement. Common operational and reporting activities include querying all pending change requests for a portfolio manager, listing historical changes for a specific contract for audit purposes, or identifying requests created within a specific date range. Sample SQL patterns often involve joining to the contract header table. For example, to find active change requests for a given contract number:

• SELECT crq.* FROM okl_vp_change_requests crq, okl_k_headers kh WHERE kh.id = crq.id AND kh.contract_number = '<CONTRACT_NUM>' AND crq.status = 'PENDING';

Another common pattern is generating a report of approved changes effective in a future period, which is vital for financial forecasting and operations planning within the leasing module.

Related Objects

The most significant related object, as explicitly defined by the foreign key, is the OKL_K_HEADERS table. This is the master contract header table in OKL, and the foreign key from OKL_K_HEADERS.CRS_ID to OKL_VP_CHANGE_REQUESTS.ID solidifies the one-to-many relationship where a single contract can have multiple associated change requests. This table is also likely referenced by various OKL APIs and PL/SQL packages that govern the vendor agreement change workflow. Furthermore, it may serve as a base for key reporting views within the module, which aggregate change request data with information from related entities like vendors, items, or parties for comprehensive reporting.