Search Results actual_draft_status




Overview
Explore in AI Chat

Overview

OKL_BPD_AR_ADJUSTMENTS_V is an APPS-owned database view in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It presents a consolidated, unified stream of receivables adjustment transactions originating from lease and finance contracts, exposing them in a flat structure suitable for reporting, reconciliation, and downstream integration. The view is part of the BPD (Business Process Document / transaction presentation) family of views that standardize lease-related transactions across multiple sources, giving a consistent column model so that consumers such as accounting extracts, contract transaction inquiries, and custom reports can query adjustment activity without navigating the normalized OLTP tables directly.

A defining characteristic of the view is that several columns are deliberately projected as NULL constants because the source records are receivables adjustments rather than other lease transaction types. Notably, ACTUAL_DRAFT_STATUS_CODE and ACTUAL_DRAFT_STATUS are returned as NULL, and the source is hard-coded with SOURCE_CODE = 'REC' and a corresponding lookup-derived SOURCE value obtained through OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING. This explains why a search for "actual_draft_status" surfaces this object: the column exists in the column list for interface conformity, but it is not populated for the REC adjustment source. Users expecting a draft status value here will always receive NULL and must obtain draft status from the applicable source view for their transaction type.

Underlying Base Objects

The view is defined through an inner join chain across the following documented base objects:

The joins enforce the correspondence between a lease contract, its product, its transaction type, and the associated AR adjustment, thereby guaranteeing that only adjustments traceable to a lease contract are exposed.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling lease receivables adjustments to AR, reporting adjustments by contract and product, and feeding accounting or analytical extracts. Because ACTUAL_DRAFT_STATUS is NULL, it should not be filtered or relied upon here.

  • Adjustments for a contract:
    SELECT contract_number, transaction_number, transaction_date, amount, currency_code FROM okl_bpd_ar_adjustments_v WHERE contract_number = :p_contract;
  • Adjustments by ledger and period:
    SELECT ledger_id, product_name, SUM(amount) FROM okl_bpd_ar_adjustments_v WHERE transaction_date BETWEEN :p_from AND :p_to GROUP BY ledger_id, product_name;
  • Multi-org reporting:
    SELECT org_id, COUNT(*), SUM(total_transaction_amount) FROM okl_bpd_ar_adjustments_v GROUP BY org_id;