Search Results igi_itr_action_history




Overview
Explore in AI Chat

Overview

IGI_ITR_ACTION_HISTORY is an Oracle EBS table owned by the IGI schema, which supports the Public Sector Financials International product. Per the ETRM documentation, the table "Maintains the Approval Action History for all charge lines," functioning as the audit and workflow tracking repository for the iterative approval lifecycle of charge lines processed through the IGI transaction reconciliation (ITR) framework. Each row captures a discrete approval action — submission, approval, rejection, return, or reassignment — recorded against a charge line, preserving the sequence, timing, performer, and routing path of that action. This supports auditability, workflow replay, and status reporting for public sector expenditure processing.

From a heuristic Data Vault modeling perspective, the FK structure mined from the object indicates a standalone classification. The table carries its own surrogate key (SEQUENCE_NUM) alongside foreign references to employee and approval path entities, so it is best treated as an event or history table rather than a hub or link. In practice, it behaves like an action-history satellite attached to the charge-line business key (IT_SERVICE_LINE_ID), with each row recording a point-in-time approval event.

Key Information Stored

  • IT_SERVICE_LINE_ID — Business key candidate identifying the charge line whose approval history is being recorded.
  • SEQUENCE_NUM — Ordinal indicator establishing the chronological order of actions on a given charge line; effectively the surrogate/sequence key.
  • ACTION_CODE — Code identifying the type of approval action performed (approve, reject, return, reassign, etc.).
  • ACTION_DATE — Timestamp when the action was executed.
  • EMPLOYEE_ID — FK to PSB_EMPLOYEES; the approver or actor who performed the action.
  • APPROVAL_PATH_ID — FK to OKE_APPROVAL_PATHS; the approval routing path governing the action.
  • NOTE — Free-text comment or justification entered by the approver.
  • REQUEST_ID — Concurrent request identifier associated with the transaction.
  • PROGRAM_ID / PROGRAM_APPLICATION_ID — Concurrent program and application identifiers for the process that created the record.
  • USE_WORKFLOW_FLAG — Indicates whether the action was routed through Oracle Workflow.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN capture standard EBS audit trail data.

Common Use Cases and Queries

Typical scenarios include approval audit reporting, cycle-time analysis of charge-line approvals, approver workload reports, and troubleshooting stalled or returned transactions. A representative query joining to employee information to derive approval history by charge line:

  • SELECT h.IT_SERVICE_LINE_ID, h.SEQUENCE_NUM, h.ACTION_CODE, h.ACTION_DATE, e.EMPLOYEE_NAME, h.NOTE FROM IGI.IGI_ITR_ACTION_HISTORY h, PSB_EMPLOYEES e WHERE h.EMPLOYEE_ID = e.EMPLOYEE_ID AND h.IT_SERVICE_LINE_ID = :line_id ORDER BY h.SEQUENCE_NUM;
  • Cycle-time analysis: compute MIN/MAX ACTION_DATE per IT_SERVICE_LINE_ID grouped by ACTION_CODE.
  • Workflow routing audit: filter on USE_WORKFLOW_FLAG = 'Y' combined with OKE_APPROVAL_PATHS joins.
  • Balancing reconciliation: reconcile REQUEST_ID against concurrent request logs for batch approvals.

Related Objects

  • PSB_EMPLOYEES — joined via EMPLOYEE_ID to resolve approver identity and reporting hierarchy.
  • OKE_APPROVAL_PATHS — joined via APPROVAL_PATH_ID to resolve approval routing configuration.
  • IGI_ITR_CHARGE_LINES (typical parent) — joined via IT_SERVICE_LINE_ID to link the audit trail to the charge-line record.
  • FND_CONCURRENT_REQUESTS — joined via REQUEST_ID for concurrent process context.
  • FND_USER — joined via CREATED_BY / LAST_UPDATED_BY for audit attribution.
  • FND_APPLICATION — joined via PROGRAM_APPLICATION_ID for concurrent program resolution.
  • WF_ITEM_ACTIVITY_STATUSES — used when workflow-driven approvals are involved, correlated by item key and action dates.