CRSJ6010 - Approved Course Transfer

Overview
Summary
Job Detail
Notes

Overview

This job transfers approved Course information from the Curriculum Amendments and Proposals (CAPS) area to the Callista Course Structure and Planning (CRS) subsystem.

A course proposal is ready for transfer when it has been approved and has a System Transfer Status of READY or ERROR. (Records with ERROR will be processed again to see if the issue has been fixed.)

As an outcome of this process: a new Course could be created, a new version of an existing Course could be created, or details of an existing Course version could be updated or deleted.

For a proposal that requests a course update, the job can update all appropriate fields that exist in the CRS subsystem except for the primary key of any table.

Note: Where a new course version is created that is based on an existing course version, the elements not specified in the proposal will be inherited from the course version on which the proposal is based, not necessarily the latest version of the course. When creating a new version of a course, it is recommended that it is based on the latest version of the course and that any data required from earlier versions, be imported into the proposal.

Verification of all existing course business rules occurs and if a business rule fails when validating, then a System Transfer Status of ERROR is recorded for the affected proposal. When a validation fails, the transfer job rolls back all Inserts, Updates and Deletes for the proposal and the processing moves onto any remaining approved proposals that are ready to transfer.

To assist in identifying errors raised during the transfer, all errors are logged into the system extract logs. More information can be accessed through Generate Extract XML File (GENJ1000), which retrieves the error messages from the log.

A successful transfer moves the proposal to a COMPLETE status. Once the job finishes, a summary in the run log will appear noting how many successful Inserts, Updates and Deletes were transferred and the number of errors that occurred.

There are no parameters for this job. It can be run in Immediate or Scheduled mode, but it is recommended that this job is run as an overnight process.

Return to Top

Summary

This is a high level summary of the actions performed by this job.

Create an S_EXTRACT record where all errors will be logged.
Check that the required system data is present.
Determine the proposals to transfer.
For each proposal, determine the data to be transferred.
For each proposal, insert, update or delete data in Course tables.
Update the status of the proposal.
Generate the completion message in the run log.

Return to Top

Job Detail

The following provides a more detailed view of the processing required to transfer approved course proposal information from the Course Proposals to the Callista Course Structure and Planning subsystem.

Note: This job calls the package CRSK_PRC_CAPS_CRS_DATA which extracts and transfers each of the fields from the Proposals (PAA) subsystem into the CRS subsystem.

1. Insert into S_EXTRACT Table

A record is inserted into the s_extract table, as this is the parent table to s_extract_record where all errors will be logged. The parameters to be inserted are:

s_extract_type = PRPSL-CRV
key = p_request_job_run_id
request_job_run_id = p_request_job_run_id
creation_dt = today

2. Check for Required System Data

Check that the required system transfer statuses and system proposal outcomes have been defined.

System Proposal Outcomes - NEW-CRS, NEW-CRS-V, UPD-CRS-V, NO-TRF-CRS, and System Transfer Statuses - ERROR, READY, COMPLETE must be defined for this job to transfer proposals, if not, the job will not proceed.

3. Determine the Proposals to Transfer

For a proposal to be transferred: the System Proposal Instance Status must be APPROVED, Proposal Transfer Status must be READY or ERROR and the Proposal Type must have a System Proposal Type of COURSE, but the System Proposal Outcome Type must not be CRS-POC.

4. For Each of the Proposals Identified, Transfer the Data into the CRS Subsystem

a). Course and Course Version Details

Select all the data from the proposal to be inserted into the COURSE_VERSION table.
Note: there may be multiple Course Versions in the one proposal.
If a new course is being created, the version number is incremented.
If it is a version update, use the version number defined in the proposal instance item. If a new version is being created, set the Expiry Date for the existing ACTIVE version of the course version to yesterday's date.
If the installed sector is not CROSS and the S_SECTOR_CD field is NULL, then set this to the installed sector.
If this is a new course, insert a record into the COURSE table.
Otherwise update the changed fields in the COURSE_VERSION record.
If required, delete the COURSE_VERSION record. If this course version is the only course version for the course, then delete the COURSE record.
If a new version of the course version is being created, the course version related data is rolled over into the new version.

