Results for “funding_date”

50+ results




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

Overview

OKL_LEASE_OPPS_ALL_B is the Lease Opportunity header table within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. It stores the master record for each lease opportunity, capturing the commercial, financial, and organizational context in which a prospective lease is evaluated before it progresses to a formal lease or contract. As the header entity, each row in this table represents one opportunity, and downstream opportunity-related details, such as opportunity lines and asset associations, reference the opportunity through the ID column.

The table resides in the OKL schema and is documented as VALID in both ETRM 12.1.1 and 12.2.2. It contains 55 columns, including the standard Oracle EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and a multi-org ORG_ID column for operating unit separation. In Data Vault terms, the metadata classifies this object heuristically as standalone. This classification suggests it functions as a hub-like entity, anchoring the opportunity identifier and its descriptive attributes with limited foreign-key fan-in to other core master tables.

Key Information Stored

The surrogate primary key is ID, enforced by the constraint OKL_LEASE_OPPS_ALL_B_PK and reinforced by the unique index OKL_LEASE_OPPS_ALL_B_U1. A second unique index, OKL_LEASE_OPPS_ALL_B_U2, is defined on REFERENCE_NUMBER, making it the documented business-key candidate. Application logic should treat REFERENCE_NUMBER as the human-readable opportunity reference while using ID for internal joins.

Common Use Cases and Queries

The most frequent access pattern is retrieving an opportunity by its business key. Because REFERENCE_NUMBER carries a unique index, the following query is index-driven and efficient:

  • SELECT * FROM okl.okl_lease_opps_all_b WHERE reference_number = :p_ref_num;
  • SELECT * FROM okl.okl_lease_opps_all_b WHERE id = :p_id; — primary-key lookup used when joining from child tables.
  • Operational reporting filtered by organization and status, for example opportunities by operating unit: SELECT reference_number, status, currency_code FROM okl.okl_lease_opps_all_b WHERE org_id = :p_org_id AND status = :p_status;
  • Legal entity reporting using the documented foreign key: SELECT o.reference_number, l.legal_entity_name FROM okl.okl_lease_opps_all_b o, fv_legal_entities l WHERE o.legal_entity_id = l.legal_entity_id;

Typical consumers include opportunity pipelines, sales-performance dashboards, and integration extracts that must resolve the opportunity identifier before posting downstream contract or order data.

Related Objects

The documented relationship data lists a single enforced foreign key, but functional dependencies follow the ID column across the OKL opportunity schema.

  • FV_LEGAL_ENTITIES — joined via LEGAL_ENTITY_ID to resolve legal entity attributes.
  • OKL_LEASE_OPPS_ALL_TL — translation table keyed by the opportunity ID for language-dependent descriptions.
  • OKL_OPP_LINES (and equivalent opportunity line tables) — child records joined through ID.
  • OKL_OPP_ASSETS (and opportunity asset associations) — assets evaluated for the opportunity, joined through ID.
  • OKL_HEADERS_ALL — formal lease headers created when an opportunity progresses, linked through the originating opportunity.

Because REFERENCE_NUMBER is unique, it is the preferred key for external interfaces, while ID remains the recommended join column for all internal OKL relationships.