Results for “okl_line_relationships_b”

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

Overview

The OKL_LINE_RELATIONSHIPS_B table is a core transactional data object within the Oracle E-Business Suite (EBS) Leasing and Finance Management module (OKL). It is documented in ETRM for both 12.1.1 and 12.2.2 implementations and resides in the OKL product schema. The object stores line relationships, which are the associations that connect individual contract or lease lines to one another. In Oracle Lease Management, lines represent the discrete financial, asset, or service components of an agreement, and relationships between lines capture structured dependencies such as bundled pricing, linked origination and associated charges, or derived amounts that flow from one line to another.

The documented physical schema consists of 29 columns, governed by the primary key constraint OKL_LRE_PK on the ID column. A unique index, OKL_LRE_UC1, also covers the ID column and serves as the documented business-key candidate. The heuristic Data Vault classification mined from the foreign-key structure is "standalone," meaning the table is not strongly tied into a conventional hub-and-link constellation. As a modeling suggestion, this classification implies the table behaves more like an independent transactional entity than a dependent satellite or an intersection link, and should be treated accordingly when designing integration or warehouse extract logic.

Key Information Stored

The most significant columns in this table are:

• ID — the surrogate primary key (OKL_LRE_PK), uniquely identifying each line relationship record.
• SOURCE_LINE_TYPE and SOURCE_LINE_ID — identify the originating line in the relationship, qualifying both the line category and its identifier.
• RELATED_LINE_TYPE and RELATED_LINE_ID — identify the counterpart line that the source line is associated with.
• AMOUNT — the monetary value associated with the line relationship, used in financial roll-ups and pricing calculations.
• ORIGINATION_INCOME — captures income generated at the origination point of the relationship, supporting revenue recognition and fee accounting.
• OBJECT_VERSION_NUMBER — supports optimistic locking during concurrent updates.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) columns enabling client-specific extension of the relationship record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who columns providing audit lineage for each row.

The source and related line type/ID pairs form the substantive business content; the ID column is purely technical and should not be exposed as a business identifier in reporting.

Common Use Cases and Queries

Typical applications include reconciliation of linked line amounts, reporting on origination income by contract, and dependency analysis when lines are restructured or terminated. A representative query joining source and related lines is:

• SELECT lr.ID, lr.SOURCE_LINE_ID, lr.RELATED_LINE_ID, lr.AMOUNT, lr.ORIGINATION_INCOME FROM OKL_LINE_RELATIONSHIPS_B lr WHERE lr.SOURCE_LINE_ID = :line_id;
• Aggregate amount reporting: SELECT SOURCE_LINE_TYPE, SUM(AMOUNT) FROM OKL_LINE_RELATIONSHIPS_B GROUP BY SOURCE_LINE_TYPE;
• Audit and change tracking using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Flexfield-based segmentation using ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for custom reporting dimensions.

Related Objects

Because the heuristic classification is standalone, the table's relationships to other OKL objects are driven through the source and related line identifiers rather than enforced foreign keys. The principal objects commonly joined are:

• OKL_LINE_RELATIONSHIPS_TL — the translation table that stores language-specific descriptive text for relationship records, joined on ID.
• OKL_LINES_B / OKL_LINES_TL — the master contract line tables joined via SOURCE_LINE_ID and RELATED_LINE_ID.
• OKL_HEADERS_B / OKL_HEADERS_TL — parent contract headers used to roll line relationships up to agreement level.
• OKL_ORIGINATIONS_B — origination records that provide context for ORIGINATION_INCOME values.
• OKL_STREAMS_B — payment or billing streams whose amounts may be derived from line relationships.
• OKL_TXN_ACCOUNTING / OKL_SUBSCRIBED_AGREEMENTS — accounting and subscription objects that consume relationship amounts for postings.