Results for “class_standing_desc”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IGF_AW_CAREER_MAP_V view is a reporting and integration object belonging to the IGF – Financial Aid product family within Oracle E-Business Suite. As the ETRM metadata indicates, this object is classified as Obsolete. The view presents the mapping that exists between a student's Program Type and the corresponding Class Standing used in financial aid processing. In practical terms, it exposes the rules that translate an academic program classification into the class-standing value leveraged by need-analysis and award-calculation logic, particularly where FISAP (Fiscal Operations Report and Application to Participate) reporting conventions apply.

The object is best understood as a read-only projection that joins or decorates underlying career-map records with a descriptive lookup value. Its role in EBS reporting and integration is to provide a single, denormalized result set in which the raw class-standing code is accompanied by its human-readable description, eliminating the need for downstream reports and interfaces to invoke the lookup routine themselves. The view was originally catalogued against release 12.1.1 and remains documented in the 12.2.2 ETRM repository, even though it is no longer actively implemented.

Underlying Base Objects

The documented view text identifies a single underlying base object: the table IGF_AW_CAREER_MAP, aliased as A in the SELECT statement. There are no additional joined tables documented; the descriptive class-standing value is not sourced from a joined table but is instead generated by an inline call to the database function IGF_AW_GEN.LOOKUP_DESC. That function is passed the lookup type IGF_AW_FISAP_CLASS_STG together with the CLASS_STANDING column value, and it returns the associated description.

The ETRM metadata states that the view is not implemented in this database and that no base objects are separately documented in the referenced-objects list. This is consistent with its obsolete status: the definition persists as reference documentation, but the physical object is absent from the current schema. Where the view did exist, it was a thin wrapper over IGF_AW_CAREER_MAP with no aggregation, no filtering, and no set operations, so its row cardinality matched the base table exactly.

Key Columns

• ROW_ID – The unique primary-key identifier of the career-map record.
• CAREER_LEVEL_ID – Foreign-key reference to the career level associated with the mapping, tying the record to a specific academic career grouping.
• PROGRAM_TYPE – The program-type code that the mapping resolves; this is the principal column referenced when searching on the program_type term.
• CLASS_STANDING – The stored class-standing code corresponding to the program type.
• CLASS_STANDING_DESC – The derived, descriptive value returned by IGF_AW_GEN.LOOKUP_DESC for lookup type IGF_AW_FISAP_CLASS_STG; not a stored column but computed per row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard Oracle EBS audit columns inherited from the base table.

Common Use Cases and Queries

The primary use case is reporting on the relationship between program type and class standing for financial aid configuration review. Because the view surfaces the descriptive value alongside the code, it suits validation reports that must confirm each program type maps to a recognized FISAP class-standing description. A representative query follows:

• SELECT program_type, class_standing, class_standing_desc FROM igf_aw_career_map_v WHERE program_type = :p_program_type; – retrieves all class-standing mappings for a given program type.
• SELECT career_level_id, program_type, class_standing_desc FROM igf_aw_career_map_v ORDER BY program_type, career_level_id; – produces an audit listing of all configured mappings.
• SELECT DISTINCT class_standing_desc FROM igf_aw_career_map_v; – enumerates the distinct descriptive class standings in use.

Integration consumers historically used the view to resolve a program type into a class standing without re-implementing lookup logic. Given the obsolete status and the absence of the object in the current database, any existing dependency should be retired in favour of supported alternatives; the documentation here is provided for migration and historical reference only.