Search Results igf_sl_cl_batch

Overview

IGF_SL_CL_BATCH is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered under the IGF (Financial Aid) product family. In the Oracle EBS 12.1.1 and 12.2.2 releases it belongs to the student loan CommonLine processing subsystem, which manages the outbound and inbound data exchange between the institution and loan guarantors, servicers, and the Department of Education. The view exposes batch-level header information for CommonLine file transmissions, allowing concurrent programs, reports, and integration extracts to read batch control totals and routing identifiers without querying the base table directly.

Because it applies the standard multi-org security predicate, the view acts as an operating-unit-filtered presentation layer. Only batches whose ORG_ID matches the operating unit in the user's session context (derived from USERENV('CLIENT_INFO')) are visible, with a default of -99 permitting access when no operating unit context is set. This makes the view suitable for responsibility-scoped reporting.

Underlying Base Objects

The view is defined entirely over a single base table, IGF_SL_CL_BATCH_ALL. The projection selects every functional column from IGF_SL_CL_BATCH_ALL, aliased CLBTCH, and adds a ROW_ID column derived from CLBTCH.ROWID for row-level identification. No joins, aggregations, or lookups against other tables are present, so the view is a straightforward secured projection of the _ALL table.

The naming convention follows the Oracle multi-org pattern: IGF_SL_CL_BATCH_ALL holds the partitioned, operating-unit-aware data, while the IGF_SL_CL_BATCH view provides the org-secured subset. The WHERE clause compares NVL(CLBTCH.ORG_ID, -99) against the operating unit value decoded from the client information string, using TO_NUMBER and NVL to tolerate blank or null session values.

Key Columns

• ROW_ID – Rowid of the underlying batch record; used for row-level access and updates.
• CBTH_ID – Primary identifier of the CommonLine batch header record.
• BATCH_ID – Business-facing batch identifier used to correlate files and responses.
• FILE_CREATION_DATE / FILE_TRANS_DATE – When the transmission file was created and transmitted.
• FILE_IDENT_CODE – CommonLine file identifier code assigned to the transmission.
• RECIPIENT_ID / RECIP_NON_ED_BRC_ID – Recipient (typically the guarantor or servicer) and its non-ED branch code.
• SOURCE_ID / SOURCE_NON_ED_BRC_ID – Originating source and its non-ED branch code.
• SEND_RESP – Flag indicating whether a response is expected or should be sent.
• ORG_ID – Operating unit that governs row visibility through the view's security predicate.
• RECORD_COUNT_NUM – Number of detail records included in the batch.
• TOTAL_NET_DISB_AMT, TOTAL_NET_EFT_AMT, TOTAL_NET_NON_EFT_AMT – Aggregate disbursement amounts, split by EFT and non-EFT settlement.
• TOTAL_REISSUE_AMT, TOTAL_CANCEL_AMT, TOTAL_DEFICIT_AMT – Reissue, cancellation, and deficit control totals.
• TOTAL_NET_CANCEL_AMT, TOTAL_NET_OUT_CANCEL_AMT – Net cancellation and net outstanding cancellation totals.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE – Concurrent request and program audit trail.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns.

Common Use Cases and Queries

The view is typically queried to reconcile file-level control totals, verify which batches transmitted during a period, or drive downstream extracts for guarantor reporting. A representative reconciliation query groups batch totals by transmission date:

• SELECT batch_id, file_ident_code, record_count_num, total_net_disb_amt, total_net_eft_amt FROM igf_sl_cl_batch WHERE file_trans_date BETWEEN :p_start AND :p_end ORDER BY file_trans_date;
• SELECT batch_id, send_resp, total_cancel_amt, total_reissue_amt FROM igf_sl_cl_batch WHERE recipient_id = :p_recipient AND org_id = :p_org;
• SELECT cbth_id, row_id, total_net_disb_amt FROM igf_sl_cl_batch WHERE batch_id = :p_batch_id;

In all cases the operating unit session context must be initialized before querying, since the view's predicate filters rows automatically. Because the view exposes no indexed derived columns, performance depends on indexes defined on IGF_SL_CL_BATCH_ALL, typically on CBTH_ID and BATCH_ID.