53
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 1 Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e) Applies to: Student Lifecycle Management. For more information, visit the Business Process Expert homepage . Summary This document provides a basic overview on the new functionalities and enhancements delivered for Student Lifecycle Management for Business Suite 7i2010e Author: IBU Education and Research Company: SAP AG Created on: December 2010

Delta Overview Student Lifecycle Management EHP 5

Embed Size (px)

DESCRIPTION

SAP SLCM Delta overview

Citation preview

Page 1: Delta Overview Student Lifecycle Management EHP 5

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 1

Delta Overview Student Lifecycle

Management EHP 5 (BS7i2010e)

Applies to:

Student Lifecycle Management. For more information, visit the Business Process Expert homepage.

Summary

This document provides a basic overview on the new functionalities and enhancements delivered for Student Lifecycle Management for Business Suite 7i2010e

Author: IBU Education and Research

Company: SAP AG

Created on: December 2010

Page 2: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 2

Table of Contents

Technical Data .................................................................................................................................................... 3

1. Admissions Enhancements ......................................................................................................................... 3 1.1. Dynamic Regeneration of Admission Audit Profile ................................................................................................ 3

1.2. Intelligent Admissions Code .................................................................................................................................. 4

2. Degree Audit Enhancements ...................................................................................................................... 5

2.1. Conversion of Degree Audit BSP to Web Dynpro ................................................................................................. 5

2.2. Requirement Profile Maintenance ......................................................................................................................... 6

2.3. Online Audits ....................................................................................................................................................... 11

2.3.1.2. Advisor vs. Student Modes in the Online Audit application ........................................................................... 17

2.3.1.3. Academic Substitutions ................................................................................................................................. 17

2.4. Academic Substitutions: Standalone Application ................................................................................................ 21

2.5. Refresh Audit ...................................................................................................................................................... 22

2.6. Audit Runs and Module Plans ............................................................................................................................. 23

2.7. Assessments and Graduation ............................................................................................................................. 25

3. Event Planning .......................................................................................................................................... 25

3.1. Demand Planning Report .................................................................................................................................... 25

3.2. Time Independent Events ................................................................................................................................... 27

3.3 Multiple Instructors for Events w/o Schedule ....................................................................................................... 30

3.4 New Selection Method for Modules ..................................................................................................................... 32

3.5. New Relationship between Module Groups and Event Packages ...................................................................... 33

4. Student File ............................................................................................................................................... 35

4.1. New Search via Specialization ............................................................................................................................ 36

4.2 Navigation to Individual Work Details ................................................................................................................... 37

4.3. Navigation to the Appraisal Note ......................................................................................................................... 38

5. Self-Service Enhancements ...................................................................................................................... 39

5.1 Additional Services included in Student and Academic Advisor Roles ................................................................ 39

5.2. View Academic Work via Student Self Service ................................................................................................... 40

5.3. Graduation Self Service ...................................................................................................................................... 41

5.4. Additional Filter Provided for Course Registration .............................................................................................. 42

5.5. Module Group Search Provided in Course Registration...................................................................................... 43

5.6. Restrict Search in Course Registration ............................................................................................................... 44

6. Miscellaneous Enhancements ................................................................................................................. 45 6.1. Enhanced Pre-requisite Extended Booking Check ............................................................................................. 45

6.2. Co-requisite Check while Cancelling Module Booking ........................................................................................ 47

6.3. Enable “Waitlist Disabled” Flag at Module Level ................................................................................................. 47

6.4. Allow Un-offered Modules in Module Plan .......................................................................................................... 49

6.5. Maintain Fee Calculation Data via Mass Assignment ......................................................................................... 50

Page 3: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 3

Technical Data

Technical Name of Business Function: ISHERCM_EXT_IAP_2

Type of Business Function: Industry Business Function

Available as of: SAP Enhancement Package 5 for SAP ERP 6.0

ECC Software Component: IS-PS-CA

ECC Application Component: IS-HER-CM

Directly dependent Business Function requiring activation in addition:

o SAP Student Lifecycle Management: Implementation Accelerator

(ISHERCM_EXT_IAP)

o SAP Student Lifecycle Management: Implementation Accelerator Package

(ISHERCM_MAIN_IAP)

o SAP Student Lifecycle Management: User Interface for Academic Advisor (ISHERCM_UI_ADVISOR)

o SAP Student Lifecycle Management: User Interface for Student (ISHERCM_UI_STUDENT)

Prerequisites

o You have installed the software component IS-PS-CA. o You have activated the following business functions:

ISHERCM_MAIN_IAP ISHERCM_EXT_IAP ISHERCM_UI_ADVISOR ISHERCM_UI_STUDENT

1. Admissions Enhancements

1.1. Dynamic Regeneration of Admission Audit Profile

Description

Admission profiles can be created based upon the module group that the student chooses. Up to EHP 5 it has not been possible to re-generate an admission profile of an applicant via the Student File, e.g., in case of a transfer or if there has been a change of Specialization.

With EHP 5 users can now directly manage the generation of an admissions audit profile when an applicant's data has changed and the student wishes to change their specialization before being admitted to a program of study. In this case, the requirement profiles of the student must be updated according to their new specialization. Now you no longer have to manually delete the existing profile and create a new one but you can regenerate the admission profiles of a student dynamically.

The newly available re-generation of the Admission Audit Profile includes the following steps:

Deletion of Audit Profile (and existing Audit Runs) and

Creation of New Audit Profile.

You can now regenerate the admissions audit requirement profile for an admissions record directly from the admissions tab in the student file. Existing audit results for old profiles are automatically deleted.

Navigation path to access the new re-generation function: Transaction: PIQST00 (Student File) -> The new Icon Regenerate Profile for Audit can be found on the Admissions Tab.

Use case example for this scenario

Page 4: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 4

A student changes specialization (Major or Minor) after being admitted. It is now possible to regenerate the admission profile dynamically. Other values beside specialization that may change include visa status, address (may be a relevant admission criteria), status (e.g. different rules may apply for transfer versus new undergraduates).

The process is looking at two technical objects:

Profile describing the requirement

Evaluation of the requirement which leads to an update of the audit result

Notes:

Whenever a profile is deleted, the audit result that refers to it must be deleted as well.

