Results for “activity_code”

10 results




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

Overview

LNS_LOAN_PRODUCT_LINES is a Loans (LNS) module table in Oracle E-Business Suite, holding the line-level component records that make up a loan product definition. Where LNS_LOAN_PRODUCTS_ALL stores the header-level attributes of a loan product, LNS_LOAN_PRODUCT_LINES captures the individual product lines — the disbursement components, activity-linked lines, and their sequencing, percentages, and effective dating — that govern how a product behaves at the transaction level. The table is owned by the LNS schema and is documented as VALID in both ETRM 12.1.1 and 12.2.2.

The ETRM metadata classifies the object heuristically as satellite-leaning in Data Vault terms. This is best treated as a modeling suggestion rather than a normative classification: the table carries a surrogate primary key and descriptive attributes that qualify it as a satellite, while its self-referencing parent-child column (PARENT_PRODUCT_LINES_ID) and its foreign key to the loan product header introduce a hierarchical, loosely link-like quality. Modelers using this table as a source for a Data Vault layer should expect to treat it primarily as a descriptive satellite attached to the loan product hub, with a recursive hierarchy to resolve.

Key Information Stored

The table exposes 17 documented columns. The most significant are:

Note that the surrogate key (LOAN_PRODUCT_LINES_ID) and the documented unique index are the same column; no separate composite business key is documented.

Common Use Cases and Queries

Typical reporting and validation scenarios include reconstructing the full line structure of a product, verifying disbursement percentages sum correctly, and resolving parent-child nesting. A representative query:

  • Lines for a product: SELECT * FROM LNS.LNS_LOAN_PRODUCT_LINES WHERE LOAN_PRODUCT_ID = :p_id ORDER BY SEQUENCE_NUMBER;
  • Top-level lines only: add AND PARENT_PRODUCT_LINES_ID IS NULL.
  • Effective-dated lines as of a date: WHERE START_DATE_ACTIVE <= :as_of AND (END_DATE_ACTIVE IS NULL OR END_DATE_ACTIVE >= :as_of).
  • Joining to the header: SELECT l.*, p.* FROM LNS_LOAN_PRODUCT_LINES l JOIN LNS_LOAN_PRODUCTS_ALL p ON p.LOAN_PRODUCT_ID = l.LOAN_PRODUCT_ID;
  • Recursive hierarchy resolution using CONNECT BY PRIOR LOAN_PRODUCT_LINES_ID = PARENT_PRODUCT_LINES_ID to walk the self-referencing structure.

These patterns support product-configuration audits, disbursement-schedule setup, and data-migration validation.

Related Objects

  • LNS_LOAN_PRODUCTS_ALL — the header table; LNS_LOAN_PRODUCT_LINES.LOAN_PRODUCT_ID references it. This is the primary parent object for every line.
  • LNS_LOAN_PRODUCT_LINES (self-reference) — PARENT_PRODUCT_LINES_ID references the same table, forming the line hierarchy.
  • LNS_LOAN_PRODUCT_LINES_PK — the primary key constraint on LOAN_PRODUCT_LINES_ID.
  • LNS_LOAN_PRODUCT_LINES_U1 — the unique index on LOAN_PRODUCT_LINES_ID.
  • LNS_LOAN_PRODUCTS_ALL-related setup tables and Loans product setup pages/APIs — the application layer that reads and maintains these lines during product definition.

No additional tables are documented as referencing LNS_LOAN_PRODUCT_LINES beyond the self-reference, so the join surface in the ETRM metadata is concentrated on LNS_LOAN_PRODUCTS_ALL and the recursive parent-child relationship.