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


TABLE: IGS.IGS_PR_RU_CA_TYPE_ALL

Object Details
Object Name: IGS_PR_RU_CA_TYPE_ALL
Object Type: TABLE
Owner: IGS
FND Design Data: TableIGS.IGS_PR_RU_CA_TYPE_ALL
Subobject Name:
Status: VALID


IGS_PR_RU_CA_TYPE_ALL contains the progression calendar types, in the progression rule that 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 or end instance regulating the period of time for their application that was current.


Storage Details
Tablespace: TablespaceAPPS_TS_TX_DATA
PCT Free: 10
PCT Used:
Indexes
Index Type Uniqueness Tablespace Column
IGS_PR_RU_CA_TYPE_ALL_U1 NORMAL UNIQUE TablespaceAPPS_TS_TX_IDX ColumnPROGRESSION_RULE_CAT
ColumnPRA_SEQUENCE_NUMBER
ColumnPRG_CAL_TYPE
IGS_PR_RU_CA_TYPE_ALL_N1 NORMAL NONUNIQUE TablespaceAPPS_TS_TX_IDX ColumnPRG_CAL_TYPE
ColumnSTART_SEQUENCE_NUMBER
IGS_PR_RU_CA_TYPE_ALL_N2 NORMAL NONUNIQUE TablespaceAPPS_TS_TX_IDX ColumnPRG_CAL_TYPE
ColumnEND_SEQUENCE_NUMBER
Columns
Name Datatype Length Mandatory Comments
PROGRESSION_RULE_CAT VARCHAR2 (10) Yes The code of an institution-defined progression rule category. Each category of progression rules is mapped to one of the system rule call codes. To maintain flexibility in the application of rules, institutions are advised to create more than one rule category for each system rule call code. For example, 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 the institution. 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) Yes Describes the progression rule sequence number
PRG_CAL_TYPE VARCHAR2 (10) Yes Describes the calendar type of type progression in that the rule is to be applied
START_SEQUENCE_NUMBER NUMBER (6)
Sequence number of the context progression calendar instance
END_SEQUENCE_NUMBER NUMBER (6)
The sequence number of the context progression 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 betested 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.
CREATED_BY NUMBER (15) Yes Standard Who column
CREATION_DATE DATE
Yes Standard Who column
LAST_UPDATED_BY NUMBER (15) Yes Standard Who column
LAST_UPDATE_DATE DATE
Yes Standard Who column
LAST_UPDATE_LOGIN NUMBER (15)
Standard Who column
ORG_ID NUMBER (15)
Operating unit identifier
Query Text

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


SELECT PROGRESSION_RULE_CAT
,      PRA_SEQUENCE_NUMBER
,      PRG_CAL_TYPE
,      START_SEQUENCE_NUMBER
,      END_SEQUENCE_NUMBER
,      START_EFFECTIVE_PERIOD
,      NUM_OF_APPLICATIONS
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      ORG_ID
FROM IGS.IGS_PR_RU_CA_TYPE_ALL;

Dependencies

[top of page]

IGS.IGS_PR_RU_CA_TYPE_ALL does not reference any database object

IGS.IGS_PR_RU_CA_TYPE_ALL is referenced by following:

SchemaAPPS
SynonymIGS_PR_RU_CA_TYPE_ALL