Relevant Activity Documents are created following the re-generation.

1.2. Intelligent Admissions Code

Description In previous releases, the Admissions Code entry field in an admissions record allowed free-form text entry which allowed for wrong data to be entered.

With EHP 5, entries into this field can be restricted to a list of fixed values. You can define Admissions Code values that are valid for various admissions statuses. Based on the configuration settings you make, the screen for maintaining admissions codes provides field help for entering a valid Admissions Code. You can still enter free-form admissions codes, even when restricted codes are defined, based on the settings you have made.

When you change the status of an admissions record from one value to another, for example from Created to Accepted, the Admissions Code automatically changes from one value to another, based on the Customizing settings. This is necessary, since the Admissions Code for the old status may not be valid for the new status.

You can create admissions codes for certain admissions periods, and class them as invalid for future periods. When an admission code is no longer valid, it can be flagged as Inactive. If an admissions code is Inactive, the system displays a warning message if a user attempts to save an admissions record with the expired admissions code.

Notes

The system does not display inactive admissions codes in the search help results

Restriction of Admissions Code values only applies to new data you enter in the system. Any existing entries are allowed and the system does not display an error message, even if the admissions record has been opened in Edit mode.

Navigation path to access the new Intelligent Admissions Code function You make the settings in Customizing for Student Lifecycle Management under Processes in Student Lifecycle Management -> Admission, Registration, and De-registration -> Admission ->

Set Up Admission Codes

Enable Free-Form Entry of Admission Codes

Automatic Change of Admission Codes

Use Case

Page 5: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 5

You wish to assign an Admission Code to applicants who submit their applications early.

Procedure:

a) Define Validated Admission Codes in IMG:

SLCM>Processes in SLCM>Admission, Registration, and De-registration>Admission>Set Up Admission Codes. In this view you define the Admission Codes and assign them to relevant Admission Statuses.

Example:

Admission Code=EARLY APPL/Status=Created

Admission Code=EARLY APPL/Status=Approved

Admission Code=EARLY APPL/Status=Rejected b) Define Automatic Change of Admission Codes in IMG SLCM>Processes in SLCM>Admission, Registration, and De-registration>Admission> Automatic Change of Admission Codes. In this view you specify how the system should convert the Admission Codes based on the Admission Status. Example Old Admit Status=Created/EARLY APPL New Admit Status=Approved/EARLY APPL

c) Define Free Form Entry Admission Codes in IMG

Use this view to specify whether the field “Admissions Code” should be maintained using IMG values or free format entries. A combination of both methods is also possible.

SLCM>Processes in SLCM>Admission, Registration, and De-registration>Admission>Enable Free-Form Entry of Admission Codes

2. Degree Audit Enhancements

2.1. Conversion of Degree Audit BSP to Web Dynpro

Description:

Up to EHP 5 SLCM delivered a BSP Application for performing Degree and Stage Audits. The BSP application was characterized by the following limitations:

1. It represented the only NON-ABAP application delivered by SLCM which required additional technical knowledge from the customer side to maintain it.

2. The BSP technology has constraints for customers who use it in Firefox:

For EHP 5 the following enhancements were developed:

Page 6: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 6

1. Technical conversion of the application: The BSP user interface is replaced by two Web Dynpro for ABAP applications (Profile Maintenance and Online Audits).

2. The overall application flow is re-designed as a Guided Activity Framework for improved usability.

3. Usage of “Exceptions” is deprecated. Instead, a new functionality “Academic Substitution” is available.

2.2. Requirement Profile Maintenance

Description

The process for creating and managing official Requirement Profiles in an interactive manner has been re-designed into Guided Activity Framework. The Guided Activity Framework represents pure configuration. You can hide/remove steps by creating variants which are assigned to specific user groups and which are only available to them when the profile is called within a specific context (e.g. approved profiles for the degree audit of a master program)

Additional features have been added, including:

Enforcement of the „locked‟ profile attribute:

„Locked‟ profiles cannot be edited except for the following tasks: Note Maintenance, Academic Substitution Maintenance, Assessment Assignment.

Ability to manage profile association with assessment processes:

New functionality has been introduced to provide institutions with more flexible control of graduation processes, assessment processes, and process-dependent audits. New graduation processes are now able to „adopt‟ existing open assessment processes, rather than always creating new ones. This decoupling also provides an option to reuse an open assessment process at the time of graduation so that the result of the degree audit can be used for the decision making. In this way the user does not have to execute the degree audit again for the student.

Flexible assignment of requirement profiles

Users are able to freely manage the assignment of requirement profiles (and any associated audit runs) to assessment processes, rather than relying on the assignment to be made only at the time of profile generation. This enhancement provides a robust functionality for the user to assign the requirement profile to the assessment at the later stage of the graduation. It eliminates the overhead of creating an assessment process at the initial stage of the degree audit. Users can create these “free floating” Requirement Profiles and only assign them to a process when the profile has been completed. In addition, individual Subrequirements or complete Requirement Profiles which are compromised of several Subrequirements can be deleted.

Scenario for Requirement Profile Maintenance

Preparation

Register a student to a Program of Study with an assigned Requirement Catalog.

Assign the Catalog to the Student via the Student File.

Open an Assessment Process using the Easy Access Menu Path: SLCM>Teaching and Examination>Academic Records>Edit Assessment Process (Transaction: PIQEVALREGM)

Create a Favorite shortcut to add the Profile Maintenance Web Dynpro Application:

o Favorites>Add Other Objects>Web Dynpro Application

Page 7: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 7

o Web Dynpro Application: PIQ_AUDIT_PROFILE_MAINT_GAF

o Parameter Name: WDCONFIGURATIONID

o Parameter Value: PIQ_AUDIT_PROFILE_CONFIG_GAF

Step 1: Select Profile Context

Select the student (e.g. by entering a student number).

Follow the guided procedure and complete the following parameters (if not already defaulted)

o Program of Study

o Requirement Profile Type

o AuditType

The fields “Reqmt Catalog” and “Catalog Version” will be defaulted.

Use the Next pushbutton to start the Profile Management process

Step 2: Requirement Profile Selection

All Requirement Profiles available for the student will be listed here. You may perform certain actions using the pushbuttons provided.

Use the “Change” or “Display” functions to view the Requirement Profile.

