Results for “igi_stp_control”

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

Overview

IGI_STP_CONTROL is a table in the IGI schema, belonging to the Oracle E-Business Suite product IGI — Public Sector Financials International. Its documented purpose is to store Netting Transaction Batch information that has been submitted for processing. In the Oracle EBS 12.1.1 and 12.2.2 releases, the IGI module supports public-sector netting and settlement processes, where multiple outstanding inter-agency or inter-entity transactions are consolidated and offset against one another before a single net payment or receipt is generated. The IGI_STP_CONTROL table acts as the control record for these submitted batches, capturing the header-level control identity that links a netting batch to its control context.

From a heuristic Data Vault classification mined from the foreign-key structure, this object is assessed as satellite-leaning. This is a modeling suggestion rather than a documented attribute: the table carries a composite primary key and descriptive/audit attributes that hang off a parent batch entity (IGI_STP_BATCHES_ALL), which is characteristic of a satellite dependent on a hub or link. Analysts building a Data Vault or dimensional model should treat IGI_STP_CONTROL as descriptive context attached to the netting batch, not as an independent business hub.

Key Information Stored

The table contains nine documented columns. The most significant are summarized below.

• BATCH_ID — Part of the composite primary key (IGI_STP_CONTROL_PK) and a business-key candidate. Identifies the netting batch to which this control record belongs.
• CONTROL_ID — The second component of the composite primary key and business-key candidate. Distinguishes individual control records within a given batch.
• IGI_STP_CONTROL_BATCH_ID — The foreign-key column referencing IGI_STP_BATCHES_ALL, formally tying this control row to its parent batch definition. This is the documented referential link in the ETRM metadata.
• ORG_ID — The operating unit / organization identifier, enabling multi-org partitioning of the control records across business units.
• CREATED_BY — The user identifier responsible for creating the control record, used for audit and accountability.
• CREATION_DATE — The timestamp when the control record was created.
• LAST_UPDATED_BY — The user who most recently modified the record.
• LAST_UPDATE_DATE — The timestamp of the most recent modification.
• LAST_UPDATE_LOGIN — The login/session identifier associated with the last update, supporting detailed audit tracing.

The surrogate primary key is the composite IGI_STP_CONTROL_PK over (BATCH_ID, CONTROL_ID), which also serves as the documented unique index and business-key candidate. The audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) follow the standard EBS WHO-column convention.

Common Use Cases and Queries

Typical scenarios include reconciling submitted netting batches, auditing control-record creation and modification, and reporting on netting activity by operating unit. A frequent pattern joins the control table back to its batch parent:

SELECT c.batch_id, c.control_id, c.org_id, c.creation_date
FROM   igi.igi_stp_control c,
       igi.igi_stp_batches_all b
WHERE  c.igi_stp_control_batch_id = b.batch_id
AND    c.org_id = :p_org_id;

Audit-oriented queries filter on LAST_UPDATE_DATE to identify recently touched controls, while aggregation reporting groups by ORG_ID to summarize control counts per business unit. Because the primary key is composite, equality predicates on both BATCH_ID and CONTROL_ID yield the most efficient single-row lookups.

Related Objects

• IGI_STP_BATCHES_ALL — The primary parent table, referenced via IGI_STP_CONTROL.IGI_STP_CONTROL_BATCH_ID = IGI_STP_BATCHES_ALL.BATCH_ID. This is the documented foreign-key relationship and the most important join partner.
• IGI_STP_CONTROL_PK — The unique index underpinning the composite primary key (BATCH_ID, CONTROL_ID).
• IGI_STP_BATCHES_ALL (reverse perspective) — As the hub-like batch entity, it depends on IGI_STP_CONTROL for control-level detail records.
• Other IGI netting and settlement tables in the same module that consume batch and control identifiers during netting calculation and payment generation are logical dependents, though only the IGI_STP_BATCHES_ALL relationship is explicitly documented in the ETRM metadata.
• Standard EBS audit and multi-org views over ORG_ID may be used to restrict access to control records by operating unit.