The standard transaction for editing requirement catalogs is transaction PIQRLCATM (
). When you generate a requirement profile for a student via a requirement catalog, the system derives the concrete requirements (rule containers) for this student from the requirement selections which are defined for the requirement elements of a requirement pattern.
The requirement profile templates are quite useful if the requirements for students are clearly defined and do not contain numerous options. An example of this is the admission audit.
You can create requirement profile templates based on academic specializations (these are also called subprofiles). When the system adopts a student’s personal requirement profiles, it only takes the subprofiles of the specializations the student has chosen into account.
You can also create and edit templates for special students. In this case, you must enter a student attribute when you create the template. These student attributes are filter-dependent implementations of the business
You can make the settings for requirement profile templates in Customizing for
If you want the system to use templates and not the standard derivation when it generates personal requirement profiles, you must specify which template is to be used in which program in the infotype (1778).
You can use the following functions to manage the usage of academic work in the Audit process:
These functions are available if you have activated the business function SAP Student Lifecycle Management: Implementation Accelerator (ISHERCM_604_EXIAP_M).
You can use this function to control how academic work is reused by subrequirements.
Most higher level institutions restrict the reuse of academic work that is already used by another subrequirement. Using this function, you can restrict the reusability of academic work effectively.
This function is used during the Audit Run. When the system evaluates a requirement profile, it observes the type of subrequirement being evaluated and assigns academic work accordingly. The order in which the subrequirements are evaluated is dependent on the priority of the subrequirement. For more information, see Prioritization.
© 2009 SAP AG
| bpx.sap.com 161