Page 8: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 8

Step 3: Profile Details: Overview

Users can perform several actions using the relevant function buttons.

For example:

o The flags “Show Description ”and “Show Detail” toggles descriptions on and off

o “Add Subrequirement” and “Remove Subrequirement”: Provides the ability to delete or insert Subrequirements.

o “CM: Note”: Can be used to add relevant notations.

Page 9: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 9

Step 3: Profile Details: Substitutions

Users can manage substitutions using the function “Academic Substitutions”.

First double click on a Subrequirement within the profile, then select the pushbutton “Maintain Substitution.”

Select a “Subrequirement Exception Type” in the pop-up window. The available options are as follows:

o Addition

o Exclusion

o Override

The student‟s profile will be updated accordingly upon completion of the Substitution.

Once all Requirement Profile amendments have been performed click on the function “Save Profile” to complete.

Navigate to the next step using the function “Next”

Note: Use the function “Exit Roadmap Step” to return to previous screen.

Page 10: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 10

Step 4: Profile Details: Process Context

Page 11: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 11

Overview:

The benefit of de-coupling the Requirement Profile and the Assessment Process is that it provides the Advisor with the ability to run as many Independent Audits as required. Once the Advisor feels the student has completed sufficient Academic Work, then the Audit Run can be assigned to an Assessment Process (e.g. Graduation).

The Advisor can first create a Process Independent Profile and perform many audit runs or keep changing the audit runs until the student has completed sufficient academic work. At the time of graduation, the Advisor can select the relevant profile and audit run to be related with the Assessment Process. The related result of the audit run will be taken into consideration when the qualification is conferred to the student.

Procedure:

• The student‟s available assessments will be listed in the step: Process Context.

• Highlight the relevant assessment and click on the button “Assign”. A message will be displayed to confirm the assignment.

2.3. Online Audits

2.3.1. General Overview

The process for creating and managing Audit Runs in an interactive manner has been re-designed into a Web Dynpro Application with a guided activity. The application flow has been streamlined from the previous BSP application, and additional features have been added. The new Audits Web application can be used by advisors and students for Degree and Stage audits. It contains the following additional features:

Refresh Audit: This is a combination of the Check and Reevaluate functions. Through this functionality, new qualifying work is assigned to a subrequirement without removing manually assigned substitutions.

Page 12: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 12

Academic Substitution: This offers an improved way of handling exceptions. Advisors can maintain persistent academic work substitutions for specific subrequirements. Substitutions survive across multiple profiles and audit runs.

Academic Work View: Advisors and students can easily see the academic work that could be taken to satisfy a subrequirement.They can view the updated academic work in a new browser, which can be triggered from the Audits Web application.

Re-usability Check: The application now checks for manual assignment of academic work that breaks defined re-use rules. Errors are presented to the user during the manual assignment. Errors are also returned by the „Check Courses‟ function.*

Use case scenario Preparation and initial steps with Guided Activity Framework

Register a student to a Program that has an assigned Requirements Catalog.

Create some Academic Work that will meet at least one Subrequirement.

Create a Favorite shortcut to add the Online Audit Web Dynpro Application: o Favorites>Add Other Objects>Web Dynpro Application o Web Dynpro Application: PIQ_AUDITS_GAF o Parameter Name: WDCONFIGURATIONID o Parameter Value: PIQAC_AUDITS_ADVISOR_CONFIG_GAF

Open the Web Dynpro Application and use the Search Function to select the student Step 1: Selection Criteria

Select the Program of Study and Audit Type (these values may already be defaulted)

Page 13: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 13

Use the pushbutton “Next” to proceed with the Online Audit. Step 2: Current Audit Results Overview Users are able to see all process dependent and independent audit runs and audit profiles on the same page. Independent means that the system checks the status of the booked Academic Work. Dependent means that the audit run is assigned to an Assessment Process and evaluates the overall result based on the Requirement Profile maintained for the student. An audit is called process dependent when the audit run and profile are linked with the assessment process. The academic work status is considered for both independent and dependent runs depending on the Execution Mode of the Audit. In customizing, you can specify which academic status is allowed for different executions modes using the IMG path: SLCM>Processes in SLCM>Audits>Audit Runs>Define Booking Statuses Relevant for Execution Modes Procedure

Select an Assessment Process and choose the function “Create Audit Run” to navigate to the audit details

Step 3 (a & b): Simulation Scenarios Overview:

This step can be incorporated in a separate variant of the Online Audit Application. This variant can then be assigned to specific users.

The relevant customizing settings must be maintained in order to carry out simulations. These are maintained using the IMG path: SLCM>Processes in SLCM>Audits>Audit Runs>Define Parameters for Simulation Audit Run

Page 14: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 14

Page 15: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 15

Step 4: Audit Run (1) Overview:

The Online Audit is a streamlined application where the user does not need to know details such as „process reference‟.

Users can maintain academic substitutions in the audit run application and also in the audit profile application. In the audit run, “Qualifying Academic Work” is provided. This qualifying academic work list takes care of the academic substitution and shows a list of the academic work that can be used for the evaluation of the subrequirement.

Users are able to easily assign/unassign academic work manually. The system checks the booking status of the academic work that is being assigned.

Some key functions are as follows:

• CM: Check ensures that manually assigned academic work does not break the re-use rule defined for the subrequirement.

• CM Re-evaluate performs a complete re-calculation and overwrites the existing results. • CM: Refresh adds new academic work. Previous work is not lost. • CM: Academic Substitutions enables the user to maintain existing substitutions and create new

ones. Note: Users can create as many independent runs as required. At the time the independent run is assigned to a Requirement Profile the audit run becomes dependent.

Page 16: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 16

Step 4: Audit Run (2) Overview:

Users can now easily move academic work between the “Assigned Academic Work” and “Qualifying Academic Work”.

For planned courses, assign the academic work to the student‟s Module Plan and not to the audit results. Procedure Select the relevant subrequirement and click on the relevant pushbutton: “Assign Module”/ “Unassign Module”.

Page 17: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 17

2.3.1.2. Advisor vs. Student Modes in the Online Audit application

Two different Web Dynpro application configurations are provided. The student configuration is limited in the following ways:

Students are not permitted to „Change‟ current audit results.

