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.

DBA Data [Home] [Help] [Dependency Information]

VIEW: APPS.IGS_PR_PRG_RU_CA_TYPE_CI_V

Object Details

Object Name:	IGS_PR_PRG_RU_CA_TYPE_CI_V
Object Type:	VIEW
Owner:	APPS
FND Design Data:	IGS.IGS_PR_PRG_RU_CA_TYPE_CI_V
Subobject Name:
Status:	VALID

View Type

A public view which may be useful for custom reporting or other data
requirements.

Contains the progression calendar types that the progression ruler as it is applied to one of the allowable system elements, a program version, program type, org unit or individual student program attempt is to be tested. The testing can be conditional on a starting and number of tests allowing control. For example, a rule that can be tested after a year and only checked once. Calendar links can have a start and end instance regulating the period of time for that their application was current.

[View Source]

Columns

Name	Datatype	Length	Mandatory	Comments
PROGRESSION_RULE_CAT	VARCHAR2	(10)		The code of an institution-defined progression rule category. Each category of progression rules is mapped to one of the system rule call codes, for example, PRG-GPA, PRG-UFAIL, PRG-WAM and others. To maintain flexibility in the application of rules, institutions are advised to create one than one rule category for each system rule call code. Forexample, three categories of GPA calculation can be appropriate one category is used to represent standard program grade point average calculations applied to the majority of programs within theinstitution. A second category could be created for progression period GPA calculations. A third category can be applicable if a particular of the institution. Note: a progression rule has no application until to one of the set of system elements.
PRA_SEQUENCE_NUMBER	NUMBER	(6)		Describes the progression rule sequence number
PRG_CAL_TYPE	VARCHAR2	(10)		Describes the progression calendar type that the rule is to be applied
PRG_CI_SEQUENCE_NUMBER	NUMBER	(6)	Yes	The unique identifier for the calendar instance
START_EFFECTIVE_PERIOD	NUMBER	(2)		Records the number of the effective progression period for a given student program attempt that the progression rule is first tested in. If progression is evaluated twice a year, setting the start effective period to '2' will cause the rule to be tested for the first time at the end of a student's first year of study.
NUM_OF_APPLICATIONS	NUMBER	(2)		Describes the number of times the rule can be applied to any particular student. For example, setting the number to "2" restricts application of the rule to two progression periods.

Query Text

Cut, paste (and edit) the following text to query this object:


SELECT PROGRESSION_RULE_CAT
,      PRA_SEQUENCE_NUMBER
,      PRG_CAL_TYPE
,      PRG_CI_SEQUENCE_NUMBER
,      START_EFFECTIVE_PERIOD
,      NUM_OF_APPLICATIONS
FROM APPS.IGS_PR_PRG_RU_CA_TYPE_CI_V;

Dependencies

[top of page]

APPS.IGS_PR_PRG_RU_CA_TYPE_CI_V references the following:

APPS: IGS_CA_INST; IGS_CA_STAT; IGS_PR_RU_APPL; IGS_PR_RU_CA_TYPE_V

APPS.IGS_PR_PRG_RU_CA_TYPE_CI_V is referenced by following:

APPS: IGS_PR_SCA_PRG_RULE_APPL_V