Results for “insurance_yn”

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

Overview

OKL_TAA_REQUEST_DETAILS_V is an Oracle EBS view owned by the APPS schema and delivered with the OKL (Leasing and Finance Management) product module. It exposes the header-level detail associated with Transfer and Assumption (T&A) requests, the mechanism by which an existing lease contract is transferred from one lessee to another, with or without associated assets, and assumed by the incoming party. The view publishes a single logical row per T&A request record, combining the descriptive, financial, insurance, and reference attributes needed for downstream processing and reporting.

In ETRM 12.1.1 and 12.2.2 the view is classified as VALID and is defined over a single base object, making it effectively a projection of the T&A request table rather than a join-based transformation view. Because it presents the request data in a flat, denormalised form, it is convenient for operational reporting, inquiry screens, and integrations that need to read request attributes without joining multiple tables. The view is particularly relevant to users searching on invoice_format_id, since that column is surfaced directly here and identifies the invoice format associated with the transferred contract.

Underlying Base Objects

The view is defined over one documented base object:

• OKL_TAA_REQUEST_DETAILS_B (referenced as a SYNONYM) — the base table that holds the persistent T&A request details.

The view text selects from OKL_TAA_REQUEST_DETAILS_B (aliased as TAA) and does not join to any other table. The _B suffix indicates the base table of a table/view pair typically used with EBS multi-language support; the corresponding translation view is OKL_TAA_REQUEST_DETAILS_TL. The _V view is the application-facing object that presents the base column set, including the standard EBS who-columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), which support auditing and concurrency handling.

Because the definition is a direct selection, there is no row multiplication; cardinality matches the base table and constraints on the base table apply equally to queries against the view.

Key Columns

The column list reflects the functional content of a T&A request:

• ID — primary key of the T&A request detail row.
• TCN_ID — link to the transfer/contract number record that the request belongs to.
• NEW_CONTRACT_NUMBER — the contract number to be assigned to the assumed lease.
• BILL_TO_SITE_ID, CUST_ACCT_ID — billing and customer account references for the incoming party.
• BANK_ACCT_ID, PAYMENT_MTHD_ID — banking and payment method defaults for the transferred contract.
• INVOICE_FORMAT_ID — the invoice format used when invoicing the transferred contract; this is the column most relevant to invoice-format inquiries.
• MLA_ID, CREDIT_LINE_ID — associated lease/agreement and credit line references.
• INSURANCE_YN, LEASE_POLICY_YN, IPY_TYPE, POLICY_NUMBER, COVERED_AMT, DEDUCTIBLE_AMT — insurance and policy attributes for the request.
• EFFECTIVE_FROM_DATE, EFFECTIVE_TO_DATE, PROOF_REQUIRED_DATE, PROOF_PROVIDED_DATE — effective dating and insurance proof tracking.
• LESSOR_INSURED_YN, LESSOR_PAYEE_YN — lessor insurance/payee indicators.
• INT_ID, ISU_ID, AGENCY_SITE_ID, AGENT_SITE_ID, TERRITORY_CODE — insurance intermediary, issuer, agency, agent, and territory references.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — DFF (descriptive flexfield) columns for customer-specific extensions.
• CREATED_BY ... LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include reporting on transfer requests by status or date, retrieving the invoice format assigned to a pending transfer, and feeding interface programs that create or amend contracts upon assumption. A simple lookup by invoice format illustrates the search term:

SELECT id, tcn_id, new_contract_number, invoice_format_id
FROM   apps.okl_taa_request_details_v
WHERE  invoice_format_id = :p_invoice_format_id;

A request-level listing for a given contract:

SELECT new_contract_number, cust_acct_id, bank_acct_id,
       invoice_format_id, effective_from_date, effective_to_date
FROM   apps.okl_taa_request_details_v
WHERE  tcn_id = :p_tcn_id;

When querying the view, apply the standard EBS APPS initialisation (FND_GLOBAL.APPS_INITIALIZE) and respect the ORG_ID security context where applicable to the underlying table. Because the view is read-only from an application perspective, all maintenance should be performed on the base table through the supported OKL forms or APIs.