b). Other Course Details

Use this table to determine if the data in each section below should be inserted, updated or deleted.

System Proposal Outcome	Insert (Element)	Update (Item)	Delete (Element)	Action
NEW-CRS	Any	Any	N	Insert and validate.
NEW-CRS	N	N	Y	Ignore (Do not Insert).
NEW-CRS-V	N	N	N	For CRS and CRV data the record will need to be inserted. All other data will be rolled over.
NEW-CRS-V	Y	N	N	Insert and validate (new data).
NEW-CRS-V	N	Y	N	Update and validate (update existing data).
NEW-CRS-V	N	N	Y	Update and validate (delete existing data).
NEW-CRS-V	Y	N	Y	Ignore (new data entered but now deleted)(a).
UPD-CRS-V	N	N	N	Context information, don't validate as not inserting.
UPD-CRS-V	Y	N	N	Insert and validate (new data).
UPD-CRS-V	N	Y	N	Update and validate (update existing data).
UPD-CRS-V	N	N	Y	Delete and validate (delete existing data).
UPD-CRS-V	Y	N	Y	Ignore (new data entered but now deleted).
NEW-USRDEF	Any	Any	Any	Not transferred.

c). Transfer Process

Select all the data from the proposal for the relevant table(s).
Determine if the data should be inserted, updated or deleted (according to the table above).
Test all related validations. If an error occurs log the error to the s_extract_record.
Insert or delete where allowed, and if updating the record, only update the changed fields.

The following data may be involved in the transfer process:

Alternative Exits - ALTERNATIVE_EXIT table
Course Awards - COURSE_AWARD, COURSE_AWARD_OWNERSHIP and COURSE_AWARD_STATEMENT tables
Course Categories - COURSE_CATEGORISATION table
Course Groups - COURSE_GROUP_MEMBER table
Default Milestones - DFLT_MILESTONE_SET table
Fields of Study - COURSE_FIELD_OF_STUDY table
Funding Source Restriction - FUNDING_SOURCE_RESTRICTION table
Course Ownership - COURSE_OWNERSHIP table
Course Reference Codes - COURSE_REFERENCE_CD table
Course Version Rules - COURSE_VERSION_RULE table
Type of Place - CRV_TYPE_OF_PLACE table
Course Version Notes - COURSE_VERSION_NOTE table
Course Offerings - COURSE_OFFERING table
Pattern of Study - PATTERN_OF_STUDY table
Pattern of Study Period - PATTERN_OF_STUDY_PERD table
Pattern of Study Unit - PATTERN_OF_STUDY_UNIT table
Course Offering Instances COURSE_OFFERING_INSTANCE table
Course Offering Patterns - COURSE_OFFERING_PATTERN table
Course Offering Pattern Applicant Portal Admission Period Override - COP_AP_ADMISSION_PERIOD_OVRD table
Course Offering Options - COURSE_OFFERING_OPTION table
Course Offering Option Note - COURSE_OFFERING_OPT_NOTE table
Course Offering Option Admissions Calendar Type Restriction - COO_ADM_CAL_TYPE_RSTRN table
Course Offering Option Admission Categories - CRS_OFF_OPTION_ADM_CAT table
Course Offering Option Admission Category Unit Set Restrictions - COO_ADM_CAT_UNIT_SET table
Course Entry Point Reference Codes - COURSE_ENTRY_POINT_REF_CD table
Course Offering Option Unit Sets - CRS_OFF_OPTION_UNIT_SET table
Course Offering Option Unit Set BAPs - BUS_ACTVTY_PRCS_TBL_REF and BUS_SCTVTY_PRCS_PE_PIG tables
Course Offering Option BAPs - BUS_ACTVTY_PRCS_TBL_REF and BUS_SCTVTY_PRCS_PE_PIG tables
Course Offering Unit Sets - COURSE_OFFERING_UNIT_SET table
Course Offering Unit Set Relationships - CRS_OFF_UNIT_SET_RELATIONSHIP table
Course Offering Unit Set BAPs - BUS_ACTVTY_PRCS_TBL_REF and BUS_SCTVTY_PRCS_PE_PIG tables
Course BAPs - BUS_ACTVTY_PRCS_TBL_REF and BUS_SCTVTY_PRCS_PE_PIG tables
Course Version Course Structures - COURSE_VERSION_STRUCTURE table
Course Volume of Learning - CRV_VOL_OF_LEARNING table
Course Learning Outcomes - LEARNING_OUTCOME table
Course Outcome Framework - LEARNING_OUTCOME_RELATIONSHIP table

