Results for “igf_sp_std_unit”

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

Overview

IGF_SP_STD_UNIT is a multi-org secured view in the APPS schema belonging to the IGF (Financial Aid) product family within Oracle E-Business Suite. Its name encodes its three defining characteristics: "IGF" identifies the Financial Aid module, "SP" refers to the Student Progress or sponsor-related tracking area, and "STD_UNIT" denotes standardized units used for fee classification. The view exists to present unit-level fee classification data with organization-level security enforcement, functioning as the reporting and integration layer over the underlying entity table.

In Oracle EBS 12.1.1 and 12.2.2, views of the form XXX_ALL paired with a secured synonym-style view (without the _ALL suffix) are a standard pattern. The secured view restricts rows based on the session's current operating unit, which is passed through the USERENV('CLIENT_INFO') context variable. This design allows users to query the view using standard SQL while inheriting the Multi-Org Access Control (MOAC) privileges defined for their responsibility, without needing to append an explicit ORG_ID predicate.

Underlying Base Objects

The view is defined over a single base table: IGF_SP_STD_UNIT_ALL. The ETRM metadata does not document any additional referenced objects, and the view text confirms a straightforward single-table projection.

The definition selects all data columns from IGF_SP_STD_UNIT_ALL and appends a ROWID column, giving callers a stable physical row identifier suitable for updates or row-level processing. The critical element of the definition is the final WHERE clause:

• The clause extracts a value from USERENV('CLIENT_INFO') — specifically the first ten bytes — decoding a leading space to NULL.
• Wherever that derived value is NULL, it is substituted with -99, which is the conventional Multi-Org sentinel representing "all organizations."
• The comparison is applied both to the base table's NVL(STDU.ORG_ID, ...) and to the session value, so that rows with a NULL ORG_ID are treated as globally visible.

The net effect is that a session operating in a specific organization sees only rows for that organization, while a session with no organization context (or a specially configured one) sees all rows.

Key Columns

• ROW_ID — The physical row identifier from the base table; useful for direct row access.
• FEE_CLS_UNIT_ID — Primary key of the underlying entity table, uniquely identifying the standardized unit record.
• FEE_CLS_PRG_ID — Foreign key to the associated fee classification program, linking the unit to its parent program definition.
• UNIT_CD — The code identifying the standardized unit. This is typically the human-readable business key used in reporting and integration interfaces.
• VERSION_NUMBER — Version indicator supporting the change-control model typical of Financial Aid configuration data.
• MAX_AMOUNT — The maximum allowable amount associated with the unit, used in award and fee calculations.
• ORG_ID — Operating unit identifier driving the Multi-Org security filter described above.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns populated by the WHO columns framework.

Common Use Cases and Queries

The view is most often used in reporting and interfaces that must respect operating unit boundaries without hard-coding them. A typical query retrieves all active unit codes for a program and exposes the maximum amount:

• SELECT unit_cd, fee_cls_prg_id, max_amount, version_number FROM igf_sp_std_unit WHERE fee_cls_prg_id = :p_prg_id ORDER BY unit_cd;
• SELECT fee_cls_unit_id, unit_cd, org_id FROM igf_sp_std_unit WHERE unit_cd = :p_unit_cd;
• SELECT COUNT(*) FROM igf_sp_std_unit; — used to verify that MOAC context is applied correctly within a responsibility.

Because the view enforces organization security, development on Integration or conversion programs should reference IGF_SP_STD_UNIT_ALL directly only when MOAC bypass is intended. Querying the secured view is the recommended approach for forms, concurrent programs, and web service payloads that execute in a user context. To diagnose which operating unit the session resolves, inspect USERENV('CLIENT_INFO'); a value of -99 indicates the "all organizations" case. The absence of documented object dependencies and the presence of only a single base table also makes this view a lightweight and predictable target for joins in downstream Financial Aid reports.