eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.IGS_PR_GEN_006 dependencies on IGS_PR_STDNT_PR_OU

Line 267: FROM IGS_PR_STDNT_PR_OU spo,

263: spo.duration,
264: spo.duration_type,
265: ci.start_dt,
266: sca.version_number
267: FROM IGS_PR_STDNT_PR_OU spo,
268: IGS_CA_INST ci,
269: IGS_EN_STDNT_PS_ATT sca
270: WHERE spo.person_id = p_person_id AND
271: spo.course_cd = p_course_cd AND

Line 281: cp_spo_duration_type IGS_PR_STDNT_PR_OU.duration_type%TYPE,

277: v_spo_rec c_spo_ci_sca%ROWTYPE;
278: CURSOR c_ci_ct_cs (
279: cp_prg_start_dt IGS_CA_INST.start_dt%TYPE,
280: cp_sca_version_number IGS_EN_STDNT_PS_ATT.version_number%TYPE,
281: cp_spo_duration_type IGS_PR_STDNT_PR_OU.duration_type%TYPE,
282: cp_spo_prg_cal_type IGS_PR_STDNT_PR_OU.prg_cal_type%TYPE) IS
283: SELECT ci.cal_type,
284: ci.sequence_number
285: FROM IGS_CA_INST ci,

Line 282: cp_spo_prg_cal_type IGS_PR_STDNT_PR_OU.prg_cal_type%TYPE) IS

278: CURSOR c_ci_ct_cs (
279: cp_prg_start_dt IGS_CA_INST.start_dt%TYPE,
280: cp_sca_version_number IGS_EN_STDNT_PS_ATT.version_number%TYPE,
281: cp_spo_duration_type IGS_PR_STDNT_PR_OU.duration_type%TYPE,
282: cp_spo_prg_cal_type IGS_PR_STDNT_PR_OU.prg_cal_type%TYPE) IS
283: SELECT ci.cal_type,
284: ci.sequence_number
285: FROM IGS_CA_INST ci,
286: IGS_CA_TYPE ct,

Line 353: -- Select IGS_PR_STDNT_PR_OU record

349: ELSE
350: RETURN cst_current;
351: END IF;
352: END IF;
353: -- Select IGS_PR_STDNT_PR_OU record
354: OPEN c_spo_ci_sca;
355: FETCH c_spo_ci_sca INTO v_spo_rec;
356: IF c_spo_ci_sca%NOTFOUND THEN
357: CLOSE c_spo_ci_sca;

Line 418: -- 1. If there is an IGS_PR_STDNT_PR_OU record linked to it

414: RETURN VARCHAR2 IS
415: gv_other_detail VARCHAR2(255);
416: BEGIN -- IGS_PR_get_sprc_dsp
417: -- Determine if the IGS_PR_SDT_PR_RU_CK record should be displayed.
418: -- 1. If there is an IGS_PR_STDNT_PR_OU record linked to it
419: -- 2. If it is the most recent of passed or failed record
420: DECLARE
421: v_dummy VARCHAR2(1);
422: CURSOR c_spo IS

Line 424: FROM IGS_PR_STDNT_PR_OU

420: DECLARE
421: v_dummy VARCHAR2(1);
422: CURSOR c_spo IS
423: SELECT 'X'
424: FROM IGS_PR_STDNT_PR_OU
425: WHERE person_id = p_person_id AND
426: course_cd = p_course_cd AND
427: prg_cal_type = p_prg_cal_type AND
428: prg_ci_sequence_number = p_prg_ci_sequence_number AND

Line 463: -- 1. Check for IGS_PR_STDNT_PR_OU records

459: p_progression_rule_cat IS NULL OR
460: p_pra_sequence_number IS NULL THEN
461: RETURN 'N';
462: END IF;
463: -- 1. Check for IGS_PR_STDNT_PR_OU records
464: OPEN c_spo;
465: FETCH c_spo INTO v_dummy;
466: IF c_spo%FOUND THEN
467: CLOSE c_spo;

Line 978: p_new_spo_person_id IGS_PR_STDNT_PR_OU.person_id%TYPE,

974: p_new_course_cd IGS_PR_RU_APPL.crv_course_cd%TYPE,
975: p_new_version_number IGS_PR_RU_APPL.crv_version_number%TYPE,
976: p_new_org_unit_cd IGS_PR_RU_APPL.ou_org_unit_cd%TYPE,
977: p_new_ou_start_dt IGS_PR_RU_APPL.ou_start_dt%TYPE,
978: p_new_spo_person_id IGS_PR_STDNT_PR_OU.person_id%TYPE,
979: p_new_spo_course_cd IGS_PR_STDNT_PR_OU.course_cd%TYPE,
980: p_new_spo_sequence_number IGS_PR_STDNT_PR_OU.sequence_number%TYPE,
981: p_call_again BOOLEAN,
982: p_message_name IN OUT NOCOPY IGS_PR_S_SCRATCH_PAD.MESSAGE_NAME%TYPE)