Transfer of Course User-Defined Data

User defined data for each element (listed above), is transferred into the COURSE_USER_DEF_DATA_STRUCTURE and COURSE_USER_DEF_DATA tables in the Course Structure and Planning (CRS) subsystem and referenced to the course. This data may be transferred back to the PAA subsystem in the case where a new proposal is created in PAA that is based on the same existing course.

Each record in the two tables referred to above, has a key corresponding to the System Table to which the record is related, for example a user defined field that has been added to a Course Offering Option will have a key that includes COURSE_CD, VERSION_NUMBER, CAL_TYPE, LOCATION_CD.

The process for transferring user-defined data from PAA to CRS is as follows:

(If the record does not already exist) Create a new record in the COURSE_USER_DEF_DATA_STRUCTURE table and assign it a Primary Key from the Proposal Instance Element.

CUDDS Column (Primary Key) values:	Data Source from Proposals:
STRUCTURE_SEQUENCE_NUMBER	PROPOSAL_INSTANCE_ITEM.PROPOSAL_INSTANCE_ ELEMENT_SEQUENCE_NUMBER
PROPOSAL_ELEMENT_CD	PROPOSAL_INSTANCE_ITEM.PROPOSAL_ELEMENT_CD
SUP_STRUCTURE_SEQUENCE_NUMBER	If the PROPOSAL_INSTANCE_ITEM.PROPOSAL_ELEMENT_CD is a User Defined element, then V_SUP_STRUCTURE_SEQUENCE
SUP_PROPOSAL_ELEMENT_CD	If the PROPOSAL_INSTANCE_ITEM.PROPOSAL_ELEMENT_CD is a User Defined element, then V_SUP_PROPOSAL_ELEMENT_CD
STRUCTURE_LABEL	PROPOSAL_ELEMENT.MENU_TITLE

If there is an existing record in the table then the current record is end-dated (for History purposes) and a new record is created with a Sequence Number and Primary Key values pointing to the new data in Proposals. (This applies to both tables referred to above.)
A new user-defined record is created (in the COURSE_USER_DEF_DATA table) based on the information provided in the Proposal:

CUDD Column (Primary Key) values:	Data Source from Proposals:
COURSE_CD	V_COURSE_VERSION_REC.COURSE_CD
VERSION_NUMBER	V_COURSE_VERSION
PROPOSAL_ELEMENT_CD	PROPOSAL_INSTANCE_ITEM.PROPOSAL_ELEMENT_CD
PROPOSAL_ITEM_CD	PROPOSAL_INSTANCE_ITEM.PROPOSAL_ITEM_CD
STRUCTURE_SEQUENCE_NUMBER	V_STRUCTURE_SEQUENCE_NUMBER
SEQUENCE_NUMBER	COURSE_USER_DEF_DATA_SEQUENCE_NUMBER.nextval, new sequential number to be created
EFFECTIVE _START_DT	SYSDATE
FIELDS 1 to 10	Field values are set depending on the column mappings between the CRS table Primary Key columns, FIELDS 1 to 10 and TABLE_NAME. See the Field Values table below for these values.
EFFECTIVE_END_DT	NULL
S_FIELD_TYPE	S_PROPOSAL_ITEM.S_FIELD_TYPE
PROMPT	NVL(PROPOSAL_ITEM.OVERRIDE_PROMPT, S_PROPOSAL_ITEM.PROMPT)
FIELD_LENGTH	S_PROPOSAL_ITEM.FIELD_LENGTH
CHARACTER_FIELD	PROPOSAL_INSTANCE_ITEM.CHARACTER_FIELD
NUMBER_FIELD	PROPOSAL_INSTANCE_ITEM.NUMBER_FIELD
DATE_FIELD	PROPOSAL_INSTANCE_ITEM.DATE_FIELD
CLOB_FIELD	PROPOSAL_INSTANCE_ITEM.CLOB_FIELD

