Search Results total_net_eft_amt

Overview

IGF_SL_CL_BATCH is a view owned by the APPS schema within the Oracle E-Business Suite environment, registered under FND Design Data as IGF.IGF_SL_CL_BATCH. It belongs to the Student Loan / grants-related functional area covered by the IGF application module and presents consolidated batch-level information for disbursement close-out processing. Each row represents a single close-out batch, identified primarily by the CBTH_ID and BATCH_ID columns, together with aggregated financial and count metrics describing the records contained in that batch. The view is defined as a multi-org view, meaning it automatically restricts the result set to records belonging to the current operating unit (ORG_ID) and ignores data belonging to other operating units. This behavior makes the view suitable for reporting and integration consumers that operate within a single operating unit context without needing to add their own ORG_ID predicate.

Underlying Base Objects

The ETRM 12.2.2 metadata for this object does not document any referenced base objects. The view is flagging STATUS: VALID in the APPS schema, which confirms that whatever underlying tables or synonyms it references are present and compilable in that environment. In practice, a multi-org view of this type is defined over one or more IGF transaction tables joined and filtered through the application's operating unit security logic, with the ORG_ID column bound to the current org context. Because the documentation excerpt does not enumerate base tables, integrators should treat the view itself as the supported interface rather than relying on assumptions about its underlying tables, since those may change without notice while the view contract remains stable.

Key Columns

• CBTH_ID (NUMBER 15) — The close-out batch header identifier. This is the primary key of the batch and the column users most commonly search on.
• BATCH_ID (VARCHAR2 40) — The external or user-facing batch identifier string.
• FILE_CREATION_DATE / FILE_TRANS_DATE — Dates when the batch file was created and when the transaction data applies.
• FILE_IDENT_CODE, RECIPIENT_ID, SOURCE_ID and the related NON_ED_BRC_ID columns — File and party identifiers used in the exchange of batch data with external recipients and sources.
• SEND_RESP — Response indicator for the transmitted batch.
• ORG_ID — Operating unit identifier; the view is filtered on this column.
• RECORD_COUNT_NUM — Total number of disbursement records in the batch.
• TOTAL_NET_DISB_AMT, TOTAL_NET_EFT_AMT, TOTAL_NET_NON_EFT_AMT — Aggregated net disbursement totals, split by electronic funds transfer and non-EFT amounts.
• TOTAL_REISSUE_AMT, TOTAL_CANCEL_AMT, TOTAL_NET_CANCEL_AMT, TOTAL_NET_OUT_CANCEL_AMT, TOTAL_DEFICIT_AMT — Reissue, cancellation, netted cancellation, netted outstanding cancellation and deficit totals for the batch.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and request/program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) supporting concurrency and audit tracking.

Common Use Cases and Queries

Typical consumers use this view to reconcile disbursement batches by operating unit, to verify aggregated totals per batch before transmission, and to feed downstream reporting. The sample below retrieves batch totals for the current operating unit:

SELECT CBTH_ID, BATCH_ID, FILE_CREATION_DATE, RECORD_COUNT_NUM, TOTAL_NET_DISB_AMT, TOTAL_NET_EFT_AMT, TOTAL_NET_NON_EFT_AMT, TOTAL_CANCEL_AMT FROM APPS.IGF_SL_CL_BATCH WHERE CBTH_ID = :p_cbth_id;

For date-range reconciliation, filter on FILE_CREATION_DATE and aggregate by BATCH_ID; for audit purposes, join REQUEST_ID back to the concurrent program request tables. Because ORG_ID filtering is applied automatically, no explicit operating unit predicate is required, and results always reflect the session's current operating unit context.