Results for “currency_cd”

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

Overview

IGS_FI_FEE_RET_SCHD_V is a VALID database view owned by the APPS schema within the IGS – Student System product of Oracle E-Business Suite. It is delivered as a reporting and integration convenience object rather than a stored table, meaning it holds no data of its own and is evaluated at query time from its underlying base object. The view exposes every column of the IGS_FI_FEE_RET_SCHD (fee_retention_schedule) table, supplemented by derived columns that resolve the start and end period for each schedule entry as well as the applicable currency code. Because fee retention schedules are keyed by calendar type, calendar instance, student relation type, fee type, fee category, date alias and date alias instance sequence, the raw table alone is difficult to interpret without invoking the Student System calendar and finance APIs. The view performs that resolution on behalf of the caller, making the retention rules directly consumable by reports, concurrent programs, and outbound interfaces in both 12.1.1 and 12.2.2 environments. Administrators and developers searching for "igs_fi_fee_ret_schd_v" are typically looking for exactly this: a read-only, API-enriched projection of retention schedule configuration that can be queried with ordinary SQL.

Underlying Base Objects

The ETRM metadata documents no formal referenced base objects for the view, but the view text unambiguously identifies IGS_FI_FEE_RET_SCHD (aliased FRTNS) as the driving table. The view is defined as a single-table SELECT with function calls layered on top of it. Three packaged functions are invoked: IGS_CA_GEN_001.CALP_GET_ALIAS_VAL, which converts a date alias and its instance sequence into a concrete start date within the specified calendar and calendar instance; IGS_FI_GEN_001.FINP_GET_FRTNS_END_DT, which derives the corresponding end date for the retention entry; and IGS_FI_GEN_001.FINP_GET_CURRENCY, whose result is truncated to fifteen characters to populate the CURRENCY_CD column. The ROWID of the base table is surfaced as ROW_ID. Because resolution depends on calendar and finance setup data, the view is only meaningful when the associated calendar types, fee calendars, and fee categories are fully configured. Callers should treat the view as read-only; DML against a view of this shape is not supported.

Key Columns

• ROW_ID — the ROWID of the underlying IGS_FI_FEE_RET_SCHD row, useful for de-duplication and correlation back to the table.
• FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER — the fee calendar type and calendar instance that scope the schedule.
• S_RELATION_TYPE, FEE_TYPE, FEE_CAT — the student relation type, fee type, and fee category to which the retention rule applies.
• SCHEDULE_NUMBER, SEQUENCE_NUMBER — identity of the schedule and ordering of its entries.
• DT_ALIAS, DAI_SEQUENCE_NUMBER — the date alias and its instance sequence, used as input to the start-date and end-date derivations.
• START_DT, END_DT — derived, human-readable validity boundaries for each retention entry, computed by the calendar and finance APIs.
• RETENTION_PERCENTAGE, RETENTION_AMOUNT, DEDUCTION_AMOUNT — the retention rule values, expressed as a percentage and/or monetary amounts.
• CURRENCY_CD — the currency resolved for the fee calendar context, truncated to 15 characters.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include validating retention configuration before a fee assessment run, extracting retention schedules for reconciliation or migration, and joining retention rules to student fee records for institutional reporting. A basic listing for one calendar is shown below; note that no WHERE clause on the API-derived columns is required because they are plain select-list expressions.

SELECT fee_cal_type,
       fee_ci_sequence_number,
       fee_type,
       fee_cat,
       schedule_number,
       start_dt,
       end_dt,
       retention_percentage,
       retention_amount,
       deduction_amount,
       currency_cd
FROM   apps.igs_fi_fee_ret_schd_v
WHERE  fee_cal_type = :p_fee_cal_type
AND    fee_ci_sequence_number = :p_ci_seq
ORDER  BY schedule_number, sequence_number;

A second pattern correlates retention entries with the calendar instance effective window, filtering only entries active on a given date:

SELECT v.*
FROM   apps.igs_fi_fee_ret_schd_v v
WHERE  TRUNC(SYSDATE) BETWEEN v.start_dt AND v.end_dt;

Because every row is evaluated through PL/SQL functions, performance on large extracts benefits from restricting the query by FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER, or the audit date columns before the derived columns are projected. Callers should avoid referencing ROW_ID across database links, since ROWID values are not portable between databases.