Field Values:

Source (System Element Code):	Field 1	Field 2	Field 3	Field 4	Field 5	Field 6	Field 7	Field 8-10	TABLE_ NAME
ALTEXIT	EXIT_ COURSE _CD	NULL	NULL	NULL	NULL	NULL	NULL	NULL	ALTERNATIVE _EXIT
CAS	AWARD _CD	SEQUEN CE_ NUMBER	NULL	NULL	NULL	NULL	NULL	NULL	COURSE _AWARD_ STATEMENT
CEPRC	CAL_TYPE	LOCATION _CD	ATTEND ANCE _MODE	ATTEND ANCE _TYPE	REFER ENCE_ CD_TYPE	SEQUENCE _NUMBER	NULL	NULL	COURSE_ ENTRY_ POINT_ REF_CD
CO	CAL_TYPE	NULL	NULL	NULL	NULL	NULL	NULL	NULL	COURSE_ OFFERING
COI	CAL_TYPE	CI_ SEQUEN CE_ NUMBER	NULL	NULL	NULL	NULL	NULL	NULL	COURSE_ OFFERING _INSTANCE
COO	CAL_TYPE	LOCATION _CD	ATTEND ANCE _MODE	ATTEND ANCE _TYPE	NULL	NULL	NULL	NULL	COURSE_ OFFERING _OPTION
COOAC	CAL_TYPE	LOCATION _CD	ATTEND ANCE _MODE	ATTEND ANCE _TYPE	ADMISS ION_ CAT	NULL	NULL	NULL	CRS_OFF _OPTION _ADM_CAT
COOACTR	ACAD_ CAL_ TYPE	LOCATION _CD	ATTEND ANCE _MODE	ATTEND ANCE _TYPE	ADM_ CAL_ TYPE	NULL	NULL	NULL	COO_ADM _CAL_TYPE _RSTRN
COOACUS	CAL_TYPE	LOCATION _CD	ATTEND ANCE _MODE	ATTEND ANCE _TYPE	ADMISS ION_ CAT	UNIT_ SET_CD	US_ VERSION _NUMBER	NULL	COO_ ADM_CAT _UNIT_SET
COOBAP	CAL_TYPE	LOCATION _CD	ATTEND ANCE _MODE	ATTEND ANCE _TYPE	BAPPP. BUSINESS _ACTIVITY _PROCESS _CD	BAPPP. BAPTR_ SEQUENCE _NUMBER	BAPPP. SEQUEN CE_ NUMBER	NULL	BAP
COON	CAL_TYPE	LOCATION _CD	ATTEND ANCE _MODE	ATTEND ANCE _TYPE	REFER ENCE _NUMBER	NULL	NULL	NULL	COURSE _OFFERING _OPT_NOTE
COOUS	CAL_TYPE	LOCATION _CD	ATTEND ANCE _MODE	ATTEND ANCE _TYPE	REFER ENCE _NUMBER	NULL	NULL	NULL	CRS_ OFF_ OPTION _UNIT_SET
COOUSBAP	CAL_TYPE	LOCATION _CD	ATTEND ANCE _MODE	ATTEND ANCE _TYPE	UNIT_ SET_CD	US_ VERSION _NUMBER	BAPPP. BUSINESS _ACTIVITY _PROCESS _CD	Field 8: BAPPP. BAPTR_ SEQUEN CE_ NUMBER Field 9: BAPPP. SEQUEN CE_ NUMBER Field 10: NULL	BAP
COP	CAL_TYPE	CI_SEQUEN CE_ NUMBER	LOCA TION _CD	ATTEND ANCE _MODE	ATTEND ANCE _TYPE	NULL	NULL	NULL	COURSE_ OFFERING _PATTERN
COPAPAPO	ACAD _CAL_ TYPE	ACAD_CI _SEQUEN CE_ NUMBER	LOCA TION _CD	ATTAN DANCE _MODE	ATTEND ANCE _TYPE	ADM_CI SEQUENCE _NUMBER	NULL	NULL	COP_AP_ ADMISSION _PERIOD _OVRD
COURSE	NULL	NULL	NULL	NULL	NULL	NULL	NULL	NULL	COURSE_ VERSION
COUS	CAL_TYPE	UNIT _SET_CD	US_ VERSION_ NUMBER	NULL	NULL	NULL	NULL	NULL	COURSE_ OFFERING _UNIT_SET
COUSBAP	CAL_TYPE	UNIT_ SET_CD	US_ VERSION_ NUMBER	BAPPP. BUSINESS _ACTIVITY _PROCESS _CD	BAPPP. BAPTR_ SEQUEN CE_ NUMBER	BAPPP. SEQUENCE _NUMBER	NULL	NULL	BAP
COUSR	CAL_TYPE	SUP_ UNIT_ SET_CD	SUP_US _VERSION _NUMBER	SUB_ UNIT_ SET_CD	SUB_US_ VERSION _NUMBER	NULL	NULL	NULL	CRS_OFF _UNIT _SET_ RELATION SHIP
CRSAWARD	AWARD _CD	NULL	NULL	NULL	NULL	NULL	NULL	NULL	COURSE _AWARD
CRSAWARDOW	AWARD _CD	ORG_ UNIT_CD	OU_ START _DT	NULL	NULL	NULL	NULL	NULL	COURSE _AWARD_ OWNERSHIP
CRSCAT	COURSE _CAT	NULL	NULL	NULL	NULL	NULL	NULL	NULL	COURSE_ CATEGOR ISATION
CRSDFLTMIL	MILESTONE _TYPE	ATTEND ANCE _TYPE	SEQUEN CE_ NUMBER	NULL	NULL	NULL	NULL	NULL	DFLT_ MILESTONE _SET
CRSFLDSTDY	FIELD_ OF_ STUDY	NULL	NULL	NULL	NULL	NULL	NULL	NULL	COURSE _FIELD_ OF_STUDY
CRSFUNDSRC	FUNDING _SOURCE	NULL	NULL	NULL	NULL	NULL	NULL	NULL	FUNDING _SOURCE _RESTRIC TION
CRSGRPMEM	COURSE _TROUP _CD	NULL	NULL	NULL	NULL	NULL	NULL	NULL	COURSE _GROUP _MEMBER
CRSOWN	ORG_ UNIT_CD	OU_ START _DT	NULL	NULL	NULL	NULL	NULL	NULL	COURSE _OWNER SHIP
CRSREFCD	REFER ENCE _CD_ TYPE	REFER ENCE _CD	NULL	NULL	NULL	NULL	NULL	NULL	COURSE_ REFER ENCE_CD
CRVBAP	BAPPP. BUSINESS _ACTIVITY PROCESS _CD	BAPPP. SEQUEN CE_ NUMBER	BAPPP. SEQUEN CE_ NUMBER	NULL	NULL	NULL	NULL	NULL	BAP
CRVNOTES	REFER ENCE_ NUMBER	NULL	NULL	NULL	NULL	NULL	NULL	NULL	COURSE_ VERSION _NOTE
CRVRULE	NULL	NULL	NULL	NULL	NULL	NULL	NULL	NULL	COURSE_ VERSION
CRVTOP	TYPE_ OF_ PLACE _CD	SEQUEN CE_ NUMBER	NULL	NULL	NULL	NULL	NULL	NULL	CRV_ TYPE _OF_ PLACE
POS	CAL_ TYPE	SEQUEN CE_ NUMBER	NULL	NULL	NULL	NULL	NULL	NULL	PATTERN _OF_ STUDY
POSP	CAL_ TYPE	POS_ SEQUEN CE_ NUMBER	SEQUEN CE_ NUMBER	NULL	NULL	NULL	NULL	NULL	PATTERN _OF_ STUDY _PERD
POSU	CAL_ TYPE	POS_ SEQUEN CE_ NUMBER	POSP_ SEQUEN CE_ NUMBER	SEQUENCE _NUMBER	NULL	NULL	NULL	NULL	PATTERN _OF_ STUDY_ UNIT
USER-CO	CAL_ TYPE	NULL	NULL	NULL	NULL	NULL	NULL	NULL	COURSE_ OFFERING
USER-COI	CAL_ TYPE	CI_SEQUEN CE_NUMBER	NULL	NULL	NULL	NULL	NULL	NULL	COURSE_ OFFERING _INSTANCE
USER-COO	CAL_ TYPE	LOCATION _CD	ATTEND ANCE _MODE	ATTEND ANCE _TYPE	NULL	NULL	NULL	NULL	COURSE_ OFFERING _OPTION
USER_ COOAC	CAL_ TYPE	LOCATION _CD	ATTEND ANCE _MODE	ATTEND ANCE _TYPE	ADMISS ION _CAT	NULL	NULL	NULL	CRS_OFF _OPTION ADM_CAT
USER_ COOUS	CAL_ TYPE	LOCATION _CD	ATTEND ANCE _MODE	ATTEND ANCE _TYPE	UNIT_ SET_CD	US_ VERSION _NUMBER	NULL	NULL	CRS_OFF _OPTION _UNIT_SET
USER _COUS	CAL_ TYPE	UNIT_ SET_CD	US_ VERSION_ NUMBER	NULL	NULL	NULL	NULL	NULL	COURSE_ OFFERING _UNIT_SET
USER_ CRS	NULL	NULL	NULL	NULL	NULL	NULL	NULL	NULL	COURSE_ VERSION
USER_ CRSAW	AWARD _CD	NULL	NULL	NULL	NULL	NULL	NULL	NULL	COURSE _AWARD

