Search Results borr_auth_code

Overview

IGF_SL_PLUS_BORW_V is a supplementary database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Financial Aid module and is catalogued within the IGS (Intelligent Grants System) product family under FND Design Data identifier IGF.IGF_SL_PLUS_BORW_V. The object is registered with a status of VALID in the EBS data dictionary.

Oracle classifies this object as a "supplementary view used to simplify forms coding." Its purpose is not to expose a general-purpose reporting interface but to flatten data required by an Oracle Forms-based user interface so that block-level queries can retrieve a person's licensing, residency, and borrower-authorization attributes in a single fetch. Because the view exists primarily for form-level data retrieval, Oracle explicitly warns that it is not recommended for direct query or data manipulation, and its definition may change significantly in subsequent minor or major releases. The classification as a supplementary view means it is generally not referenced by other database objects, making it a terminal consumer of its underlying base table rather than a building block for further schema constructs.

Underlying Base Objects

The view is defined over a single base object: the table APPS.IGF_SL_PLUS_BORW. No other tables, synonyms, or packaged functions are documented as participating in its definition. The dependency list is one-directional: IGF_SL_PLUS_BORW_V references IGF_SL_PLUS_BORW, and the view is not referenced by any other database object in the EBS schema.

Because the view is a simple projection over the base table rather than a join of multiple entities, the column list maps essentially one-to-one with the columns of IGF_SL_PLUS_BORW. This parity means the view does not enrich or aggregate the source data; it re-labels and exposes it in a form suited to a specific Forms block, including the addition of the ROW_ID pseudocolumn to support row identification within the form's data block.

Key Columns

The view exposes fourteen columns. The most consequential are listed below, including BORR_AUTH_CODE, which is the column referenced in the user's search.

• ROW_ID (ROWID) — A pseudocolumn identifying the physical row, used by Oracle Forms for block navigation and DML targeting.
• PERSON_ID (NUMBER, 15) — The primary identifier of the person or borrower record, linking to HZ_PARTIES and related person tables.
• LICENSE_NUM (VARCHAR2, 60) — Professional or institutional license number on file.
• LICENSE_STATE (VARCHAR2, 30) — The state or jurisdiction issuing the license.
• CITIZENSHIP_STATUS (VARCHAR2, 30) — Citizenship classification relevant to financial aid eligibility.
• ALIEN_REG_NUM (VARCHAR2, 30) — Alien registration number for non-citizen records.
• STATE_OF_LEGAL_RES (VARCHAR2, 30) — State of legal residence used for residency determinations.
• LEGAL_RES_DATE (DATE) — Effective date of the legal residence designation.
• BORR_AUTH_CODE (VARCHAR2, 30) — The borrower authorization code. This attribute records the borrower's authorization designation used in loan origination processing, reflecting the consent or authorization status associated with the borrower record.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard EBS who-did-what auditing.

Common Use Cases and Queries

Typical usage is limited to form support and ad hoc diagnostics. A conventional query to retrieve borrower attributes for a given person follows the documented query text:

SELECT ROW_ID, PERSON_ID, LICENSE_NUM, LICENSE_STATE, CITIZENSHIP_STATUS, ALIEN_REG_NUM, STATE_OF_LEGAL_RES, LEGAL_RES_DATE, BORR_AUTH_CODE FROM APPS.IGF_SL_PLUS_BORW_V WHERE PERSON_ID = :person_id;

To isolate records by borrower authorization, the query can be filtered on BORR_AUTH_CODE:

SELECT PERSON_ID, BORR_AUTH_CODE, LICENSE_STATE, STATE_OF_LEGAL_RES FROM APPS.IGF_SL_PLUS_BORW_V WHERE BORR_AUTH_CODE = :auth_code;

Because Oracle explicitly discourages direct querying of the view, integration and reporting developers should prefer the base table APPS.IGF_SL_PLUS_BORW or the official public APIs where a supported interface exists. The view remains useful for understanding what the corresponding Oracle Forms block retrieves and for troubleshooting UI behavior, but it should not be treated as a stable interface contract across releases.