Students can only view the details of „Released‟ audit runs.

Students cannot maintain Academic Substitutions (view only).

Views can be customized in IMG: SLCM>Processes in SLCM >Audits> Adjustment of User Interfaces

2.3.1.3. Academic Substitutions Description:

Up to EHP5 it was not possible to substitute academic work objects for audit subrequirements for an individual student.

Development for EHP 5:

Academic substitutions can be made for audit purposes. Different academic work objects can be used to fulfill a subrequirement.

Page 18: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 18

The following types of academic substitutions can be defined:

1. Addition: The defined work substitutions can be used in addition to the regular academic work. (Rule relaxation).

2. Exclusion: The specifically defined substitutions cannot be used, even when they are selected by the subrequirement filter during the regular process. (E.g. Module 3 does not count for a specific student)

3. Override: The defined work substitutions completely replace the academic work found by the subrequirement filter (Individual substitution overwrites rules).

Continued Scenario Step 4 (page 4): Audit Run – Substitutions(1)

Overview:

This function will help the user to create options for the student to fulfill the subrequirement with the help of substituted academic work.

When defining Subrequirements you can now specify other academic work that can be used to satisfy that Subrequirement.

For example: you have defined a requirement for Mathematics 101.;Grade to be achieved is B. For that Subrequirement you can now also specify other academic work that will be accepted in place of the Mathematics 101. For example Physics 101; grade to be achieved is C. In this case, Physics will be considered as the Substitution if the advisor has maintained Physics as an substitution for the Mathematics 101 subrequirement for that student.

In summary: Academic substitutions have to be maintained for students individually. If an advisor needs to maintain an academic substitution for a certain subrequirement, this can be done using the Profile Management Application, Audit Run Application or Substitution Stand Alone Application.

Note:

Academic Substitutions are only possible for Index-Dependent Subrequirements and may only be maintained in the Official Execution mode…

Step 4: Audit Run – Substitutions(2)

Procedure:

• This function will assist the user to create options for the student to fulfill the subrequirement with the help of substituted academic work.

• To create a substitution, double-click on the subrequirement and use the pushbutton “CM: Academic Substitution”.

Note:

Audit runs automatically apply academic substitutions to audit results (both assigned work and qualifying work) for Index-Dependent Subrequirements.

For Index-Independent Subrequirements, the customer BADi implementation for the Subrequirement condition must consider any substitutions!

Page 19: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 19

Step 4: Audit Run – Substitutions(3)

Procedure:

Creating an Academic Substitution can be done when

creating or maintaining a Requirement Profile for the student OR

while creating or maintaining an Audit Run.

Page 20: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 20

Qualifying Academic Work can be derived from two sources:

Defined substitutions

The actual course work

Note:

Audit runs automatically apply academic substitutions to audit results (both assigned work and qualifying work) for Index-Dependent Subrequirements.

For Index-Independent Subrequirements, the customer BADi implementation for the Subrequirement condition must consider any substitutions!

While executing the Audit run you can select the qualifying academic work for the Subrequirements. If Academic work is available and Academic substitutions were maintained then the Check Box “Via Substitution” will be visible.

Example: A student has a Major in History. When the student changes the Major it does not affect the substitutions assigned to the Minor. Note: when the student gets an exemption for a subrequirement for a specific Program, it cannot be realized with this scenario because the functionality does not look at the Program.

Notes:

Beside the standalone option for creating academic substitutions, both the Online Profile Management application and Online Audits Application (see rest of this document) permit the creation and maintenance of academic substitutions.

It is not possible to create a substitution while creating a subrequirement.

The value is stored on the level of the student and is not dependant on any Program context.

Page 21: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 21

2.4. Academic Substitutions: Standalone Application

Description: A standalone Web Dynpro Application is provided for viewing and maintaining Academic Substitutions. Additionally, a button for maintaining academic substitutions is also available in Requirement Profile Maintenance and Online Audits (see sections above). This option provided to maintain substitutions is offered as a standalone application. The substitution functions provided in this application are the same as those available in the Requirement Profile and Online Audit Applications.

Procedure

Create a Favorite shortcut to add the Substitution Web Dynpro Application:

• Favorites>Add Other Objects>Web Dynpro Application

• Web Dynpro Application: PIQ_AUDITS_ST_SUBSTITUTION

• Parameter Name: WDCONFIGURATIONID

• Parameter Value: PIQAC_AUDIT_ST_SUBSTITUTION_IND

Page 22: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 22

2.5. Refresh Audit

Description:

Up to EHP 5, the Degree Audit functionality provided the option to „Check‟ and „Re-evaluate‟ Audit results. It was not possible to refresh existing results. In EHP 5 a new function is available to „Refresh‟ existing audit results. The Refresh function is a hybrid of the previously available „Check‟ and „Re-evaluate‟ functions. Through the new functionality, new qualifying work is assigned to a subrequirement without removing manually assigned substitutions. The Refresh function can be executed as a mass processing activity or through a Web Dynpro application. Overview Depending on the result and type of each subrequirement, the “Refresh Audit” function will perform the following actions:

Passed (green) – only the booking status and earned credits will be re-checked. Any resulting loss of academic work will change the status to „In Process‟. No new academic work will be added.

Not Passed (red) – the entire subrequirement will be re-evaluated „from scratch‟, including looking for new academic work to assign. The result will be „Passed‟ or „Not Passed‟ as a result.

In Process (yellow) Index-Dependent – invalid booking statuses are discarded; result is re-calculated based on remaining work; no new work is added; if result is not „Passed‟, the subrequirement remains „In Process.‟

In Process Index-independent – invalid booking statuses are discarded; results ALWAYS stays „In Process.‟

Irrelevant – invalid booking statuses are discarded; results ALWAYS stays „Irrelevant.‟

Page 23: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 23

2.6. Audit Runs and Module Plans

Description: Courses can be added to a student‟s Module Plan directly from the audit results view. Procedure The student must have an initial Module Plan created. Use the pushbutton “Maintain Module Plan” and specify the Modules in the pop-up window. To allow the Audit Simulation to include Module Plan courses, the following customizing settings are

required:

SLCM>Processes in SLCM>Audits>Basic Settings>Define Execution Modes. Activate the flag “Mod.Plan” for the Execution Mode “Simulation”.

