Search Results lns_event_actions




Overview
Explore in AI Chat

Overview

LNS_EVENT_ACTIONS is a Loans (LNS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores actionable events defined for a given loan type and loan class. Each row represents a discrete action that may be triggered by an event recorded in LNS_EVENTS, together with the delivery mechanism, recipient routing, and scheduling parameters that govern how that action is executed. The table therefore acts as the configuration repository that links the event model of the Loans module to the notification and processing behavior expected by the institution.

From a dimensional modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table carries descriptive attributes about event actions and is keyed by a surrogate identifier, while also pointing to parent entities such as LNS_EVENTS and LNS_LOAN_TYPES. This classification should be treated as a modeling suggestion rather than an EBS-imposed construct; the physical implementation remains a standard Oracle relational table owned by the LNS schema.

Key Information Stored

The table contains 26 documented columns. The surrogate primary key is EVENT_ACTION_ID, enforced by the constraint LNS_EVENT_ACTIONS_PK. A secondary unique index, LNS_EVENT_ACTIONS_U1, is defined on (EVENT_ACTION_ID, ZD_EDITION_NAME), which supports the editioning and multi-version characteristics of the 12.2.2 data model and can serve as a business-key candidate for edition-aware access paths.

The most significant columns include:

Common Use Cases and Queries

Typical usage centers on verifying which actions are configured for a loan type, auditing notification routing, and troubleshooting missing or duplicated event processing. A representative query joining the action to its parent event follows:

  • SELECT a.EVENT_ACTION_ID, a.EVENT_ACTION_NAME, a.ACTION_TYPE, a.DELIVERY_METHOD, a.ENABLED_FLAG FROM LNS.LNS_EVENT_ACTIONS a, LNS.LNS_EVENTS e WHERE a.EVENT_ID = e.EVENT_ID AND a.LOAN_TYPE_ID = :loan_type_id AND a.ENABLED_FLAG = 'Y';
  • Reporting actions by delivery method and recipient to assess notification coverage.
  • Reconciling configured actions against entries in LNS_EVT_ACTION_HISTORY_H to confirm execution history.
  • Using PRIORITY_NUM combined with DAYS_PRIOR_NUM and ACTIVE_FOR_NUM to model reminder, escalation, and expiry schedules.
  • Filtering on ZD_EDITION_NAME when querying under the 12.2.2 editioning model to avoid cross-edition row duplication.

Related Objects

The table participates in a small but tightly coupled set of relationships:

  • LNS_EVENTS — parent event definition; joined on LNS_EVENT_ACTIONS.EVENT_ID = LNS_EVENTS.EVENT_ID.
  • LNS_LOAN_TYPES — loan type lookup; joined on LNS_EVENT_ACTIONS.LOAN_TYPE_ID = LNS_LOAN_TYPES.LOAN_TYPE_ID.
  • LNS_EVT_ACTION_HISTORY_H — history table referencing EVENT_ACTION_ID, providing an audit trail of action execution.
  • LNS_EVENT_ACTIONS_PK — primary key constraint enforcing uniqueness of EVENT_ACTION_ID.
  • LNS_EVENT_ACTIONS_U1 — unique index supporting edition-aware access on (EVENT_ACTION_ID, ZD_EDITION_NAME).

Together these objects support configuration of loan events, their actionable outcomes, and the historical record of actions taken.