For a list of user-defined data for each core System Element, see Proposals Course System Data.

Deletion of User Defined Data in the CRS Subsystem:

If data is manually deleted from forms or tables in the CRS subsystem by an administrator, any associated child user-defined data is also deleted. User-defined data is located using the primary key value of its parent data. (Course user-defined data is stored in the COURSE_USER_DEF_DATA tables.)

Transfer of Course Structures

The job transfers the Course Structure (CRSW2600), Dependencies (CRSW2600) and Timelines (CRSW2650) associated with an approved Course Proposal Instance (PAAW1100) to the CRS subsystem, as follows:

Copies the Structure, Dependencies and all Timelines from the Course Proposal to create a new instance of each.
Assigns the Structure and Dependencies a unique Structure ID and Start Date (equal to the system date and time), thereby making them the latest instances in the CRS subsystem.
End-dates the existing Structure and Dependencies instances in the CRS subsystem, which are automatically replaced by the transferred Structure and Dependencies.
Assigns a Relationship Start Date (equal to the system date and time) to all Relationships and curriculum items belonging to the transferred Structure and Dependencies.
Transfers all Timelines belonging to the transferred Course Structure, and assigns them the new Structure ID.
The status of the transferred Timelines remains set to INCOMPLETE. Existing Timelines belonging to the previous instance of the Course Structure in the CRS subsystem are not altered.
If a 'Default' INCOMPLETE Timeline already exists in the CRS subsystem, the job makes the earliest created Timeline that was transferred, the Default Timeline. For more information, see Timeline Instructions.

