Results for “igf_sp_std_prg”

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

Overview

IGF_SP_STD_PRG is a Multi-Organization (MO) view within the Oracle E-Business Suite IGF — Financial Aid module. This module is documented as obsolete in the ETRM 12.2.2 metadata, meaning it is retained for backward compatibility and historical reference but is no longer actively implemented or supported in current deployments. The view presents student program fee classification data, specifically the relationship between fee classifications and academic programs, along with associated percentage and monetary limits.

The view's primary design purpose is to enforce organizational data security through Oracle's Multi-Org architecture. By filtering records based on the organization context established in the user's session, it ensures that users accessing financial aid data only see records belonging to the operating unit (ORG_ID) to which they are currently assigned. This view would have been consumed by Oracle Forms, concurrent programs, and reporting tools within the Financial Aid module.

Underlying Base Objects

The view is defined entirely over a single base table: IGF_SP_STD_PRG_ALL. The "_ALL" suffix follows Oracle's standard naming convention, indicating that the underlying table stores records across all organizations without any organizational filtering. The view applies a WHERE clause that compares the table's ORG_ID column against the organization identifier retrieved from the session environment.

The filtering logic relies on the USERENV('CLIENT_INFO') function. Oracle extracts the first ten characters of CLIENT_INFO, decoding a leading space as NULL, and converts the result to a number. If no valid organization context exists, the NVL logic defaults both sides of the comparison to -99, which typically returns no rows or only records with a matching sentinel value. This is the canonical Oracle Multi-Org security pattern (sometimes called the "MO view" or "VPD-less" filtering approach) used prior to the introduction of Virtual Private Database policies. Notably, the documented metadata lists no referenced base objects beyond IGF_SP_STD_PRG_ALL, and the view is marked as not implemented in the current database, confirming its obsolete status.

Key Columns

• ROW_ID (mapped from STDP.ROWID): The physical row identifier of the underlying table row. It provides a unique handle for the record but is not stable across table reorganization.
• FEE_CLS_PRG_ID: The primary identifier linking a fee classification to a specific program.
• FEE_CLS_ID: Foreign key reference to the fee classification definition.
• COURSE_CD: The course code associated with the program fee setup.
• VERSION_NUMBER: Version indicator supporting record versioning or effective-dating of the fee program setup.
• FEE_PERCENT: The percentage of the fee applied under this classification/program combination.
• MAX_AMOUNT: The ceiling amount for the fee calculation.
• ORG_ID: The operating unit identifier that drives Multi-Org filtering.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN: Standard Oracle audit columns tracking who created and last modified each row and when.

Common Use Cases and Queries

Because the object is obsolete and not implemented, practical use is limited to legacy reporting, data migration audits, or historical reconciliation in environments that still retain the IGF schema. A typical query retrieves program fee percentages for the current organization context:

SELECT fee_cls_id, course_cd, version_number, fee_percent, max_amount
FROM igf_sp_std_prg
WHERE fee_cls_id = :fee_cls_id;

To audit fee ceilings across programs, a reporting query might aggregate the MAX_AMOUNT values. Administrators performing a data migration should query the view from an environment where the IGF tables still exist, or query IGF_SP_STD_PRG_ALL directly with an explicit ORG_ID predicate if the Multi-Org session context is unavailable. Given the module's obsolete classification, any integration point referencing this view should be reviewed for replacement or retirement in 12.2.2 and later releases.