Search Results igs_fi_crd_int

Overview

IGS_FI_CRD_INT is an Oracle E-Business Suite view owned by the APPS schema and registered in the IGS — Student System product family. It presents credit instrument records — a category that encompasses credit card transactions, miscellaneous credits, and externally sourced payment credits — in a denormalized column layout suitable for reporting and downstream integration. The view is documented as VALID, meaning the compiled definition exists in the data dictionary, but the ETRM description explicitly states "No longer used," indicating that Oracle has retired the view from active functional use in the Student System credit/payment flow.

Historically, views in the IGS_FI_* namespace (IGS Financials) served as the integration and inquiry layer between the Student System financials and General Ledger, Receivables, and third-party payment gateways. IGS_FI_CRD_INT provided a convenient projection over the credit interface staging table so that reporting tools, concurrent programs, and external interfaces could retrieve credit records without writing directly against the base table. It remains available in EBS 12.1.1 and 12.2.2 for backward compatibility and for customers who have not yet refactored legacy customizations that reference it.

Underlying Base Objects

The view is defined entirely over a single base object: IGS_FI_CRD_INT_ALL. No other tables, synonyms, or views are referenced in the documented view text, consistent with the ETRM metadata note that no base objects are separately documented.

The defining query is a SELECT that exposes ROWID plus the full column list of IGS_FI_CRD_INT_ALL, and applies a multi-org security predicate:

• WHERE (NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTRB(USERENV('CLIENT_INFO'),1,10))), -99)) = (same expression))

This is the classic Multi-Org org_id filter pattern used by _ALL/_V views, restricting returned rows to the operating unit currently set in the session's client information. The view therefore functions as the operating-unit-scoped (org-specific) presentation of the _ALL table.

Key Columns

The column list reflects the credit interface structure:

• CREDIT_INT_ID — primary key of the credit interface record.
• CREDIT_NUMBER / CREDIT_SOURCE — the credit's reference number and the origin of the credit (the column most relevant to the "credit_source" search).
• PARTY_ID, CREDIT_TYPE_ID, CREDIT_INSTRUMENT — student/party identifier, credit classification, and instrument type.
• AMOUNT, CURRENCY_CD, EXCHANGE_RATE — monetary value and currency conversion data.
• TRANSACTION_DATE, EFFECTIVE_DATE, GL_DATE — transaction, effective, and accounting dates.
• ORG_ID, RECEIPT_LOCKBOX_NUMBER, SOURCE_TRANSACTION_ID, SUBACCOUNT_ID, STATUS — operating unit, lockbox, source reference, subaccount, and processing status.
• MERCHANT_ID and the CREDIT_CARD_* columns (code, holder name, number, expiration, approval code) — payment card capture details.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the standard DFF (descriptive flexfield) columns.
• WHO columns (LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY) and REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — audit and concurrent request tracking.

Common Use Cases and Queries

Typical use is read-only reporting and reconciliation of staged credits for a given operating unit. Because of the multi-org predicate, queries must run in a session where CLIENT_INFO is populated (for example, through FND_GLOBAL.APPS_INITIALIZE or a standard Forms responsibility).

Example — retrieve credits by source and currency:

SELECT credit_int_id, credit_number, credit_source,
       party_id, amount, currency_cd, transaction_date, status
FROM   apps.igs_fi_crd_int
WHERE  credit_source = :p_source
AND    currency_cd   = 'USD'
ORDER BY transaction_date DESC;

Example — summarize by credit source:

SELECT credit_source, currency_cd, COUNT(*) cnt, SUM(amount) total_amount
FROM   apps.igs_fi_crd_int
GROUP BY credit_source, currency_cd;

Example — join to the operating unit for readable output:

SELECT c.credit_number, c.credit_source, c.amount, o.name operating_unit
FROM   apps.igs_fi_crd_int c, hr_operating_units o
WHERE  c.org_id = o.organization_id;

Given the "No longer used" status, new development should not depend on this view. Existing customizations that reference it should be reviewed, since the view and its base table may be removed in a future release; the supported replacement is to use the current Student System financials or Receivables credit/payment APIs and interface tables instead.