Search Results igs_as_servic_plan




Overview
Explore in AI Chat

Overview

The IGS_AS_SERVIC_PLAN table is a core data object within the Oracle E-Business Suite (EBS) Student System (IGS) module, specifically for versions 12.1.1 and 12.2.2. It functions as the master repository for defining and managing institutional transcript service plans. Each row in this table represents a distinct plan offered by the institution, which dictates the terms, conditions, and potentially the pricing associated with requesting official transcripts. A critical secondary function of this table is to support institutional policies allowing a specified number of "free" transcript requests per student career or academic year, thereby automating fee waivers. The table's design also accommodates the deactivation of pre-seeded service offerings if they do not align with the institution's operational model.

Key Information Stored

While the provided metadata does not list specific column names beyond the primary key, the table's structure is designed to encapsulate all necessary attributes for a service plan. The central identifier is the PLAN_ID column, which serves as the unique primary key. Based on its described functionality, other likely columns would store data such as the service plan name, description, an active/inactive flag, the type of plan (e.g., standard, expedited, electronic), associated fee amounts, and rules governing free transcript allowances. These rules would include parameters like the number of free transcripts permitted and the period to which they apply (career or academic year). This data collectively enables the system to correctly apply fees and validate transcript requests against institutional business rules.

Common Use Cases and Queries

The primary use case involves the transcript ordering process. When a student or administrative user requests a transcript, the application references the IGS_AS_SERVIC_PLAN table to determine the applicable plan, calculate any fees, and verify if a free transcript allowance applies. Common reporting and administrative queries include listing all active service plans, analyzing transcript request volumes by plan type, and auditing the usage of free transcript allowances. A typical SQL pattern for retrieving core plan information would involve selecting from this table, often joined to related transactional tables. For example, to find details for a specific plan referenced in a document request, one might query: SELECT * FROM igs.igs_as_servic_plan WHERE plan_id = :p_plan_id;. Another common query would identify all plans currently in use within the system for reporting purposes.

Related Objects

The IGS_AS_SERVIC_PLAN table is centrally linked to key transactional tables in the Student System through foreign key relationships, as documented in the provided metadata. Its primary key (PLAN_ID) is referenced by the following objects:

  • IGS_AS_DOC_DETAILS: The PLAN_ID column in this table links individual document details (likely per transcript request) to a specific service plan, recording which plan was applied to that request.
  • IGS_AS_DOC_FEE_PMNT: The PLAN_ID column in this fee payment table ties financial transactions for transcripts back to the governing service plan, ensuring fee calculations are auditable and consistent with the plan's rules.
These relationships confirm that IGS_AS_SERVIC_PLAN is a foundational setup table, with its PLAN_ID propagating into downstream document processing and financial transactions.