Results for “okl_open_int_v”

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

Overview

OKL_OPEN_INT_V is a reporting and integration view within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. Its documented purpose is to serve as an open interface for reporting to a credit bureau or for transferring data to an external agency. The view presents a denormalized, flat projection of lease and finance contract data together with associated party, address, and delinquency information, allowing external systems or downstream reporting processes to consume the data through a single queryable object rather than navigating the normalized OKL schema.

The view is defined with a straightforward SELECT over the single base table OKL_OPEN_INT, aliased OIN. It exposes the source table's ROWID as ROW_ID, which supports row-level identification useful in correction or purge routines. According to the ETRM metadata, the underlying implementation object is not present in the documented database, indicating that the view is a seeded but optional component whose population depends on the OKL open interface being loaded and activated.

Underlying Base Objects

The view is defined exclusively over the table OKL_OPEN_INT. No additional base tables are documented as participating in the view definition; joins to party, contract, or case data are presumed to be performed during the load of OKL_OPEN_INT rather than at query time. This design keeps the interface view performant and independent of the transactional OKL_OBJECTS, OKL_K_HEADERS, and OKL_K_LINES structures that hold live contract data.

Because the view contains no joins, filtering and projection pushdown to the base table is complete. The presence of ORGANIZATION_ID (ORG_ID), REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE columns confirms that the source table is populated by a concurrent program, consistent with standard EBS open interface conventions. The WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER support auditing and optimistic locking on the underlying records.

Key Columns

• ROW_ID, ID — ROWID of the base row and the primary identifier of the interface record.
• Party attributes — PARTY_ID, PARTY_NAME, PARTY_TYPE, DATE_OF_BIRTH, PLACE_OF_BIRTH, PERSON_IDENTIFIER, and PERSON_IDEN_TYPE describe the customer for credit bureau submission.
• Address attributes — COUNTRY, ADDRESS1 through ADDRESS4, CITY, POSTAL_CODE, STATE, PROVINCE, COUNTY, PO_BOX_NUMBER, HOUSE_NUMBER, STREET, STREET_NUMBER, STREET_SUFFIX, APARTMENT_NUMBER, BUILDING, FLOOR, SUITE, ROOM, RURAL_ROUTE_NUMBER, and POSTAL_PLUS4_CODE provide the granular address detail required by reporting agencies.
• Case and contract attributes — CAS_ID, CASE_NUMBER, KHR_ID, CONTRACT_NUMBER, CONTRACT_TYPE, and CONTRACT_STATUS identify the lease or loan and its lifecycle state.
• Financial attributes — ORIGINAL_AMOUNT, MONTHLY_PAYMENT_AMOUNT, PAST_DUE_AMOUNT, REMAINING_AMOUNT, START_DATE, CLOSE_DATE, TERM_DURATION, and LAST_PAYMENT_DATE quantify the obligation and its performance.
• Credit and agency attributes — DELINQUENCY_OCCURANCE_DATE, CREDIT_INDICATOR, NOTIFICATION_DATE, CREDIT_BUREAU_REPORT_DATE, EXTERNAL_AGENCY_TRANSFER_DATE, EXTERNAL_AGENCY_RECALL_DATE, and REFERRAL_NUMBER track bureau and collection agency activity.
• Contact attributes — CONTACT_ID, CONTACT_NAME, CONTACT_PHONE, and CONTACT_EMAIL identify the responsible contact.
• Interface control and DFF — ORG_ID, REQUEST_ID, PROGRAM_ID, OBJECT_VERSION_NUMBER, and ATTRIBUTE_CATEGORY with ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical usage includes extracting delinquent contracts for monthly credit bureau submission, transferring qualifying cases to an external collection agency, and auditing the status of prior submissions and recalls.

Example query listing open delinquent contracts prepared for bureau reporting:

• SELECT id, party_name, contract_number, contract_status, past_due_amount, delinquency_occurance_date, credit_bureau_report_date FROM okl_open_int_v WHERE credit_indicator = 'Y' AND past_due_amount > 0 ORDER BY past_due_amount DESC;
• SELECT id, contract_number, external_agency_transfer_date, external_agency_recall_date, referral_number, org_id FROM okl_open_int_v WHERE external_agency_transfer_date IS NOT NULL AND external_agency_recall_date IS NULL;
• SELECT request_id, program_id, COUNT(*) FROM okl_open_int_v GROUP BY request_id, program_id ORDER BY request_id;

These patterns align with the documented role of the view: an open interface that decouples OKL contract data from external credit bureau and agency reporting requirements.