| Top of ADM | Index | Table of Contents | Feedback | ![]() |
| Purpose | This job transfers Admission application reference data from the Callista SMS to Tribal Admissions. | ||
| Subsystem | Admissions | ||
| Normally Run By | Admissions Specialist | ||
| Anticipated Frequency | As required | ||
| Structure |
Block | Process Tribal Reference Data | |
| Tab | Parameters | ||
| Buttons | Find Course (ADMF1220) | ||
| In order to successfully transfer admission applications from Callista to Tribal Admissions, certain reference data must exist in Tribal Edge. The following Edge reference data will be populated by ADMJ9100 (other reference data must be entered manually in Tribal Edge):
The set of course related reference data to be transferred is controlled by the parameters selected. If only the Academic Year is selected, then reference data for all courses offered in that year will be transferred - except courses with a Course Category of NO-TRIBADM. Any applications for NO-TRIBADM courses are excluded from being transferred to Tribal Admissions by ADMJ9000. Institutions can further limit the reference data transferred by selecting parameters for Course Type, Responsible Organisational Unit, or a Course Code. Regardless of the parameters, all Countries, Institutions, Qualifications, Qualification Levels and Qualification Subjects will be included. Unit sets are defined as Routes in Tribal Admissions. The job will transfer unit sets per course where:
If any reference data is updated or deleted in Callista, the change will not be reflected in Edge. With the exception of Qualification Levels and Routes, Callista stores the Globally Unique Identifier (GUID) of each record transferred by ADMJ9100 and will not transfer any data for these records upon subsequent runs ( a message is displayed in the System Log). So, if the short title is changed in Callista for a course that already exists as an Admissions Programme in Edge, it will not be updated in Edge by ADMJ9100. However if a new course version is added to Callista, this will be transferred to Edge as a new Admissions Programme record by ADMJ9100. The transfer of reference data is one-way from Callista to Edge. So if reference data is updated or added in Edge, the change will not be brought back into Callista. If reference data is deleted in Edge and needs to be reinserted, the record’s GUID must first be deleted in the Callista Integration External ID database table before running ADMJ9100 so it is treated as a new record and transferred again. The processing of Admission applications via Tribal Admissions is described in Callista SMS and Tribal Admissions Integration. This job can only be run in scheduled mode. This job is accessed via the main menu. |
The Process Tribal Reference Data block contains:
Primary - Secondary Unit Sets
|
Rules/Notes: An Academic Period value must always be selected. If a Course Type is selected, then reference data related to all courses of that Course Type with an offering in that year will be transferred, unless limited by Responsible Org Unit or Course parameters. If a Responsible Org Unit is selected then reference data related to all courses in that year, for which that org unit is responsible will be transferred, unless limited by Course Type or Course parameters If a Course Code is selected, then only reference data related to that course will be transferred. The job will transfer single unit sets as individual route codes unless a Unit Set Category has been defined, whereby any unit sets with that category will also be transferred as a combination of two unit sets.However, where a single COO Unit Set record exists for a Course Version in CRSF1282, and ADMJ9100 is run with the Unit Set Category value corresponding to this COO Unit Set record, only single Route and Admissions Options records will be transferred as reference data (since a combination of two unit sets will not be possible). Only reference data for active records (e.g. courses with the status of ACTIVE) is transferred. With the exception of Qualification Levels and Routes, ADMJ9100 will only transfer new records (not updates) from Callista to Edge. |
At the end of the ADMJ9100 job processing, a summary is written to the job scheduler Run Log by JBSF5301.
Details and messages encountered during processing are written to the S_LOG_ENTRY table. These are identified by system log type TRIB-REF for ADMJ9100. The transfer state of each API and the details of each record will be displayed in the Text field. HTTP ‘409’ conflict errors will also be handled by displaying a message if the record has already been processed by ADMJ9100 and has an entry in the INTEGRATION_EXTERNAL_ID table so could not be resent.
This information can be extracted using the GENJ1100. Administrators may use this functionality to generate a report with details of the records processed.
In addition, the API request and response JSON output is stored in the S_WEB_SERVICE_ACCESS_LOG_PARM table. This excludes HTTP ‘409’ conflict errors, as they are already handled by the reference data procedure in the system log entry as described above. If required, this table can be queried to view and debug what was sent and received by the job.
The only mandatory parameter for the job is the Academic Period, which defaults to the current period. Institutions can then limit the reference data by Course Type, Responsible Organisational Unit, and/or a Course Code. For example:
| Parameters | Reference Data Transferred |
|---|---|
| Academic period =% Course Type = % Responsible Org Unit = % Course Code = % |
Job won't run because Academic Period is not selected. |
| Academic period =2022 Course Type = % Responsible Org Unit = % Course Code = % |
All reference data values for the 2022 Academic year are transferred. |
Academic period =2022 |
All reference data values for all Bachelors degrees offered in the 2022 Academic year are transferred. |
| Academic period =2022 Course Type = 10 Responsible Org Unit = 01 (Faculty of Business) Course Code = % |
All reference data values for all Bachelors degrees with that Responsible Org Unit for the 2022 Academic year are transferred. |
Academic period =2022 |
If M300 has Course Type 10 and Reponsible Org unit 01, then reference data values for the 2022 Course Offering Options for M300 are transferred. |
Academic period =2022 |
Reference data values for the 2022 offerings of M300 are transferred.(Course Type and Responsible Org Unit selections are higher level restrictions and are not really required). |
| Academic period =2022 Course Type = 1 (Higher Doctorate) Responsible Org Unit = % Course Code = M300 |
No data will be transferred if M300 is not of Course Type 1. |
The Unit Set Category parameter is only used if admission options need a combination of two unit sets (routes) for that unit set category.
Regardless of the parameters, all Countries, Institutions, Qualifications, Qualification Levels and Qualification Subjects will be included.
Last Modified on 17 August, 2022 12:50 PM
History Information
| Release Information | Project | Change to Document |
| 23.1.0.3, 24.0.0.1, 24.1.0.3 & 25.0.0.1 | 2535 - Callista Edge Admissions Integration | New job |