Search Results manage_accounts

Overview

APPS.IGS_FI_CONTROL is a financial control view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environment. The IGS prefix places it within the Student Systems / Financials integration area, where it serves as a single-row configuration repository that governs how financial transactions are processed, posted, and reconciled. The view exposes control-level parameters such as accounting methods, general ledger code combinations, refund destinations, invoice numbering, and supplier defaults that drive the behavior of the receivables and payables interfaces used by student financials.

In practice, the view functions as a reporting and integration surface rather than a transactional object. Application logic reads these control records to determine which GL accounts to debit or credit, how payment terms and invoice types are assigned, and whether credits, waivers, and account conversion processes are enabled. Because it presents this configuration in a denormalized, easy-to-query form, it is commonly used by developers and analysts building reports, validation queries, and diagnostic scripts.

Underlying Base Objects

The view is defined over the base table IGS_FI_CONTROL_ALL. The naming convention of the base table indicates that it holds a superset of data across operating units, with each row identified by ORG_ID. The view applies a security predicate based on USERENV('CLIENT_INFO'), the mechanism EBS uses to propagate the current operating unit context for multi-org (MOAC) security. Specifically, the predicate compares the ORG_ID column against the operating unit identifier embedded in the client information, defaulting to -99 when no value is available.

This design means the view returns only the row (or rows) relevant to the operating unit in the user's current session context. No additional base tables are documented as being referenced directly by the view definition; all columns are drawn from the single control table.

Key Columns

The view exposes columns that fall into several functional groups, and several are directly relevant to the "manage accounts" search that surfaced this object:

• MANAGE_ACCOUNTS — A control flag indicating whether account management functionality is enabled for the operating unit.
• REC_GL_CCID, CASH_GL_CCID, UNAPP_GL_CCID — Code combination identifiers for the receivables, cash, and unapplied cash accounts used in accounting entries.
• REC_ACCOUNT_CD, REV_ACCOUNT_CD, CASH_ACCOUNT_CD, UNAPP_ACCOUNT_CD — Textual account codes corresponding to the GL CCIDs above.
• REFUND_DR_GL_CCID, REFUND_CR_GL_CCID and their account code counterparts — Debit and credit accounts used when processing refunds.
• SET_OF_BOOKS_ID, ORG_ID, AR_INT_ORG_ID, AP_ORG_ID — Organizational and ledger identifiers establishing the accounting and inter-org context.
• ACCOUNTING_METHOD, ACCT_CONV_FLAG, CONV_PROCESS_RUN_IND — Parameters controlling accounting method selection and account conversion processing.
• NEXT_INVOICE_NUMBER, CUST_TRX_TYPE_ID, TERM_ID, BATCH_SOURCE_ID — Receivables defaults for invoice generation, transaction type, payment terms, and batch source.
• LAST_ACCOUNT_TRANS, LAST_PAY_TERM_TRANS, LAST_PAYMENT_TRANS — Timestamps indicating the last successful interface transaction of each type.
• CURRENCY_CD, RFND_DESTINATION, DFLT_SUPPLIER_SITE_NAME — Currency, refund routing, and supplier default configuration.

Common Use Cases and Queries

The view is most often queried to validate financial configuration for an operating unit before running interface or conversion programs. A typical query to inspect account management and GL defaults is:

• SELECT org_id, manage_accounts, rec_gl_ccid, cash_gl_ccid, unapp_gl_ccid, set_of_books_id FROM apps.igs_fi_control;

Analysts use it to confirm that refund accounts and accounting methods are correctly populated, and to audit the timestamps of the last account, payment term, and payment transactions for troubleshooting stalled interfaces. Because the view enforces operating unit security automatically, queries return only the applicable configuration row, making it suitable for embedded validation logic in concurrent programs and custom reports.