5. For Each Proposal, Update the Proposal Status

If errors occur update the proposal instance transfer status to the value where the system value is ERROR and the system default ind is selected.

If no errors have occurred update the proposal instance transfer status to the value where the system value is COMPLETE and the system default ind is selected.

Once a NEW-CRS, NEW_CRS_V or UPD_CRS_V proposal has been successfully transferred, the new course version details are inserted into the PROPOSAL_INSTANCE_CRS_VERSION table. This is to help identify which proposal created which course version.

6. Generate Completion Message in Run Log

On completion of the job, the following details are recorded in the run log:

Started processing date and time
   Total records processed: NN (Successful: NN, Unsuccessful: NN)
   Total number of system extract records created: NN
   Completed processing date and time
Please query the system extract records for details of all errors and exceptions.
   System Log:
   - System Extract Type: PRPSL-CRV
   - System Extract Creation Date: date and time
Return to Top

Notes

Where the Proposal Type has a Single Core Instance and the Proposal Element is not multi-instance, the basic course details may be split across many elements. When the job is identifying data to be transferred for these proposals, the process searches over the whole proposal instance for the items with a system proposal element of COURSE.

The ability for the client to alter upper-case constraints should be taken into account. All fields in the upper-case constraint should have an upper clause added to the data when inserting or updating values. If the field is not in the upper-case constraint, then the data should be inserted as per the case entered into the proposal subsystem.

