Search Results credit_desc

Overview

IGS_FI_PP_INS_APPLS_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data as IGS.IGS_FI_PP_INS_APPLS_V. It exposes installment application records within the Oracle Student System (IGS) financials module, correlating credits applied against student installment obligations. The view is classified as a supplementary view intended to simplify forms coding — Oracle explicitly warns that it is not a supported query or data-manipulation interface, and that its definition may change substantially between minor or major releases. Consequently, it should be treated as a read-only convenience layer rather than a stable integration contract. In EBS 12.1.1 and 12.2.2 the object remains valid, and its primary value lies in surfacing denormalized credit descriptive data (notably CREDIT_DESC) alongside installment application amounts, which is otherwise dispersed across the underlying IGS financial tables.

Underlying Base Objects

The ETRM metadata for 12.2.2 does not document the specific base tables referenced by this view; the dependency section is limited to stating that IGS_FI_PP_INS_APPLS_V references subordinate objects without enumerating them. Based on the column profile and IGS naming conventions, the view is constructed over installment application and credit activity entities within the IGS financials schema — typically joining an installment application table to a credit or credit-activity table to resolve credit identifiers, credit numbers, and credit descriptions. Because the base objects are not exposed, customers and integrators should not assume a fixed join graph. Any direct dependency on internal IGS tables carries the same release-volatility caveat that Oracle applies to the view itself.

Key Columns

The view returns twenty columns. The principal functional columns are:

• ROW_ID (ROWID) — row identifier for the underlying record.
• INSTALLMENT_APPLICATION_ID (NUMBER) — unique identifier of the installment application event.
• APPLICATION_TYPE_CODE (VARCHAR2, 30) — source classification of the application.
• INSTALLMENT_ID (NUMBER) — the installment against which the application was made.
• CREDIT_ID and CREDIT_ACTIVITY_ID (NUMBER, 15) — credit and credit-activity identifiers.
• CREDIT_NUMBER (VARCHAR2, 60) — the credit's reference number.
• CREDIT_DESC (VARCHAR2, 240) — the description of the credit record. This is the column most frequently targeted by users searching for credit_desc, as it provides a human-readable credit label suitable for reporting and reconciliation.
• APPLIED_AMT (NUMBER) — the amount of credit applied.
• TRANSACTION_DATE (DATE) — date of the application transaction.
• LINK_APPLICATION_ID (NUMBER) — linkage to a related application record.

The remaining columns are standard WHO audit fields (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program WHO columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

Typical usage centers on financial reconciliation and reporting: identifying which credits were applied to which installments, tracing applied amounts by transaction date, and surfacing credit descriptions for user-facing extracts. A representative query filters on the credit description and date range:

• SELECT installment_application_id, installment_id, credit_number, credit_desc, applied_amt, transaction_date FROM apps.igs_fi_pp_ins_appls_v WHERE credit_desc LIKE '%<search>%' AND transaction_date BETWEEN :start_date AND :end_date ORDER BY transaction_date;
• Aggregation by credit: SELECT credit_id, credit_number, credit_desc, SUM(applied_amt) FROM apps.igs_fi_pp_ins_appls_v GROUP BY credit_id, credit_number, credit_desc;
• Audit trace by program: SELECT * FROM apps.igs_fi_pp_ins_appls_v WHERE request_id = :request_id;

Because Oracle discourages direct querying of supplementary views, production integrations should favor supported APIs or documented base tables, using this view only for diagnostic and reporting purposes where its volatility is acceptable.