Search Results lns_approval_actions




Overview
Explore in AI Chat

Overview

The LNS_APPROVAL_ACTIONS table resides in the LNS schema and belongs to the Oracle Loans (LNS) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. Its documented description — "Loans Approval Actions Table" — identifies it as the transactional store in which the approval and rejection decisions applied to individual loan records are captured. Every time a loan proceeds through the approval workflow, the action taken against that loan is persisted here, providing the auditable trail required for loan servicing, compliance review, and downstream disbursement processing.

The table is owned by LNS and is reported as VALID in the ETRM data dictionary for 12.2.2. It carries a documented physical schema of 32 columns. From a Data Vault modeling perspective, the mined FK structure suggests a satellite-leaning classification: the table's identity is anchored to a parent loan (via LOAN_ID) while the rows themselves describe descriptive, time-stamped state changes rather than independent business entities. This classification should be treated as a modeling suggestion rather than a documented property of the EBS schema.

Key Information Stored

The most significant columns in LNS_APPROVAL_ACTIONS include the following:

  • ACTION_ID — the surrogate primary key, enforced by LNS_APPROVAL_ACTIONS_PK and also covered by the unique index LNS_APPROVAL_ACTIONS_U1. It is a system-generated identifier, not a user-facing business key.
  • LOAN_ID — the foreign key referencing the parent loan record. This is the primary linkage that ties each approval action to the loan it affects.
  • ACTION_TYPE — the classification of the action performed (for example, approval, rejection, or re-submission) against the loan.
  • AMOUNT — the monetary value associated with the action, typically the loan amount considered or approved at that step.
  • REASON_CODE — a coded justification accompanying the action, commonly populated for rejections or exceptions.
  • OBJECT_VERSION_NUMBER — the optimistic locking token used by the Oracle Applications Framework to detect concurrent updates.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — the standard WHO columns providing audit lineage for each action row.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the DFF/descriptive flexfield segment used for client-specific extensions and configuration.

Of the 32 documented columns, 20 are generic DFF attributes, leaving a compact set of functional columns that carry the real business meaning.

Common Use Cases and Queries

Typical uses include auditing the approval history of a specific loan, identifying the approver and date of a decision, reporting on approval throughput by ACTION_TYPE, and joining approval actions to the parent loan for servicing reports. A common query pattern joins the action rows to the loan master:

SELECT a.ACTION_ID, a.LOAN_ID, a.ACTION_TYPE, a.AMOUNT,
       a.REASON_CODE, a.LAST_UPDATE_DATE, a.LAST_UPDATED_BY
FROM   LNS_APPROVAL_ACTIONS a
WHERE  a.LOAN_ID = :loan_id
ORDER  BY a.LAST_UPDATE_DATE DESC;

A summary report of approval activity by action type and period follows naturally:

SELECT ACTION_TYPE, COUNT(*), SUM(AMOUNT)
FROM   LNS_APPROVAL_ACTIONS
WHERE  LAST_UPDATE_DATE BETWEEN :start_date AND :end_date
GROUP  BY ACTION_TYPE;

Because LOAN_ID is the only documented foreign key, joins to the loan header are straightforward and index-friendly when filtering by loan.

Related Objects

  • LNS_LOANS (or the LNS loan header table) — joined via LNS_APPROVAL_ACTIONS.LOAN_ID = LNS_LOANS.LOAN_ID; the parent object from which approval actions derive their identity.
  • LNS_APPROVAL_ACTIONS_PK — the primary key constraint on ACTION_ID.
  • LNS_APPROVAL_ACTIONS_U1 — the unique index on ACTION_ID, a business-key candidate.
  • LNS_APPROVAL_RULES / LNS_APPROVAL_CONFIGURATION — supporting configuration objects that govern which ACTION_TYPE values and REASON_CODE values are valid.
  • LNS_LOAN_DISBURSEMENTS — downstream object whose disbursements depend on an approved action row.
  • LNS_LOAN_TRANSACTIONS — the ledger of subsequent loan movements that frequently references approval outcomes.

Because the table's only documented foreign key is LOAN_ID, the object functions as a dependent satellite within the LNS data model, and related objects are reached primarily through the loan identifier rather than through additional documented FK links.