Search Results lns_cond_assignments




Overview

LNS_COND_ASSIGNMENTS is the Loan Condition Assignment table within the Oracle Loans (LNS) module of Oracle E-Business Suite, documented as VALID in release 12.1.1 and 12.2.2. The table records the association between a specific loan and the conditions that must be satisfied before, during, or after disbursement. Each row represents a single condition assigned to a single loan, carrying the fulfillment state, mandatory status, and effective dating for that assignment.

The object functions as an intersection entity: it links a loan to a reusable condition definition, so that the same condition can be applied to many loans while preserving an independent fulfillment outcome for each. In Data Vault terms, the mined foreign-key structure suggests a link classification, since the table's documented role is to resolve the many-to-many association between loans and conditions, with the fulfillment attributes behaving as link-level descriptive data. This classification is a heuristic modeling suggestion derived from the FK structure, not an ETRM-declared attribute.

Key Information Stored

The physical schema is owned by LNS and documents 20 columns. The surrogate primary key is COND_ASSIGNMENT_ID, enforced by LNS_COND_ASSIGNMENTS_PK and reinforced by the unique index LNS_COND_ASSIGNMENTS_U1 on the same column; COND_ASSIGNMENT_ID is therefore the only documented business-key candidate, and no natural composite business key is exposed in the metadata.

Common Use Cases and Queries

Condition fulfillment tracking is the dominant reporting use case. Lending operations query outstanding mandatory conditions per loan to determine disbursement readiness, and compliance functions review fulfillment dates and the user who closed each condition.

  • Conditions pending for a loan: select from LNS_COND_ASSIGNMENTS where LOAN_ID equals the target loan and CONDITION_MET_FLAG is not set.
  • Mandatory backlog: filter on MANDATORY_FLAG in combination with an unset CONDITION_MET_FLAG to isolate blocking items.
  • Effective-dated view: constrain by START_DATE_ACTIVE and END_DATE_ACTIVE to obtain currently active assignments.
  • Audit trail: join FULFILLMENT_UPDATED_BY to FND_USER to attribute fulfillment actions to named users.
  • Owner resolution: use OWNER_TABLE with OWNER_OBJECT_ID to route records back to the originating object.

Related Objects

  • LNS_CONDITIONS — referenced through COND_ASSIGNMENTS.CONDITION_ID; the condition definition master.
  • Loan header table — referenced through COND_ASSIGNMENTS.LOAN_ID; documented as a foreign relationship.
  • FND_USER — referenced through FULFILLMENT_UPDATED_BY for fulfillment attribution.
  • LNS_COND_ASSIGNMENTS_PK / LNS_COND_ASSIGNMENTS_U1 — primary key constraint and unique index on COND_ASSIGNMENT_ID.
  • Disbursement header objects — associated via DISB_HEADER_ID.