Search Results sup_splrg_sequence_number




Overview

The view APPS.IGS_CO_S_PERLT_RPTGP is a security-filtered representation of the underlying table IGS_CO_S_PERLT_RPTGP_ALL within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It is part of the Correspondence Generation (IGS) module, specifically managing the complex structure of repeating data groups within personalized correspondence letters. The view's primary function is to enforce Multi-Org Access Control (MOAC) security. It achieves this by filtering the base table's data based on the ORG_ID context set in the user's session (via the CLIENT_INFO application context), ensuring users only access data relevant to their operating unit. This object is central to tracking hierarchical relationships between repeating data elements in generated letters, such as when one repeating group is subordinate to another.

Key Information Stored

The view exposes columns that define the core relationships and audit trail for letter repeating groups. The primary key columns—PERSON_ID, CORRESPONDENCE_TYPE, LETTER_REFERENCE_NUMBER, SPL_SEQUENCE_NUMBER, LETTER_REPEATING_GROUP_CD, and SEQUENCE_NUMBER—uniquely identify a specific instance of a repeating group for a person's letter. The columns SUP_REPEATING_GROUP_CD and SUP_SPLRG_SEQUENCE_NUMBER define the parent or superior repeating group to which this group is linked, establishing the hierarchy. The column specifically referenced in the user's search, SUP_SPLRG_SEQUENCE_NUMBER, holds the sequence number of the superior repeating group. Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) and program context columns (REQUEST_ID, PROGRAM_ID) are also present. The ORG_ID is a critical column used by the view's WHERE clause for security filtering.

Common Use Cases and Queries

This view is primarily accessed for reporting and troubleshooting the structure of generated correspondence. A common use case is to analyze all subordinate repeating groups for a specific letter sent to a person. For example, to find all repeating groups where the user-specified column SUP_SPLRG_SEQUENCE_NUMBER is populated, indicating a hierarchical relationship, one might use a query such as: SELECT * FROM apps.igs_co_s_perlt_rptgp WHERE person_id = 12345 AND letter_reference_number = 100 AND sup_splrg_sequence_number IS NOT NULL;. Another typical scenario involves joining this view to the person letter header information (e.g., IGS_CO_S_PER_LTR) to produce comprehensive correspondence audit reports that include the nested structure of repeating data elements. The view is integral for validating data integrity in complex letter generation processes.

Related Objects

Based on the provided relationship metadata, this view has direct dependencies on several core tables. Its primary key is enforced by the constraint IGS_CO_S_PERLT_RPTGP_PK. The view's data is sourced from and filtered on the base table IGS_CO_S_PERLT_RPTGP_ALL. Foreign key relationships indicate it references the person letter header table, IGS_CO_S_PER_LTR, via the PERSON_ID column. The metadata also suggests a recursive relationship, where the view references itself (APPS.IGS_CO_S_PERLT_RPTGP) via the PERSON_ID column, which likely supports the hierarchical data model for repeating groups. These relationships are essential for constructing accurate joins in reports or data extracts.