Results for “perform_action_ind”

9 results




Overview
Explore in AI Chat

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

Overview

The IGS_EN_MRG_ID_ACT_CH table belongs to the IGS (Student System) product family within Oracle E-Business Suite. In ETRM 12.1.1 and 12.2.2 this module is documented as obsolete, meaning the table is retained for historical and upgrade-compatibility purposes rather than active transactional processing. Functionally, it defines the permissible actions that may be applied to an individual row during the merge identification process. Each record pairs a specific source row (referenced through SMIR_ID) with a table alias and an action identifier, thereby describing which operation — for example acceptance, rejection, or deferral — the merge engine is entitled to perform against that row.

The ETRM metadata offers a heuristic Data Vault classification of link. Read as a modeling suggestion, this reflects the table's structure: it is essentially a many-to-many association between merge-id rows and merge-id actions, carrying its own descriptive attributes. It is not a hub (no single natural business key) and not a pure satellite (it holds no single parent's descriptive payload). The documented physical schema reports nine columns under owner IGS.

Key Information Stored

The primary key IGS_EN_MRG_ID_ACT_CH_PK is composite, comprising SMIR_ID, TABLE_ALIAS, and ACTION_ID. A unique index, IGS_EN_MRG_ID_ACT_CH_U1, is defined over the same three columns and therefore serves as the business-key candidate; uniqueness is enforced at the intersection of a merge-id row, a table alias, and an action.

  • SMIR_ID — foreign key to IGS_EN_MERGE_ID_ROWS; identifies the merge-id staging row to which the action applies.
  • TABLE_ALIAS — foreign key to IGS_EN_MRG_ID_ACTION; names the logical table or entity context for the permitted action.
  • ACTION_ID — foreign key to IGS_EN_MRG_ID_ACTION; identifies the specific action permitted.
  • PERFORM_ACTION_IND — indicator controlling whether the action is actually performed for the row.
  • CREATED_BY, CREATION_DATE — standard audit columns recording row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording the most recent modification and the login that made it.

Together, SMIR_ID, TABLE_ALIAS, and ACTION_ID form the join nexus; the audit columns support change tracking and are populated automatically by the EBS framework.

Common Use Cases and Queries

Typical scenarios involve diagnosing why a particular merge-id row was or was not processed. Because the table is obsolete, queries are generally investigative or migration-oriented rather than part of live processing.

Listing all actions permitted for a given merge row:

  • SELECT SMIR_ID, TABLE_ALIAS, ACTION_ID, PERFORM_ACTION_IND FROM IGS_EN_MRG_ID_ACT_CH WHERE SMIR_ID = :smir_id;

Resolving the human-readable action description through the action table:

  • SELECT c.SMIR_ID, c.TABLE_ALIAS, a.ACTION_NAME, c.PERFORM_ACTION_IND FROM IGS_EN_MRG_ID_ACT_CH c, IGS_EN_MRG_ID_ACTION a WHERE c.ACTION_ID = a.ACTION_ID AND c.TABLE_ALIAS = a.TABLE_ALIAS;

Reporting counts by action to gauge merge behaviour across a population of merge rows is also common, as is auditing rows where PERFORM_ACTION_IND is null or set contrary to expectation. The composite unique index supports efficient lookup by the full business key.

Related Objects

The most significant related objects are the two tables referenced by the documented foreign keys, plus the parent structures of the merge-id process.

  • IGS_EN_MERGE_ID_ROWS — parent of SMIR_ID; supplies the merge-id row against which the action is recorded.
  • IGS_EN_MRG_ID_ACTION — referenced by both TABLE_ALIAS and ACTION_ID; defines valid actions and their aliases.
  • IGS_EN_MRG_ID_ACT_CH_PK / _U1 — the primary key and unique index enforcing the composite business key.
  • IGS_EN_MERGE_ID and related merge-id header tables — contextual parents of the row set.
  • IGS_EN_MRG_ID_* process tables — sibling structures participating in the merge-id workflow.