One of the very first steps when both using and/or customizing SAP SLcM (Student Lifecycle Management) is to work the Academic Structure (
de: Akademische Struktur). It represents the structural organization (
de: Aufbauorganisation) of the entire SAP System. In SLcM, it is used to map the study programs and formal curriculums into their digital representations (
de: Abbildung von Prüfungordnungen). And typically looks like this:
 |
| Academic Structure (de: Akademische Struktur) |
The above shows some Bachelor Thesis that also includes a Seminar ("VS Bachelorarbeit Betriebswirtschaft", SAP object type D). Now let's say the work load/teaching activity credits for that seminar change, beginning with the upcoming Fall term (
de: neue Prüfungsordnungsversion) - a common scenario in all Higher Education institutions.
In most software systems, you'd be required to create a new object of some kind that is then used from the upcoming Fall term on.
In SLcM, you can just be awesome: create an additional work load/teaching activity (SAP-terminology: additional infotype), dated with the valid time period. The previous adjust itself automatically. And this typically looks like this (relevant date here: Oct 1st, 2011):
 |
| timeline-validity awesomness |
Now, whenever you work with any activity related to that seminar prior to 01.10.2011, the system calculates with 9 units. From there on, it uses the 10 units that are valid from October first.
No fuzz, no hassle, nice data model, that simple.
Oh, and did I mention that this works with any kind of objects in SLcM?
Organizational Units, Study Programs, Exams, Modules, Export- and Import-Associations (
de: Verknüpfungen), ... etc ?
So you can pretty easily map all past, present and future changes in study programs (
de: Prüfungsordnungs-Änderungen) at any time?
Without jeopardizing exam results, score bookings, calculations or reports (
de: Auswertungen)? All audit-proof (
de: revisionssicher)?
I didn't mention all this? Really?
Well, now you know ;)