Line 979: p_new_spo_course_cd IGS_PR_STDNT_PR_OU.course_cd%TYPE,

975: p_new_version_number IGS_PR_RU_APPL.crv_version_number%TYPE,
976: p_new_org_unit_cd IGS_PR_RU_APPL.ou_org_unit_cd%TYPE,
977: p_new_ou_start_dt IGS_PR_RU_APPL.ou_start_dt%TYPE,
978: p_new_spo_person_id IGS_PR_STDNT_PR_OU.person_id%TYPE,
979: p_new_spo_course_cd IGS_PR_STDNT_PR_OU.course_cd%TYPE,
980: p_new_spo_sequence_number IGS_PR_STDNT_PR_OU.sequence_number%TYPE,
981: p_call_again BOOLEAN,
982: p_message_name IN OUT NOCOPY IGS_PR_S_SCRATCH_PAD.MESSAGE_NAME%TYPE)
983: RETURN NUMBER

Line 980: p_new_spo_sequence_number IGS_PR_STDNT_PR_OU.sequence_number%TYPE,

976: p_new_org_unit_cd IGS_PR_RU_APPL.ou_org_unit_cd%TYPE,
977: p_new_ou_start_dt IGS_PR_RU_APPL.ou_start_dt%TYPE,
978: p_new_spo_person_id IGS_PR_STDNT_PR_OU.person_id%TYPE,
979: p_new_spo_course_cd IGS_PR_STDNT_PR_OU.course_cd%TYPE,
980: p_new_spo_sequence_number IGS_PR_STDNT_PR_OU.sequence_number%TYPE,
981: p_call_again BOOLEAN,
982: p_message_name IN OUT NOCOPY IGS_PR_S_SCRATCH_PAD.MESSAGE_NAME%TYPE)
983: RETURN NUMBER
984: IS

Line 1607: v_spo_expiry_dt IGS_PR_STDNT_PR_OU.expiry_dt%TYPE;

1603: v_message_text1 VARCHAR2(255) DEFAULT NULL;
1604: v_message_text2 VARCHAR2(255) DEFAULT NULL;
1605: v_message_level VARCHAR2(10) DEFAULT NULL;
1606: v_encumbrance_type igs_pr_ou_type.encumbrance_type%TYPE;
1607: v_spo_expiry_dt IGS_PR_STDNT_PR_OU.expiry_dt%TYPE;
1608: v_unresolved_clash BOOLEAN DEFAULT FALSE;
1609: v_clash_type VARCHAR2(10);
1610: v_expire BOOLEAN;
1611: v_warning BOOLEAN;

Line 1615: FROM IGS_PR_STDNT_PR_OU spo,

1611: v_warning BOOLEAN;
1612: v_dummy VARCHAR2(1);
1613: CURSOR c_spo1 IS
1614: SELECT pot.encumbrance_type
1615: FROM IGS_PR_STDNT_PR_OU spo,
1616: igs_pr_ou_type pot
1617: WHERE spo.person_id = p_person_id AND
1618: spo.course_cd = p_course_cd AND
1619: spo.sequence_number = p_spo_sequence_number AND

Line 1626: FROM IGS_PR_STDNT_PR_OU spo,

1622: SELECT spo.sequence_number,
1623: spo.progression_outcome_type,
1624: spo.expiry_dt,
1625: pot.encumbrance_type
1626: FROM IGS_PR_STDNT_PR_OU spo,
1627: igs_pr_ou_type pot
1628: WHERE spo.person_id = p_person_id AND
1629: spo.course_cd = p_course_cd AND
1630: spo.sequence_number <> p_spo_sequence_number AND

Line 1659: cp_spo_sequence_number IGS_PR_STDNT_PR_OU.sequence_number%TYPE) IS

1655: SELECT s_encmb_effect_type
1656: FROM igs_fi_enc_dflt_eft etde
1657: WHERE etde.encumbrance_type = cp_encumbrance_type);
1658: CURSOR c_spo_expire (
1659: cp_spo_sequence_number IGS_PR_STDNT_PR_OU.sequence_number%TYPE) IS
1660: SELECT spo.*, spo.ROWID
1661: FROM IGS_PR_STDNT_PR_OU spo
1662: WHERE spo.person_id = p_person_id AND
1663: spo.course_cd = p_course_cd AND

Line 1661: FROM IGS_PR_STDNT_PR_OU spo

1657: WHERE etde.encumbrance_type = cp_encumbrance_type);
1658: CURSOR c_spo_expire (
1659: cp_spo_sequence_number IGS_PR_STDNT_PR_OU.sequence_number%TYPE) IS
1660: SELECT spo.*, spo.ROWID
1661: FROM IGS_PR_STDNT_PR_OU spo
1662: WHERE spo.person_id = p_person_id AND
1663: spo.course_cd = p_course_cd AND
1664: spo.sequence_number = cp_spo_sequence_number
1665: FOR UPDATE NOWAIT;

