Results for “repeatable_indicator”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view APPS.IGSFV_USEC_REPEAT_CONDITIONS belongs to the Oracle E-Business Suite Student System product (IGS) and is registered in the ETRM as a VALID view owned by the APPS schema. It presents the full definition of repeat conditions attached to a unit section, exposing both the configuration attributes that govern whether a student may repeat a unit offering and the descriptive context of the parent unit offering. In Oracle EBS 12.1.1 and 12.2.2 the object is therefore a reporting and integration surface rather than a transactional table: it consolidates repeat-condition setup data with unit offering identity so that downstream queries, concurrent programs, and interfaces can resolve a repeat condition to its unit code, version, calendar type, location, and class without performing the join themselves. The ETRM description notes that the view is associated with the Case and Seed document PS201_Enhancements_Nov03_PS_3045069_CS_DP2.doc, which is marked obsolete; the view itself remains valid, and its structure reflects the historical enhancement that introduced repeat condition tracking in the Student System.

Underlying Base Objects

The view text is a two-table join defined WITH READ ONLY, so it cannot be used as an update target. The documented base objects are:

• IGS_PS_USEC_RPT_COND (aliased US) — the repeat-condition entity. It supplies the primary key UNIT_SECTION_REPT_CONDITION_ID, the repeatable flag, the credit and funding repeat limits, and the standard WHO audit columns.
• IGS_PS_UNIT_OFR_OPT_ALL (aliased UN) — the unit offering option entity, supplying unit code, version, calendar type, calendar instance sequence, location, and unit class. The join predicate is US.UOO_ID = UN.UOO_ID, linking each repeat condition to its unit offering option.

The ETRM metadata records no additional referenced base objects beyond these two tables. Because the join is an inner equijoin on UOO_ID, a repeat condition is only visible when its parent unit offering option row exists in the _ALL table; orphaned or in-progress setups are not returned. The _ALL suffix indicates that row-level security (multi-org / operating unit) is applied by the underlying unit offering option object, so the effective row set returned to a query is also constrained by the caller's security profile.

Key Columns

• UNIT_SECTION_REPT_CONDITION_ID — surrogate primary key of the repeat condition record.
• REPEATABLE_INDICATOR — the renamed REPEATABLE_IND column, the primary flag indicating whether the unit section may be repeated. This is the column most frequently targeted by the search term "repeatable_indicator".
• SAME_TEACHING_PERIOD, SAME_TEACH_PERIOD_REPEATS, SAME_TEACH_PERIOD_REPEATS_CP — controls and counters relating to repeats permitted within the same teaching period, including the associated credit point allowance.
• MAX_REPEATS_FOR_CREDIT, MAX_REPEATS_FOR_FUNDING, MAX_REPEAT_CREDIT_POINTS — the maximum repeat allowances for credit purposes, funding purposes, and the maximum credit points that may be earned through repeats.
• UNIT_SECTION_ID — exposes UOO_ID under a section-oriented alias.
• UNIT_CODE, VERSION_NUMBER, CALENDAR_TYPE, CAL_INST_SEQUENCE_NUMBER, LOCATION_CODE, UNIT_CLASS — descriptive identity of the parent unit offering.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns supporting change tracking and data lineage reporting.

Common Use Cases and Queries

Typical uses include validating repeatability rules during enrolment processing, producing setup reports for admissions and student records administrators, and extracting repeat condition data for reconciliation or migration. A common pattern filters on the repeatable flag:

• SELECT unit_code, version_number, calendar_type, repeatable_indicator, max_repeats_for_credit FROM igsfv_usec_repeat_conditions WHERE repeatable_indicator = 'Y';
• SELECT unit_code, location_code, unit_class, same_teaching_period, max_repeat_credit_points FROM igsfv_usec_repeat_conditions WHERE unit_code = :unit_code;
• SELECT unit_section_id, repeatable_indicator, last_update_date, last_updated_by FROM igsfv_usec_repeat_conditions ORDER BY last_update_date DESC;

Because the view is read only and inner-joined, reports should not assume exhaustive coverage of repeat condition rows; any diagnostic query intended to detect repeat conditions whose unit offering is missing must instead query IGS_PS_USEC_RPT_COND directly.