Search Results igs_as_doc_fee_stup_pk

Overview

IGS_AS_DOC_FEE_STUP is a configuration table in the Oracle E-Business Suite Student System (IGS) product family, holding the document fees assessed for each type of document delivery method. It sits at the intersection of academic document issuance and financial fee setup, allowing institutions to define graduated, range-based charges that depend on the delivery method chosen for transcripts, certificates, and similar student documents. Rows are referenced during document request processing to determine the monetary amount to charge a student or applicant, and the associated fee type ties the charge back to the institutional fee structure defined in the financials fee type table.

From a Data Vault modeling perspective, the metadata's foreign-key structure suggests a satellite-leaning classification. The table carries descriptive attributes — delivery method, amount ranges, and payment type — that qualify a business key rather than serving as an independent hub or an associative link. Analysts modeling this data in a warehouse should consider treating TFEE_ID as the driving key and the fee and document attributes as satellite payload.

Key Information Stored

The table is documented with twelve physical columns. The most operationally significant are:

• TFEE_ID — the surrogate primary key, enforced by the IGS_AS_DOC_FEE_STUP_PK constraint and additionally protected by unique index IGS_AS_DOC_FEE_STUP_U1. It uniquely identifies each fee setup row.
• DOCUMENT_TYPE — identifies the category of document to which the fee applies (for example, transcript or certification type). Together with LOWER_RANGE this forms the second business-key candidate, unique index IGS_AS_DOC_FEE_STUP_U2.
• LOWER_RANGE / UPPER_RANGE — the boundaries of the quantity or value band within which the configured amount applies, supporting tiered or graduated fee schedules.
• AMOUNT — the monetary value charged when a request falls within the corresponding range and document type.
• PAYMENT_TYPE — the accepted or required method of payment for the fee.
• FEE_TYPE — the foreign key referencing IGS_FI_FEE_TYPE_ALL, linking the document charge into the broader fee taxonomy.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns capturing who created and last modified each row and when.

The distinction between the surrogate key (TFEE_ID) and the composite business key (DOCUMENT_TYPE, LOWER_RANGE) is important for deduplication and integration logic, since neither unique index alone guarantees row identity across environments.

Common Use Cases and Queries

Typical usage centers on fee determination and fee-schedule maintenance. A common query retrieves the applicable charge for a given document and quantity:

• Fee lookup: SELECT amount FROM igs_as_doc_fee_stup WHERE document_type = :p_type AND :p_qty BETWEEN lower_range AND upper_range;
• Fee schedule reporting: join to IGS_FI_FEE_TYPE_ALL to report document fees by fee type and delivery method for financial reconciliation.
• Setup validation: identify overlapping or missing ranges per DOCUMENT_TYPE (gaps between UPPER_RANGE and the next LOWER_RANGE) to detect misconfigured fee bands.
• Audit and change tracking: query by LAST_UPDATE_DATE to review recent modifications to the fee setup.
• Integration extraction: pull all rows with the joined fee type description for downstream billing or student account systems.

Related Objects

The documented relationship data identifies the following significant dependencies:

• IGS_FI_FEE_TYPE_ALL — referenced via IGS_AS_DOC_FEE_STUP.FEE_TYPE. This is the primary foreign-key parent and the most important join target, providing fee type descriptions and validation for document charges.
• IGS_AS_DOC_FEE_STUP_PK / _U1 / _U2 — the primary and unique constraints that enforce identity and business-key uniqueness.
• IGS document request and delivery objects — the transactional tables that consume document fee configuration during academic document processing; these depend on this setup table at runtime through the shared DOCUMENT_TYPE attribute.
• Student account and billing components — the fee amounts configured here flow into charge calculation, inheriting the linked fee type for posting.

Because the documented metadata is limited to a single declared foreign key, integration work should confirm additional soft dependencies on document type and payment type lookup tables within the IGS schema.