Line 1684: cp_spo_sequence_number IGS_PR_STDNT_PR_OU.sequence_number%TYPE,

1680: cst_rstr_at_ty,
1681: cst_rstr_ge_cp,
1682: cst_rstr_le_cp);
1683: CURSOR c_pen_pee (
1684: cp_spo_sequence_number IGS_PR_STDNT_PR_OU.sequence_number%TYPE,
1685: cp_spo_expiry_dt IGS_PR_STDNT_PR_OU.expiry_dt%TYPE) IS
1686: SELECT pee.s_encmb_effect_type
1687: FROM IGS_PE_PERS_ENCUMB pen,
1688: IGS_PE_PERSENC_EFFCT pee

Line 1685: cp_spo_expiry_dt IGS_PR_STDNT_PR_OU.expiry_dt%TYPE) IS

1681: cst_rstr_ge_cp,
1682: cst_rstr_le_cp);
1683: CURSOR c_pen_pee (
1684: cp_spo_sequence_number IGS_PR_STDNT_PR_OU.sequence_number%TYPE,
1685: cp_spo_expiry_dt IGS_PR_STDNT_PR_OU.expiry_dt%TYPE) IS
1686: SELECT pee.s_encmb_effect_type
1687: FROM IGS_PE_PERS_ENCUMB pen,
1688: IGS_PE_PERSENC_EFFCT pee
1689: WHERE pen.person_id = p_person_id AND

Line 2153: IGS_PR_STDNT_PR_OU_PKG.UPDATE_ROW(

2149: BEGIN
2150: OPEN c_spo_expire (
2151: v_spo2_rec.sequence_number);
2152: FETCH c_spo_expire INTO v_spo_expire_rec;
2153: IGS_PR_STDNT_PR_OU_PKG.UPDATE_ROW(
2154: X_ROWID => v_spo_expire_rec.ROWID,
2155: X_PERSON_ID => v_spo_expire_rec.PERSON_ID,
2156: X_COURSE_CD => v_spo_expire_rec.COURSE_CD,
2157: X_SEQUENCE_NUMBER => v_spo_expire_rec.SEQUENCE_NUMBER,

Line 2498: -- IGS_PR_STDNT_PR_OU that has been approved. The encumbrance details

2494: gcst_sysdate CONSTANT DATE := TRUNC(SYSDATE);
2495: gcst_sysdatetime CONSTANT DATE := SYSDATE;
2496: BEGIN -- IGS_PR_upd_spo_pen
2497: -- Maintain the person encumbrance structure related to a
2498: -- IGS_PR_STDNT_PR_OU that has been approved. The encumbrance details
2499: -- resulting from spo detail are only maintainable through this routine, via
2500: -- changes through the progression screens. The routine also handles the
2501: -- removal of encumbrances if the outcome has been Cancelled/Removed.
2502: -- A database relationship exists between the IGS_PE_PERS_ENCUMB and

Line 2503: -- IGS_PR_STDNT_PR_OU from which it has resulted.

2499: -- resulting from spo detail are only maintainable through this routine, via
2500: -- changes through the progression screens. The routine also handles the
2501: -- removal of encumbrances if the outcome has been Cancelled/Removed.
2502: -- A database relationship exists between the IGS_PE_PERS_ENCUMB and
2503: -- IGS_PR_STDNT_PR_OU from which it has resulted.
2504: -- Note: If a student has multiple IGS_PR_STDNT_PR_OUs then they
2505: -- will result in separate IGS_PE_PERS_ENCUMB entries related accordingly.
2506: -- Overlap between encumbrance effects is possible and is resolved where
2507: -- required.

Line 2504: -- Note: If a student has multiple IGS_PR_STDNT_PR_OUs then they

2500: -- changes through the progression screens. The routine also handles the
2501: -- removal of encumbrances if the outcome has been Cancelled/Removed.
2502: -- A database relationship exists between the IGS_PE_PERS_ENCUMB and
2503: -- IGS_PR_STDNT_PR_OU from which it has resulted.
2504: -- Note: If a student has multiple IGS_PR_STDNT_PR_OUs then they
2505: -- will result in separate IGS_PE_PERS_ENCUMB entries related accordingly.
2506: -- Overlap between encumbrance effects is possible and is resolved where
2507: -- required.
2508: -- Note: the authorising person ID parameter is designed to be passed from

Line 2563: FROM IGS_PR_STDNT_PR_OU spo,

2559: spo.restricted_attendance_type,
2560: spo.expiry_dt,
2561: pot.encumbrance_type,
2562: att.closed_ind
2563: FROM IGS_PR_STDNT_PR_OU spo,
2564: igs_pr_ou_type pot,
2565: igs_en_atd_type att
2566: WHERE spo.person_id = p_person_id AND
2567: spo.course_cd = p_course_cd AND