Search Results fund_code_txt

Overview

The IGF_SE_AUTHORIZATION_V view is a public database object owned by the APPS schema within the IGF (Financial Aid) product family of Oracle E-Business Suite. It is documented with a status of VALID and is defined as a "public view to derive active work authorizations." In the context of Oracle EBS 12.1.1 and 12.2.2, this view serves as a reporting and integration surface that consolidates student financial-aid work-authorization records into a single queryable structure, allowing external reports, concurrent programs, and interfaces to retrieve authorization data without directly joining the underlying transactional tables. Because the view already resolves lookup descriptions and computed date values, it is well suited to operational reporting, data extracts, and third-party integration where a stable, denormalized representation of authorizations is required.

Underlying Base Objects

The view is defined over the following base objects, joined within a single SELECT statement:

• IGF_SE_AUTH (aliased SE) — the primary authorization table, filtered so that only rows with SE.FLAG = 'A' (active authorizations) are returned.
• IGF_AW_FUND_MAST_ALL (aliased FM) — the fund master, joined on FM.FUND_ID = SE.FUND_ID to resolve fund details.
• IGF_AW_FUND_CAT (aliased FC) — the fund category table, joined on FM.FUND_CODE = FC.FUND_CODE to supply fund source and fund type attributes.
• IGF_LOOKUPS_VIEW (aliased LK1) — resolves the fund source lookup, constrained by LOOKUP_TYPE = 'IGF_AW_FUND_SOURCE'.
• IGF_LOOKUPS_VIEW (aliased LK2) — resolves the system fund type lookup, constrained by LOOKUP_TYPE = 'IGF_AW_SYS_FUND_TYPE'.

Two stored functions, IGF_SL_LAR_CREATION.GET_LOAN_START_DT and IGF_SL_LAR_CREATION.GET_LOAN_END_DT, are invoked against SE.AWARD_ID to derive the authorization start and end dates. The documented ETRM metadata lists no additional referenced base objects beyond these.

Key Columns

• AUTHORIZATION_ID — derived from SE.AUTH_ID; the unique identifier for the authorization.
• PERSON_ID — the person identifier linking the authorization to the individual.
• AUTHORIZED_AMT — the accepted authorization amount (SE.ACCEPTED_AMNT).
• AUTHORIZATION_DATE — the date the authorization was recorded.
• PERSON_FIRST_NAME_TXT / PERSON_LAST_NAME_TXT — the individual's first and last names.
• BIRTH_DATE — the person's date of birth.
• SOCIAL_SECURITY_NUMBER — the individual's SSN, sourced from SE.SSN_NO. This is the column most relevant to the search term "social_security_number" and is a sensitive personal identifier subject to data-privacy controls.
• FUND_ID, FUND_CODE_TXT, FUND_TYPE_TXT — fund identification and classification attributes.
• SYS_FUND_SOURCE_CODE / SYS_FUND_SOURCE_NAME — the fund source lookup code and its descriptive meaning.
• SYS_FUND_TYPE_CODE / SYS_FUND_TYPE_NAME — the system fund type lookup code and meaning.
• AW_CAL_TYPE_TXT / AW_SEQUENCE_NUMBER — the academic award calendar type and sequence.
• AUTHORIZATION_START_DATE / AUTHORIZATION_END_DATE — computed loan dates returned by the IGF_SL_LAR_CREATION functions.

Common Use Cases and Queries

Typical scenarios include auditing active authorizations, extracting award data for financial-aid reporting, and reconciling fund sources. Because the view exposes SSN data, queries should be restricted and handled under applicable privacy policy.

• Listing active authorizations by person: SELECT AUTHORIZATION_ID, PERSON_ID, AUTHORIZED_AMT FROM APPS.IGF_SE_AUTHORIZATION_V WHERE PERSON_ID = :person_id;
• Retrieving a person's SSN as required: SELECT PERSON_ID, SOCIAL_SECURITY_NUMBER FROM APPS.IGF_SE_AUTHORIZATION_V WHERE AUTHORIZATION_ID = :auth_id;
• Summarizing authorization amounts by fund source: SELECT SYS_FUND_SOURCE_CODE, SUM(AUTHORIZED_AMT) FROM APPS.IGF_SE_AUTHORIZATION_V GROUP BY SYS_FUND_SOURCE_CODE;
• Filtering by authorization period: SELECT AUTHORIZATION_ID, AUTHORIZATION_START_DATE, AUTHORIZATION_END_DATE FROM APPS.IGF_SE_AUTHORIZATION_V WHERE AUTHORIZATION_DATE BETWEEN :from_dt AND :to_dt;

These patterns illustrate the view's role as a consolidated reporting source that abstracts the multi-table joins and function calls required to present authorization data in a consumable form.