Search Results sup_splrg_sequence_number

Overview

The IGS_CO_S_PERLT_RPTGP view is a critical data object within the Oracle E-Business Suite (EBS) Student System (IGS) module, specifically for the Correspondence functionality. It provides a filtered, organization-specific perspective on the repeating groups associated with a system-generated letter for a person. The view acts as a security layer over its underlying base table, IGS_CO_S_PERLT_RPTGP_ALL, by enforcing Multi-Org Access Control (MOAC). It restricts rows based on the ORG_ID context from the user's session (USERENV('CLIENT_INFO')), ensuring users only see data relevant to their operating unit. Its primary role is to manage the complex, hierarchical structure of repeating data elements (like course lists or fee details) that can be dynamically inserted into standardized correspondence templates.

Key Information Stored

The view's columns store metadata that defines the hierarchy and sequence of repeating data blocks within a person's letter. The composite primary key uniquely identifies a specific repeating group instance for a specific letter. Key columns include:

• PERSON_ID, CORRESPONDENCE_TYPE, LETTER_REFERENCE_NUMBER, SPL_SEQUENCE_NUMBER: These columns collectively link the repeating group to a specific person and a specific instance of a system-produced letter (SPL).
• LETTER_REPEATING_GROUP_CD and SEQUENCE_NUMBER: Identify the type of repeating group and its order within the letter.
• SUP_REPEATING_GROUP_CD and SUP_SPLRG_SEQUENCE_NUMBER: Define a parent-child hierarchy between repeating groups, allowing for nested data structures.
• SPL_SEQUENCE_NUMBER: As indicated by the user's search, this is a crucial identifier that distinguishes between multiple instances or versions of a system-produced letter for the same person and correspondence type.
• ORG_ID: The operating unit identifier, used by the view's WHERE clause to enforce data partitioning.

Common Use Cases and Queries

This view is primarily accessed for reporting on correspondence content and for troubleshooting letter generation. A common use case is to extract all hierarchical repeating data for a specific letter sent to a student to verify its content. For example, to retrieve all repeating groups for a specific system-produced letter instance, one might use:

SELECT * FROM apps.IGS_CO_S_PERLT_RPTGP WHERE person_id = 123456 AND correspondence_type = 'ENROL_CONF' AND letter_reference_number = 100 AND spl_sequence_number = 1 ORDER BY sequence_number;

Another critical pattern is generating a tree-structured report of nested repeating groups, which requires a hierarchical query (CONNECT BY) using the SUP_REPEATING_GROUP_CD and SUP_SPLRG_SEQUENCE_NUMBER columns to establish parent-child relationships. Developers and functional consultants also query this view to understand the data structure populated by the letter generation engine for a given correspondence template.

Related Objects

Based on the provided relationship data, IGS_CO_S_PERLT_RPTGP has integral ties to other objects in the Correspondence schema.

• Primary Key: IGS_CO_S_PERLT_RPTGP_PK on (PERSON_ID, CORRESPONDENCE_TYPE, LETTER_REFERENCE_NUMBER, SPL_SEQUENCE_NUMBER, LETTER_REPEATING_GROUP_CD, SEQUENCE_NUMBER).
• Base Table: The view sources all data from IGS_CO_S_PERLT_RPTGP_ALL.
• Foreign Key Reference: A documented foreign key indicates that the view's PERSON_ID column references the IGS_CO_S_PER_LTR table (or its corresponding view). This links the repeating group data to the master record of the person's letter.
• Self-Reference: The metadata also indicates a foreign key where the view's PERSON_ID references the view itself, suggesting a potential recursive hierarchical relationship managed within the same structure.