Search Results okl_cure_report_pk

Overview

The OKL_CURE_REPORTS table is a core data object within the Oracle E-Business Suite (EBS) module OKL (Leasing and Finance Management). It functions as the primary repository for request header details associated with a cure repurchase request. In the context of leasing and asset finance, a cure repurchase request is a formal process where a vendor or other obligated party is requested to repurchase a leased asset, typically due to a contractual default or failure to meet specific conditions. This table serves as the master record for initiating and tracking such requests, anchoring a key workflow in the portfolio management and asset recovery processes of the leasing lifecycle.

Key Information Stored

While the full column list is not detailed in the provided metadata, the structure and foreign keys indicate the table stores essential identifiers and relational data. The primary key, CURE_REPORT_ID, uniquely identifies each cure repurchase request. Crucially, the table maintains links to the purchasing vendor details through foreign key columns: VENDOR_ID (linking to PO_VENDORS), VENDOR_SITE_ID (linking to PO_VENDOR_SITES_ALL), and VENDOR_CONTACT_ID (linking to PO_VENDOR_CONTACTS). This design ensures the request is tied to the correct legal entity, remittance address, and point of contact. Other header information likely includes request dates, status, originating contract or asset identifiers, and descriptive information about the cure event.

Common Use Cases and Queries

This table is central to operational reporting and process tracking for cure repurchases. Common use cases include generating a list of all active cure requests, tracking the status of requests against a specific vendor, and auditing the cure process lifecycle. A typical query might join OKL_CURE_REPORTS with vendor tables to produce a vendor-centric report. For example:

• Identifying all cure requests for a vendor: SELECT cr.cure_report_id, cr.creation_date, pv.vendor_name FROM okl_cure_reports cr, po_vendors pv WHERE cr.vendor_id = pv.vendor_id AND pv.vendor_name = '&VENDOR_NAME';
• Linking a cure request header to its detailed line amounts: SELECT cr.*, cra.* FROM okl_cure_reports cr, okl_cure_report_amounts cra WHERE cr.cure_report_id = cra.cure_report_id;

These queries support financial analysis, vendor management, and compliance reporting.

Related Objects

The OKL_CURE_REPORTS table is part of a defined data model with specific dependencies. Its primary child table is OKL_CURE_REPORT_AMOUNTS, which stores the detailed financial amounts (e.g., repurchase price, fees) associated with the parent request header. As noted, it has three key foreign key relationships to foundational Purchasing (PO) tables: PO_VENDORS, PO_VENDOR_SITES_ALL, and PO_VENDOR_CONTACTS. This integration ensures vendor data consistency across EBS. The existence of the primary key constraint OKL_CURE_REPORT_PK confirms its role as a referenced parent entity. It is important to note the metadata states it is "Not implemented in this database," which may indicate the object is seeded but not populated in a specific instance or requires a particular setup or product usage to be active.