Search Results igs_as_doc_fee_stup_u1

Overview

The IGS.IGS_AS_DOC_FEE_STUP table is a setup table within the Oracle E-Business Suite (EBS) Student Systems / Academic Records (IGS) product family. It defines the fee schedule that applies when a student requests a document — most commonly a transcript — under a particular document delivery method. Each row establishes a pricing rule for a document type across a numbered range of copies, and ties that rule to a payment type and a fee type recognized by the Oracle Financials fee engine.

Because the table holds configuration rather than transactional history, it functions as a reference source consumed at the time a document order is priced. Every transcript or document request processed by the Academic Records module resolves its charge by matching the requested document type and copy count against the upper and lower bounds recorded here, then applying the resulting amount and payment model.

From a Data Vault modeling perspective, the heuristic classification for this object is satellite-leaning. The table is descriptive by nature: it carries the attributes and effectivity of a document fee rule rather than asserting a new business entity or a many-to-many association. The suggested treatment is therefore a satellite attached to a document-type hub, with the range, payment type, amount, and fee type as descriptive payload.

Key Information Stored

The table contains twelve documented columns. The most significant are:

• TFEE_ID — The system-generated surrogate primary key, populated through the sequence IGS_AS_DOC_FEE_STUP_S. It is enforced by unique index IGS_AS_DOC_FEE_STUP_U1 and is the column to use in all foreign-key joins from downstream pricing or order tables.
• DOCUMENT_TYPE — The transcript or document type the fee applies to. Together with LOWER_RANGE it forms the business-key candidate enforced by unique index IGS_AS_DOC_FEE_STUP_U2, which guarantees that only one fee rule exists per document type and starting copy count.
• LOWER_RANGE / UPPER_RANGE — The inclusive copy-count band for which the fee is valid. A request for three transcripts, for example, resolves to the row whose lower and upper bounds bracket the value three.
• PAYMENT_TYPE — Determines how the charge is calculated: F for a flat rate, P for per-copy pricing, or L for a lifetime fee. This single-character flag drives the pricing arithmetic at order time.
• AMOUNT — The monetary value associated with the rule, interpreted according to PAYMENT_TYPE.
• FEE_TYPE — The fee category against which the resulting charge is posted. This column carries the foreign key to IGS_FI_FEE_TYPE_ALL, linking the document fee definition to the central fee type registry.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the identity and timestamp of the user who inserted or last amended each rule.

Common Use Cases and Queries

The principal scenario is fee resolution during document ordering. The application searches for the rule that matches the requested document type and copy count, then reads PAYMENT_TYPE and FEE_TYPE to compute the charge. A representative lookup follows:

SELECT TFEE_ID, PAYMENT_TYPE, AMOUNT, FEE_TYPE
FROM IGS.IGS_AS_DOC_FEE_STUP
WHERE DOCUMENT_TYPE = :document_type
AND :copies BETWEEN LOWER_RANGE AND UPPER_RANGE;

Administrators and functional analysts also use the table to audit the published fee schedule, verify that ranges do not overlap or leave gaps, and confirm that each FEE_TYPE is valid in the financials setup:

SELECT s.DOCUMENT_TYPE, s.LOWER_RANGE, s.UPPER_RANGE,
       s.PAYMENT_TYPE, s.AMOUNT, f.FEE_TYPE_NAME
FROM IGS.IGS_AS_DOC_FEE_STUP s,
     IGS.IGS_FI_FEE_TYPE_ALL f
WHERE s.FEE_TYPE = f.FEE_TYPE
ORDER BY s.DOCUMENT_TYPE, s.LOWER_RANGE;

Additional reporting uses include reconstructing historical pricing for reconciliation, and exporting the schedule for institutional fee publications.

Related Objects

• IGS_FI_FEE_TYPE_ALL — Referenced by the FEE_TYPE foreign key; supplies the validated fee type definitions used when posting document charges.
• IGS_AS_DOC_FEE_STUP_S — The sequence that generates TFEE_ID values on insert.
• IGS_AS_DOC_FEE_STUP_PK — The primary-key constraint on TFEE_ID, alongside unique indexes U1 and U2, which together enforce row and business-key integrity.
• Document order and transcript request tables within the IGS Academic Records schema, which resolve pricing against this setup data at processing time.
• Financials fee and charge interfaces that consume the resulting AMOUNT and FEE_TYPE during accounting.