For the deletion of data, child records are deleted along with the parent record.

Proposal elements flagged for deletion (including user defined data flagged for deletion) are not transferred by the job.

An exception will occur when an attempt is made to update a locked record.

Course Plan data is not transferred.

Return to Top

Page last modified: 14 July, 2016 10:26 AM

History Information:

Release Version Project Change to Document

19.0 2106 - Learning Outcomes Added Course Learning Outcomes and Outcome Framework to Section 4c.

18.0.0.1 2087 - Entry Credit Added Volume of Learning to section 4c, list of data, and a new section for Course Structures.

17.0 1955 - Course Structures in PAA Added Course Structures to section 4c, list of data, and a new section for Course Structures.

17.0 1994 - New CS&P Data Added a new section for user defined data and related information.

16.1 1820 - Phase 3 Added new tables to the 'Transfer Process' section & a note to the Job Detail section.

15.0 1722 - 11g Upgrade Help page revised

13.0 1578 - CAPS 3 New Help page

Release Version	Project	Change to Document
19.0	2106 - Learning Outcomes	Added Course Learning Outcomes and Outcome Framework to Section 4c.
18.0.0.1	2087 - Entry Credit	Added Volume of Learning to section 4c, list of data, and a new section for Course Structures.
17.0	1955 - Course Structures in PAA	Added Course Structures to section 4c, list of data, and a new section for Course Structures.
17.0	1994 - New CS&P Data	Added a new section for user defined data and related information.
16.1	1820 - Phase 3	Added new tables to the 'Transfer Process' section & a note to the Job Detail section.
15.0	1722 - 11g Upgrade	Help page revised
13.0	1578 - CAPS 3	New Help page

CRSJ6010 - Approved Course Transfer

Table of Contents

Overview

Return to Top

Summary

Return to Top

Job Detail

1. Insert into S_EXTRACT Table

2. Check for Required System Data

3. Determine the Proposals to Transfer

4. For Each of the Proposals Identified, Transfer the Data into the CRS Subsystem

a). Course and Course Version Details

b). Other Course Details

c). Transfer Process

Transfer of Course User-Defined Data

5. For Each Proposal, Update the Proposal Status

6. Generate Completion Message in Run Log

Return to Top

Notes

Return to Top