Results for “primary_key_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
LNS_LOAN_HISTORIES_H is a loan history table residing in the LNS (Loans) schema within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It functions as an audit and change-tracking repository for loan records maintained elsewhere in the Loans module. Rather than holding the current state of a loan, the table captures historical snapshots and field-level modifications, recording the table name, column name, prior value, and new value associated with each change event. This design supports regulatory auditability, dispute resolution, and downstream reconciliation of loan servicing activity.
From a Data Vault modeling perspective, the table is heuristically classified as satellite-leaning. Its structure — a descriptive detail set anchored to a parent business entity via a foreign key, with change-tracking attributes — resembles a satellite table attached to a hub or link. This classification is a modeling suggestion only; in the physical EBS schema the object is a conventional transactional history table.
Key Information Stored
The table comprises 14 documented columns. The most consequential are:
- LOAN_HISTORY_ID — The surrogate primary key and the sole documented unique index (LNS_LOAN_HISTORIES_U1). It uniquely identifies each history row.
- LOAN_ID — Foreign key to LNS_LOAN_HEADERS_ALL. This is the business-key linkage that ties every history record to its parent loan.
- TABLE_NAME — Identifies the source table whose row was modified, enabling multi-table audit coverage from a single history repository.
- COLUMN_NAME — The specific attribute that changed, providing field-level granularity for audit trails.
- OLD_VALUE and NEW_VALUE — The before-and-after values, forming the core of the change comparison used in audit and reconciliation reporting.
- DATA_TYPE — Describes the datatype of the captured value, which is necessary because values are stored in a generic format.
- PRIMARY_KEY_ID — Associates the history row with the primary key of the affected source record, allowing precise row identification in the originating table.
- OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrency control consistent with the EBS multi-tier architecture.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard EBS audit columns recording who created and last modified the record, when, and from which login session.
The business-key candidate for uniqueness is LOAN_HISTORY_ID via the unique index; LOAN_ID is a foreign key rather than a unique attribute, reflecting the one-to-many relationship between a loan and its history entries.
Common Use Cases and Queries
Typical usage centers on audit reconstruction and change reporting for loan servicing. A common pattern retrieves the full change history for a given loan, ordered chronologically:
SELECT h.LOAN_HISTORY_ID, h.TABLE_NAME, h.COLUMN_NAME, h.OLD_VALUE, h.NEW_VALUE, h.CREATION_DATE, h.CREATED_BY FROM LNS.LNS_LOAN_HISTORIES_H h WHERE h.LOAN_ID = :loan_id ORDER BY h.CREATION_DATE;- Audit reporting that isolates changes to a specific column (for example, interest rate or status fields) by filtering on
COLUMN_NAME. - Reconciliation between the current loan record in LNS_LOAN_HEADERS_ALL and its historical values to detect unauthorized or unexpected modifications.
- Reconstruction of a point-in-time loan state by replaying ordered OLD_VALUE and NEW_VALUE pairs.
- Compliance extracts that join history rows to the parent loan to attribute changes to a borrower, portfolio, or servicing agent.
Related Objects
The principal related objects are:
- LNS_LOAN_HEADERS_ALL — The parent loan header table, joined on
LNS_LOAN_HISTORIES_H.LOAN_ID = LNS_LOAN_HEADERS_ALL.LOAN_ID. This is the documented foreign-key relationship and the primary anchor for all history queries. - LNS_LOAN_HISTORIES_U1 — The unique index on LOAN_HISTORY_ID, enforcing surrogate-key integrity.
- Loan detail and schedule tables in the LNS schema that supply the TABLE_NAME and COLUMN_NAME values recorded in history rows, sourced through the generic history mechanism.
- Standard EBS audit infrastructure tables (such as FND_LOGINS and FND_USER) referenced indirectly through CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for user attribution.
- Loan servicing and reporting APIs or concurrent programs in the Loans module that consume history data for audit output and reconciliation.
Together these objects position LNS_LOAN_HISTORIES_H as the change-tracking satellite for the loan entity, supporting audit, compliance, and historical reporting requirements across EBS 12.1.1 and 12.2.2.
-
Loan History Table
-
Stores status and error infomation of replay
-
Primary and unique keys registered with Oracle Application Object Library
-
Loan History Table
-
Foreign keys registered with Oracle Application Object Library
-
Primary and unique key columns registered with Oracle Application Object Library
-
Primary and unique key columns registered with Oracle Application Object Library
-
Primary and unique keys registered with Oracle Application Object Library
-
Foreign keys registered with Oracle Application Object Library
-
This table is used to record account merge audit history
-
This table is used to record account merge audit history
-
PACKAGE BODY: APPS.JL_CMERGE 12.1.1
-
PACKAGE: APPS.JL_CMERGE 12.2.2
-
PACKAGE BODY: APPS.JL_CMERGE 12.2.2
-
PACKAGE: APPS.JL_CMERGE 12.1.1
-
APPS.AD_DD SQL Statements 12.1.1
-
PACKAGE: APPS.GMS_CMERGE 12.1.1
-
PACKAGE: APPS.GMS_CMERGE 12.2.2
-
APPS.AD_DD SQL Statements 12.2.2