Search Results rqrmnts_complete_indicator

Overview

The view IGSBV_STU_PRG_CNCTRN_ATTEMPT belongs to the IGS — Student System product family, a module designated as obsolete in Oracle EBS 12.1.1 and 12.2.2. Its stated description is: "Describes student's attempt at program unit set." The name decomposes as Student, Program, and Concurrent attempt — spelled phonetically as "CNCTRN" — indicating that the view exposes a student's attempt record against a unit set within a program of study, together with the parent unit set relationship.

Functionally, this view consolidates attempt-level data from the student unit set attempt table with party, program version, enrollment, and unit set descriptive information. It is a read-only, denormalized reporting object intended for inquiry screens, concurrent reports, and integration extracts where a single row per student attempt is required with human-readable labels attached. Because IGS is obsolete, the view is retained for backward compatibility rather than for new development.

The ETRM metadata explicitly records that the object is Not implemented in this database, meaning no physical definition exists in the reference environment, although the view text and column list are documented.

Underlying Base Objects

The view is defined over five base objects joined on person, course, and unit set keys, and is created WITH READ ONLY:

• IGS_AS_SU_SETATMPT SUSA — the driving table holding the student's attempt at a unit set (the "SU SETATMPT" record), including sequence, dates, and confirmation flags.
• HZ_PARTIES HP — the Trading Community Architecture party record, supplying the person number.
• IGS_EN_STDNT_PS_ATT_ALL SCA — the student program attempt record, joined on PERSON_ID and COURSE_CD.
• IGS_PS_VER_ALL PSV — the program (course) version, supplying the program title; joined via COURSE_CD and VERSION_NUMBER.
• IGS_EN_UNIT_SET_ALL US — the unit set definition, supplying the unit set title; joined via UNIT_SET_CD and US_VERSION_NUMBER.

No referenced base objects are documented in the ETRM 12.2.2 metadata beyond those present in the view text, and no owner is recorded.

Key Columns

The view exposes twenty-seven columns. The most significant, particularly relative to the search term parent_unit_set_code, are:

• PERSON_IDENTIFIER / PERSON_NUMBER — the party identifier and party number of the student.
• PROGRAM_CODE — the course/program code of the attempt.
• UNIT_SET_CODE / US_VERSION_NUMBER — the unit set being attempted and its version.
• SEQUENCE_NUMBER — distinguishes multiple attempts at the same unit set.
• PARENT_UNIT_SET_CODE — the unit set that contains the current set, enabling hierarchical navigation of nested unit sets.
• PARENT_SEQUENCE_NUMBER — the attempt sequence of the parent set.
• SELECTION_DATE, END_DATE, AUTHORISED_ON — temporal attributes of the attempt.
• STUDENT_CONFIRMED_INDICATOR, PRIMARY_SET_INDICATOR, VOLUNTARY_END_INDICATOR, RQRMNTS_COMPLETE_INDICATOR — status flags.
• RQRMNTS_COMPLETE_DATE, S_COMPLETED_SOURCE_TYPE — completion tracking.
• PROGRAM_TITLE, UNIT_SET_TITLE, OVERRIDE_TITLE — descriptive labels.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.

Common Use Cases and Queries

The view is typically used to report a student's unit set attempt history, to trace hierarchical parent-child unit set structures, and to reconcile enrollment against unit set definitions.

To locate attempts by parent unit set code:

SELECT person_number,
       program_code,
       unit_set_code,
       parent_unit_set_code,
       sequence_number,
       selection_date,
       student_confirmed_indicator
FROM   igsbv_stu_prg_cnctrn_attempt
WHERE  parent_unit_set_code = :p_parent_unit_set_code
ORDER  BY sequence_number;

To list all attempts for a person with titles:

SELECT person_identifier,
       program_title,
       unit_set_title,
       primary_set_indicator,
       rqrmnts_complete_indicator
FROM   igsbv_stu_prg_cnctrn_attempt
WHERE  person_identifier = :p_person_id;

Because the view is read-only and IGS is obsolete, integration should target supported replacements where available; existing queries remain valid for legacy reporting and migration reconciliation.