SLCM>Processes in SLCM>Audits>Audit Runs>Define Booking Statuses Relevant for Execution Modes. Create a blank booking status for the Execution Mode “Simulation”.

Page 24: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 24

Page 25: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 25

2.7. Assessments and Graduation Description:

Up to EHP 5, the graduation function always created a new assessment process for each student during graduation registration.

In EHP 5, a graduation process for a student can now “adopt” an existing assessment process, rather than creating a new one.

Procedure

To allow adoption of existing assessment processes use the IMG path: SLCM>Processes in SLCM>Academic Records>Assessment Process>Reuse Assessment Process for Graduation

o AUDIT/ASSESSMENT = X

To implement the Badi for choosing an assessment object use the IMG path: : SLCM> Processes in SLCM>Academic Records>Assessment Process>Business Add-ins>BAdI: Assessment Object and Assessment Process Selection

3. Event Planning 3.1. Demand Planning Report Description

Up to EHP 5 it was difficult to estimate the capacity for a course in future sessions based on the demand. It was not possible to evaluate current student bookings and course details.

Developments for EHP 5

1. Anticipated course demand can be determined by looking at students who have indicated that they plan to book

a module, but have not yet done so. A “Course Demand Report” shows bookings, module plan assignments,

Page 26: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 26

and registration cart counts for students. The report results help to determine how many students are likely to book a course for a particular academic year and session.

2. The report provides details of current course bookings including wait-listed and conditional bookings.

3. Anticipated course demand can be determined by looking at students who have indicated that they plan to book a module, but have not yet done so.

Note: The report does not modify any kind of data.

Preparation

The report results are based on the selection criteria. To obtain results, you must set up at least one of following:

Create registration cart bookings using the Self-Service Course Registration.

Create a Module Plan

Create Module bookings

Procedure:

Access the report via the Easy Access Menu Path: SLCM>Event Planning>Reports>Course Demand Report (Transaction: PIQCOURSEDETAIL)

Selection Method : SMEV or SMQ1

Selection Variant: Use the Evaluation Path: MODBENCH

IMG path: SLCM>Processes in SLCM>General Settings>Selection Methods>Assign Selection Methods to Selection Method Group

Check flag “Show Offerings” to see capacities broken down

to Events/Event Packages

This section is only visible when flag “Display Booked

Modules is checked

Page 27: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 27

Overview: Report Parameters:

“Display Module Plan”: displays Modules which are contained with a Module Plan

“Display Registration Cart” displays Modules within the student‟s registration cart

“Display Booked Modules”: can be used to display Normal/Conditional/Waitlist bookings.

The report can only be executed in dialog mode. The program to be used is RHIQSTUDENT_COURSE_DETAILS.

3.2. Time Independent Events

Description Start/End Dates:

Up to EHP 5 it was not possible to delimit Time Independent Events (EL), e.g., e-learning courses, for a specific Year and Session as these Events were created as long living objects.

Developments for EHP 5:

In transaction „PIQACADOFFER00‟, while creating or editing Time Independent Events (EL), start and end dates can now be assigned. By default, the Event takes the start and end date of the selected Academic Year and Session. Users can set the start date a week after the start of the class date, or the end date can be set

a month before the end of the class period by selecting the appropriate unit.

Description – Capacity:

Time Independent Events (EL) are typically set up for e-learning courses (“Eventless Events”). Up to EHP 5, capacities maintained for a Time Independent Event were not evaluated during Module Booking scenarios.

Developments for EHP 5:

When creating or editing an EL Object (Time Independent Event) the capacity for this Event can be maintained. You can enter minimum, optimum, and maximum capacities. However, it is not necessary to maintain

these capacities. By default, the capacity of the Event Type is displayed.

When capacities are maintained for an EL Object, the capacity is considered both for „Available Places‟ calculations as well as during Module Booking (including Web Course Registration).

Preparation

An Event Type must exist and the “Category” Infotype must be created with the Delivery Mode “ELEA” (E Distance Learning).

The category is maintained using the IMG path: SLCM>Master Data in SLCM>Academic Structure> Business Event Types>Create Delivery Modes

Page 28: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 28

Procedure:

Easy Access Menu: SLCM>Event Planning>Edit Event Offerings (PIQACADOFFER00)

Select an Access Object and specify an Academic Year and Session

Select an Event Type and click on the Icon: [Create}.

Select the option “Create Time Independent Event”.

Specify the Event Delivery Mode in the “Category” infotype

The Event creation is based on the Delivery Mode specified at the Event Type

Page 29: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 29

1. Procedure Maintain Start/End Dates

The following options are provided:

(a) Edit Validity (System Default)

The Event Start and End Dates are defaulted from the Module Session of Offering. These dates may be overwritten by selecting the radio button “Edit Validity”.

(b) Edit Relative Dates

This option is used to specify Start/End Dates relative to a Time Unit (e.g. one week before start of class period).

Select the ratio button “Edit Relative Dates”. The fields below the radio button will be changed from display to input.

Specify Units for the Relative Start and End of the Event. The fields “Start/End Date” will be adjusted according to your selections.

Note: When the dates are changed using the radio button „Edit Relative Dates‟, the start and end dates are always changed based on the Session start and end date and are not based on the dates that are displayed in the start date and end date fields.

Maintain

capacity

Page 30: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 30

2. Procedure: Maintain Capacity

Specify the required capacities in the fields: Minimum/Optimum/Maximum.

Note: The field “Places Available” in the ALV is updated based on the capacity of the EL.

3.3 Multiple Instructors for Events w/o Schedule Description:

Up to EHP 5, it was not possible to assign multiple instructors to Events without a schedule. An Event w/o schedule (E) was limited to having only one instructor.

Developments for EHP 5:

In transaction „PIQACADOFFER00‟, while creating or editing an Event without schedule, multiple instructors can now be assigned with percentages. If multiple instructors are assigned, a visual indicator is displayed.

Note: An Event w/o schedule is simply a standard Event (E) that has not yet been scheduled. It is not to be confused with an EL object (timeless event)!

Procedure:

Easy Access Menu: SLCM>Event Planning>Edit Event Offerings (PIQACADOFFER00)

Select an Access Object and specify an Academic Year and Session

