Search Results free_form1




Overview
Explore in AI Chat

Overview

APPS.OKL_ASSET_DFF_EXTRACT_LINE_V is a reporting and integration view within the Oracle E-Business Suite (EBS) Enterprise Contracts / Lease Management (OKL) module, part of the ETRM (Enterprise Transaction Resource Management) schema family. The view is designed to extract Descriptive Flexfield (DFF) attribute data associated with contract lines that are specifically typed as FREE_FORM1. The name of the view reflects its purpose: it surfaces asset-related flexfield segments from contract line records for downstream extraction, conversion, or interface processing.

The view exists primarily because contract lines in the OKL_TXL_CNTRCT_LNS_ALL table carry a CONTRACT_LINE_TYPE discriminator, and the DFF attributes stored on those lines are only meaningful in the context of a particular line type. FREE_FORM1 designates a free-form contract line category, and the view isolates the flexfield columns applicable to that type while returning NULL for all other line types. This conditional projection allows reporting and integration routines to consume a clean, consistent set of asset DFF columns without needing to embed the DECODE logic themselves.

In the context of EBS 12.1.1 and 12.2.2, the view behaves identically with respect to its definition; the primary differences across those releases concern underlying table partitioning, editioning, and the Online Patching (adop) infrastructure in 12.2.2, none of which alter the logical column set described here.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms in the APPS schema:

  • OKL_TXL_CNTRCT_LNS_ALL — the primary contract lines table, aliased as TCL in the view text. It holds the contract line records, including the DFF columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.
  • OKL_TXL_EXTENSION_B — the extension table, aliased as TEL, which holds supplemental line-type information. It is joined with an outer join on TCL.ID = TEL.SOURCE_ID(+) and TEL.SOURCE_TABLE(+) = 'OKL_TXL_CNTRCT_LNS'.

The outer join ensures that contract lines without a corresponding extension record are still returned, with the CONTRACT_LINE_TYPE evaluated as NULL. In that case, the DECODE expressions resolve to NULL, and the TCL_ID is still populated. The SOURCE_TABLE predicate restricts the extension join to rows originating from the contract lines table, preventing incorrect matches against other source entities.

Key Columns

  • TCL_ID — the identifier of the contract line (TCL.ID). This is the primary key used to correlate extracted rows back to the contract line record.
  • TCL_ASSET_ATTRIBUTE_CATEGORY — the DFF structure/context name, returned only when CONTRACT_LINE_TYPE equals FREE_FORM1; otherwise NULL.
  • TCL_ASSET_ATTRIBUTE1 … TCL_ASSET_ATTRIBUTE15 — the fifteen DFF segments from the contract line, each projected through an identical DECODE so that values are exposed only for FREE_FORM1 lines.

All attribute columns share the same conditional logic. Because the DECODE compares against the single literal 'FREE_FORM1', any other line type (for example leased or service line types) yields a NULL for every asset attribute column, producing a sparse row that still carries TCL_ID.

Common Use Cases and Queries

The view is typically used when a report, interface, or data conversion must extract the descriptive flexfield values of free-form contract lines only, without filtering the base table directly. A representative query returns the identifiers and populated attributes for such lines:

  • SELECT tcl_id, tcl_asset_attribute_category, tcl_asset_attribute1, tcl_asset_attribute2 FROM apps.okl_asset_dff_extract_line_v WHERE tcl_asset_attribute_category IS NOT NULL;
  • Joining the view to OKL_TXL_CNTRCT_LNS_ALL to enrich the extracted DFF data with contract header or line metadata for reporting.
  • Using the view as a source in an outbound interface or staging table load where only FREE_FORM1 line attributes are relevant.

Because the view enforces the line-type filter through DECODE rather than a WHERE clause, consumers should test for NULL on the attribute columns or join to the base table to positively identify FREE_FORM1 lines. This preserves the outer-join semantics and ensures that lines lacking extension records are not silently dropped during extraction.