Integration
Timetabling alongside PeopleSoft
Campus Solutions keeps the catalogue and the schedule in two layers and links them through the Associated Class. That link is the most useful thing on this page, because it is what tells you which sections have to be scheduled as a set.
Two layers, and the number that joins them
The Course Catalog describes the course once. The Schedule of Classes creates the offerings for a term. That much is familiar. What is specific to PeopleSoft is the Associated Class number: sections carrying the same one belong together, so a lecture and the laboratories that hang off it are a set rather than four independent events.
Get that into the extract and most of the timetable’s structure arrives with it. Leave it out and every section looks independent, which is how a student ends up enrolled in a lecture and a lab that meet at the same hour.
Which PeopleSoft object holds what
| PeopleSoft | What it holds | What the timetable does with it |
|---|---|---|
| Course Offering — Subject Area and Catalog Nbr | Which course | Becomes the course. |
| Class Section | One offering of it in a term | The thing being scheduled. |
| Associated Class | Which sections belong together | The set that must be scheduled as one. This is the row that carries the structure. |
| Component — Mode of Instruction | Lecture, Laboratory, Seminar | The teaching type most room rules are written against. |
| Class Nbr | The section’s identifier in the term | The key to match results back on. |
| Meeting Pattern | Days and times | The session. |
| Facility ID | Where it meets | The room, where PeopleSoft already holds one. |
| Enrollment Capacity | How many may enrol | The planned size a room has to hold. |
| Reserve Cap | Seats held for a particular population | Why a section that looks half full cannot take the group you wanted to put in it. |
| Combined Sections | Sections taught together | One event, several groups. See combining student groups. |
| Class Association Requisites | Requirements enforced at section level | Not timetabled, but it explains enrolment patterns that look wrong. |
| Term and Session | When | The academic year and the week range. |
| Academic Organization | Which department owns it | Which planner owns it. See faculty synchronisation. |
Which direction each thing travels
Into the timetable: the term’s section list with subject, catalog number, section, component, associated class, enrolment capacity and instructor. In PeopleSoft this is a report off Schedule of Classes or Update Sections of a Class, and it is one extract per term.
Out of the timetable: the meeting pattern and the Facility ID, matched back on Class Nbr. Whether that is written back into Campus Solutions or published beside it is your institution’s decision, and both are common.
The general form of this argument, without the object names, is in integrating your timetable with your SIS.
What we do not have, said plainly
There is no PeopleSoft connector in this product and no Oracle partnership. If your requirement is a certified Campus Solutions integration, we are not it.
What there is: Excel, CSV, XML and a documented REST API — importing data covers the 67 custom import codes and the 112-page reference, and SIS integration covers scheduled synchronisation.
GET https://wise-tt.com/api/v2/meta answers with the version and the endpoint list, with no token and no account, so your IT people can judge the REST API before anyone books a call.
Want to see this working?
Book a 45-minute online presentation and we will walk through it against your institution's own scheduling problem.