Select an Event Type and click on the Icon: Create

Select the option “Create Business Event w/o Schedule.”

Click on the Icon “No. Multiple Assignment of Instructors”

Page 31: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 31

A pop-up window will be presented to select the instructor(s)

Select the relevant Object Type (e.g. Person) and choose instructors using the search function

Specify a percentage is applicable.

Click on the [Continue] Icon and [Save] to complete.

Maintain multiple instructors

Page 32: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 32

3.4 New Selection Method for Modules

Description:

Selection Methods are used to select a set of objects of the same type for performing an activity or completing a process within SLCM. Up to EHP 5, it was not possible to select Modules based on their position in the Academic Structure hierarchy.

Developments for EHP 5:

Selection Method „SMEV‟ is provided. Its evaluation path selects the relevant Modules along the Academic Structure. The Selection Method can be used in

Reports to copy roll forward the academic offerings

Reports to view Module booking details

Preparation

You have created an evaluation path to select your Modules from multiple levels of the academic structure. The evaluation path can be created using the IMG view: SLCM>Master Data in SLCM>Academic Structure> Organizational Management>Basic Settings>Maintain Evaluation Paths or Transaction SM30 / View:T77AW

You may also use existing Evaluation Path such as: MODBENCH or PROGBEN1

Transaction PIQSELT1 can be used to test the Selection Method.

Page 33: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 33

Notes:

The Selection Method can be executed with different Evaluation Paths and root objects. Modules are returned based on the construction of the Evaluation Path.

3.5. New Relationship between Module Groups and Event Packages

Description

Learning Communities are groups of course sections that have been defined by the Universities to enable students to search and book courses easily. Up to EHP 5 it was not possible to search and book Learning Community sections.

Developments for EHP 5:

A new Relationship 507 is created between Event Packages (SE) and Module Groups (CG). It enables customers to maintain their own Module Group Category to designate Learning Communities.

Customers are now able to relate Event Packages of Modules (Sections) to a Module Group. The Module Group will be a Learning Community. Also, they can designate only certain sections of a course as being „Honors‟ or „Distance Learning‟ (via the „Special Course Type‟ Module Group Category).

The relationship can be maintained through

Program Catalogue (Transaction PIQ_ACTSRUC)

Module Catalogue (Transaction PIQ_ACCATLG).

The Web course registration UI has been enhanced to return Learning Community sections. Event packages related in this way can be easily searched in the UI using the learning community or the module group name.

Customizing:

Overview

When you search for Modules by the Learning Community Category, Event Packages that are related to the Module Group, through Relationship 507, are returned in the result.

Also, the search returns Modules that are directly related to the Module Group.

Page 34: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 34

Example: The School of Architecture (Organizational Unit = Object type O) has set up English Honors Classes. They belong to the Module English 101 which has overall 50 sections assigned to it but only two of them represent actually Honors Classes. Students must be able to quickly identify them using the search function. Therefore they can use these Learning Communities as identification criteria.

Customization

IMG path: SLCM>Master Data in SLCM>Academic Structure>Module Groups>Set Up Module Group Categories

Enter a “Group Type” and “Description” to create a Learning Community.

Note: Leave the flag “Specialization” blank.

Master Data Maintenance:

Transaction PP01 (Maintain Object)

Select a Module Group and click the Infotype “Module Group Data”

Select a Category representing a Learning Community from the drop-down list and [Save].

Procedure:

Transaction PIQ_ACSTRUC (Program Catalog)

Select a Module Group that has been assigned a Learning Community Category and click on the Icon “Create Relationship”.

In the pop-up window, select the relationship “A 507 consists of Event Package.”

A second pop-up window is presented with a preview of the relationships to be created. Use the pushbutton [Period] to view/change the relationship dates.

Use the [Save] button to create the relationship.

Page 35: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 35

4. Student File

Page 36: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 36

4.1. New Search via Specialization

Description:

In Student Lifecycle Management the Object Manager is used – either from within the Student File or Student Maintenance transaction – to select students based on certain conditions. Until now it has only been possible to search for students based on names or program of study. Developments for EHP 5:

The Object Manager has been enhanced to allow the selection of students who are registered for particular Specializations.

Procedure:

Easy Access Menu: SLCM>Student File (Transaction: PIQST00)

In the Object Manager, expand the folder “Student” and click on the search option Name

Fill in the selection criteria In the pop-up window, for example:

o Assigned: “DI Directly and Indirectly”

o To: “CG Module Group”

o Object: Enter a search criteria (e.g. wild card) and click on [Find]

o The students assigned to the Module Group will be displayed in the Object Manager.

Page 37: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 37

4.2 Navigation to Individual Work Details Description:

Individual Work details were previously only accessible from the Module Booking record.

Developments for EHP 5:

Individual Work details can be directly accessed from the Academic Work Overview.

Procedure:

Easy Access Menu: SLCM>Student File (Transaction: PIQST00)

Select the Icon [Academic Work Overview].

Click on the Icon [Individual Work] to display the details (see following slide).

Individual Work details may be edited using the Extended Maintenance Dialogue (TA PIQST10)

Page 38: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 38

4.3. Navigation to the Appraisal Note

Description

The Appraisal Note for a student‟s academic work can now be viewed and maintained directly from the Academic Work Overview transaction.

Procedure:

Easy Access Menu: SLCM>Student File (Transaction: PIQST00)

Select the Icon [Academic Work Overview].

Double-click on a Module to navigate to the detail screen.

Click on the Icon “Create Note” to view or amend an Appraisal Note.

Note:

Switch to the Extended Maintenance Dialogue (PIQST10) to make changes to an Appraisal Note,

Page 39: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 39

5. Self-Service Enhancements

5.1 Additional Services included in Student and Academic Advisor Roles

Description:

New services have been added to the Student and Academic Advisor roles:

1. Student Role

Online Audits - Audit run application in Student Mode

View academic work information

2. Academic Advisor Role

Academic substitution management

Online requirement profile management

Online audits - Advisor Mode of audit run application

Preparation: Student Role

Create a Favorite shortcut to add the Profile Maintenance Web Dynpro Application:

Favorites>Add Other Objects>Web Dynpro Application

Web Dynpro Application: PIQ_AUDITS_GAF

Page 40: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 40

