Search Results fee_cal_inst_sequence_number




Overview
Explore in AI Chat

Overview

IGSBV_PERSON_DEPOSITS is a read-only reporting view belonging to the IGS (Student System) product family, specifically the Student Finance component. According to the documented ETRM metadata, the view "Stores all Student Deposits in Student Finance." It presents a denormalized, business-friendly projection of student deposit activity by joining credit header records with their corresponding credit activities, party records, and credit type definitions. The view is classified under the Obsolete product designation, and the ETRM metadata explicitly notes "Not implemented in this database," indicating that in many 12.1.1 and 12.2.2 environments the view is absent or has been superseded. Where it exists, its primary role is to support inquiry screens, deposit reconciliation reports, and downstream integrations requiring a single row per deposit with both credit and cash-application attributes.

Underlying Base Objects

The view text is defined over four base tables joined on their primary foreign keys:

  • IGS_FI_CREDITS_ALL (CR) — the credit header, holding deposit amounts, currency, dates, instrument details, and reversal information.
  • IGS_FI_CR_ACTIVITIES (CA) — the credit activity or cash-application lines, carrying the accounting code combinations and general ledger posting information.
  • HZ_PARTIES (PA) — the Trading Community Architecture party record supplying party number and name.
  • IGS_FI_CR_TYPES_ALL (CP) — the credit type definition, used here to restrict results to the 'OTHDEPOSIT' and 'ENRDEPOSIT' credit classes.

The join is established as CR.CREDIT_ID = CA.CREDIT_ID, CR.PARTY_ID = PA.PARTY_ID, and CR.CREDIT_TYPE_ID = CP.CREDIT_TYPE_ID. The view is defined WITH READ ONLY. The ETRM metadata records no referenced base objects, so the preceding mapping is derived entirely from the embedded view text.

Key Columns

Common Use Cases and Queries

The view supports deposit reconciliation, student account inquiry, and audit reporting. A typical query retrieving deposits with their debit accounting code is:

SELECT credit_number, credit_desc, amount, currency_cd, deposit_date, dr_account_cd, dr_gl_ccid, cr_account_cd FROM igsbv_person_deposits WHERE party_number = :party_number AND deposit_date BETWEEN :from_date AND :to_date;

To isolate unapplied deposits for follow-up:

SELECT credit_number, party_name, amount, unapplied_amount, deposit_date FROM igsbv_person_deposits WHERE unapplied_amount > 0 ORDER BY deposit_date;

Because the view is read-only and filtered to OTHDEPOSIT and ENRDEPOSIT credit classes, it cannot be used for data maintenance; update operations must target IGS_FI_CREDITS_ALL or IGS_FI_CR_ACTIVITIES directly. Given the obsolete designation and the "Not implemented" note, DBAs should verify existence before referencing the view and confirm whether a replacement object has been provided in the target 12.1.1 or 12.2.2 instance.