Search Results interface_line_attribute

Overview

The view IGS_FI_CONTROL belongs to the IGS — Student System product family within Oracle E-Business Suite. In the ETRM metadata for release 12.2.2 it is explicitly flagged as Obsolete, and the documented implementation note states "Not implemented in this database." This view is therefore best understood as a legacy financial-control construct that was designed for institutions running the Oracle Student System financial aid and receivables integration, rather than an object that is actively deployed in a standard Oracle EBS 12.1.1 or 12.2.2 installation.

Functionally, IGS_FI_CONTROL exposes a single configuration/control record per operating unit that governs how the Student System interacts with Oracle Receivables, Oracle Payables, and the General Ledger. It carries setup defaults such as the accounting method, the Receivables transaction type, payment terms, batch source, set of books, GL account combinations for receipts, cash, unapplied and revenue accounts, refund destinations, and the AR interface organization identifier. Because the view isolates the current operating unit's control row using the USERENV('CLIENT_INFO') mechanism, it behaves as an org-striped reporting view over the underlying control table.

Underlying Base Objects

The view text supplied by ETRM shows that IGS_FI_CONTROL is defined over the table IGS_FI_CONTROL_ALL. The _ALL suffix indicates that the base table stores rows for every operating unit (ORG_ID), while the view applies a WHERE clause to filter the row whose ORG_ID matches the current session's operating unit derived from USERENV('CLIENT_INFO'). The ETRM metadata does not document any referenced base objects, but the view text identifies IGS_FI_CONTROL_ALL as the direct source. The view definition also includes column expressions that are not physically in the table, such as NULL placeholders and the aliased columns that appear in the column list.

Key Columns

• ORG_ID — Operating unit identifier; the primary driver of the view's row filtering logic.
• AR_INT_ORG_ID — The Oracle Receivables interface organization identifier, used to map Student System financial transactions into the correct Receivables organization. This is the column referenced by the search term "ar_int_org_id".
• SET_OF_BOOKS_ID — The ledger (set of books) that receives the accounting entries generated by the integration.
• ACCOUNTING_METHOD — Determines the accounting convention applied to generated transactions.
• CUST_TRX_TYPE_ID, TERM_ID, BATCH_SOURCE_ID — Receivables setup defaults for transaction type, payment terms, and batch source.
• REC_GL_CCID, CASH_GL_CCID, UNAPP_GL_CCID — GL account combinations for receivables, cash, and unapplied amounts.
• REFUND_DR_GL_CCID, REFUND_CR_GL_CCID and the corresponding account code strings — Debit and credit accounts used for refund processing.
• AP_ORG_ID, DFLT_SUPPLIER_SITE_NAME, RFND_DESTINATION — Payables-side defaults for supplier and refund destination handling.
• NEXT_INVOICE_NUMBER, CURRENCY_CD, FEE_CALC_MTHD_CODE, PLANNED_CREDITS_IND, MANAGE_ACCOUNTS, ACCT_CONV_FLAG — Operational controls governing numbering, currency, fee calculation, and account management.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns inherited from the base table.

Common Use Cases and Queries

Although obsolete, this view would have been queried to inspect or validate the financial control configuration for a given operating unit, to troubleshoot AR interface mapping failures, and to confirm which GL accounts and Receivables defaults were in effect. A typical diagnostic query resembles:

• SELECT org_id, ar_int_org_id, set_of_books_id, cust_trx_type_id, term_id, batch_source_id FROM igs_fi_control;
• SELECT org_id, accounting_method, rec_gl_ccid, cash_gl_ccid, unapp_gl_ccid FROM igs_fi_control WHERE org_id = :p_org_id;
• SELECT org_id, ap_org_id, dflt_supplier_site_name, rfnd_destination FROM igs_fi_control;

Because the view filters on the session operating unit, any query must be executed in the context of the intended ORG_ID. Given the "not implemented" status, these queries are relevant primarily for legacy environments or migration analysis from earlier Student System releases into a supported EBS 12.1.1 or 12.2.2 footprint.