Parameter Name: WDCONFIGURATIONID

Parameter Value: PIQAC_AUDITS_STUDENT_CONFIG_GAF

Preparation: Advisor Role

Create a Favorite shortcut to add the Profile Maintenance Web Dynpro Application:

Favorites>Add Other Objects>Web Dynpro Application

Web Dynpro Application: PIQ_AUDITS_GAF

Parameter Name: WDCONFIGURATIONID

Parameter Value: PIQAC_AUDITS_ADVISOR_CONFIG_GAF

5.2. View Academic Work via Student Self Service Description

This application can be used by students to view their complete academic work. The information shown includes academic details such as: course abbreviation, credit information, academic specializations and performance index data, etc.

Preparation

Web Dynpro Application PIQ_ST_ACAD_WORK_OV

Note: This Web Dynpro application can also be launched from the Online Audits Application.

Page 41: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 41

5.3. Graduation Self Service

Description:

Up to EHP 5 students could not re-register for Graduation through the Self-Service Web Dynpro application PIQ_GRADUATION_REQUEST.

Development for EHP 5:

The application has been enhanced to allow students to re-register for graduation if their earlier request was rejected or withdrawn.

Preparation: Register for Graduation

Register a student for graduation using the Easy Access Menu: SLCM>Teaching and Examination>Graduation>Edit Graduation for Student (Transaction: PIQGRADST)

Use the Icon “Execute Action” to deny the graduation

Preparation: Graduation Application

Create a Favorite shortcut to add the Profile Maintenance Web Dynpro Application:

o Favorites>Add Other Objects>Web Dynpro Application

o Web Dynpro Application: PIQ_GRADUATION_REQUEST

o Parameter Name: STUDENT_OBJID

o Parameter Value: xxxxxxx (Student Object)

Procedure

Select the relevant Program and click on the button [Register for Graduation]

Note: A number of backend processes can be included in the graduation process (e.g. automatically charging a student a fee when they register for graduation).

Page 42: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 42

5.4. Additional Filter Provided for Course Registration Description and Development for EHP 5:

BADI HRPIQ00MBSS_SEARCH_CRIT_FILTER can be used to restrict the values shown in the dropdowns in advanced search mode for Academic Level, Grading Scale, Special Course Type, etc. which are available in the “Advanced Search” option of the Course Registration Application.

Parameters Student Objectid & Program Context (Student and Booking Contexts) have been added to the BADI interface so that the search options that are displayed to the student can be filtered in a student-specific manner.

Preparation

The BADI can be found using the IMG path: SLCM>Role-Based Web UI>Student Role>Course Registration UI>Business Add-Ins (BAdIs)>BAdI: Filter Values of Search Criteria

Examples of available BADI definitions are:

BAdI: Set Booking Level for a Module (HRPIQ00MBSS_BOOKING_LEVEL)

BAdI: Filter Values of Search Criteria (HRPIQ00MBSS_SEARCH_CRIT_FILTER)

Note:

The course registration search functionality provides higher degree of user friendliness than the backend search functionality of the Program Content.

Page 43: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 43

5.5. Module Group Search Provided in Course Registration Description and Development for EHP 5:

The Advanced Search function in Web Course Registration now offers the student the ability to choose a Module Group Category. Once selected, the system presents a list of possible Module Groups to the student.

Preparation

Implement the BADI HRPIQ00MBSS_SEARCH_CRIT_FILTER in order to use this search function.

Note

Use this BADI to enable students to search for Module Groups designated as “Learning Communities”. This Search Criteria is controlled by the parameter “Special Course Type”.

Page 44: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 44

5.6. Restrict Search in Course Registration Description

A new BADI (HRPIQ00MBSS_RESTRICT_SEARCH) has been introduced in the Course Registration application to restrict the search terms that students can enter to search for a course. This can be used to prevent the triggering of long-running searches, e.g. a search with no search term entered but just dates within a large interval in the “From/To” values will not return useful data but will load the application server (if many such requests come in together).

Preparation

The BADI can be found using the IMG path: SLCM>Role-Based Web UI->Student Role->Course Registration UI->Business Add-Ins (BAdIs)->BAdI: Restrict Search Activity

Notes

Two search options are available: to decide which data the students can see and whether they can continue the search.

Import parameter IS_ROOT_OBJECT contains any specific Org. Unit, Program, Module Group, etc. chosen by the student in the Advanced Search.

Set CV_STOP_SEARCH to X to cancel the search

Fill CT_RETURN with helpful messages to the student to narrow the search criteria.

Page 45: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 45

6. Miscellaneous Enhancements

6.1. Enhanced Pre-requisite Extended Booking Check Description:

The Extended Booking Check functionality is used to maintain Pre-requisites and Co-requisites for Modules. The default BADI Implementation "HRPIQ00_CON_PREREQ“ (SAP8) Is provided for Index-Independent Subrequirements to check prerequisite courses.

Developments for EHP 5:

Two additional optional parameters are offered for the delivered BAdi implementation HRPIQ00_CON_PREREQ (SAP8):

o Grade Value

o Grade Scale

If these parameters populated, the completed academic work that normally qualifies for the pre-requisite sub-requirement is filtered such that, if the grade value is less than the parameter value, it will be treated as „unsuccessfully completed‟.

The BAdi is available for index-independent subrequirements which can be used to check the prerequisite courses. The result of the extended booking check states whether the module can be booked Normally, Conditionally, or Cannot Be Booked at all.

If the grade for the completed academic work is recorded using a different grade scale, the grade will be converted to the parameter Grade Scale for comparison purposes.

Page 46: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 46

A single pair of Grade Value and Grade Scale will be allowed as parameters.

The entire evaluation of the extended booking condition is carried out at a new callup point: CP0090.

The above parameters are optional. If they are filled in the system, the academic work that is normally considered as qualifying for the prerequisite subrequirement is filtered. This leads to completed academic work where the grade value is less than the entered value being treated as unsuccessfully completed. If the grade for the completed work is recorded using a different grade scale, the grade is converted to the parameter Grade Scale for comparison purposes.

Preparation

Easy Access Menu: SLCM>Academic Structure>Study Planning>Module Catalog (TA: PIQ_ACCATLG)

Procedure

Select a Module and click on the pushbutton [Edit Extended Booking Check].

