Results for “deduction_amount”

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

Overview

The view APPS.IGS_FI_FEE_RET_SCHD_F_TYPE_V belongs to the Oracle E-Business Suite Student System (IGS) product family, which is delivered as part of the Oracle Student System / Enterprise Trading and Relationship Management (ETRM) footprint. Its documented purpose is to determine the fee retention schedule entries that are specific to a given fee category and fee liability. In practical terms, the view resolves the relationship between a fee retention schedule and the fee category context under which that schedule applies, filtering and reconciling records so that downstream fee calculation, invoicing, and retention processing operate against the correct set of schedule lines.

Because it is a database view and not a table, it stores no data of its own. It is a reporting and integration surface: enquiry screens, concurrent programs, and interfaces that need to know "which retention schedule applies to this fee category, fee type, and calendar instance" can query the view rather than reimplementing the join and UNION logic. The view is owned by the APPS schema, is marked VALID, and is therefore a supported object for read access in both Oracle EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over three principal sources. First, IGS_FI_FEE_RET_SCHD_V (aliased FRSV) supplies the core retention schedule line attributes. Second, IGS_FI_F_CAT_FEE_LBL (aliased FCFL) provides the mapping between fee categories and fee types, and carries the fee calendar type and calendar instance sequence number needed to correlate the two sides. Third, IGS_FI_FEE_TYPE (aliased FT) supplies fee type attributes used to include or exclude schedule lines.

Structurally the view is a UNION of multiple SELECT statements. The documented first branch restricts output to rows where S_RELATION_TYPE = 'FCFL' and joins to the fee type table while excluding institutional fee triggers (S_FEE_TRIGGER_CAT != 'INSTITUTN') and HECS fee types (S_FEE_TYPE != 'HECS'). The second branch handles the S_RELATION_TYPE = 'FTCI' case and includes a correlated NOT EXISTS style subquery against IGS_FI_FEE_RET_SCHD, ensuring a fee-type/calendar-instance retention entry is returned only when no more specific fee-category level entry exists. Additional UNION branches follow the same pattern, giving the view its "type" resolution behaviour.

Key Columns

• FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER — identify the fee calendar and the specific calendar instance, the context keys for any retention lookup.
• S_RELATION_TYPE — indicates whether the schedule entry is tied to a fee category ('FCFL') or a fee type/calendar instance ('FTCI'); this is central to how the view resolves precedence.
• FEE_TYPE, FEE_CAT — the fee type and fee category to which the schedule line applies.
• SCHEDULE_NUMBER — the retention schedule identifier.
• DT_ALIAS, DAI_SEQUENCE_NUMBER — the date alias and its sequence, used for effective dating of the schedule.
• START_DT, END_DT — the validity window of the retention schedule line.
• RETENTION_PERCENTAGE, RETENTION_AMOUNT, DEDUCTION_AMOUNT, CURRENCY_CD — the financial terms applied when fees are retained or deducted.
• Standard WHO/audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for traceability.

Common Use Cases and Queries

Typical uses include fee retention enquiry screens, reconciliation reports, and custom interfaces that must derive the applicable retention terms for a fee category. A basic lookup by fee category and calendar instance:

• SELECT fee_cat, fee_type, schedule_number, retention_percentage, retention_amount, deduction_amount, start_dt, end_dt FROM igs_fi_fee_ret_schd_f_type_v WHERE fee_cal_type = :p_cal_type AND fee_ci_sequence_number = :p_seq AND fee_cat = :p_cat;
• To inspect the resolution path: SELECT s_relation_type, fee_type, fee_cat, schedule_number FROM igs_fi_fee_ret_schd_f_type_v WHERE fee_cal_type = :p_cal_type ORDER BY s_relation_type, fee_type, fee_cat;
• For effective-date validation: SELECT schedule_number, start_dt, end_dt FROM igs_fi_fee_ret_schd_f_type_v WHERE TRUNC(SYSDATE) BETWEEN start_dt AND NVL(end_dt, TRUNC(SYSDATE)) AND fee_type = :p_fee_type;

Note that the view is read-only by nature; retention schedule maintenance is performed on the underlying base tables through the Student System forms and APIs, with this view serving purely as the consolidated query interface.