Search Results immediate_repurchase_yn

Overview

ZOKL_BANKRUPTCIES_V is a reporting and integration view within the Oracle E-Business Suite (EBS) OKL – Leasing and Finance Management module. It presents bankruptcy information recorded against lessees, contracts, and related parties in the leasing lifecycle. According to the ETRM documentation, the view is described simply as the "View for table OKL_BANKRUPTCIES_B," indicating that it exposes the operational bankruptcy record data maintained in the base bankruptcy entity for reporting, inquiry, and downstream integration purposes. The view is available in both EBS 12.1.1 and 12.2.2, and its primary role is to provide a flattened, read-consistent projection of bankruptcy attributes for use by concurrent programs, reports, and interfaces without requiring consumers to navigate the normalized base tables directly.

Notably, the ETRM metadata states that this object is "Not implemented in this database." This means the view may be a seeded or planned object that is absent from certain environments or patch levels, and any implementation referencing it must first confirm its existence in the target instance.

Underlying Base Objects

The view is defined over the bankruptcy base table. The SELECT statement references two aliases: BANB, corresponding to OKL_BANKRUPTCIES_B (the bankruptcy header/base record), and BANT, corresponding to the associated translation table, typically OKL_BANKRUPTCIES_TL. The view joins the base and translation records so that descriptive, language-dependent fields — such as the bankruptcy filed name, category, file city, comments, and state — are presented alongside the operational fields from the base table.

Columns such as ROW_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID confirm the base table's standard EBS WHO-column and concurrent-program audit structure. The ORG_ID column confirms that the entity is operating-unit (multi-org) enabled.

Key Columns

• ID / ROW_ID: The primary identifier and physical row identifier of the bankruptcy record.
• CAC_ID: The contract or customer account identifier associated with the bankruptcy. Because this is the term the user searched, it is the key link between a bankruptcy record and the leased contract/account context in OKL.
• PTY_ID: The party identifier, linking the bankruptcy to the lessee or counterparty.
• BANKRUPTCY_CASE_NUMBER / BRS_CODE: The case number and bankruptcy reference status code.
• BANKRUPTCY_FILE_DATE / COURT_ORDER_DATE / PROOF_OF_CLAIM_BAR_DATE: Critical legal milestone dates governing bankruptcy proceedings.
• CEASE_COLLECTION_ACTIVITY_YN / TURN_OFF_INVOICING_YN / IMMEDIATE_REPURCHASE_YN: Operational flags that suppress collection activity, halt invoicing, or trigger repurchase treatment upon a bankruptcy filing.
• TRUSTEE_CONTACT_ID / DEBTOR_CONTACT_ID: References to the trustee and debtor contacts.
• BANKRUPTCY_STATUS / BANKRUPTCY_STATE: Current workflow and geographic state of the bankruptcy.
• ATTRIBUTE1 through ATTRIBUTE15 / ATTRIBUTE_CATEGORY: Descriptive flexfield values.
• SFWT_FLAG: Translation-table flag indicating whether the descriptive column value is stored in the current session language.

Common Use Cases and Queries

This view is typically used for bankruptcy tracking reports, collection-suppression analysis, and integration extracts that must convey the contract (CAC_ID), party, status, and key dates to external systems.

A representative query filtering by the searched identifier:

• SELECT id, cac_id, pty_id, bankruptcy_case_number, bankruptcy_status, bankruptcy_file_date, cease_collection_activity_yn FROM zokl_bankruptcies_v WHERE cac_id = :p_cac_id;
• SELECT id, pty_id, bankruptcy_category, bankruptcy_file_city, court_order_date FROM zokl_bankruptcies_v WHERE turn_off_invoicing_yn = 'Y';

Analysts frequently join CAC_ID back to contract tables to correlate bankruptcy events with lease balances and billing status. Because the metadata records no documented base dependencies beyond the bankruptcy base and translation tables, tests should precede any production use, particularly since the object may not be implemented in all environments.