Create a Requirement for the Pre-requisite rule. (Rule Container)

Create an Index Independent Subrequirement

Select the Condition “SAP 8 Pre-requisite Condition”. The parameters “GRADE_SCALE” and “GRADE_VALUE” will be inserted as pre-requisite conditions.

Use the drop-down list to specify the Scale and Minimum Grade.

Subrequirement using Condition 8.

Page 47: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 47

6.2. Co-requisite Check while Cancelling Module Booking

Developments for EHP 5:

The module booking process has been enhanced to automatically re-enforce Co-requisite requirements during module cancellation. Previously, Co-requisites rules were enforced only during the initial booking of modules.

With this enhancement, the Co-requisite checks will also be performed at the time of the Module cancellation so that the user does not go ahead and cancel the co-requisite. Module even though the main Modules requires it . This will prevent booking inconsistencies.

Preparation

To specify conditions to be checked during module cancellation use the IMG path: SLCM>Processes in SLCM>Module Booking>Extended Booking Checks>Corequisite Conditions Maintained for Extended Booking Check

Note: A message log is provided to facilitate error handling during the cancellation process.

6.3. Enable “Waitlist Disabled” Flag at Module Level Description

Students on waiting lists can book modules using the waiting-list booking functionality. The priority of the module booking indicates whether the booking is normal or waiting-list. The waitlist process has been enhanced to perform the following additional functions

Make use of the ‟Waitlist Disabled‟ flag at the Module level:

If the waitlist disabled flag is checked, then irrespective of the waitlist level and the waitlist percentage, the system should not allow booking this Module under waitlist priority. The system should display the error message:“Waitlist booking is not allowed for Module”.

Customers can define their own rules for automatically assigning the waitlist priority

In some scenarios, customers would like to set the priority of the waitlist booking based on different credentials of the student. As these dynamic conditions cannot be captured in the application, a BADI

Page 48: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 48

exit is provided to customers which they can implement. Using this, customers can set the priority of the waitlist booking as desired.

Preparation

The BADI is available in the IMG path: SLCM>Processes in SLCM>Module Booking>Waiting Lists>BAdI: Change Waitlist Booking Priority

Notes:

You can check the student‟s attribute before you decide on their position on the waitlist. During the course registration students can actually see their position on the waiting list.

You can assign top priority students the highest number during the waitlist move up.

Preparation (ctd.):

Navigate to the Waitlist Report from the Easy Access Menu: SLCM>Student Administration>Mass Processing Functions>Waitlist Administration (Transaction: PIQWAITLMOVE)

Note:

The re-calculations only take effect if you also perform some real follow-up actions: such as performing a move-up. If you only display the waiting list, you will see the re-calculated priorities on the screen, but they are not saved!

Page 49: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 49

6.4. Allow Un-offered Modules in Module Plan Description

The Module Plan for a student can be created using the Cohort Builder tool or through the Advisor UI. Building a Module plan is like building a Cohort with “Module Plan” as Cohort context. Up to EHP 5, while adding Context Objects (Modules) to a Cohort, the system checks whether a Module offering exists for the selected year and session. If the Module is not offered, the system returns an error message and does not allow the Module to be added to the Cohort.

Development for EHP 5

Modules can be added to Module Plans regardless of whether a sessions of offering exists based upon rules defined in a new BAdI. An advisor can build a module plan for a student, as a suggestion of modules a student can take for the year and session ahead. Building a module plan is like building a cohort with Module Plan as the cohort context.

Procedure:

A customizing entry must be maintained to allow the unoffered modules to be added in the Module Plan. Use the IMG path: SLCM>Processes in SLCM>Cohorts>Allow unoffered modules in Module Plan.

To allow addition of unoffered modules to a Cohort with a Module Plan context, enter the following value:

„X‟: Modules can be added even they are not offered for the selected year and session.

Additionally, a BAdI is called by the cohort builder when the user adds a context object to the Cohort . Users can implement this BAdI to include additional check conditions on the Module which is to be added.

The BAdI takes effect only:

if the Cohort in question has Cohort Context „0002‟ (Module plan)

if the Addition of unoffered modules in the Module plan is allowed.

IMG Path: Student Lifecycle Management >Processes in Student Lifecycle Management >Cohorts >Business Add-Ins (BAdIs) > BAdI: Allow Unoffered Cohort Context Object in a Module Plan (HRPIQ00COHORT_MODULE_PLAN)

Users can implement their own BAdi which can contain extended check conditions. To do this, users need to code the EVALUATE method in their implementation.

Procedure (ctd.)

A customizing entry must be maintained to allow the unoffered modules to be added in the Module Plan. Use the IMG path: SLCM>Processes in SLCM>Cohorts>Allow unoffered modules in Module Plan.

To allow addition of unoffered Modules to a Cohort with a Module Plan context, enter an “X” in the field “Setting Value”.

Additionally, a BAdI is called by the Cohort Builder when the user adds a Context Object to the Cohort . Users can implement this BAdI to include additional check conditions on the Module which is to be added. Use the IMG path: SLCM>Processes in SLCM>Cohorts>Business Add-Ins (BAdIs)>BAdI: Allow Unoffered Cohort Context Object in a Module Plan (HRPIQ00COHORT_MODULE_PLAN)

The BAdI takes effect only:

if the Cohort in question has the Cohort Context „0002‟ (Module Plan)

if the Addition of unoffered modules in the Module plan is allowed.

Page 50: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 50

Note:

Users can implement their own BAdi which can contain extended check conditions. To do this, users need to code the EVALUATE method in their implementation.

Customizing

Assign unoffered modules to module plan

6.5. Maintain Fee Calculation Data via Mass Assignment Description:

A Mass-processing report for assignment of Student Fee Category now allows assignment of all Fee Calculation Data fields. The report can be located via the Easy Access Menu path: SLCM>Student Administration >Mass Processing Functions>Assign Student Group or Fee Category (Transaction: PIQMPSTATTR ).

Page 51: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 51

Page 52: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 52

Related Content

For more information, visit the Business Process Expert homepage

Page 53: Delta Overview Student Lifecycle Management EHP 5

Delta Overview Student Lifecycle Management EHP 5 (BS7i2010e)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 53

Copyright

© 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.

Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.