Search Results netting_trx_type




Overview
Explore in AI Chat

Overview

The view APPS.IGI_STP_BATCHES_V is a reporting object in the Oracle E-Business Suite product IGI – Public Sector Financials International. Its documented purpose is to display netting batch information, presenting a denormalized and human-readable projection of settlement processing batch data held in the underlying netting tables. The view resolves stored lookup codes into their descriptive meanings, so that consumers see the translated NETTING_TRX_TYPE and BATCH_MEANING values rather than raw identifiers. Because the view is owned by the APPS schema and remains VALID in both the 12.1.1 and 12.2.2 releases, it is a stable interface used by concurrent programs, Oracle Reports/BI Publisher layouts, and custom SQL extracts. It is read-only and does not support DML, which makes it appropriate for inquiry and integration scenarios where batch status and transaction type reporting is required without touching base tables directly.

Underlying Base Objects

The documented ETRM metadata states that the view is defined over two referenced base objects: IGI_LOOKUPS (a VIEW) and IGI_STP_BATCHES_ALL (registered as a SYNONYM). The published view text describes the join structure in detail. The netting batch header, aliased STPB, supplies the batch identifier, batch status, and the netting transaction type identifier. Two aliased instances of IGI_LOOKUPS are joined to translate the codes: alias NTYPE joins on LOOKUP_CODE = NETTING_TRX_TYPE_ID with LOOKUP_TYPE = 'STP_NETTING_TYPE', and alias BTYPE joins on LOOKUP_CODE = STPB.BATCH_STATUS with LOOKUP_TYPE = 'STP BATCH STATUS'. In practice the "_ALL" synonym resolves to the multi-org base table IGI_STP_BATCHES, so the view is a lookup-enriched presentation of the netting batch header with no aggregation applied.

Key Columns

  • ROW_ID – The ROWID of the underlying batch record, retained for row-level identification and debugging.
  • BATCH_ID – The unique identifier of the netting/settlement batch; the primary key used to link to batch line and payment detail tables.
  • BATCH_STATUS – The stored status code of the batch, as held on the base record.
  • NETTING_TRX_TYPE – The descriptive meaning of the netting transaction type, translated from the STP_NETTING_TYPE lookup set. This is the column most commonly searched, and it is the anchor for the "netting_trx_type" query pattern.
  • BATCH_MEANING – The descriptive meaning of the batch status, translated from the STP BATCH STATUS lookup set, providing a readable status label alongside the raw code.

Common Use Cases and Queries

Typical usage includes batch status monitoring dashboards, reconciliation extracts, and ad hoc investigation of netting activity by transaction type. A straightforward listing by netting transaction type is shown below:

SELECT batch_id,
       batch_status,
       netting_trx_type,
       batch_meaning
FROM   apps.igi_stp_batches_v
WHERE  netting_trx_type = :p_netting_trx_type
ORDER  BY batch_id;

To examine batch progress by descriptive status:

SELECT batch_status,
       batch_meaning,
       COUNT(*) batch_count
FROM   apps.igi_stp_batches_v
GROUP  BY batch_status, batch_meaning;

Because the view supplies only header-level attributes, integration queries should join BATCH_ID to the corresponding batch line and settlement detail objects to obtain amounts and counterparty information. The view is best treated as the lookup-resolved entry point for netting batch inquiries.