Search Results batch_meaning

Overview

APPS.IGI_STP_BATCHES_V is a reporting view in the Oracle E-Business Suite (EBS) Treasury module, part of the Oracle Financials for Government/Public Sector settlement and netting functionality introduced through the IGI (International Government Information) schema. The view exposes settlement batch records from the underlying transaction table IGI_STP_BATCHES_ALL, enriching each row with decoded lookup meanings so that status codes and transaction types are presented in a human-readable form. It is a read-only presentation layer intended for inquiry screens, concurrent reports, and integration extracts rather than for transactional DML.

The view is particularly relevant when a user searches for batch_meaning, since one of its projected columns, BATCH_MEANING, provides the descriptive translation of the batch status code held on the base table. This makes the view the natural source for reports that must display batch status in business language rather than as an internal lookup code.

Underlying Base Objects

The view is defined over two documented base objects:

• IGI_STP_BATCHES_ALL (SYNONYM) – the settlement batch header table, aliased STPB. It supplies ORG_ID, ROWID, BATCH_ID, BATCH_STATUS, and the netting transaction type identifier.
• IGI_LOOKUPS (VIEW) – the lookup translation view, joined twice: once as NTYPE for netting transaction types and once as BTYPE for batch statuses.

The join predicates bind the lookup codes to the batch attributes: NTYPE is restricted to LOOKUP_TYPE = 'STP_NETTING_TYPE' and BTYPE to LOOKUP_TYPE = 'STP BATCH STATUS'. Because IGI_LOOKUPS is itself a view over the FND lookup infrastructure, the effective lineage extends to the standard Oracle lookup tables. All joins are inner joins, so a batch row is returned only when valid lookup entries exist for both its netting type and its status.

Key Columns

• ORG_ID – the operating unit identifier, enabling multi-org security and filtering in reports.
• ROW_ID – the ROWID of the underlying IGI_STP_BATCHES_ALL row, useful for row-level navigation or drill-down to the base record.
• BATCH_ID – the unique settlement batch identifier.
• BATCH_STATUS – the raw status lookup code for the batch.
• NETTING_TRX_TYPE – the decoded MEANING of the netting transaction type, sourced from lookup type STP_NETTING_TYPE.
• BATCH_MEANING – the decoded MEANING of the batch status, sourced from lookup type STP BATCH STATUS. This is the column most commonly referenced in status-oriented reporting queries.

Common Use Cases and Queries

Typical usage includes batch status monitoring, netting reconciliation, and operational dashboards that must show descriptive status text. A representative query filtering on a specific batch follows:

• SELECT batch_id, batch_status, batch_meaning, netting_trx_type FROM apps.igi_stp_batches_v WHERE org_id = :p_org_id;
• SELECT batch_meaning, COUNT(*) FROM apps.igi_stp_batches_v GROUP BY batch_meaning ORDER BY 1; — aggregates batch volumes by decoded status.
• SELECT b.batch_id, b.batch_meaning FROM apps.igi_stp_batches_v b WHERE b.org_id = :p_org_id AND b.netting_trx_type = :p_type; — restricts to a given netting transaction type for reconciliation extracts.

Because the view relies on inner joins to IGI_LOOKUPS, maintenance of the STP BATCH STATUS and STP_NETTING_TYPE lookup values directly affects row visibility; if a lookup entry is missing or disabled, the corresponding batch will not appear in the view even though it exists in the base table.