Search Results definition_code_meaning




Overview
Explore in AI Chat

Overview

IGS_PS_NSUS_RTN_V is a reporting view in the Oracle E-Business Suite application schema APPS, associated with the Student System (IGS) product family. Its name, combining the prefixes for non-standard use, and return, identifies it as a denormalized presentation layer over the IGS_PS_NSUS_RTN base table, which stores non-standard use fee return records. The view enriches the base entity with decoded, human-readable descriptions so that consumers—Oracle Forms blocks, concurrent programs, BI Publisher reports, and integration extracts—can display meaningful values rather than raw coded identifiers. Because the view is owned by APPS, it is accessible to end-user responsibility queries, and because Oracle treats it as a supported read-only interface, customizations should reference the view rather than the underlying table.

The view is particularly relevant to the reporting of fee returns calculated against non-standard use definitions, where the meaning of the definition_code lookup is required for both functional display and downstream auditing. The documentation provided by ETRM (Electronic Technical Reference Manual for 12.2.2) lists no separately documented base objects, so the definition must be read directly from the view text.

Underlying Base Objects

The view is defined over three objects. The driving table is IGS_PS_NSUS_RTN NR, which supplies the return identifier, unit of offering, fee type, definition code, formula and rounding methods, weekend-duration flag, and WHO audit columns. Two lookup/master joins decorate this record. IGS_LOOKUP_VALUES lv is joined with an inner join on NR.definition_code = lv.lookup_code and constrained to lv.lookup_type = 'DEFINITION_LEVEL', producing the definition_code_meaning column. IGS_FI_FEE_TYPE_ALL fee is joined with an outer join (NR.fee_type = fee.fee_type (+)) to supply fee_type_desc, preserving return rows even where no matching fee type definition exists. The view text exposes the ROWID of the base table as ROW_ID, which Oracle Forms uses for optimistic locking. The inner join on lookup values means any return row whose definition code is missing from the DEFINITION_LEVEL lookup set will be filtered out, a behavior worth noting when reconciling view row counts against the base table.

Key Columns

Common Use Cases and Queries

Typical uses include reporting non-standard use returns with readable definition text, validating that definition codes are correctly configured in the DEFINITION_LEVEL lookup, and extracting data for interfaces. A representative query:

SELECT non_std_usec_rtn_id, uoo_id, fee_type_desc, definition_code, definition_code_meaning, formula_method, round_method FROM apps.igs_ps_nsus_rtn_v WHERE uoo_id = :p_uoo_id ORDER BY non_std_usec_rtn_id;

A lookup-coverage query identifies coding gaps:

SELECT definition_code, COUNT(*) FROM apps.igs_ps_nsus_rtn_v GROUP BY definition_code ORDER BY 2 DESC;

Because the DEFINITION_LEVEL join is inner, comparing these results against SELECT COUNT(*) FROM igs_ps_nsus_rtn isolates records whose definition codes are absent from the lookup values, which is a frequent source of missing rows in reports.