Results for “translated_date”

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

Overview

The IGSFV_AS_SU_ATMPT_OUTCOMES view in the Oracle E-Business Suite Student System (IGS) product family provides a denormalized, presentation-layer representation of student unit attempt outcomes. It is owned by the APPS schema and is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2. The view consolidates data from the assessment outcomes table together with party, enrollment, course, unit version, calendar instance, and grading schema tables, producing a single row per student unit attempt outcome enriched with descriptive titles and lookup meanings.

Its principal role is to serve as a reporting and integration interface. Because raw outcome records in IGS_AS_SU_STMPTOUT_ALL store coded values (for example, grading schema codes, grading period codes, and yes/no indicators), the view translates these into human-readable descriptions. It is commonly consumed by academic history reports, transcript generation processes, student records extracts, and downstream integration interfaces where a flattened view of assessment results is required without exposing the full normalization of the base schema.

Underlying Base Objects

The view is defined over a set of joined base tables. The central driving table is IGS_AS_SU_STMPTOUT_ALL (aliased SUAO), which stores the student unit attempt outcome records. The remaining objects provide contextual and descriptive data:

• HZ_PARTIES (HP) supplies the student party name and party number via PERSON_ID.
• IGS_EN_SU_ATTEMPT_ALL (SUA) supplies unit attempt context such as unit code and version.
• IGS_EN_STDNT_PS_ATT_ALL (SCA) links the student to the program (course) attempt.
• IGS_CA_INST_ALL (CI) provides calendar instance description and start/end dates.
• IGS_PS_UNIT_VER_ALL (UV) supplies the unit version title.
• IGS_PS_VER_ALL (CRV) supplies the program version title.
• IGS_AS_GRD_SCHEMA (GS1 and GS2) provides grading schema descriptions for both the primary and incomplete grading schemas.

The joins are keyed on PERSON_ID, COURSE_CD, UOO_ID, UNIT_CD, and VERSION_NUMBER, ensuring the outcome aligns with the correct attempt, program, and unit version.

Key Columns

The view exposes a broad set of columns. Identifying and outcome-related columns include PARTY_NAME, PARTY_NUMBER, COURSE_CD, UNIT_CD, CAL_TYPE, CI_SEQUENCE_NUMBER, OUTCOME_DT, MARK, GRADE, and COMMENTS. The column directly relevant to the user's search, TRANSLATED_DT, holds the translated (adjusted or finalized) outcome date, distinct from the original outcome date. Closely related are TRANSLATED_GRADE, TRANSLATED_GRADING_SCHEMA_CD, and TRANSLATED_VERSION_NUMBER.

• FINALISED_OUTCOME_IND, MARK_CAPPED_FLAG, SHOW_ON_ACADEMIC_HISTRY_FLAG, and MANUAL_OVERRIDE_FLAG are decoded into YES/NO meanings through IGS_LOOKUP_VALUES.
• GRADING_PERIOD_CD is resolved to its lookup meaning.
• Incomplete outcome administration is captured by INCOMP_DEADLINE_DATE, INCOMP_DEFAULT_GRADE, INCOMP_DEFAULT_MARK, and INCOMP_GRADING_SCHEMA_CD.
• The derived column returned by IGS_AS_DERIVE_GRADE.GET_ASSESSMENT_STATUS provides the current assessment status per student, course, unit, and attempt.
• Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) are present.

Common Use Cases and Queries

Typical scenarios include producing student result extracts, validating grade finalization, and reconciling translated versus original outcome dates. A representative query retrieving translated outcomes for a student is:

• SELECT party_number, party_name, course_cd, unit_cd, grade, translated_grade, outcome_dt, translated_dt FROM igsfv_as_su_atmpt_outcomes WHERE party_number = :p_party_number AND translated_dt IS NOT NULL;
• Reporting finalized results: SELECT course_cd, unit_cd, grade, finalised_outcome_ind FROM igsfv_as_su_atmpt_outcomes WHERE finalised_outcome_ind = 'Y';
• Filtering by grading period: SELECT unit_cd, mark, grade, grading_period_cd FROM igsfv_as_su_atmpt_outcomes WHERE grading_period_cd = :p_period;

Because the view performs multiple outer joins and a function call, queries should be constrained by PERSON_ID or COURSE_CD where possible to control execution cost.