Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Overview


Objective

upon Completion of this KB the user will be able to produce and validate the Past Course Completions File (PS) ready for import into HEPCAT

Assumptions

  • The user has Admin access 
  • The user has entered required data to generate the Campus File
  • The user has an understanding of Element numbers required in HEPCAT reporting / Paradigm
  • The user has access to HEPCAT to import and validate the HEIMS reports

Key terms and concepts


Field NameBrief Overview
Institution*Select the Institution(s) that the report is being submitted for. If Multiple select as many as required
  • HEIMS Report (Year Students Completed)
From the Drop down field select the Collection Year that the report is for
  • Submission Year (Year Students Completed)
Enter the Year the submission is for e.g 2018
Period NumberSelect the Period Number. January 1 to June 30 is Period 1 and July 1 to December 31 is Period 2
Submission Number*Within Each Period multiple submissions can be made, select the submission number next in the sequence remembering that the first one for each new year is 1. A Submission will be allocated a number from 3 pieces of data e.g. 2018 1.2 - meaning 2018, period one submission 2
Course Level*
  • Elicos
  • Postgraduate
  • Undergraduate
  • VET
  • Secondary
  • Non-Award
Course Enrolment Status*
  • Applied
  • Completed
  • Confirmed
  • Deferred
  • Enrolled
  • Exempt
  • Incomplete
  • Internal Offered
  • Provisional
  • Withdrawn
HEIMS Start Date*
HEIMS End Date*
HEIMS Revision NumberSelect this number only if producing a PS revision file
Output to DESTPAC (Do not Tick for HEPCAT)
Report Mode
  • Non-Interactive Mode (Files will be emailed)
  • On Screen Summary Mode
  • On Screen Full details Mode


Implications

This section of the KB will explain what potential issues or problems users can come across and why they happen.


Workflow

This section explains the exact workflow of how a task/process should be conducted.

It is recommended to divide the task into sub headings.


Further reading

This section of the KB contains links to any further related information that would be helpful for the purpose  understanding this topic.



  • No labels