Results for “wf_itemkey”

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

Overview

LNS_EVT_ACTION_HISTORY_H is a Loans (LNS) module table in Oracle EBS 12.1.1 and 12.2.2 that stores the audit history of workflow actions performed against a loan event. It acts as an operational journal: each time a workflow activity or action is executed for a loan event, a corresponding history record is written. This provides the traceability required to reconstruct how a loan event progressed through its approval or processing lifecycle, including the workflow item that carried it, the timestamp of the activity, and the concurrent request that triggered it.

From a Data Vault modeling perspective, the mined FK structure suggests this object is best classified as a link. It sits at the intersection of two business entities — the loan (LOAN_ID) and the event action definition (EVENT_ACTION_ID) — and records the fact that an action occurred. The presence of extensive audit and program columns reinforces this role as an associative, event-oriented record rather than a descriptive hub or a pure satellite.

The table is owned by the LNS schema and is documented as VALID in the ETRM metadata, with 16 physical columns. Its primary key is LNS_EVT_ACTION_HISTORY_H_PK on EVENT_ACTION_HISTORY_ID, and a unique index (LNS_EVT_ACTION_HISTORY_U1) exists on the same column.

Key Information Stored

The most important columns in LNS_EVT_ACTION_HISTORY_H fall into three groups: identity, relationship, and operational context.

• EVENT_ACTION_HISTORY_ID — the surrogate primary key, unique per history row.
• EVENT_ACTION_ID — foreign key to LNS_EVENT_ACTIONS, identifying the action definition that was performed.
• LOAN_ID — identifies the loan against which the action was taken; the second leg of the link relationship.
• WF_ITEMKEY / WF_ITEMTYPE — the Oracle Workflow item key and item type, enabling correlation back to the workflow instance and its runtime status.
• ACTIVITY_DATE — the effective date/time of the workflow activity, the primary timing attribute for history reporting.
• CONCURRENT_REQUEST_ID — the concurrent request that generated or processed the action, useful for diagnosing batch-driven event flows.
• CREATION_DATE / CREATED_BY — standard audit columns recording when and by whom the history row was inserted.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — standard "who last changed and when" audit columns.
• PROGRAM_UPDATE_DATE / PROGRAM_APPLICATION_ID / PROGRAM_ID / REQUEST_ID — the standard EBS "who program" tracking set, identifying the concurrent program and request that last touched the row.

Note that EVENT_ACTION_HISTORY_ID is the documented unique-index candidate and therefore the effective business key candidate, while the remaining columns hold the contextual and audit payload of the link record.

Common Use Cases and Queries

Typical applications include reconstructing the action history of a specific loan event, auditing workflow progression for compliance, and reporting on event throughput over time.

• Retrieving all actions for a loan:

  SELECT h.EVENT_ACTION_HISTORY_ID, h.EVENT_ACTION_ID, h.WF_ITEMKEY, h.ACTIVITY_DATE
  FROM   LNS_EVT_ACTION_HISTORY_H h
  WHERE  h.LOAN_ID = :loan_id
  ORDER BY h.ACTIVITY_DATE;

• Joining history to action definitions to obtain descriptive action names:

  SELECT h.ACTIVITY_DATE, a.*
  FROM   LNS_EVT_ACTION_HISTORY_H h, LNS_EVENT_ACTIONS a
  WHERE  h.EVENT_ACTION_ID = a.EVENT_ACTION_ID
  AND    h.LOAN_ID = :loan_id;

• Activity volume by concurrent request or program for performance and throughput analysis, and exception reporting on events with missing or repeated actions.

Because the table contains workflow item keys, it is also commonly used to reconcile EBS workflow runtime tables (WF_ITEM_ACTIVITY_STATUSES, WF_ITEM_ATTRIBUTES) against loan event records.

Related Objects

• LNS_EVENT_ACTIONS — referenced via LNS_EVT_ACTION_HISTORY_H.EVENT_ACTION_ID; the master definition of actions available to loan events.
• LNS_EVENTS / LNS_EVENT_ACTIONS related tables — the broader event framework that LOAN_ID and EVENT_ACTION_ID ultimately resolve into.
• WF_ITEM_ACTIVITY_STATUSES, WF_ITEM_ATTRIBUTES, WF_ITEMS — Oracle Workflow runtime tables joinable on WF_ITEMKEY and WF_ITEMTYPE.
• FND_CONCURRENT_REQUESTS — joinable on CONCURRENT_REQUEST_ID or REQUEST_ID to identify the triggering concurrent program run.
• LNS_EVT_ACTION_HISTORY_U1 — the unique index enforcing uniqueness of EVENT_ACTION_HISTORY_ID.

Together these objects allow full reconstruction of the loan event workflow lifecycle from action definition through execution history.